When I copied my f21 KVM image to a real partition and edited the UUIDs and msdos partition numbers that were laying around, I found I could only boot the rescue menu entry, the default one wouldn't work.
After being confused by this for a bit, I finally noticed that the root= line on the default entry said /dev/vda1 not UUID=
I could have sworn it always used UUID for all kernel entries in previous fedoras.
Anyway, I now have a new thing to look for when copying install images around :-).
On Tue, Dec 9, 2014 at 11:32 AM, Tom Horsley horsley1953@gmail.com wrote:
When I copied my f21 KVM image to a real partition and edited the UUIDs and msdos partition numbers that were laying around, I found I could only boot the rescue menu entry, the default one wouldn't work.
After being confused by this for a bit, I finally noticed that the root= line on the default entry said /dev/vda1 not UUID=
I could have sworn it always used UUID for all kernel entries in previous fedoras.
Anyway, I now have a new thing to look for when copying install images around :-). --
I've seen this a handful of times, but I'm very uncertain if it was Fedora 20 or Fedora 21 or both. Or even UEFI or BIOS, or both. The closest I got to identifying this was while /mnt/sysimage was still in chroot for the installation, and I captured grub.cfg immediately after grub2-mkconfig created it and it had the root=/dev/sdX designation. But after the installation was complete, while still not quitting out of the installer, I did this:
chroot /mnt/sysimage grub2-mkconfig -o /boot/grub2/grub.cfg
And the replacement grub.cfg now has root=UUID= So it's a bit of a WTF moment. The same command did something different in one chroot than another, with the same damn mounts. Very weird. And maybe not easy to troubleshoot since grub2-mkconfig is just a script that gets this information from grub-prober or maybe os-prober. So it's an intermittent bug is sounds like. It might be worth posting this to the grub help list and see if they have some idea where to look for such a thing.
Allegedly, on or about 09 December 2014, Tom Horsley sent:
After being confused by this for a bit, I finally noticed that the root= line on the default entry said /dev/vda1 not UUID=
I could have sworn it always used UUID for all kernel entries in previous fedoras.
On my Fedora 20 installation, the special rescue option used a UUID, and the normal boot kernel option used a device name. It wouldn't boot up for me, either, post installation. Thanks to the device names being different from booting via a DVD versus the HDD. Looks like my BIOS may be one of those that re-orders things when it automatically steps through the list of which device to boot.
-
Chris Murphy -
Tim -
Tom Horsley