Have no time right now for full smart test (will do in the night for system disk, just in case), i’ve canceled it and checked usual smart (all seems fine no bad sectors of failures), but after i’ve done fsck on all disks i still have that warning message on reboot
“So, if you now include the ‘fsck’ hook in /etc/mkinitcpio.conf and specify neither ‘ro’ or ‘rw’ on your kernel commandline, or explicitly specify ‘ro’, systemd will fsck your root device again. This is why the warning exists”
Guess this is the important part of his post. So i try to simplify this one:
If fsck hook is in your mkinicpio.conf and you specify either “ro” in your kernel commandline
(-> /etc/default/grub) OR nothing (in your kernel commandline)
systemd will fsck your root device again. This is why the warning exists
Hope this helps. Maybe you check those points on your system
Just in case i’ve update grub - nothing changed, still have the message…
So, what i don’t understand is why it keeps warning then?
My settings haven’t been changed manually whatsoever, so that freeze + hard reset have lead to something like this failure mechanism to auto-fsck root device, but why it keeps bugging me then, even after manual fsck?
Logically i would assume this mechanism should auto-fsck and then shut up with the warning…
However, when you reboot and remove rw - it still shows warning.
I don’t understand why it works that way, what happened?
I have a feeling that system tells me that something needs to be repaired for defaults to be adequate again, but what?
I’ve runned fsck on all disks already, nothing found, smart is fine…I’ve rebuild grub…
I don’t quite understand.
So adding rw works? If you then remove rw afterwards the message is back again?
If so, why not just leave the option in then? You actually do want to mount the device writable anyway, so I don’t see the downside. Fsck can now potentially run on that device and you don’t have the warning message at boot.