Comment 7 for bug 33106

Recurring issue, grub writing incorrect drive designations in 8.10 as of 11/15/2008. Sqame issue in 8.04.

I have 4 HDD's:[QUOTE]
 sudo blkid
/dev/sda1: UUID="32dd3252-53b9-4647-b538-95793e7a55e2" TYPE="ext3"
/dev/sda5: TYPE="swap" UUID="d81a0c0e-1b88-40fb-abed-2c9b15d0db6f"
/dev/sdc1: UUID="30F70D6E790F4174" LABEL="Backups" TYPE="ntfs"
/dev/sdd1: UUID="25610e0c-64f0-4512-a31c-49ddf2a9c1ff" TYPE="ext2"
/dev/sdb3: UUID="4f92449d-38a5-4453-b22e-9e3785987a02" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb4: TYPE="swap" UUID="67e9932c-9bf7-4186-b147-0b534ed4080f"
/dev/sdf1: SEC_TYPE="msdos" UUID="48F4-EAEE" TYPE="vfat"
/dev/sde1: SEC_TYPE="msdos" UUID="48EA-8696" TYPE="vfat"
/dev/sdd5: TYPE="swap" UUID="bf5881cf-1674-4f8e-a1b7-96083c9f0dd2"
/dev/sdg1: UUID="48F4-EAEE" TYPE="vfat" SEC_TYPE="msdos"
/dev/sdd2: UUID="1306a0e0-da49-4c2a-bc75-87a7c682aba3" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdg: LABEL="NEW VOLUME" UUID="E4B5-EDFE" TYPE="vfat"
/dev/sdh1: UUID="0000-0000" TYPE="vfat" SEC_TYPE="msdos"
/dev/sdi1: SEC_TYPE="msdos" UUID="0000-0000" TYPE="vfat"
/dev/sdi: LABEL="NEW VOLUME" UUID="E4B5-EDFE" TYPE="vfat"
/dev/sdb5: TYPE="swap" UUID="4e1e2438-4522-4134-95c5-af5de6d4b796"
/dev/sdc3: UUID="4f92449d-38a5-4453-b22e-9e3785987a02" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc4: TYPE="swap" UUID="67e9932c-9bf7-4186-b147-0b534ed4080f"
/dev/sdc5: TYPE="swap" UUID="4e1e2438-4522-4134-95c5-af5de6d4b796"
/dev/sdb1: UUID="ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d" SEC_TYPE="ext2" TYPE="ext3" [/QUOTE]

I have Ubuntu 8.10 on hd0,0/sda1.
I just installed Kubuntu 8.10 on hd1,0/sdb1

The grub was written to hd1,0 but is incorrect. This is the grub menu.lst that comes up upon start-up and was created after Kubuntu unstall:

[QUOTE]title Ubuntu 8.10, kernel 2.6.27-7-generic
uuid ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic
quiet

title Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
uuid ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d ro single
initrd /boot/initrd.img-2.6.27-7-generic

title Ubuntu 8.10, memtest86+
uuid ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda1.
title Ubuntu 8.10, kernel 2.6.27-7-generic (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=32dd3252-53b9-4647-b538-95793e7a55e2 ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic
savedefault
boot

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda1.
title Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode) (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=32dd3252-53b9-4647-b538-95793e7a55e2 ro single
initrd /boot/initrd.img-2.6.27-7-generic
savedefault
boot
[/QUOTE]

The first menu choice above is Kubuntu and the second, Ubuntu. As you can see the Ubuntu is shown as hd0,0. If I select that it starts loading with the Kubuntu splash but login is Ubuntu. I used Super Grub to boot from and edit the Ubuntu drive to hd1,0 and it loads with the Ubuntu splash and goes to the Ubuntu login.

Below is the Ubuntu menu.lst. which I edited. I removed the "root (hd0,0)" which was written in originally. This menu.lst is not the one loading at this time. I will edit the menu;lst which is currently loading and incorrect for Ubuntu.

[QUOTE]
title Ubuntu 8.10, kernel 2.6.27-7-generic
uuid 32dd3252-53b9-4647-b538-95793e7a55e2
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=32dd3252-53b9-4647-b538-95793e7a55e2 ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic
quiet

title Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
uuid 32dd3252-53b9-4647-b538-95793e7a55e2
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=32dd3252-53b9-4647-b538-95793e7a55e2 ro single
initrd /boot/initrd.img-2.6.27-7-generic

title Ubuntu 8.10, memtest86+
uuid 32dd3252-53b9-4647-b538-95793e7a55e2
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems: KUBUNTU 8.10
root

title Ubuntu 8.10, kernel 2.6.27-7-generic
uuid ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic
quiet

title Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
uuid ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d ro single
initrd /boot/initrd.img-2.6.27-7-generic

title Ubuntu 8.10, memtest86+
uuid ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d
kernel /boot/memtest86+.bin
quiet[/QUOTE]

I know that I can delete any reference to hd0 or whatever and the OS will load according to the uuid without any problem.

I bring this up because I feel that this is where a lot of confusion and boot failures occur after an installation. This can be especially difficult to a new user.

The physical order of my HDD's is never anywhere similar to how grub writes or even how booting from a LiveCD reads it.

The actual order is, according to the bios boot listing:
(1) /dev/sdb3: UUID="4f92449d-38a5-4453-b22e-9e3785987a02" SEC_TYPE="ext2" TYPE="ext3" ATA Hitachi 250Gib No OS
(2) /dev/sda1: UUID="32dd3252-53b9-4647-b538-95793e7a55e2" TYPE="ext3" SATA Western Digital 160 Gib with Ubuntu
(3) /dev/sdd2: UUID="1306a0e0-da49-4c2a-bc75-87a7c682aba3" SEC_TYPE="ext2" TYPE="ext3" SATA Maxtor 160 Gib
(4) /dev/sdc1: UUID="30F70D6E790F4174" LABEL="Backups" TYPE="ntfs" ATA with SATA adapter Western Digital 40 Gib, No OS