After today's Rawhide grub2 update, I ran "grub2-install /dev/sda" and "grub2-mkconfig -o /boot/grub2/grub.cfg". When rebooting, I can't boot any of the installed kernels because of "error: you need to load the kernel first". This is a VirtualBox guest and AFAIK /dev/sda is the correct device (it worked in the past). Did I do something wrong or is the latest grub2 broken?
I did boot in rescue mode and ran the same commands again after doing "chroot /mnt/sysimage/". No change.
On Friday, June 29, 2012 10:54 PM Andre Robatino wrote:
After today's Rawhide grub2 update, I ran "grub2-install /dev/sda" and "grub2-mkconfig -o /boot/grub2/grub.cfg". When rebooting, I can't boot any of the installed kernels because of "error: you need to load the kernel first". This is a VirtualBox guest and AFAIK /dev/sda is the correct device (it worked in the past). Did I do something wrong or is the latest grub2 broken?
I did boot in rescue mode and ran the same commands again after doing "chroot /mnt/sysimage/". No change.
That reminds me of what I got when I reversed the kernel and initrd lines in the grub.conf for GRUB1.
Does your grub.cfg have linux lines preceding the initrd lines?
Fred
Frederick William New <Frederick-William.New <at> Elion.ee> writes:
That reminds me of what I got when I reversed the kernel and initrd lines in the grub.conf for GRUB1.
Does your grub.cfg have linux lines preceding the initrd lines?
On Fri, 2012-06-29 at 19:53 +0000, Andre Robatino wrote:
After today's Rawhide grub2 update, I ran "grub2-install /dev/sda" and "grub2-mkconfig -o /boot/grub2/grub.cfg". When rebooting, I can't boot any of the installed kernels because of "error: you need to load the kernel first". This is a VirtualBox guest and AFAIK /dev/sda is the correct device (it worked in the past). Did I do something wrong or is the latest grub2 broken?
I did boot in rescue mode and ran the same commands again after doing "chroot /mnt/sysimage/". No change.
Try doing another grub2-install . I think you're really supposed to do the install _after_ the mkconfig.
Using grub2-install with grub2-2.00-1.fc18 breaks booting. Do *not* run grub2-install while using this version. Recovery requires downgrading to an earlier version of grub2 and running grub2-install and grub2-mkconfig again.