Hello, Installed f19, during the prep didn't see any thing about boot so I proceeded with installation on reboot this is what I got: Booting from local disk ... error:no such device:fe0662f9-2f9b-4a9c-81ff-2d77f98c331b grub rescue> I tried to install grub by using rescue disk, shell and enter "chroot /mnt/sysimage" then "grub-install /dev/sda" grub-install: command not found did I missed some thing during the installation? is there a remedy? I greatly appreciate some help thank you in advance Vinny.
On 19.07.2013 22:58, Vinny Onelli wrote:
Hello, Installed f19, during the prep didn't see any thing about boot so I proceeded with installation on reboot this is what I got: Booting from local disk ... error:no such device:fe0662f9-2f9b-4a9c-81ff-2d77f98c331b grub rescue> I tried to install grub by using rescue disk, shell and enter "chroot /mnt/sysimage" then "grub-install /dev/sda" grub-install: command not found did I missed some thing during the installation? is there a remedy? I greatly appreciate some help thank you in advance Vinny.
2 :)
poma
Hi,
I don't know if those are related, but I had one system where fedup did not updated grub... It ended up booting and running F19 ok, but grub menu dsiplaying the old F17 entries. And it boots to the F1 kernel, although I could not find a thing that didn't work so far.
Maybe anaconda "forgot" to run grub2-install?
[]s, Fernando Lozano
On 22.07.2013 22:08, Fernando Lozano wrote:
Hi,
I don't know if those are related, but I had one system where fedup did not updated grub... It ended up booting and running F19 ok, but grub menu dsiplaying the old F17 entries. And it boots to the F1 kernel, although I could not find a thing that didn't work so far.
Maybe anaconda "forgot" to run grub2-install?
[]s, Fernando Lozano
Anaconda is the installation program used by Fedora, among others. FedUp i.e. upgrade != installation, so the question is whether the installation of the bootloader is actually needed.
poma