On Mon, 23 Dec 2013 19:25:49 -0600, Ranjan Maitra wrote:
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora, with Linux 3.11.10-301.fc20.x86_64' --class fedora
--class gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-3.11.10-301.fc20.x86_64-advanced-f96397ae-311d-4826-8fb0-6a0fe710dd9c'
{ load_video
set gfxpayload=keep insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1
--hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'
54f94607-a593-4d5c-b03a-356574992f4e else search --no-floppy --fs-uuid
--set=root 54f94607-a593-4d5c-b03a-356574992f4e fi
linux /vmlinuz-3.11.10-301.fc20.x86_64 resume=/dev/sda2
root=/dev/sda3 ro vconsole.font=latarcyrheb-sun16 nomodeset rhgb
quiet }
There is no "initrd" parameter for this first boot entry!
What are the contents of the /boot directory?
If the initramfs image file for this kernel is missing, it's no surprise that
grubby doesn't recognise this boot menu entry. The image may be regenerated
using "dracut" (see "man dracut").
That it refers to the root device with UUID and /dev/sda3 is strange, too.