Mailinglist Archive: opensuse (3996 mails)
| < Previous | Next > |
Re: [SLE] grub hangs after sata & 9.1 upgrade
- From: Johan Nielsen <yep@xxxxxxxxxxxxxx>
- Date: Mon, 6 Sep 2004 17:25:23 +0200
- Message-id: <200409061725.23292.yep@xxxxxxxxxxxxxx>
Mandag den 6. september 2004 16:46 skrev Dave Howorth:
> Doug B wrote:
> > On Monday 06 September 2004 04:26 am, Dave Howorth wrote:
> >>I have an Intel system with SATA disks. I've been running it in
> >>'legacy' mode with Suse 9.0 but have just upgraded to 9.1. It boots
> >>OK and seems fine when it is still running in legacy mode with 9.1
> >>(using kernel 2.6.4-52). I boot off the PATA disk, /dev/hda.
> >>
> >>Then I switched the BIOS to 'enhanced' mode (where the SATA disks
> >>appear native) and the machine hangs after the BIOS boots but before
> >>GRUB shows anything on screen.
> >>
> >>I can still boot into the rescue system on the boot CD. fdisk shows I
> >>have hda (PATA disk), hdb (DVD drive), sda (SATA 1) and sdb (SATA 2).
> >>
> >>In my /boot/grub directory, there is a device.map that says
> >>(hd0) /dev/hda
> >>(hd1) /dev/hdc
> >>(hd2) /dev/hdd
> >>
> >>I don't think anything in the menu.lst can be relevant, since I don't
> >>even get a 2nd stage loader message. I suspect that GRUB is seeing
> >>the disks in a different order with the BIOS in enhanced mode.
> >
> > I don't have SATA - yet, but it appears from what you posted that (hd1)
> > is now /dev/sda and (hd2) is now /dev/sdb
> >
> > If that is the case, you should check menu.lst for references to hdc and
> > hdd and change them to sda and sdb.
>
> Thanks for the response, Doug.
>
> It's a little more complicated than that, I fear :(
>
> Certainly (2.4.*) hdc -> sda (2.6.*) and hdd -> sdb
> but neither of those drives appear in my menu.lst.
> In fact, sda isn't mounted at all (I use it only for backups) and sdb
> appears as /home after Suse starts up. But none of that matters (I think
>
> :) ...
>
> grub isn't getting as far as displaying a menu. It isn't even displaying
> the message as it transitions stages. I suspect that the machine is
> trying to boot from sda instead of from hda now, and there's nothing in
> the boot sector.
>
> I used the Suse install CD to 'repair' my system and it has written a
> new device.map:
>
> (hd2) /dev/hda
> (hd0) /dev/sda
> (hd1) /dev/sdb
>
> I'm trying to figure out how to get grub to install itself on the sda
> MBR, to boot the Suse that's installed on hda1, but I'm not having much
> luck so far. Can anybody point me to a HOWTO, or tell me how to do it?
>
> Thanks, Dave
You might be able to create a new grub setup with the help of the repair
option on the install-media. So boot from it and go to the repair option and
try it out. Just make sure that you have the last call (so don't go automatic
at first "try").
Johan
> Doug B wrote:
> > On Monday 06 September 2004 04:26 am, Dave Howorth wrote:
> >>I have an Intel system with SATA disks. I've been running it in
> >>'legacy' mode with Suse 9.0 but have just upgraded to 9.1. It boots
> >>OK and seems fine when it is still running in legacy mode with 9.1
> >>(using kernel 2.6.4-52). I boot off the PATA disk, /dev/hda.
> >>
> >>Then I switched the BIOS to 'enhanced' mode (where the SATA disks
> >>appear native) and the machine hangs after the BIOS boots but before
> >>GRUB shows anything on screen.
> >>
> >>I can still boot into the rescue system on the boot CD. fdisk shows I
> >>have hda (PATA disk), hdb (DVD drive), sda (SATA 1) and sdb (SATA 2).
> >>
> >>In my /boot/grub directory, there is a device.map that says
> >>(hd0) /dev/hda
> >>(hd1) /dev/hdc
> >>(hd2) /dev/hdd
> >>
> >>I don't think anything in the menu.lst can be relevant, since I don't
> >>even get a 2nd stage loader message. I suspect that GRUB is seeing
> >>the disks in a different order with the BIOS in enhanced mode.
> >
> > I don't have SATA - yet, but it appears from what you posted that (hd1)
> > is now /dev/sda and (hd2) is now /dev/sdb
> >
> > If that is the case, you should check menu.lst for references to hdc and
> > hdd and change them to sda and sdb.
>
> Thanks for the response, Doug.
>
> It's a little more complicated than that, I fear :(
>
> Certainly (2.4.*) hdc -> sda (2.6.*) and hdd -> sdb
> but neither of those drives appear in my menu.lst.
> In fact, sda isn't mounted at all (I use it only for backups) and sdb
> appears as /home after Suse starts up. But none of that matters (I think
>
> :) ...
>
> grub isn't getting as far as displaying a menu. It isn't even displaying
> the message as it transitions stages. I suspect that the machine is
> trying to boot from sda instead of from hda now, and there's nothing in
> the boot sector.
>
> I used the Suse install CD to 'repair' my system and it has written a
> new device.map:
>
> (hd2) /dev/hda
> (hd0) /dev/sda
> (hd1) /dev/sdb
>
> I'm trying to figure out how to get grub to install itself on the sda
> MBR, to boot the Suse that's installed on hda1, but I'm not having much
> luck so far. Can anybody point me to a HOWTO, or tell me how to do it?
>
> Thanks, Dave
You might be able to create a new grub setup with the help of the repair
option on the install-media. So boot from it and go to the repair option and
try it out. Just make sure that you have the last call (so don't go automatic
at first "try").
Johan
| < Previous | Next > |