At boottime fsck displays messages although boot-option quiet is set…
Now I read, that replacing “udev” by “systemd” in /etc/mkinitcpio.conf
will not show this message.
...
# HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
HOOKS=(base systemd autodetect modconf block filesystems keyboard fsck)
...
This works, are there any drawbacks - and why is the mentioned replacement not standard?
Because there are still people who are disliking systemd.
If you switch to systemd hooks, make sure to understand the ArchWiki Hooks.
E.g. my hooks look like this:
HOOKS=(base systemd keyboard sd-vconsole modconf block sd-encrypt lvm2 fsck filesystems)
I thought that fsck was proposed to be replaced by the systemd-fsck-root.service that will be triggered at reboot/shutdown and will actually start the systemd-fsck@.service to do the fsck … on the other hand, based on some research, seems BIOS does not need base & udev, when autodetect is set, but will have to check that at some point. So, while systemd is used, still wonder why the need for fsck and also in some cases the shutdown ?! 
there is a way to display these messages in other TTYs
That is exactly what I did not really knew until now, thank You!
HOOKS=(base systemd autodetect modconf block keyboard keymap fsck filesystems)
is the correct order, afaik now…
That had i done on our Ubuntu-PC - that works too
(as Ubuntu is a little ticklish with changes)
Another Question - may be or not related to this thema:
Since systemd251 I get this error-line in journalctl:
systemd-udevd[442]: event2: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
As far as I know, the change to systemd fsck is :
Delete fsck fom hooks in etc/mkinitcpio
In grub go down to the bottom and uncomment the
GRUB_ROOT_FS_RO=true
Then
sudo mkinitcpio -P && sudo update-grub
…no anoying boot message.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.