Re: Debian 6 / Grub 2 problem

On Wednesday 07 September 2011 14:29:04 Ross wrote:
> > I think, for some reason, Grub failed to install  (certainly the second
> > time, when I was using the Deb6 DVD in 'rescue' mode, I got an error
> > message to that effect).
> > 
> > I was going to ask what the Grub file is called, but I guess if it's
> > installed to the boot sector an 'ls' wouldn't show it up anyway.
> > 
> > Anyway thanks for the help, I think I might try a Deb6  install on one of
> > my laptops (which don't have vital data on them) and get a 'feel' for it
> > before I attack my big box again.
> 
> I think you have two MBRs, one on each drive.
> 
> You could try changing your BIOS disk boot order in CMOS setup if that
> option is available to see if mbr is on other drive and bootable. As
> long as you note the original order it should be simple to switch back
> if it is unsuccessful.
> You could also try using a Super Grub Disk or similar to boot the mbr
> from the other drive.
> 
> Ross.

I think you might be right   :)

After a successful install of Deb 6.0.2.1 Squeeze (32-bit) on my laptop, I 
thought I'd try 6.0.2.1 (AMD64) on the desktop.   And the same thing happened 
as with 6.0 previously - an apparently successful install, then it rebooted 
into my old (Lenny) grub menu.

I've got three hard disks, a 40GB Seagate (which I use for Linux distros), a 
160GB Seagate for data, and a 500GB WD SATA for data.   The BIOS sees them in 
that order.

And yes, changing my boot sequence in the BIOS found the new Grub2 menu, on 
the 500GB  WD SATA.

Complications persist though - 

Debian Lenny sees them as /dev/hda,  /dev/hdc and /dev/sda, whether booted 
from Grub on /hda or Grub2 on sda.

Debian Squeeze, if booted from Grub, sees them as /dev/sda (40GB), /dev/sdb 
(160GB), and /dev/sdc in that order.   If booted from Grub2, it sees them as 
/dev/sdb, /dev/sdc and /dev/sda.   I assume Squeeze gets its drive ID's from 
Grub.
This obviously leads to complications in Squeeze with identifying my data 
partitions in /etc/fstab, since it changes according to which Grub I boot it 
off.   I was hoping to shun UUID's which look like digital garbage.
I suppose I shall have to bite the bullet and fill my /etc/fstab with UUID's   
(why do they have to be so damn _long_  - I could tolerate 12 digits like MAC 
addresses!).
 Can somebody confirm, do these UUID's remain the same no matter which drive 
the system was booted from?    

Then I'll hafta try and get Grub2 installed on the MBR of my 40GB drive (since 
booting a system on one drive off the MBR of another seems like setting up for 
trouble next time I shuffle drives around).   
Which raises the question, why did Debian install the system on one hard drive 
and the Grub boot stage on another anyway?

cr

_______________________________________________
NZLUG mailing list [email protected]
http://www.linux.net.nz/cgi-bin/mailman/listinfo/nzlug