Will all those experiencing this bug with Gutsy give us detailed information as to the physical configuration of the motherboard disk interfaces and disk drives so we can understand the precise circumstances that cause this?
Right now we have a combination of comments, some of which indicate an issue with the BIOS boot-order, others that the BIOS drive-detection & reported order is different to that of Linux and/or GRUB.
Will all those experiencing this bug with Gutsy give us detailed information as to the physical configuration of the motherboard disk interfaces and disk drives so we can understand the precise circumstances that cause this?
Right now we have a combination of comments, some of which indicate an issue with the BIOS boot-order, others that the BIOS drive-detection & reported order is different to that of Linux and/or GRUB.
So, as an example:
Asus A8V
Mobo > SATA-1 > Drive-1
> SATA-2 > Drive-2
> PATA-1-1 > Drive-3 [master]
> PATA-1-2 > Drive-4 [slave]
> PATA-2.1 > DVD-1 [master]
During Installation:
BIOS boot order
DVD-1
Drive-1 Master Boot Record (MBR), /boot partition /dev/sda5
Drive-3 root partition /dev/hd2
USB
Linux (GRUB)
Drive-1 /dev/sda (GRUB hd1)
Drive-2 /devsdb (GRUB hd2)
Drive-3 /dev/hda (GRUB hd3)
Drive-4 /dev/hdb (GRUB hd4)
DVD-1 /dev/scd0
Output of:
$ ls -l /dev/disk/by-id
After Installation:
BIOS boot order
Drive-1
Drive-3
DVD
USB
Linux (GRUB)
Drive-1 /dev/sda (GRUB hd0)
Drive-2 /devsdb (GRUB hd1)
Drive-3 /dev/hda (GRUB hd2)
Drive-4 /dev/hdb (GRUB hd3)
DVD-1 /dev/scd0
Output of:
$ ls -l /dev/disk/by-id