Re: Fresh Install of F20 failed to install bootloader

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/22/2014 12:53 PM, Arthur Dent wrote:
On Tue, 2014-04-22 at 12:17 +0100, Arthur Dent wrote:
The reboot put me back into my old F16 install (at least I know that
hasn't been screwed up!) with the grub menu offering me only varying
kernels from F16.

It seems F20 has not installed the bootloader properly.

What are the steps for getting F20 to boot (while, if possible still
giving me the option to boot into F16)?
OK - So now I'm really flummoxed. Here's what I did:
I booted into the F16 install. I ran os-prober which found the new F20
kernel on the other partition (it still listed it below all the F16
ones) and ran grub2-mkconfig -o /boot/grub2/grub.cfg

This allowed me to reboot and see the new F20 install (listed about
half-way down the list of choices on the grub menu). The F16 install is
still the default. I was then able to boot into this
3.11.10-301.fc20.x86_64 kernel. I did a bit of tinkering (pointed /home
to the /home partition etc) and then ran yum update.

This brought in the latest kernel (3.13.10-200.fc20.x86_64). I ran
os-prober and grub2-mkconfig -o /boot/grub2/grub.cfg again. For good
measure I even installed grub-customizer and, sure enough, running that
showed a lovely list with 3.13 at the top, 3.11 beneath it and 3.6 (F16)
below that. My thinking here is that I am booted *into the F20 kernel*
therefore any changes will now be written to /boot *here*.

A save and a reboot and...

Back to the original grub screen...

F16 kernels at the top, the 3.11 F20 kernel below them and NO 3.13
kernel listed!

So when I run grub2-mkconfig -o /boot/grub2/grub.cfg from within the F20
kernel where is it writing to and why isn't the bootloader seeing it?

Any help much appreciated. I can boot into F20 at least now (but not the
latest kernel) but i have to do it manually (the default it still the
F16 kernel).

Thanks

Mark




I had this same problem.
 I install F20 on a second drive, Like sdb instead of sda ??
I put a second drive in computer sdb and installed F20 on it but i couldn't boot into F20 sdb it kept going back to F18 on sda, after all the work on Grub2, the only way I could get it to work was to put the NEW drive in as sda from sdb and original sda with F18 on it  as sdb by changing the cables on drives.
I then reinstalled F20 on sda and walla I can boot up  on F20, F18, and Windows 7.

I don't know your configuration but that is how I got into work. LOL!
-- 
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
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux