• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Lilo probs.

Q

Quaggoth

Senior member
I have installed Redhat 7.0 to /dev/hdb1. Windows 98 SE is /dev/hda1. Linux swap is /dev/hdb5 I believe.

If I boot with no redhat startup disk, Lilo starts and gives me a "Win" and a "Lin" option. Lin is the default.

If I tell it to load Linux, it gets to a point where it says something like
/dev/hdb1 is already mounted. Can not continue. It then says to press ctrl-D to boot normally, or enter root password for maintenance. If I press ctrl-D, it reboots. If I type the root password, it gives me a prompt, but I have NO FREAKIN idea what to do from there. I am thinking I could probably edit lilo.conf, but it's so much easier not to.

Windows boots fine. If I have the redhat disk inserted, it boots to Linux fine. I have tried writing the boot sector to /dev/hda1, but then Windows won't boot either, and I have to boot to linux and change that setting to /dev/hda, then boot to a win98 boot disk and sys /dev/hda1. That puts the machine back to the original state where I have to use a disk for Linux. I have made Lilo work right with redhat 6.2 a while back, but can't seem to put the pieces together now.

Thanks for your help.

P.S. When I tell it to install the boot sector to /dev/hda1, linux boots from lilo, but won't mount /dev/hda1 because it says that it is not a valid umsdos (It doesn't seem to like me trying to call it a fat32 partition under any circumstances) partition or something to that effect.
 
Did you tell it to load lilo to the MBR? Linux shouldn't have any problems with FAT32, and if the boot loader's written to the MBR, it won't matter what that first partition is written to anyway.
 
I Think I have told it that. Isn't that what it does when I tell it to install the boot sector to /dev/hda1? the only reason I suspect that is the case is because I don't remember seeing anything in linuxconf about the master boot record.
 
There should have been a little selection box, right under "create boot disk", that allows you to tell it to write to the MBR. Make sure you're doing that. Otherwise, check Redhat's site, they probably have more information about this error.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top