lilo l 01 01 01 01
 

Hi everybody
Here's the situation
Currently I have xp on /dev/hda and try to install linux on /dev/hdd
I partition hdd into 2 , hdd1 for swap and hdd2 for linux.
I've instlal linux in this machine before, and it was fine until a week ago, my hd that had linux died, so I fix the hda mbr using xp recovery tool.

Today I got a new hd and try to install linux. I install linux on the MBR but when i reboot it gives me l 01 01 01

I've check the lilo conf it says boot=/dev/hda

You will need to give a clearer description of what you are doing.

First, you do not "install Linux on the mbr". The mbr is where the initial boot code goes--regardless of the OS.

You need to tell us what version of Linux you are installing, and what stage of the boot process produces the error message. Also, there must be more to the error message than just "01 01 01"

I'm trying to install slack 11, using lilo as boot loader
I've instll slack 11 before on my pc but the hd is dead now , so i'm trying to install to my new wd caviar.

I install lilo on MBR, during installation everything seems to be fine, until i reboot my machine and I get l 01 01 01 01 error

my hdd is western digital 160gb caviar

thank you for reply

Again---where exactly in the boot process are you getting this error message?

Does Slackware have a GRUB option? (There are more people that know about GRUB and can help)

Is this just one drive with only Slackware?

I remember at the ol' good time of LILO... this was the only and unique error message on the screen. A single "L" followed by an endless string made of "01". This does mean that the second stage of the boot process cannot be reached and 01 is the error code from LILO. Again in the ol' good time of floppy, this could be fixed by booting from /dev/fd0 and reinstalling the MBR from there. Anyway, as pixellany suggested, the easiest way to workaround this problem is to re-install and select GRUB as boot loader (if available). By the way, usually the problem is due to an erroneous configuration of lilo.conf.

Slackware's installer isn't very good and "seldom" manages to install Lilo for me.

Here are several cures.

(1) Use Slackware installation CD to selectively re-install Lilo. Not much a chance but may be an improvement.

(2) Use Slackware installation CD terminal mode to restore Lilo. Details as per Task B3 of the last link in my signature.

(3) Same as (2) but using any Linux Live CD. This is in case you are confused between the boot-up Slackware with the unbootable Slackware. The Live CD is the general method. Instruction same as Task B3 mention in above.

(4) Install Grub as suggested by Pixellany. Slackware has all the parts required by Grub and it is a 10 minutes job but you need to know how to write menu.lst for Slackware which is possiblest the easiest of all Linux. I would give more details if you choose this route but (2) or (3) is good enough in my experience with Slackware.

After I reboot my computer when it normally shows the red screen that says lilo 22.7.1, now that screen doesn't shows up and gives me l 01 01 01 01 01

my lilo.conf looks something like this
boot = /dev/hda ( this one has xp)
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773

# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdd2
label = Linux
read-only
# Linux bootable partition config ends

I have xp on hda and try to get linux on hdd2
so my hda has only xp, and hdd has only slack.
So in bios , i boot to my hda and here is where 01 01 01 occurs

You can always restore Lilo by "chroot" into the unbootable Slackware.

The universal method is to boot up a Live CD, click terminal, invoke root privilege (like typing "su" as the password is waived for a Live CD), make a temporary directory in /mnt, mount it, chroot to it and issue the "lilo -b" command, like this
When the "lilo -b /dev/hda" command is issued Lilo will go through /etc/lilo.conf and report any warning and error. Lilo only fails to boot if there is a fatal error. If none is reported it will say
and it will boot on a next reboot.

If it doesn't edit the lilo.conf again. Your lilo.conf looks normal to me.

Lastly once after the chroot command you are "inside" the unbootable Slackware and use it as though it is a normal Linux. You must "exit" first before you can reboot.

I try using knoppix to do task b3 and follow your steps but when i try to write it, it says
fataal operation not permitted on hda1
so i boot my disk 1 of slack instllation and do boot: linux root=/dev/hdd2 and try to repeta the step but now it gives me a warning that says
ignoring entry boot
warning boot sector and map files are on different disks
added windows *
added linux
but then still 01 01 01

I also try lilo -M /dev/hda, it gives no warning but still 01 01 01

Try to simplfy it by disabling some of the lines. The red bits are my proposed changes to your original lilo.conf

I tried your suggestion, still no luck

This hda is working fine with lilo until last week when my hdd died, and I fix the hda MBR using xp recovery, after that everything seems to go wrong because I remember I follow the same procedure, and used my backup file

It seems that my MBR for hda got hijack by xp, since lilo -M /dev/hda which suppose to install lilo on MBR, boot me straight to xp without showing any existance of lilo

I will try swapping my new hdd to be hda, old hda to be hdd.

You will have to investigate which of the hda or hdd is being booted first if the problem persists.

If you swap hdd to boot before hda you may find the second link of my signature helpful as it has the commands to allow hda to switched back to the first bootable status on-the-fly so that XP will still boots.

Yes thank you , it finally works
but as always another problem awaits
Now I can not boot to xp.

Here's how I do it

I have my new hard drive as primary master which has linux (hda) in bios that the first thing that it boots.
I put my old hda which has xp in it into secondary slave in bios, so now it become hdd
In bios everything looks ok to me.

Lilo works perfect when loading linux, but when it tries to boot xp, it says error ox01 and returns to the red screen where you can choose which os you want to load.

this is snippet of my lilo.conf
boot = /dev/hda

# Windows bootable partition config begins
other = /dev/hdd1
label = Windows
#table = /dev/hdd
# Windows bootable partition config ends

I'm starting to think about using grub now, since lilo is such a pain to setup in my pc.
What is the diffirent between those two? What I have in my is both of them are loader, so if one doesn't work, I don't see why the other will

I have mentioned to you before that you need to swap the xp disk on-the-fly and these are the lines, marked red, in Lilo that will do it for you.
Mind you I made a mistake by giving you the wrong link in Post #12 which I have since corrected. The information is in 2nd Link of my signature.

thank you for suggestions but I think I will take break first with lilo since it has tremendous potential of ruining my currently running linux, as I have deadline to meet.
I will get to the bottom of this lilo as soon as time allows me to.