Click to See Complete Forum and Search --> : how do i reinstall lilo?


The Anti-Void
07-22-2001, 11:37 AM
Windows broke again so i need to reinstall it. The problem is since windows overwrites the MBR it's going to kill lilo.
How do I reinstall lilo. My floppy drive doesn't work but i can boot with my RH7.1 cd.

P.S. I know this question has probably been posted before, but whenever I try to search the board, my web browser times out.

scott_R
07-22-2001, 12:22 PM
Assuming you already have installed windows, and dont have a rescue disk, the best way is to install lilo to the MBR without any more optionsperhaps off a lowly rawwrite floppy, then use the prompt to get to your system. Then just edit /etc/lilo.conf, and type /sbin/lilo -t to test, and /sbin/lilo to install it. You may also want to use the verbose option -v.

Or you could do it the easy way, and use your cd as a rescue disk ... :)

Of course, the easiest way is to have arescue disk so you dont have to putz aroudn with boot parameters

[ 22 July 2001: Message edited by: scott_R ]

sn9ke eyes
07-22-2001, 05:26 PM
I'm having the same problem. I'm running suse 7.1. I removed the windows hard drive that had lilo on the mbr and now it just displays 01010101010 and so on when I try to boot. I've booted the machine off the install boot disk, which doesn't load my modules correctly, but I can get in. I edited lilo.conf and had yast write to lilo to the mbr, but I still get the 010101010 stuff. The install tells me that I've got

/dev/hdf1 linux native partition
/dev/hdf2 linux swap
/dev/hdf3 root partition

I've got lilo.conf pointed to /dev/hdf1 and then the different kernels all point to /dev/hdf3 for root.

Please help

sn9ke eyes
07-23-2001, 04:00 PM
Actually I resolved my problems. I had forgotten to switch my hard drive jumper back to master. Once I did that, the system recognized the partitions as hde1,2, and 3. I had to edit the fstab so it would auto mount correctly and then edit the lilo.conf to reflect hde. Then I ran /sbin/lilo and it was able to write to the mbr. Problem solved.