RedHat Linux GRUB trouble!!!!

mike3001 · 06-16-2003, 06:22 PM

I recently installed a software package on a LAN that failed and in the process returned the nodes (except server) to GRUB. I have tried MANY WAYS to get linux up & running on the nodes, but to no avail. Tha latest think I did was create a GRUB floppy and try to load Redhat Linux 7.2 that way: no go!
the kernel is vmlinuz-2.4.7-10 ro root=/dev/hda2
When I boot, it begins the uncompressing process and then jumps back to GRUB. I am feeling pretty grubby about now. Any help would be greatly appreciated!

jvannucci · 06-17-2003, 09:04 AM

I'm not sure what you mean "returned the nodes to GRUB". They rebooted spontaneously? You were using LILO? Can you use a rescue disk? Just boot the original install CD and type 'linux rescue' at the prompt. (I think that's an option for RH 7.2). Then you may be able to figure things out, but if not you can at least snag a listing of one of the nodes' /boot directory. Please post this along with your grub.conf.

mike3001 · 06-18-2003, 10:25 AM

As I stated before: I loaded some network software on the lan, which failed. The nodes of the lan now only load to GRUB. I tried to reload Linux from the GRUB screen, but it would begin the uncompress process for Linux and jump back to GRUB. I created a GRUB floppy, thinking it might be better. I insert the GRUB floppy and loaded GRUB and the linux commands. The pc begins the uncompress process to load linux. I hear it read the HDD and then it brings up the GRUB screen from the HDD.

jvannucci · 06-18-2003, 10:30 AM

This clarifies things a little. Thanks. As I asked before, can you boot a rescue disk? Can you post your /boot directory and grub.conf?

mike3001 · 06-18-2003, 10:49 AM

The network is at the college. I will go there today. From the server I will create a boot rescue disk and try to bring up a node. I will get back to you with the results. Thanks SO much for you help!

jvannucci · 06-18-2003, 11:00 AM

Oh, when you get there, please include a posting of 'fdisk -l' and 'e2label' so we can tell what the disk layout is on the given node.

Thanks.

# e2label /dev/hda1
# e2label /dev/hda2
...