Ciao,
thanks for your reply.
I see there is something more complex than I'm able to figure out, but I
must report that upon reboot some trivial problems with the filesystem
persist so it doesn't seem like anything has really done.
Is expecting a clean "fsck -n -f XXX" run wrong?
thx, ciao
On 12/11/23 19:39, Michael Biebl wrote:
> Am 11.12.23 um 18:30 schrieb Alessandro -oggei- Ogier:
>> Package: systemd
>> Version: 255-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> while doing some checks for the recent kernel ext4 problem, I've
>> noticed fsck does not seem to be able to run at boot, the command
>>
>> journalctl -u systemd-fsck-root
>>
>> reports:
>>
>> -- Boot 2bb7b10680a74ab4854998cb33154999 --
>> dic 11 18:17:16 orso 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).
>>
>
> this flag file means, that the / fs has already been checked by the
initrd.
>
>
