Am 11.12.23 um 21:52 schrieb Alessandro Ogier:
On 12/11/23 20:20, Michael Biebl wrote:
Is expecting a clean "fsck -n -f XXX" run wrong?
Have you tried "fsck.mode=force fsck.repair=yes" as well?
while not suspecting a defect in the manual pages, I tried all
combinations of yes/auto
On 12/11/23 20:20, Michael Biebl wrote:
Is expecting a clean "fsck -n -f XXX" run wrong?
Have you tried "fsck.mode=force fsck.repair=yes" as well?
while not suspecting a defect in the manual pages, I tried all
combinations of yes/auto yes/preen. I have also tried rebooting now with
[please always CC the bug report on replies]
Am 11.12.23 um 19:47 schrieb Alessandro Ogier:
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
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?
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
5 matches
Mail list logo
