machine stops at GRUB screen during boot process
in [General Linux]
|
Prev: NYC LOCAL: Tuesday 27 April 2010 NYLUG: Squeak Hack Fest
Next: Fancast compared to Hulu plus my not so quick look at a bunch of the Linux OS
From: Robert Heller on 28 Apr 2010 15:33 At Wed, 28 Apr 2010 18:43:21 +0000 (UTC) Rahul <nospam(a)nospam.invalid> wrote: > > Robert Heller <heller(a)deepsoft.com> wrote in > news:2O2dnbs2uokx40XWnZ2dnUVZ_tudnZ2d(a)posted.localnet: > > Thanks Robert! > > > > *Exactly* what sort of disks are on this internal MegaRAID controller? > > SCSI disks for sure. I opened the box. > > > Do you know *exactly* what make/model of MegaRAID controller it is? > > Its start up screen *should* tell you something. If nothing else, > > crack open the case and have a look at the drives & controller board. > > Sure. I'll find that out and post. I have a strong suspicion this has to do > with the drivers. Somehow my rescue disk doesn't have the drivers needed to > access the MegaRAID. That seems odd. The CentOS 5.4 kernel (2.6.18-164.15.1.el5) includes megaraid.ko and megaraid/megaraid_mbox.ko in its SCSI drivers, which should support this -- I looked at the modules.alias file and /usr/share/hwdata/pci.ids -- a large number of controllers seem to be covered. What kernel / distro rescue disk are you using? Maybe you need a better rescue disk... -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller(a)deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
From: TomT on 28 Apr 2010 16:06 Rahul <nospam(a)nospam.invalid> wrote: >Rahul <nospam(a)nospam.invalid> wrote in >news:Xns9D6774522A7896650A1FC0D7811DDBC81(a)81.169.183.62: > >> I rebooted a machine today (after a RAID rebuild) and it stops at a >> black screen with "GRUB" as the only text. Unfortunately the keyboard >> doesn't >> > >I should correct: GRUB and a blinking cursor. Rahul, GRUB is obviously installed. You may want to reinstalled it but first, just for laughs, after the cursor, type "find /boot/grub/stage1" (without the quotes of course) and see if it returns anything. If it does we'll go from there. If not, you're no worse off. TomT
From: Rahul on 28 Apr 2010 16:08 Robert Heller <heller(a)deepsoft.com> wrote in news:g9Gdneffvu8KEEXWnZ2dnUVZ_smdnZ2d(a)posted.localnet: > That seems odd. The CentOS 5.4 kernel (2.6.18-164.15.1.el5) includes > megaraid.ko and megaraid/megaraid_mbox.ko in its SCSI drivers, which > should support this -- I looked at the modules.alias file and > /usr/share/hwdata/pci.ids -- a large number of controllers seem to be > covered. What kernel / distro rescue disk are you using? Maybe you > need a better rescue disk... > You are right again! Thanks very much! I downloaded the latest RHEL rescue disk and now I can see my drive as /mnt/sysimage. That's a big relief! I think it is the megaraid_mbox driver. My older Rescue disk didn't seem to have that driver. At the same time not full success: If I reboot the machine without the Rescue disk it again hangs at the GRUB screen. What do I need to change to make it boot successfully? Any ideas? When I used the rescue mode /mnt/sysimage had pretty much my original / partition. So no data loss. In /mnt/sysimage/etc/ grub.conf is present too. There is one other drive that is mountable /dev/sda1. This seems to be the boot partition from its contents. My grub.conf has lines of the sort: title foo root (hd0,0) kernal bar module ... ro root=/dev/VolGroup00/LogVol100 How should I make grub boot off the /dev/sda1? Not sure what's broken here. -- Rahul
From: Rahul on 28 Apr 2010 16:23 TomT <TomT(a)UnrealBox.invalid> wrote in news:to4ht5de837u69h83go5fhkbb5rnukv9o1(a)4ax.com: > GRUB is obviously installed. You may want to reinstalled it but first, > just for laughs, after the cursor, type "find /boot/grub/stage1" > (without the quotes of course) and see if it returns anything. If it > does we'll go from there. If not, you're no worse off. > Thanks TomT! The scren with "GRUB" and blinking cursor doesn't accept any input. But now that I can boot into rescue mode and find the disk I ran grub in the rescue shells command line (after doing a chroot /mnt/sysimage) I get the grub prompt but "find /boot/grub/stage1" give me: "Error15:File not found" But further snooping reveals that the "stage1" file is indeed present at two locations: /mnt/sysimage/boot/grub. and /dev/sda1/grub -- Rahul
From: Robert Heller on 28 Apr 2010 16:57
At Wed, 28 Apr 2010 20:08:02 +0000 (UTC) Rahul <nospam(a)nospam.invalid> wrote: > > Robert Heller <heller(a)deepsoft.com> wrote in > news:g9Gdneffvu8KEEXWnZ2dnUVZ_smdnZ2d(a)posted.localnet: > > > That seems odd. The CentOS 5.4 kernel (2.6.18-164.15.1.el5) includes > > megaraid.ko and megaraid/megaraid_mbox.ko in its SCSI drivers, which > > should support this -- I looked at the modules.alias file and > > /usr/share/hwdata/pci.ids -- a large number of controllers seem to be > > covered. What kernel / distro rescue disk are you using? Maybe you > > need a better rescue disk... > > > > You are right again! Thanks very much! I downloaded the latest RHEL rescue > disk and now I can see my drive as /mnt/sysimage. That's a big relief! I > think it is the megaraid_mbox driver. My older Rescue disk didn't seem to > have that driver. > > At the same time not full success: > If I reboot the machine without the Rescue disk it again hangs at the GRUB > screen. What do I need to change to make it boot successfully? Any ideas? > > When I used the rescue mode /mnt/sysimage had pretty much my original / > partition. So no data loss. In /mnt/sysimage/etc/ grub.conf is present too. > > There is one other drive that is mountable /dev/sda1. This seems to be the > boot partition from its contents. > > My grub.conf has lines of the sort: > title foo > root (hd0,0) > kernal bar > module ... ro root=/dev/VolGroup00/LogVol100 > > How should I make grub boot off the /dev/sda1? Not sure what's broken here. You probably need to just do something like: chroot /mnt/sysimage grub-install /dev/sda I suspect that what has happened is that without the external RAID disk connected, what maps as '/dev/sda' changed. It is possible that the external RAID was in fact /dev/sda<mumble> and the (internal) system disk was /dev/sdb<mumble> (because of the order the *BIOS* saw things). You might want to do something to 'fix' this problem by swapping the PCI cards for the internal and external RAID disks. I'm guessing you have some flavor of (LSI) MegaRAID SCSI RAID controller in a PCI slot and an Ataptec (?) SCSI card in another PCI slot for the external SCSI connected (self-contained) RAID unit. Swap the two PCI cards. This will reverse the order they are seen by the BIOS. I am assuming that the /boot file system is mounted using the LABEL= feature in the system's /etc/fstab file. -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller(a)deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/ |