Hi James

Thanks for the reply.

While what you say is correct re UUIDs, there are boot problems with the Gigabyte GA7N500 Pro2 mobos with the new Ubuntu Hardy and Hardy-based distros.

To try to sort out my problem I attached an empty formatted IDE HD and an empty formatted SATA hd to another of my PCs with an identical mobo. I also attached a DVD-RW.

I then installed LinuxMint 5.0 from the LiveCD - this is Hardy based.

The install was to the IDE HD and after the install was complete, Mint booted fine from the IDE hd.

THe PC's BIOS is set to boot from the first hd (hd0), and I'm not sure that I can boot from SATA, which is set in the PC BIOS to "BASE" ( rather than RAID) - it may boot as SCSI but I haven't tried that yet. THese mobos are over 3 years old.

If I detach the SATA hd and try to boot I get an "ERROR 15" message.

The reason for this is that GRUB/MINT sees the SATA hd as the first hd in the system, and the IDE hd as the second HD.

This is bor out by /boot/grub/menu.lst, the first entry of which is:-

root (hd0,0)
kernel /boot/vmlinuz-2.6.24-16-genric root=/dev/sdb1 ro quiet splash.

Notice the /dev/sdb1 which indicates that the IDE hd is the SECOND hd.

This is fine, but if one is in the habit of adding/removing SATA hds, especially if one has an ESata hd, then it is necessary to continually change the GRUB boot set-up.

If I remove the SATA hd, then /dev/sdb1 has to be changed to /dev/sda1, or possibly /dev/hda1

The short of all of this is that if I want to attach a SATA hd to my main system which currently has 3 IDE hds, I need to change the GRUB boot entry and be prepared for all of the IDE drives (hds and DVD-RW) to be deprecated by 1 - ie /sda becomes /sdb, /sdb becomes /sdc etc.

Bill

James Rogers wrote:
Hi Bill,

If you are using Ubuntu doesn't that mean you use UUIDs to identify the drives?
Thus the drive letters (hda,sda) are irrelevant?

James





--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to