Red Hat Bugzilla – Bug 817347
No root device in the grub2.cfg after kernel upgrade with an empty /etc/fstab
Last modified: 2013-03-16 03:23:38 EDT
My two systems doesn't have anything in /etc/fstab anymore (i killed all these entries in the favour of systemd-based mounts). Unfortunately after recent update they both failed to reboot complaining on missing root partition. After a quick check I found that instead of something like
linux /vmlinuz-3.3.4-1.fc17.x86_64 root=UUID=468c16fc-abf1-41cd-9e30-79d94badb3c8 ro SYSFONT=latarcyrheb-sun16 LANG=ru_RU.UTF-8 KEYTABLE=us
linux /vmlinuz-3.3.4-1.fc17.x86_64 root= ro SYSFONT=latarcyrheb-sun16 LANG=ru_RU.UTF-8 KEYTABLE=us
I copied proper root partition UUID from another entry and not it boots fine. What is even more strange is that grub2-mkconfig produces completely valid config - with proper UUID for rootfs so I'm not sure whether this bug is in grubby, dracut, or in grub2. Feel free to change component for this ticket if necessary
Created attachment 697317 [details]
Patch which fixes this
Ok, I've made a patch which fixes this. Could you please take a look?
Created attachment 699327 [details]
Fix empty root device in case of an empty /etc/fstab
Created attachment 699328 [details]
Suppress error message if /etc/fstab doesn't exists.
Another one patch for suppressing error message in case of a missing /etc/fstab