installation of redhat 5.2, problemo???

I have once installed linux on my machine and had it working with redhat 4.2.  I reformated the hd, installed DOS 6.22 with a working cdrom.  I have acquired redhat 5.2 and have installed it successfully.  When I boot/reboot, the system halts at :


I have not had a successful login because it will not let me get there, just sticks.  I had created a rescue disk and when that is used the system freezes with:

   crc error


My questions are these:  Can I fix this without a reinstallation??  And how??  And at the end of the installation it asks you if you want the loader to be installed in a certain place, where should that be installed in order to boot directly into linux, like you would with dos????????

Thank you very much.
Who is Participating?

Improve company productivity with a Business Account.Sign Up

debug22Connect With a Mentor Commented:
What is your partition status ? Do you have
a) one DOS & one Linux partition, or
b) just one partition on which you have installed Linux ?

If b), you have to prepare a boot disk to run FDISK.EXE (or COM) off.  If not, use the FDISK already installed in DOS/Win.

Problem: Something is wrong with the way LILO is installed in your MBR.  After booting off a standard DOS bootable disk, do FDISK /MBR to clean up your MBR. Now you can
boot into DOS w/o getting stuck, and later put a fresh LILO in there.  

NOTE: I don't know if this step is necessary, but I'd recommend it.

The next step is to try to get into Linux somehow, & then reinstall LILO.
I think your rescue disk has a bad sector or something, borrow someone else's. OR
find your old boot/root install disks, use them to boot (or use the diskless install option if your distrib provides it), and at the boot: prompt, type in

root=/dev/hda3 ro

(change this for your Linux native partition).

Or go to the install prompt and then type

mount -t ext2fs /dev/hda3 /mnt

By now you should be in Linux... go to the mounted filesystem & then install LILO
properly to the MBR.  Run "setup" (the one on your mounted partition, not the bootkernel
one!!! Find it in /mnt/one of the usual bins).  Install LILO to the MBR.  Edit the /etc/lilo.conf
to check that it is OK.  Run /sbin/lilo to fix the new boot images in the MBR.
If it installed properly, reboot.

At this stage you could have problems - mainly due to inconsistency between the
/mnt filesystem & the / filesystem where lilo etc. "expects" to find its config files.
Make a copy of lilo.conf in the /etc directory and of the kernel onto / .  Anyway,
if you have a DOS partn, now is the time to (mount it and) copy LOADLIN and the kernel to it.  Now you have another entry point to Linux.  Or maybe you can convince LILO to
accept the mounted files by some parameter.

Tell me if it worked. Once you've broken into your Linux parttion with Linux running, 3/4th the battle is won.  If you have a really screwed-up reinstall, I'd recommend a backup of your important files & a reinstall.

To evacuate the data off your Linux partition, mount it from Win95/some other OS, and then reinstall.  One Linux mounter for Win95 is fsdext2, it works most of the time at least for reading stuff from the Linux partition. Search for other better mounters.  I don't know where you can get fsdext2, I got it off a BBS, maybe you could try a public ftp archive.

Getting back to LILO stuff: To boot to Linux directly, make the /vmlinuz image the first one in your LILO.conf  (I think setup should help you do this.  The keyword before it should be "image=", and before the DOS partition's section should be "other=".  

Tell me if this doesn't work or you need details.
I don't think you will be able to fix it without a reinstall.
About Lilo (thez loader):
you can install it in one of two places:
* the Master Boot Recard (MBR).
It's the recommended place to install Lilo, unless the MBR already starts another operating system loader(system commander ...)
* The first sector of your root partition.
It's thre recommended place if you are alreadyusing another boot Loader on your system.

but in this case, you should install it on the MBR

To boot directly : Lilo will boot automatically after his timeout period (by default  5 seconds)  if you're doing nothing at Lilo's prompt. If you want to boot directly, just change this timeout period.

Wish it'll help.

oups, forgot to tell you how to change lilo's timeout period.

you have 2 options :

* edit the file /etc/lilo.conf and change the line timeout=50 by
what you want

* or type lilo -d <what_you_want>

Warning : the timeout delay is in deciseconds.
Well ?  Did you try it yet ?
Ladies and gentlemen if you have access to the CD then you can boot.
Go to the CD (directory dosutils) and copy loadlin.exe. Somewhere nearby is a file named vmlinuz.
Place the two files to the dos directory.
Then type "loadlin vmlinuz root=/dev/<your_linux_partition> ro"
You can do your lilo stuff when you get in.
If you really want to fix without booting from your copy get
the hal91 distribution (its fits on a single floppy) from
Boot from the hal91 floppy, mount your hard disk and start fiddling.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.