Re: Access a SCO 3.0 drive from 5.0.6?
- From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
- Date: Sat, 01 Mar 2008 09:40:55 +0000
Steve M. Fabac, Jr. wrote:
jfranks1970@xxxxxxxxx wrote:I have an old machine with SCO 3.0 and no networking. I need the data
off the IDE drive. I put this drive in a 5.0.6 box that I have and
ran mkdev hd, but it would never show the partitions on the drive (I
have since put the drive back in the old box and it boots fine.).
When the old server boots, it does show /usr mounting as S51K
Left unsaid is what type drive do you have in the 5.0.6 box?
If it is SCSI, then you've a problem as SCO booted from a SCSI drive
will not mount an IDE drive. You can boot from IDE and mount a
SCSI drive as long as the SCSI controller is configured into the
kernel (mkdev hd the first time).
If this is a SCSI vs IDE problem, then you should be able to set
the new box to boot from IDE and boot the old drive in the new
system. Then you can run mkdev hd and configure the 5.0.6 drive
into the 3.0 kernel, reboot and run divvy /dev/hd10 and
name the division for the 5.0.6 as boot, nswap, nroot, and
nu (if you have a u file system) in that order.
Until you name the file systems, you can't mount them. Divvy writes
the name of the file system in /dev on the root file system of the
booted disk where you already have root, rroot, u, and ru.
You can't use the names already used for the 3.0 disk
(root, u, etc.). Note that Open server 3.0 does not have a boot
file system. That disk will start with root and then swap and then
u (if used). mount the 5.0.6 drive and then copy your data.
Caution: Don't run mkdev hd a second time as that is only needed to
run the commands to initialize the hard disk partition and devision
tables. See Bela's post on stamping the drive geometry.
It would be safer to run fdisk -r /dev/rhd10 to view the partition
table. If fdisk shows you reasonable information, then carefully
run divvy /dev/hd10 to see if you can see the division table.
The 3.0 version may choke on the 5.0.6 division table. Even so, it
should be safe to use it to name a target division as naming does
not write to the division table and only creates the nodes in /dev.
Hmmm. You know......
Have you played with virtualization at all? Do you have a Linux box floating around? While the file systems used in the SCO systems I've dealt with aren't really readable by anyone else, it's pretty straightforward to virtualize a licensed SCO installation, and with that running you could blow a disk image from your old drive into a mountable disk image for your virtualization.
If you want to avoid possibly corrupting your antique drive, I'd consider pulling this stunt with a modern RHEL or similar system. I'm doing just this sort of stunt right now, to move good quality server iron into a usable OS and keeping freshly installed copies of the old OS around for access to old software and data formats.
Nico Kadel-Garcia
.
- References:
- Re: Access a SCO 3.0 drive from 5.0.6?
- From: Steve M. Fabac, Jr.
- Re: Access a SCO 3.0 drive from 5.0.6?
- Prev by Date: Re: Access a SCO 3.0 drive from 5.0.6?
- Next by Date: Re: Access a SCO 3.0 drive from 5.0.6?
- Previous by thread: Re: Access a SCO 3.0 drive from 5.0.6?
- Next by thread: Re: Access a SCO 3.0 drive from 5.0.6?
- Index(es):
Relevant Pages
|
