bug-grub
[Top][All Lists]
Advanced

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

menuentry order


From: Donald Norman
Subject: menuentry order
Date: Tue, 02 Nov 2010 00:19:19 -0400
User-agent: Opera Mail/10.63 (Linux)

Dear Sirs,

I have installed Ubuntu 10.10 intending to duel boot with MS Vista. When I tried to go into windows on boot it went into recovery mode. I had messed with WINE some prior to rebooting into windows and assumed this facilitated the error. So, I ran fixmbr to repair the windows boot. That worked fine for windows, but... Then I reinstalled Ubuntu and found the same issue.

Below is a copy of the appropriate section of grub.cfg:


### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos6)'
        search --no-floppy --fs-uuid --set b458b50e-b7b8-4346-b8f4-257dbd3135e8
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=b458b50e-b7b8-4346-b8f4-257dbd3135e8 ro quiet splash
        initrd  /boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos6)'
        search --no-floppy --fs-uuid --set b458b50e-b7b8-4346-b8f4-257dbd3135e8
        echo    'Loading Linux 2.6.35-22-generic ...'
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=b458b50e-b7b8-4346-b8f4-257dbd3135e8 ro single
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos6)'
        search --no-floppy --fs-uuid --set b458b50e-b7b8-4346-b8f4-257dbd3135e8
        linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos6)'
        search --no-floppy --fs-uuid --set b458b50e-b7b8-4346-b8f4-257dbd3135e8
        linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows Recovery Environment (loader) (on /dev/sda1)" {
        insmod part_msdos
        insmod ntfs
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 16a0c71ca0c7016b
        drivemap -s (hd0) ${root}
        chainloader +1
}
menuentry "Windows Vista (loader) (on /dev/sda3)" {
        insmod part_msdos
        insmod ntfs
        set root='(hd0,msdos3)'
        search --no-floppy --fs-uuid --set 2c88743c8874071c
        chainloader +1
}
### END /etc/grub.d/30_os-prober ###

What I have found is that Grub has incorrectly identified Windows Recovery Environment (loader) (on /dev/sda1) when it is really on sda3 and
Windows Vista (loader) (on /dev/sda3) when it is on sda1.

I have never submitted a bug or anything like one before; I hope that this is helpful and not a wild goose chase.

BTW,
The only way have found around this is to boot to the "wrong" loader to get to the "right" OS.

--
Using Opera's revolutionary email client: http://www.opera.com/mail/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]