topic Re: Stuck at grub in Operating System - Linux

Stuck at grub

fushigi — Mon, 03 Dec 2007 02:01:10 GMT

I'm a newbie to lunix and would like to seek advise. This morning, one of our DL385 G1, RHEL 3 Update 6 hung on console after weekly schedule reboot.

The server stuck at console, getting below message.

Attempting Boot From CD-ROM
Attempting Boot From Hard Drive(C:)
GRUB

tried to have rebooted twice but again stuck on GRUB.

..is this a boot loader problem? Any help would be much appreciated.

Re: Stuck at grub

James ~ Happy Dude — Mon, 03 Dec 2007 04:56:38 GMT

Hello There,

Seems like the Boot files have to be set again to the correct image location.
As in, the images reside in /boot directory.

;) Regards.

PS: I am not a linux expert either; Watchout !! :D

Re: Stuck at grub

~sesh — Tue, 04 Dec 2007 05:31:10 GMT

It appears like a boot loader problem. Have you added any other drives? I had a similar problem when I added a drive & grub /boot/grub/device.map had to be changed to get it working.

Is there any error code? You can try booting with a Linux Live CD (Knoppix, SystemRescueCD, etc) & have a look at the device.map & menu.lst file to see if the entries match. Else you would need install grub again using the Rescue Mode.

Boot from the RedHat installation disc, at boot: type "linux rescue".

Type /sbin/grub-install /dev/hda to reinstall the GRUB boot loader, where /dev/hda is the boot partition.

Check the link for more information:

http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/s1-rescuemode-boot.html

Re: Stuck at grub

~sesh — Tue, 04 Dec 2007 05:32:37 GMT

The instructions to re-install boot loader:

http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/s1-rescuemode-boot.html

Re: Stuck at grub

fushigi — Wed, 05 Dec 2007 00:31:10 GMT

hello guys..just got back from the loop.
By the way thank you for the heads up. The box is up now after reinstalling the boot loader.

Thanks for all the help.

Re: Stuck at grub

fushigi — Wed, 05 Dec 2007 00:36:52 GMT

issue resolved!!!