[solved] using rootflags= option

Docbroke · 2016-03-21 04:46:12

based on https://wiki.archlinux.org/index.php/Im … tem_mounts I decided to remove my root device from /etc/fstab.

The article says that mount options can be specified with rootflags= option on kernel parameters, so I am using this now,

root=/dev/sda2 rootflags=rw,noatime,data=ordered quiet loglevel=3 vga=current libahci.ignore_sss=1

This makes my system boot fine without any issues, but what I want to ask is do I need to specify "0 1" as we do in /etc/fstab for fsck scan priority, + have I done anything wrong in specifying in "rootflags=', as I couln't find example of using that option anywhere.

Note: my root device is samsung evo840 ssd

EDIT: after this change my journal shows that fsck only check /boot and /home partitions, while root is not checked.

Last edited by Docbroke (2016-03-22 04:52:57)

ooo · 2016-03-21 13:21:38

You've specified rootflags correctly.

If you remove your root partition from fstab, it won't get fsck'ed by systemd. You're supposed to enable fsck mkinitcpio hook, which runs fsck for root (and /usr if separate partition) before the partition is mounted.

Naturally you don't need the fsck pass value, since your init doesn't run fsck for the partition.

There's a link to more lengthy explanation on mkinitcpio wiki page: https://bbs.archlinux.org/viewtopic.php … 5#p1307895

Docbroke · 2016-03-22 04:34:46

thanks!

So what I understood is, my "/" is checked by fsck early in boot process, (but not by systemd), so it doesn't appear in logs. While my other partitions are checked by systemd and it appears in log. I will now try "rd.log" kernel parameter to write logs of what happens in early boot.

EDIT: "/" gets fsck'ed early in boot. Marking this thread [solved]

Last edited by Docbroke (2016-03-22 04:52:36)

Arch Linux

#1 2016-03-21 04:46:12

[solved] using rootflags= option

#2 2016-03-21 13:21:38

Re: [solved] using rootflags= option

#3 2016-03-22 04:34:46

Re: [solved] using rootflags= option

Board footer