Having trouble mount SCO UNIX partition on 2nd drive

You don't want to "create" slices on the drive since that will wipe out the data, you just want them to have names (which it looks like you did).  I assume the start block of Division1 is a typo - it overlaps Division0.

What /dev/hdaX nodes got created?  You would want to divvy the proper one - it won't hurt to look at the other nodes.  hd1a sounds like the first partition on the second disk - is there a /dev/hd1c ?

That may not be it at all since the divvy table you posted looks like an SCO table:
D0=boot
D1=swap
D2=root
D6=recover

But, the slice for the whole disk is way wrong - should be from 0 to 12284936
D6 would be that 12284927  to  12284936 if it were a recover slice.

Oops there was a typo, Here is what the divvy table reall looks like.


Name          Type          New FS          #     First Block          Last Block

Division0     Non FS         no             0                 0         49999
Division1     Non FS         no             1             5000         149999
Division2     Non FS         no             2            15000       12284926
Division3     NOT USED       no             3                    -          
Division4     NOT USED       no             4                    -          
Division5     NOT USED       no             5                    -          
              NON FS         no             6       12284927     -   12284936
hd1a          WHOLE DISK     no             7       12284927     -   12284936


Here is fdisk:

Partition      Status           Type         Start          End         Size

2              Inactive         DOS ( 32)    585358     1240559       655202
3              Active           UNIX         195120      585357       390239
4              Inactive         OS/2              1      195119       195119


devices:

/dev/hd10
/dev/hd11
/dev/hd12
/dev/hd13
/dev/hd14
/dev/hd1a
/dev/hd1d

Also, the last two lines from hwconfig -h:

disk     0x1f0-0x1f7     14   -     type=W0 unit=0 cyls=4865 hd=255 secs=63
disk     0x1f0-0x1f7     14   -     type=W0 unit=1 cyls=4865 hd=255 secs=63

Should the address be the same for both drives?

If I'm looking at this right; you have two 40 Gig disks - the primary is booting SCO and the secondary has three partitions, one of which is SCO - and you need data from that partition (with multiple filesystems in the partition).  The address should be the same since it's a single IDE controller with a primary (unit 0) and secondary (unit 1) disk.  Looks like the two drive are identical?

Questions and observations:

Is the primary drive also partitioned with three OS's (if so a divvy of it may be helpful)?  I've never run one with multiple OS's - only the whole disk for SCO.

Is the secondary bootable if you set it as a primary disk all by itself?

That "whole disk" is still all wrong - should start at 0, also div0 and div1 overlap.  If the partition is not bootable (above question) then maybe the OS is just plain screwed up on the secondary and is reporting odd things.  The  12 Gig size of the hd1a seems to jive with the about 12 Gig size of the SCO partition so it looks like you have the partition you want - it's just not in good health.

You could try to do "divvy /dev/hd1X" for all of the above devices to see if anything makes more sense.

You might want to get a disk image before going too far.  ghost or some such would work.

I think this would be really easy if the whole disk were SCO - the multiple partitions strike me as the possible issue.  

The drive with 3 different OS partitions is used to control an industrial lathe.  Manufacturer of lathe provided this setup.  Drive was originally setup to boot to OS/2 partition and, when booted, moves directly to a multiboot partitioning/menu program.  You have the choice of booting to Windows or SCO.  You may also format, resize or drop partitions from that program.  The SCO partition holds a complete catalog of the lathe patterns.  There is no backup.

Even though the other OS's operate properly, the SCO partition appears to have problems with indexing and I have not had experience mounting a drive with this setup.  All help is appreciated