Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Recently, after performing the initial update on SuSe 9.2, which had a kernel update, my multi-boot (XP Pro SP2/SuSe 9.2) was totally wiped out. Now all that I get is a black screen with a L99 error on XP and an L04 error on SuSe which are on separate drives. I know that something went wrong with LILO, and some general idea of what is required to restore the boot, but not enough to proceed.
I'm hoping that someone will take the time to give step by step instructions on this, without any unnecessary Linux jargon.
If you are sure that somthing is wrong with your "lilo"
then insert the cd with which u installed the linux distro.......boot from this cd.......
then at the prompt type "linux rescue"...........then follow the instructions there.
(probably you will only have to type "lilo" at the bash prompt to get it on work)
The first link was interesting in that he found a solution by installing LILO to the MBR...this is something that I have not tried. However, let me explain my reluctance to do so at this point.
My first concern is to not to take my XP drive to a point of no return. From what I have read, the L99 error only pertains to this drive, because it is drive 0 and where the MBR is located. I think that the list of LILO errors said that this number was something about broken or invalid indexes.
L04 is the error generated by drive 1 which is the Linux install. Again, I'm not positive but I think that the error mean't that it couldn't locate the bootloader on drive 0.
In the process of trying to fix this, I used both fixboot and fixmbr on the XP drive, but this didn't work to boot either system. It seemed that both of the links that you gave, was primarily concerned about restoring just the Linux system, but to reiterate, my primary concern is to restore XP, because reinstalling Linux would be far less of a burden, with less data lost.
The second link did not indicate a clear solution, merely possibilities, many of which I have either tried or at least know of. Until I can find a solution that ensures restoration of XP, I shall try nothing.
Originally posted by seeker1
The first link was interesting in that he found a solution by installing LILO to the MBR...this is something that I have not tried.
??????.
What then was your boot-loader - XP, then using boot.ini to load Linux ???.
The "Lnn" error codes indicate to me that Lilo is in the MBR (of the first disk), and can't find the later stage files (note that I haven't used lilo in years, so big chance I'm wrong).
Maybe the Suse update did a (partial ???) update to lilo.
Quote:
In the process of trying to fix this, I used both fixboot and fixmbr on the XP drive, but this didn't work to boot either system.
What happens when you try to boot XP after doing this ???.
Originally posted by syg00 ??????.
What then was your boot-loader - XP, then using boot.ini to load Linux ???
No, I used LILO, as I have already said. However, it has never been clear to me as to where the install location of it was, because I used the default option on install, which was : "Don't touch the MBR". For this reason, I'm quite confused.
Quote:
The "Lnn" error codes indicate to me that Lilo is in the MBR (of the first disk), and can't find the later stage files (note that I haven't used lilo in years, so big chance I'm wrong).
Maybe the Suse update did a (partial ???) update to lilo.
What happens when you try to boot XP after doing this ???.
Assuming that you are right, where would this "later stage files" be located? You may also be correct about the partial update, I found an article which says to always update LILO, after a kernel update. Unfortunately, I didn't read this before. If I try to boot to XP, whether using the Linux CD, or simply by unplugging the Linux drive and booting, I only get the L99 error.
O.K., now it makes (a little) more sense.
But I can't help, as I don't know lilo - hopefully someone else can.
Re-running lilo from the install disk, and fixmbr from the XP resource centre should both have re-written the MBR loader code (on the BIOS primary boot disk).
Why it didn't is the issue I'd be persuring - bit hard to do from the other side of the 'net I'm afraid.
O.K., now it makes (a little) more sense.
But I can't help, as I don't know lilo - hopefully someone else can.
Re-running lilo from the install disk, and fixmbr from the XP resource centre should both have re-written the MBR loader code (on the BIOS primary boot disk).
Why it isn't is the issue I'd be persuing - bit hard to do from the other side of the 'net I'm afraid.
Originally posted by ruudra Is it possible ???
I mean to boot from XP boot - loader using boot.ini to load linux
If yes, then what would be the entries in boot.ini ???
u can use "loadlin" to load linux from ur winXP bootloader
Originally posted by syg00 Doesn't need loadlin.
Simply a matter of copying the boot sector record to the XP system partition.
A *very* poor option compared to the linuxloaders.
plz be a little descriptive about copying the boot sector record ......i mean from where should i copy, what should be copied etc. etc..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.