Quoting Ivan Boro (magwa....@yandex.ru): > On 10/19/2015 07:07 PM, Karl E. Jorgensen wrote:
> > /etc/fstab is in the root file system. Thus, the system can only > > examine /etc/fstab _after_ the root file system has been mounted... > > > > Instead you may want to examine the kernel command line (e.g. in grub > > or /proc/cmdline) - it should have "root=xxxx" in it. Nowadays that is > > often specified via a UUID - and the UUID stays the same if if you move > > disks about. > > > > Hope this helps > > > > Yes. Fun thing, I've accidentally put /dev/vda1 to my host's > filesystem's fstab, and the host system runs init as pid=0. > Everything boots normally. Now I doubt, is the root entry present in the > fstab file generated automatically during system setup. As others have said, when the system boots, grub will know which filesystem is wanted as root for each menu entry. However, grub can only find out which filesystem that is in the first place by being told correctly by you. So keep your /etc/fstab up-to-date with correct entries. /etc/fstab should never be modified by the system, but only by you/the sysadmin. One difference with systemd is that incorrect information is more likely to cause problems than with sysv-style booting. A way of thinking about this is that sysv "interprets" fstab line by line whereas systemd "compiles" it whole. Cheers, David.
