F17 Beta installed but lost after 3rd reboot

[taytong888]

Hi,

This thread is different from my previous F17 thread. Multiboot lappy with openSUSE 12.1 as default OS. Originally when Suse 12.1 was installed, legacy Grub bootloader was placed in the MBR and common boot partition sda5. Later on, added Kubuntu, F16 and Suse 12.2 which are all Grub2. This arrangement allows chainloading into Windows, Kubuntu, F16 or Suse 12.2. Boot menu is from Grub Stage 1.5.

Recently, I installed F17 Beta in the root partition sda11 of F16 to overwrite the latter, and had no choice but to place Grub2 bootloader in the MBR;I tried but failed to boot F17 if Grub2 is in either boot partition sda5 or root partition sda11. After the first reboot, I can boot into F17 Beta allright. However, after I logout, boot into openSUSE 12.1, logout then boot into F17, Grub 1.5 menu shows error 15: File not found.

Please refer to the attached file RESULT.TXT = output of Boot Info Script.

I would appreciate your help fixing this problem.

:confused:

[kc1di]

if you can boot into opensuse reinstall grub 1.5 and you should find that all will work again.

[chrismurphy]

I tried but failed to boot F17 if Grub2 is in either boot partition sda5 or root partition sda11.

GRUB2 upstream is pretty much suggesting that installing GRUB2 anywhere but in the MBR and MBR gap, is flakey, dangerous, not advisable, and prone to problems, etc. I wish the installers wouldn't let users even attempt it, but whatever. The best solution is GPT, and having a "BIOS Boot' partition expressly for GRUB2's core.img. Rather than this sloppy embedding in partition boot sectors.

---------- Post added at 01:52 PM ---------- Previous post was at 01:22 PM ----------

As for your bootinfo script.

Sorry but I'm going to say this is a total mess. I count *four* grub configuration files on sda5 alone. I count four grub legacy stage 2 embeds in partition boot sectors, and one grub2 core.img embed in a boot sector. And it's your MBR stage1 embed that's looking to sda5, which has myriad embeds and configuration files. And syslinux is on sda7.

First, I really think you should use GPT instead of MBR because you have so many partitions, instead of using extended partitions.

Second, there is no good reason for having installed so many instances of GRUB in so many partitions. You need one installation of either GRUB legacy or GRUB 2 to do what you want. Next time you install a Linux distro, just don't have it install a bootloader. You already have one (well now you have 6, at least).

Third, pick a bootloader and version. Realize that GNU upstream grub-devel@ and help-grub@ have not worked on GRUB legacy in 6+ years. It's not supported. No one there will answer questions about it anymore.

---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------

Recently, I installed F17 Beta in the root partition sda11 of F16 to overwrite the latter, and had no choice but to place Grub2 bootloader in the MBR

Boot Info Script says GRUB legacy stage 1 is in the MBR. Not GRUB2. GRUB2's boot.img is only found in the boot sector for sda13.

---------- Post added at 07:53 PM ---------- Previous post was at 01:56 PM ----------

After a bike ride it dawns on me you have no choice but to use MBR and extended partitions because of Windows 7. If this is BIOS hardware, the boot disk must use MBR. *sigh*

So ignore the commentary on using GPT. But I'll stand firm that you need to pick a boot loader version, and seriously consider (at least) abandoning embedded in partition boot blocks. Since partition 1 starts at sector 2048, there will be plenty of room to embed GRUB2's core.img in the space between the MBR and partition 1.