Announcement

Collapse
No announcement yet.

grub-pc 30_os-prober script not working correctly.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    grub-pc 30_os-prober script not working correctly.

    I have a slightly complicated setup and I'm doing my best to get along with grub-pc. I'm using Karmic 64-bit and grub-pc 1.97.

    My issue is the 30_os-prober script is incorrectly creating menu entries that overlap each other.

    The CLI output from update-grub:
    root@office:/boot/grub# update-grub
    Generating grub.cfg ...
    Found Debian background: background.png
    Found linux image: /boot/vmlinuz-2.6.31-20-generic
    Found initrd image: /boot/initrd.img-2.6.31-20-generic
    Found memtest86+ image: /memtest86+.bin
    Found Ubuntu 9.10 (9.10) on /dev/sda5
    done
    The results in grub.cfg
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Ubuntu, Linux 2.6.31-19-generic (on /dev/sda5)" {
    insmod ext2
    set root=(hd0,5)
    search --no-floppy --fs-uuid --set ebffb916-98b7-4f9c-85c5-4a91796710d1
    linux /boot/vmlinuz-2.6.31-19-generic root=UUID=ebffb916-98b7-4f9c-85c5-4a91796710d1 ro quiet splash ipv6.disable=1
    initrd /boot/initrd.img-2.6.31-19-generic
    }
    menuentry "Ubuntu, Linux 2.6.31-19-generic (recovery mode) (on /dev/sda5)" {
    insmod ext2
    set root=(hd0,5)
    search --no-floppy --fs-uuid --set ebffb916-98b7-4f9c-85c5-4a91796710d1
    linux /boot/vmlinuz-2.6.31-19-generic root=UUID=ebffb916-98b7-4f9c-85c5-4a91796710d1 ro single
    initrd /boot/initrd.img-2.6.31-19-generic
    }
    menuentry "openSUSE 11.2 (on /dev/sda5)" {
    insmod ext2
    set root=(hd0,5)
    search --no-floppy --fs-uuid --set ebffb916-98b7-4f9c-85c5-4a91796710d1
    linux /vmlinuz root=UUID=418db53a-2d85-4148-a693-c721bca71af0 ro quiet splash
    initrd /initrd
    }
    ### END /etc/grub.d/30_os-prober ###
    The first two entries are correct, the last one isn't.
    I do have openSUSE 11.2 installed, but it's installed as /boot on /dev/sdb2 with / on /dev/md7 (a raid device). The correct entry for the openSUSE install I put in 40_custom like this
    menuentry "openSUSE 11.2" {
    insmod raid
    insmod mdraid
    insmod reiserfs
    set root=(hd1,2)
    search --no-floppy --fs-uuid --set 418db53a-2d85-4148-a693-c721bca71af0
    linux /vmlinuz-2.6.31.12-0.1-desktop root=UUID=c04e1c76-8305-43f5-b6a8-db37947a0636 ro quiet splash ipv6.disable=1
    initrd /initrd-2.6.31.12-0.1-desktop
    }
    It's odd that it doesn't report finding openSUSE, still puts it in (wrong), and I can't get it to detect it correctly.

    Please Read Me

    #2
    Re: grub-pc 30_os-prober script not working correctly.

    grub-pc 30_os-prober also does not handle Arch properly.

    This is what ends up in grub.cfg
    Code:
    menuentry "Arch (on /dev/sda8)" {
        insmod ext2
        set root=(hd0,8)
        search --no-floppy --fs-uuid --set 1d88233e-5f1d-4fbd-8718-bdab2f7f6ca4
        linux /boot/vmlinuz26 root=/dev/sda8
    }
    I ended up having to put the correct entry into /etc/grub.d/40_custom
    Code:
    menuentry "ArchLinux (on /dev/sda8)" {
        insmod ext2
        set root=(hd0,8)
        search --no-floppy --fs-uuid --set 1d88233e-5f1d-4fbd-8718-bdab2f7f6ca4
        linux /boot/vmlinuz26 root=/dev/sda8 ro vga=834
        initrd /boot/kernel26.img
    }
    .
    .
    .
    I believe that a bug has been opened against grub2 for the Arch snafu.

    Comment


      #3
      Re: grub-pc 30_os-prober script not working correctly.

      I thought it was rather odd that it apparently detects openSUSE, then puts it in wrong.

      My setup is a bit more advanced than the usual I think.

      4 sata hard drives and 1 ssd.

      I have space for three RAID0 installs with separate /boot partitions, a dedicated GRUB partition, and four spaces for non-RAID standard installs, four large backup partitions, a RAID5 setup for my data files, 4 swap partitions and RAID0 /tmp, all on the 4 sata drive. The ssd is just for playing around at the moment.

      The "overlapping" occurs with the openSUSE install being detected by GRUB as being on sda5 - which it's not, I have a backup kubuntu install there. openSUSE is on sdb2 for /boot and a RAID0 device for /.

      Please Read Me

      Comment

      Working...
      X