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.
You need to reinstall Lilo. Do this by booting into the installation with the install cd with the command at boot screen: bare.i root=<insert /dev/hd**> noinitrd ro
Then when in the system (as root), just typing the command "lilo" will probably suffice, but you may have to reconfigure Lilo completely with the command liloconfig, or editing the file /etc/lilo.conf.
In my experience that is the error message comes up when a Lilo install doesn't take and is usually solved by a reinstall of Lilo. The "stage index sector" is probably part of the MBR where Lilo was installed.
Use the Slack install disk to boot, type pkgtool as root, reinstall lilo to the MBR then type lilo then reboot and that should do it. That same thing has happend to me several times.
I've gotten the same thing before, what fixed it for me was to install on root partition instead of MBR. or visaversa. Of course you would have to find a way to remove the bootloader fromt the mbr without messing up partition tables.
Use the Slack install disk to boot, type pkgtool as root, reinstall lilo to the MBR then type lilo then reboot and that should do it. That same thing has happend to me several times.
That worked... I used pkgtool to install LILO on MBR... the SETUP utility says installing on MBR can cause corruption, so I didn't take that option.
Hey all, I have a similar issue. I have two drives that I swap back and forth as the boot/os drive and one of them now gives me the L 99 99 etc whenever I try to boot it by itself. HOWEVER, if the other drive is on the bus it boots fine?? Is there a way to run lilo but have it target the particular drive? For instance, lilo the hdb rather than the hda? When booted off of hda? I'm scared to lilo the hdb's lilo.conf for fear it will mess up the hda's lilo.
" Hey all, I have a similar issue. I have two drives that I swap back and forth as the boot/os drive and one of them now gives me the L 99 99 etc whenever I try to boot it by itself. HOWEVER, if the other drive is on the bus it boots fine?? Is there a way to run lilo but have it target the particular drive? For instance, lilo the hdb rather than the hda? When booted off of hda? I'm scared to lilo the hdb's lilo.conf for fear it will mess up the hda's lilo.
That make any sense?? "
Do you mean you physically remove the drives and swap them? or you just reconfigure lilo?
well if you mean that you're going to use both disks constantly but just need a system (lilo) for changing which OS/HD you want to drive at boottime, oh yes i would say it's possible .
Just do a 'liloconfig', but, read the man_page first.
And if you are using MS_Os and want a dual boot be shure to place XP? as your primary hda ( C: )
(physically to - master hd - that is).
And yes, put lilo to your MBR when that question arises.
Still i'm not shure how you're setup ???
These are both running linux. I want to have both drives on the bus or be able to take one off. What I do is keep all data on a SCSI Raid array and then use the IDEs (hda/b) to do upgrades to Linux, Apache, PHP etc. This lets me have an easy and safe rollback environment without having to "uninstall" anything.
I'm thinking that I must not have run lilo but only changed the lilo config so most likely hdb is still looking for hda in some fashion and when the drive isn't there problems arise.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.