Very Computer

We have 2 disks that original was running in a SCO ODT 3 system. Now
we need some data from these disks and want to mount them in a SCO ODT
5 system.

What is the safest, best and easiest way to do that so its sure the
data on the disks are not corrupted ?

Thanks in advance

 -- Eigil Krogh Sorensen

--------------------------------------------------------------------
VKI                                    Phone: +45 86 20 20 00
Science Park Aarhus             Direct phone: +45 86 20 20 11 - 2114
Gustav Wieds Vej 10                      Fax: +45 86 19 75 11
8000  Aarhus C                         Telex: 37874 VKICPH

--------------------------------------------------------------------

--

Kirk J. Farquhar
Infinity Systems Inc.           905-946-0060
Markham, Ontario, Canada

 >
 >We have 2 disks that original was running in a SCO ODT 3 system. Now
 >we need some data from these disks and want to mount them in a SCO ODT
 >5 system.
 >
 >What is the safest, best and easiest way to do that so its sure the
 >data on the disks are not corrupted ?
 >
 >Thanks in advance
 >
 > -- Eigil Krogh Sorensen
 >

Hi !

Well, I didn't exactly crossed this problem but I was
able to mount OS5 primary EIDE HDs on another
OS5 powered machine equipped with a primary EIDE
HD (this method *should* work even with ODT 3.0
filesystems).

Please, take a look at the hd(HW) man page; you'll
find a table which depicts the 'hard disk minor device
bit representation'. You'll have to combine the bit
pattern which gives you the exact representation of the
disk you want to mount.

As an example, let's suppose you configure your ODT 3.0
disk as the secondary EIDE disk (by jumpering accordingly
to your HD manufacturer). In order to get the minor device
number you'll have to create to get it recognized by SCO OS5,
you perform the following calculations:

   --------------------------------------------
            Bits
   7  6  5  4  3  2  1  0   Description
   --------------------------------------------
   X  X  -  -  -  -  -  -   disk # (0-3)
   -  -  X  X  X  -  -  -   partition # (1-4)
   -  -  -  -  -  X  X  X   division # (0-6)
   -  -  X  X  X  1  1  1   whole partition
   -  -  0  0  0  0  0  0   whole physical disk
   -  -  1  0  1  -  -  -   active partition
   -  -  1  1  0  -  -  -   DOS partition
   -  -  1  1  0  X  X  X   DOS drive (C-J)

The bit pattern should be:

0 1 1 0 1 0 0 0

0 1 = Disk number 1 (starting from 0)
1 0 1 = Active partition
0 0 0 = First division

Which gives 104 (dec) (giving the fact that you want to
mount the active partition/first division - please change the bit
pattern above accordingly).

So, cd to the /dev directory and use the mknod
command to create the following node:

mknod disk2 b 1 104

Next, phisically plug the ODT 3.0 HD, configure it
and reboot the system; you should now be able to
access the requested partition by using the above
node (e.g., mount /dev/disk2 /mnt).

I'm under the impression that the above stuff (which comes
directly from my memory so please use it with care) is not
100% correct (I bet I've missed something which presently
I cannot remember) but I hope you'll get some points from
which to start.

Hope this helps (anyway ;-) !

Best,
Roberto

--
---------------------------------------------------------------------          

Strhold Sistemi EDP                                                            
Reggio Emilia      ITALY                                                        
---------------------------------------------------------------------          
"Has anybody seen an aircraft carrier around ?"                                
        (Pete "Maverick" Mitchell - Top Gun)                                    
---------------------------------------------------------------------

If the disks are ST506/ESDI/IDE, you only run one pass of `mkdev hd`,
and you can access the disks immediately without relinking/rebooting.

You may run into an issue with disk geometries.  Solving such issues
will be much easier if you already know what geometries the disks were
using under the previous OS: which you can probably learn from the file
/usr/adm/messages on the previous root filesystem.

Quote:>Bela<