[systemd-devel] systemd-fsck question
Nikolai Zhubr
n-a-zhubr at yandex.ru
Tue Jan 6 07:23:01 PST 2015
Hi again,
Now a have another question.
In systemd-fsck at .service I see "StandardOutput=journal+console", and
"StandardOutput" not set, AFAICS defaulting to "inherit" according to
system config file, which looks good, as all diagnostic and error
messages coming from systemd-fsck (and they are quite important) would
therefore (supposedly) go to both journal and physical console.
Now, through fsck.c in systemd sources, I can see that any unsuccessfull
exit (errorcode) is reasonably accompanied by some descriptive message,
such as "Failed to stat %s" etc. Looks good.
However, here is my console log:
----------- console fragment start ----------
[ OK ] Found device
/dev/disk/by-uuid/7290addb-123e-44bf-96d5-eaedc37c1852.
Starting File System Check on
/dev/disk/by-uuid/7290...eaedc37c1852...
[ OK ] Found device
/dev/disk/by-uuid/4c25dd37-c555-4fbf-8349-f1470d0e924c.
[ OK ] Started dracut initqueue hook.
Starting dracut pre-mount hook...
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
[ OK ] Started dracut pre-mount hook.
[FAILED] Failed to start File System Check on
/dev/disk/by-uu...5-eaedc37c1852.
See "systemctl status 'systemd-fsck at dev-disk-by\x2duuid-729...ce'" for
details.
[DEPEND] Dependency failed for /sysroot.
----------- console fragment end -----------
There are absolutely no messages relevant to systemd-fsck between
"Starting File System Check ..." and "Failed to start File System Check
..." ! How can this be possible, and how do I find the reason for
failure then?
Thanks in advance,
Nikolai
More information about the systemd-devel
mailing list