My first guess would be to check that you're using the exact same UUID in the boot parameter as on the drive partition. Check the partition UUID is what you thought it is. Check for typos in the boot configuration. So how exactly would I be able to do that from dracut? I simply can't imagine the UUID would be different since I originally had an LVM partition when installing F16 but when I went install F19 fresh I wiped the LVM partition completely in favor of ext4 partitions and formatted those during the install. I suppose it's not impossible the UUID isn't the same, but I just don't see how. Also, I had this exact problem with F16 and used grub commands to force the system to use the device name. (IIRC, it may be that Fedora isn't able to get the UUID from the HDD, but can use the device name without trouble.) Not to mention, I'm really more interested in how to get those grub commands I used to use to work with the new boot process/grub version. Based on what I've read Fedora uses /boot/grub/i386-pc/normal.mod as part of the boot process. Which seems to be the problem, the documentation on the new grub process is either sparse or just not easily found on the internet. I've got a couple of links that might have the information I need, but had hoped someone on the list might be able to point me in the right direction a little quicker than the 2+ hours I spent on my own the last few days on it. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
