Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 4061

Troubleshooting • Re: bookworm forced fsck on boot

$
0
0
I understand about "!". That's why I tried deleting the file before rebooting. That had no effect, I presume because the file is merely a status marker for the resident initramfs.
The file /run/initramfs/fsck-root exists only in RAM, and can only have been created if the filesystem has been checked in the current boot.

If you are not able to observe the screen during boot then try sudo less /run/initramfs/fsck.log. (The timestamps in that file will be wrong, unless you use a Pi5, which has RTC in the PMIC. But again it exists only in RAM, so it can only prove that fsck did run in the current boot.)
So that raises the question, how do I force the initramfs NOT to be resident? The machine I'm trying to fix is remote and I only have SSH access.
It is much better to run fsck from the initramfs, as you are, rather than from systemd after the rootfs is mounted. If the machine has some issue that you were hoping fsck would fix, and fsck is not fixing it, then you should start a thread about the actual issue.

Statistics: Posted by jojopi — Wed Dec 18, 2024 11:50 pm



Viewing all articles
Browse latest Browse all 4061

Trending Articles