Linux Won't load under Grub
 

K, I am trying to get RH 7.1 to run under Grub, My windows partition boots fine no problems, but my linux partition freaks out when it gets to the "Checking the root Filesystem" sequence. It gives an error saying that "/dev/hda6" is already mounted. and fails. I have noticed in this boot sequence that it normally mentions how it is re-mounting / in rw mode, so I tried adding the ro option at the end of the kernel line in grub, but that provided no relief. Anyideas??

TIA!!
Mike.

Please, anybody, I am taking the RHCE exam friday and am just about ready, but I am almost possitive this problem will be on the debug portion. Any help is greatly appreciated!!!

Thank you!
Mike.

k, I have it narrowed down to the fact that when I boot from grub, my root filesystem is being mounted Read/Writeable before fsck is run, meaning it will not let me continue. What would the line in Grub.conf look like to make it load the root filesystem read-only. I am running rh 7.1, with an initrd. I have tried the following:

kernel /vmlinuz ro root=/dev/hda6
kernel /vmlinuz root=/dev/hda6 ro

anyother suggestions?

Thanks again!

anybody?

Grrrrrrrrrrr! The mighty grub
 

Grub always boots your system if there's a bootable image.

First try tab searching for the vmlinuz file.

When you get the grub menu, press e on the system you're trying to boot, to edit the boot command line.

try this:

kernel (hd0,1)/<TAB>

this will give you a list of options


This is assuming the vmlinuz file is on the second partition of the first disk. Grub counts from 0 like a computer should.

My command line looks like this:

kernel(0,1)/vmlinuz root=/dev/hda5

But the vmlinuz file could just as easily be a bzImage.

Post if you get it working

Bert

Thank you for the response!

vmlinuz is there, and grub is actually booting the kernel, but it is booting it read writeable, meaning when it comes time to fsck it it can't get passed this. I will do the TAB thing to see if that gets me anywhere, but technically the vlminuz is starting up, I just think it is being called slightly incorrectly.

Thanks!

Mike.

try 'rootnoverify'
 

Oh sorry, I didn't read your post correctly. :rolleyes:

Have a look here .

Why don't you just look and see what options were passed in to the kernel by lilo, they should be no different with grub.


John

the problem is this system was originally configured with a bootdisk, and not lilo so I have no lilo config to look at... what kernel parameter makes it load read-only?

Thank you so much for the help!
Mike.

finally found a possible read only parameter! After skimming my many linux books I found a sample lilo.conf file. It has the following entry:

root= /dev/hda6
read-only

so I will give that read-only parameter a shot and see waht happens, unfortunaly I won't find out till Sun-Mon, but I can be patient.

I'll let ya know what happens!

Thanks a lot!
Mike.