Re: editing GRUB options

Steven Kurylo wrote:
> Perhaps it wrote the boot map while you had hda working? Then during
> boot it pulled the kernel from hda (hence the hd0) and with the root
> being sda1, you got that install. Since the kernel on both your
> installations is the same, vmlinuz-2.6.17-11-generic, it worked.
>
> Then hda was removed. Grub would go looking for hd0 during boot, and
> the bios would hand it sda this time - sda is the only drive so it
> would become hd0 for grub. Again, the kernel is the same, so you
> never really noticed.
>
> Now that hda is back in there, the first part is happening again.
>
> Thats my theory.

Good theory, but the sequence of actual events was complicated by
several more steps that you've imagined (including a re-install to SATA
drive while the IDE was completely disconnected).
> Lets test it.
>
> Reboot your computer and when the grub menu appears (or ESC to make
> the menu appear), hit e (?) to edit the menu entry. Then goto the
> root lined and edit it (e again?). Change it to read "root (hd1,0).
> Then I believe you hit b to boot the kernel.
>
> This change is only good for the single boot, so it doesn't risk
> wrecking anything. Does it boot? If so my theory is correct.

Yep: it boots from the SATA drive, though. You were expecting that?

> So the next thing is to make sure your device map is correct.
> 'mv /boot/grub/device.map /boot/grub/device.map.bk'
> Then
> `grub-install --recheck hd0'
> What device map does it give you?

Now the IDE is indeed hd0, and the SATA is hd1.

> If sda is hd1, then change the
> groot line in menu.lst to to (hd1,0). Then run `grub-install hd1' and
> finally `update-grub'. This should update your list of kernels to all
> have root (hd1,0).
>
> You should be able to reboot and everything will work.
>
>> From there you can go back to my original suggestion off adding manual
> boot entries to the bottom of the menu.lst.

That's done. Here goes for a reboot. I'll report results as possible.
Received on Wed Apr 18 16:57:44 2007