Re: How to get a log of fsck on boot partition when using systemd-sysv

2014-05-11 Thread Sven Joachim
On 2014-05-10 23:49 +0200, Jape Person wrote: In various logs on these systems I see an indication that touch /forcefsck doesn't work with systemd running the show, and that adding fsck.mode=force to the linux boot line in Grub is now the proper way to force fsck to run at boot time. It

Re: How to get a log of fsck on boot partition when using systemd-sysv

2014-05-11 Thread Michael Biebl
Am 11.05.2014 09:35, schrieb Sven Joachim: Something like journalctl -b | grep systemd-fsck. I haven't figured out how to get journalctl -u to work here. That, or something like systemctl status systemd-fsck-root.service or systemctl status systemd-fsck@your device.service works for me as

Re: How to get a log of fsck on boot partition when using systemd-sysv

2014-05-11 Thread Jape Person
On 05/11/2014 03:35 AM, Sven Joachim wrote: On 2014-05-10 23:49 +0200, Jape Person wrote: In various logs on these systems I see an indication that touch /forcefsck doesn't work with systemd running the show, and that adding fsck.mode=force to the linux boot line in Grub is now the proper

Re: How to get a log of fsck on boot partition when using systemd-sysv

2014-05-11 Thread Jape Person
On 05/11/2014 08:29 AM, Michael Biebl wrote: Am 11.05.2014 09:35, schrieb Sven Joachim: Something like journalctl -b | grep systemd-fsck. I haven't figured out how to get journalctl -u to work here. That, or something like systemctl status systemd-fsck-root.service or systemctl status

[SOLVED] Re: How to get a log of fsck on boot partition when using systemd-sysv

2014-05-11 Thread Jape Person
On 05/11/2014 12:17 PM, Jape Person wrote: On 05/11/2014 03:35 AM, Sven Joachim wrote: On 2014-05-10 23:49 +0200, Jape Person wrote: In various logs on these systems I see an indication that touch /forcefsck doesn't work with systemd running the show, and that adding fsck.mode=force to the

How to get a log of fsck on boot partition when using systemd-sysv

2014-05-10 Thread Jape Person
Hi, I just used # apt-get install systemd-sysv on several Debian testing systems (fully up-to-date). It has been my habit to use # touch /forcefsck to force a file system check at reboot once per week on each system and to keep track of the results by copying the contents of

Re: How to get a log of fsck on boot partition when using systemd-sysv

2014-05-10 Thread Brandon Vincent
Jape, It sounds like the fsck is being conducted while the initramfs is loaded and thus no log is being saved. Ideally, there would be a way to have the console dumped to dmesg. Brandon Vincent On Sat, May 10, 2014 at 2:49 PM, Jape Person jap...@comcast.net wrote: Hi, I just used #

Re: How to get a log of fsck on boot partition when using systemd-sysv

2014-05-10 Thread Jape Person
On 05/10/2014 06:32 PM, Brandon Vincent wrote: On Sat, May 10, 2014 at 2:49 PM, Jape Person jap...@comcast.net wrote: Hi, I just used # apt-get install systemd-sysv on several Debian testing systems (fully up-to-date). It has been my habit to use # touch /forcefsck to force a file system