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 > > # 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 > /var/log/fsck/checkroot into a sort of diary I keep on system maintenance. > > 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. > > However, though I see that fsck is running when I boot the system after > altering the boot process, there is still no output from the operation > written to the checkroot file. I presume this is part of the rhubarb I've > noticed on various lists concerning the logging of the boot process when > using systemd. > > This is hardly a huge problem for me, but I'd like to keep practicing this > slightly OCD behavior if I can on a couple of the more critical machines. > > Would anyone have thoughts on how I can get a record of the file system > check on the boot drive when using systemd? > > If there's something about this in the man pages, I'm certainly not > finding it. > > Thanks for any pointers you can provide. > > > -- > 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/536e9ed8.5050...@comcast.net > >
