I have a customer that had their SCO system go down. They are getting HD errors after boot: I have a working SCO dev system here but whenever I plug the HD in (IDE) it tried to boot from it instead of the scsi disks. I've looked in the bios and there seems to be no way to force the system to boot from scsi first. I do have access to SCO boot media.
They have no backups (of course) and need the data. This is the first time I've added a disk and had to preserve the layout. I've seen a few threads on here about loading a SCSI disk into a system but since this is so critical I wanted to get some opinions on the best and safest way to proceed.
I think these are my options:
1) use boot media to break out into a shell and try to mount the root drive from the IDE (damaged) drive and the root drive from the SCSI (working) and then copy the two needed directories from the IDE to the SCSI if possible.
2) Put together another SCO system with IDE drives and put the damaged IDE drive on the secondary channel so it will not try to boot. Once booted I found these directions for adding a drive and keeping the layout
but I'd like to ask if someone has done this before. I'd hate to make a mistake on the divvy table and loose their data.