Quoting Jape Person (jap...@comcast.net):

> Not sure this will be at all helpful considering that the consensus
> seems to be that fsck is probably not what you need right now. I
> just wanted to be sure that you got some sort of answer regarding
> the running of systemd-fsck.
> 
> You should be able to see the result of an fsck run with
> $ cat /run/initramfs/fsck.log
> I use
> # tune2fs -c -1 /dev/sda1
> to set the system to prevent a full fsck from running at boot time
> and
> # tune2fs -c 1 /dev/sda1
> to cause the system to force a full fsck during the next boot.

Like you in https://lists.debian.org/debian-user/2015/04/msg01423.html
I revisit this problem once in a while.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783410
seems to have fallen on deaf ears, so in the meantime, here's a
solution:

Reboot,
At grub's prompt type e to edit,
Add   forcefsck   to the end of the   linux ...    line,
Ctrl-X or F10 to boot.

This will fsck (just this once) all the partitions that
shutdown -t1 -a -r -F now
would do in the traditional manner in wheezy and previously.
All that's missing is any progress indication because that bit
of code in  /etc/init.d/checkroot.sh didn't get copied.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150722212122.GA14981@alum

Reply via email to