How is /etc/fstab accessed before root is mounted?

I was making some changes to /etc/fstab, when this chicken and egg question occurred to me – if /etc/fstab contains the instructions for mounting the file systems, including the root partition, then how does the OS read that file in the first place?

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

When the boot loader calls the kernel it passes it a parameter called root. So once the kernel finished initializing it will continue by mounting the given root partition to / and then calling /sbin/init (unless this has been overriden by other parameters).

Then the init process starts the rest of the system by loading all services that are defined to be started in your default runlevel.

Depending on your configuration and on the init system that you use, there can be multiple other steps between the ones that I mentioned. Currently the most popular init systems on Linux are SysVInit (the traditional one), Upstart and Systemd. You can find more details about the boot process in this wikipedia article.

Here is a simplified example of my Grub config. The important part to answer your question is on the second to last line, there is a root=/dev/sda3:

menuentry 'Gentoo GNU/Linux' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-40864544-2d0f-471a-ab67-edd7e4754dae' {
    set root='hd0,msdos1'
    echo    'Loading Linux 3.12.6-gentoo-c2 ...'
    linux   /kernel-3.12.6-gentoo-c2 root=/dev/sda3 ro  
}

In many configurations the kernel mounts / in read-only mode and all the rest of the options are set to the defaults. In /etc/fstab you might specify file system parameters which would then be applied once init remounts it.

Method 2

An entry in fstab is needed, if you want to specify some non-default mount options. However, nowadays with systemd, a correct kernel device and fstype in fstab are unncesessary. You can replace the root entry with something like:

#UUID=8f74237d-b689-4beb-9d1f-f60b426c9969 /            ext4        rw,relatime,data=ordered    0 1
dummy /             auto        rw,relatime,data=ordered,debug  0 1

and the mount options are still honored by systemd.

You can use any bad device name, e.g. /dev/sdz1, except for bad UUID. With a bad UUID the message will be printed at boot: Failed to start Remount Root and Kernel File Systems, but the system boots anyway.

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0