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: Rahul on 27 Apr 2010 12:25 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 seem to work at this point except for Ctrl+Alt+Del which, of course, causes it to reboot. What could I be doing wrong? Any ideas? The machine has an internal HDD from where its supposed to boot plus an external RAID array containing user homes. The RAID array is connected via a SCSI interface. More background: The reason I was booting was that yesterday one disk on the RAID had died. At that point the "user home" file system had gone "read only" but otherwise the machine worked OK. Then I replaced the bad disk and the RAID array has now successfully rebuilt itself. Unfortunately the machine aborts its boot process. -- Rahul
From: Rahul on 27 Apr 2010 13:48 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
From: J G Miller on 27 Apr 2010 17:30 On Tue, 27 Apr 2010 17:48:19 +0000, Rahul wrote: > I should correct: GRUB and a blinking cursor. GRUB cannot find the stage whatever files it needs which should be under /boot/grub to continue into the GRUB menu phase. They may still be there but the relative disk and partition number may not be what grub thinks it should be. The only way to resolve this problem is to get out the rescue disk and reinstall grub.
From: Rahul on 28 Apr 2010 11:27 J G Miller <miller(a)yoyo.ORG> wrote in news:1272403802_15(a)vo.lu: > On Tue, 27 Apr 2010 17:48:19 +0000, Rahul wrote: > >> I should correct: GRUB and a blinking cursor. > > GRUB cannot find the stage whatever files it needs > which should be under /boot/grub to continue into > the GRUB menu phase. > > They may still be there but the relative disk and partition > number may not be what grub thinks it should be. > > The only way to resolve this problem is to get out > the rescue disk and reinstall grub. > > Thanks! I used a rescue disk for RHEL but it says no Linux partitions were found. Furthermore the /dev folder shows no mountable sd* devices. Should I still be able to reinstall grub? I know that this disk is connected via a scsi interface and the BIOS + RAID-BIOS see this disk. (The singe loical disk is actually 3 physical drives on a RAID5 in the machine) -- Rahul
From: unruh on 28 Apr 2010 11:55
On 2010-04-28, Rahul <nospam(a)invalid.invalid> wrote: > J G Miller <miller(a)yoyo.ORG> wrote in news:1272403802_15(a)vo.lu: > >> On Tue, 27 Apr 2010 17:48:19 +0000, Rahul wrote: >> >>> I should correct: GRUB and a blinking cursor. >> >> GRUB cannot find the stage whatever files it needs >> which should be under /boot/grub to continue into >> the GRUB menu phase. >> >> They may still be there but the relative disk and partition >> number may not be what grub thinks it should be. >> >> The only way to resolve this problem is to get out >> the rescue disk and reinstall grub. >> >> > > Thanks! I used a rescue disk for RHEL but it says no Linux partitions were > found. Furthermore the /dev folder shows no mountable sd* devices. Should I > still be able to reinstall grub? Sorry, you talk about "this disk" and then you talk about raid, which implies more than one physical disk. You talk about "raid-bios" but I do not know wthat that means. Is this the abortion known as software raid contained on many motherboards, which is, as far as I can tell, a useless piece of junk. You will probably need at least one partition on one of your disks that is NOT raid. and use that to contain the /boot directory, so your bios can find the absolute sectors on that disk and download the second stage grub loader. Remember that on bootup, the ONLY thing available is the disk access software in the bios. It has access to no drivers or any other software. It can only load absolute disk sectors into memory to run them. If the boot loader is not at some absolute disk address on one disk ( and if you use striped raid, it is not) the bios disk reader cannot do anything. > > I know that this disk is connected via a scsi interface and the BIOS + > RAID-BIOS see this disk. (The singe loical disk is actually 3 physical > drives on a RAID5 in the machine) > |