Broke LILO during upgrade to 12.2 ><

gegechris99 · 12-16-2008, 01:44 PM

After some googling, I found these commands to run if you still have a error after running /sbin/lilo:

1- Boot with CD1
2- Run the following commands (no chroot):

Code:

mount /dev/sda2 /mnt
mount --bind /dev /mnt/dev
mount -t proc proc /mnt/proc
lilo -r /mnt

What these commands do:

- Mount your partition into /mnt

- Remount /dev into /mnt/dev so that /dev/sda2 is available when you'll run lilo.

- Do a chroot to the /mnt directory before running lilo

27thSunshine · 12-16-2008, 05:05 PM

Ah...thanks so much for all your help, but I guess my problems went much deeper than that, and I think I remember where I went wrong [thats what happens when you don't pay STRICT attention to the upgrading rules before you know enough to vary from them]. I'm sorry for all the trouble, and appreciate all the work, but ultimately I ended up doing a fresh install. Luckily I didn't loose much -- a movie and a powerpoint presentation, both easily replaceable.

Again, thanks so much for your help, I'm going to try upgrading to 12.2 again after class and such [I didn't burn 12.2 to CD, I downloaded all the packages via ftp and did it that way].

Andersen · 12-16-2008, 07:11 PM

Quote:

Originally Posted by 27thSunshine

Hey guys, thanks for all your help so far.
I fixed lilo.conf, added the new lines, but I guess that wasn't the problem. It's still complaining about a bad superblock, and the suggested one [8193] doesn't work either. I've tried e2fsck /dev/sda2, but it doesn't work, not even with -f, nor does mke2fs -n /dev/sda2...any ideas on how to fix what seems to be the real problem?

I had that problem after upgrading 12.1 --> 12.2, I posted it here:

http://www.linuxquestions.org/questi...o-12.2-690421/

Looks like it's the rc.udev problem, but I did not wait enough to try the probable solution, I did a fresh install to cut the "knot".

sykes · 12-27-2008, 12:10 PM

Quote:

Originally Posted by brianL

I think you should always run lilo as root.

I had exactly the same problem. I manged to fix it after I replaced the rc.udev with rc.udev.new.

Thanks