OK...this one is weird too (I’ve had a lot of these types of problems this week.)
I have a functional Linux 2.4-20 box. life is good with it. I have taken a drive, which was the boot and OS drive from another box, and want to add it to this functional box as a second disk, so I can read the data. I MUST KEEP THE DATA on the new “second” drive, so I can’t reformat it.
Here’s what’s weird...when I put the “second” disk into the existing functional machine...NO MATTER HOW I SET IT UP the system will use the original functional machine’s boot loader...BUT THEN IT SEEMS TO TRY AND USE THE SECOND DISKS “OS” files.
/dev/hda1 = boot partition
/dev/hda2 = swap
/dev/hda3 = OS files
/dev/hdb1 = boot partition from other machine
/dev/hdb2 = swap from other machine
/dev/hdb5 = OS file from other machine (not, it is partition FIVE not three.)
When I boot, it uses the correct boot loader from “/dev/hda1” BUT THEN seems to try and use the OS files from “/dev/hdb5”.
Is there an ID on the second drive which is causing the boot loader to think it is the disk with the OS files on it?
The system is Intel and DOES use ATAPI connectors. It doesn’t seem to matter how I add the second disk physically to the machine (I.E. on the second connector to the first cable, as the only drive on the second cable, as DS master, as DS slave, as cable select and every combination of the pervious)