Thank you. That log file seems to show that fsck was run:
And /dev/mmcblk0p2 is my root filesystem.
But /var/log/syslog seems to say that fsck was NOT run.
(The difference in the reported times is due to the local time zone.)
The reason I want to run fsck is because this machine keeps finding basic system utility programs that are somehow corrupt, they report "Segmentation fault". Copying a known good file from a different Pi cures the problem. Rebooting also cures the problem -- for that program but some other one shows up later.
Code:
# cat /run/initramfs/*gLog of fsck -C -f -y -V -t ext4 /dev/mmcblk0p2 Wed Dec 18 18:27:32 2024fsck from util-linux 2.38.1[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p2] fsck.ext4 -f -y -C0 /dev/mmcblk0p2 e2fsck 1.47.0 (5-Feb-2023)Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationrootfs: 277858/7467264 files (0.3% non-contiguous), 10246136/30317056 blocksCode:
# dfFilesystem 1K-blocks Used Available Use% Mounted onudev 2027024 0 2027024 0% /devtmpfs 414208 5888 408320 2% /run/dev/mmcblk0p2 119309024 39026724 74202508 35% /tmpfs 2071040 48 2070992 1% /dev/shmtmpfs 5120 48 5072 1% /run/lock/dev/mmcblk0p1 522230 77344 444886 15% /boot/firmwaretmpfs 414208 176 414032 1% /run/user/1000Code:
2024-12-18T13:27:40.127494-05:00 nyrpi kernel: [ 0.000000] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave smsc95xx.macaddr=2C:CF:67:1B:0B:00 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=6ff2ddfe-02 rootfstype=ext4 fsck.repair=yes fsck.mode=force rootwait splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=US biosdevname=0 net.ifnames=0 selinux=02024-12-18T13:27:40.127612-05:00 nyrpi systemd-fsck[575]: fsck.fat 4.2 (2021-01-31)2024-12-18T13:27:40.127616-05:00 nyrpi systemd-fsck[575]: /dev/mmcblk0p1: 388 files, 38672/261115 clusters2024-12-18T13:27:40.127657-05:00 nyrpi systemd[1]: Starting systemd-fsck@dev-disk-by\x2dpartuuid-6ff2ddfe\x2d01.service - File System Check on /dev/disk/by-partuuid/6ff2ddfe-01...2024-12-18T13:27:40.127660-05:00 nyrpi systemd[1]: Started systemd-fsckd.service - File System Check Daemon to report status.2024-12-18T13:27:40.127960-05:00 nyrpi systemd[1]: Finished systemd-fsck@dev-disk-by\x2dpartuuid-6ff2ddfe\x2d01.service - File System Check on /dev/disk/by-partuuid/6ff2ddfe-01.2024-12-18T13:27:40.128013-05:00 nyrpi systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root).2024-12-18T13:27:40.128055-05:00 nyrpi systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root).2024-12-18T13:28:09.163387-05:00 nyrpi systemd[1]: systemd-fsckd.service: Deactivated successfully.The reason I want to run fsck is because this machine keeps finding basic system utility programs that are somehow corrupt, they report "Segmentation fault". Copying a known good file from a different Pi cures the problem. Rebooting also cures the problem -- for that program but some other one shows up later.
Statistics: Posted by compata — Thu Dec 19, 2024 1:30 am