I recently added a 20GB hard drive to a system that already had a 6.4GB hard drive (hda - master) with Redhat Linux 5.2 installed. After installing Redhat 6.2 on the new drive (hdb - slave) I can't seem to configure Lilo properly so that it sees the boot image on hda. I was configuring lilo from the the hdb drive. Anyone have any ideas about solving this problem?? [sig][/sig]
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Lilo question with two separate Linux drives??
- Thread starter Muaddib
- Start date
My setup was a bit different, one of my partitions was windows, and my spare drive was SCSI, but I just made sure that LILO had both specified, and was written to the mbr of hda. Then it worked without problem. (This was with Mandrake 7.0, but it shouldn't matter).
OTOH, as a work around, until you get the final answer, you could make two separate boot floppys, one for each system that you want to use.
I'm actually about to encounter a close match to your exact situation. I intend to create an emergency copy of Linux on a 2GB Jaz disk. I figure that this should allow me space for plenty of tools. And my current plan was to figure that I would be booting from a floppy. Well, it's an emergency system, so that's perhaps a bit more acceptable, but my thought was that after the thing was built, there should be an disk that had the option of which system to boot. But I don't think that this could be built until after both had been booted after the second install. So I expect to make several temporary boot disks before I get the final lilo working.
One thing I've never had reason to check was whether the new lilo's/grub's are compatible with the old kernels. I assume that they are, but don't know for certain, so you might need to check that out. You could just be stuck with floppy boots for one system or the other.
[sig][/sig]
OTOH, as a work around, until you get the final answer, you could make two separate boot floppys, one for each system that you want to use.
I'm actually about to encounter a close match to your exact situation. I intend to create an emergency copy of Linux on a 2GB Jaz disk. I figure that this should allow me space for plenty of tools. And my current plan was to figure that I would be booting from a floppy. Well, it's an emergency system, so that's perhaps a bit more acceptable, but my thought was that after the thing was built, there should be an disk that had the option of which system to boot. But I don't think that this could be built until after both had been booted after the second install. So I expect to make several temporary boot disks before I get the final lilo working.
One thing I've never had reason to check was whether the new lilo's/grub's are compatible with the old kernels. I assume that they are, but don't know for certain, so you might need to check that out. You could just be stuck with floppy boots for one system or the other.
[sig][/sig]
- Thread starter
- #3
Kudagai,
Initially I did set it up with two boot floppies as a last resort but I was able to get this working. I copied the vmlinuz-* from the boot floppy of the Redhat 5.2 system to the /boot directory on the hdb (Redhat 6.2) drive and ran lilo. It was able to reference anything it needed from the hda drive and works great. Not sure if this is the best way to do this but it works. Thanks for the reply. [sig][/sig]
Initially I did set it up with two boot floppies as a last resort but I was able to get this working. I copied the vmlinuz-* from the boot floppy of the Redhat 5.2 system to the /boot directory on the hdb (Redhat 6.2) drive and ran lilo. It was able to reference anything it needed from the hda drive and works great. Not sure if this is the best way to do this but it works. Thanks for the reply. [sig][/sig]
- Status
Similar threads
