[arch-general] Unwanted forced fsck at each startup - Was: How do I _really_ fix the superblock?

Ralf Mardorf ralf.mardorf at rocketmail.com
Sat Jun 7 16:34:12 EDT 2014


On Sat, 2014-06-07 at 13:23 -0400, Leonid Isaev wrote:
> That's actually interesting. Whether / will be fsck'ed or not depends
> on your mkinitcpio hooks (fsck) and kernel cmdline. What are them? Do
> you have "ro" in the cmdline?

The GRUB lines for my kernels all include 'ro'.

[rocketmouse at archlinux ~]$ grep HOOKS /etc/mkinitcpio.conf | grep -v "#"
HOOKS="base udev autodetect modconf block filesystems keyboard fsck vboxhost"

"1) Use the 'fsck' hook, use 'rw' on the kernel commandline.
2) Don't use the 'fsck' hook, use 'ro' on the kernel commandline." -
https://bbs.archlinux.org/viewtopic.php?pid=1307895#p1307895

So I should remove fsck from the hooks? If so, why didn't it cause the
issue before the systemd update?

Regards,
Ralf

Off-topic PS:
> Just an advice: replace this with a continuously tunning ntpd or at
> least with ntpd -q.

Is this useful for a DAW? Part of the audio tuning could be turning off
Internet connections, but at least I will run as less services as
possible. Ok, the -q "ntpd will not daemonize and will exit after the
clock is first synchronized" seems to be something I could use.



More information about the arch-general mailing list