[SOLVED] the "L 02 02 02" error on when upgrading to Slack 13.37
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
the "L 02 02 02" error on when upgrading to Slack 13.37
I just upgraded from 13.1 to 13.37 and I'm getting the L 02 02 02 error. This means that lilo can't find the partition it's told to boot. It's strange because:
- I haven't tweaked anything in the hardware
- I kept the same partitions, just formated
- I'm using ext3, as with 13.1
- I installed lilo on MBR (while on setup, and later with -M /dev/sda)
- I choose the huge smp kernel, as with 13.1
- I have only two partitions, root (sda1) and swap (sda2)
- the root partition is the active one (asterisk), on fdisk
So I tried:
- reseting the BIOS
- removing the UTF8 setting on lilo.conf
- using the lilo.conf that worked with 13.1
They all failed. I don't even know what to try! Any ideas?
PS: The hardware is a Pentium 4 1500Mhz with 512MB RAM on Asus P4B.
I don't think the -M option actually installs LILO to the MBR, it just writes a generic MBR that tries to load boot code from an active partition (useful if you installed LILO or another boot loader to a partition boot sector)
You can boot your system using the Slackware install disc (it gives you instructions when you boot from it). Then check your lilo.conf and reinstall with just '/sbin/lilo'
Last edited by piratesmack; 06-22-2011 at 06:43 PM.
You can boot your system using the Slackware install disc (it gives you instructions when you boot from it).
I've been booting by just pressing ENTER, mounting and chroot'ing my partition. Then I did lilo -v. I just tied your way. Didn't make any difference.
Quote:
Originally Posted by piratesmack
Then check your lilo.conf and reinstall with just '/sbin/lilo'
Well, I've already checked lilo.conf. And again tried with '/sbin/lilo', but no results. I'm all out of ideas. If you can think of a change to make in lilo.conf, I'm all ears!
After everything else failed, I installed again Slack 13.1 (base system) and it booted without any problems.
So then I went and installed Slack 13.37 base system, aaaand... it booted with any problems. That's very strange. I did the same choices, kept the same options.
After that I did one more install of 13.37 to get my typical functional system.
A thanks to everyone who replied.
Problem is solved but I don't know what caused it! So, if anyone has an idea, please tell me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.