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

Any ideas on how to get this to work? Do I need to mkdev hd first or
can I just access the filesystem directly somehow?

I'm lost.

Thanks!

jf

jfranks1970@gmail.com 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
>
> Any ideas on how to get this to work? Do I need to mkdev hd first or
> can I just access the filesystem directly somehow?
>
> I'm lost.
>
> Thanks!
>
> jf

Does the antique drive have *ANY* networking on its OS? Can you transfer the
data over the network, via rcp or tar over an rlogin or somehting?

On Fri, Feb 29, 2008, jfranks1970@gmail.com 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.).

What is SCO 3.0??? Perhaps you mean Xenix something or other?

If you want to see Xenix drives on OSR 5.0.x, you need to first
run ``mkdev xenix'' to enable Xenix file systems.

>When the old server boots, it does show /usr mounting as S51K
>
>Any ideas on how to get this to work? Do I need to mkdev hd first or
>can I just access the filesystem directly somehow?
>

After running ``mkdev xenix'' with a full rebuild of all devices,
you then have to run ``mkdev hd'' twice, the first time to enable
the additional drive, the second time to run divvy to create
device names for the partitions in the Xenix slice (SCO is more
like FreeBSD in the way it handles disk partitioning than like
Linux).

Bill
--
INTERNET: bill@celestial.com Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676

Windows is a computer virus with a user interface!!

<jfranks1970@gmail.com> 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
>
> Any ideas on how to get this to work? Do I need to mkdev hd first or
> can I just access the filesystem directly somehow?
>
> I'm lost.

Boot the old machine, run:

# dparam /dev/rhd00 `dparam /dev/rhd00`

Shut down, insert drive into OSR506 box, see if it plays any better.

The command "stamps" the drive's partition table with the geometry being
used by the kernel on the old system. Without such a stamp, the kernel
figures out a geometry every time it boots. Many factors go into the
calculation, and the results can come out different on a different
machine. If you stamp the results onto the partition table, the other
machine will no longer have to guess & calculate, it'll just use the
right geometry.

>Bela<

jfranks1970@gmail.com 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.

>
> Any ideas on how to get this to work? Do I need to mkdev hd first or
> can I just access the filesystem directly somehow?
>
> I'm lost.
>
> Thanks!
>
> jf
>
>

--
Steve Fabac
S.M. Fabac & Associates
816/765-1670

Steve M. Fabac, Jr. wrote:
> jfranks1970@gmail.com 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

On Feb 29, 3:52*pm, jfranks1...@gmail.com 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
>
> Any ideas on how to get this to work? *Do I need to mkdev hd first or
> can I just access the filesystem directly somehow?

http://aplawrence.com/SCOFAQ/FAQ_sco...overdrive.html

Uzytkownik <jfranks1970@gmail.com> napisal w wiadomosci
news:7d432477-cef7-42d3-9b02-101e1f2c176b@h25g2000hsf.googlegroups.com...
>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
>
> Any ideas on how to get this to work? Do I need to mkdev hd first or
> can I just access the filesystem directly somehow?
>

I don't know haw was it on SCO 3.0, but on 3.2v4.2 and 5.0.5 system don't
mount partitions - only divisions. And I'm not shure, it is posiible to use
2 disks witch the same names of divisions.?

Jerry

"jerry" wrote:

> Uzytkownik <jfranks1970@gmail.com> napisal w wiadomosci
> news:7d432477-cef7-42d3-9b02-101e1f2c176b@h25g2000hsf.googlegroups.com...
> >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
> >
> > Any ideas on how to get this to work? Do I need to mkdev hd first or
> > can I just access the filesystem directly somehow?
>
> I don't know haw was it on SCO 3.0, but on 3.2v4.2 and 5.0.5 system don't
> mount partitions - only divisions. And I'm not shure, it is posiible to use
> 2 disks witch the same names of divisions.?

Division names are not stored in the division table. Names are
associated with divisions by the existence of device nodes in /dev with
the right major/minor numbers. So if you add an old root drive to an
existing system (no longer the root drive), all the minor numbers will
have changed and its divisions appear "nameless".

Recent versions of `divvy` will show you the embedded filesystem names
(as written by `fsname` and/or `labelit`), and sufficiently new systems
will even have had those stamps put in automatically. Definitely not
3.2v4.2, ODT 3.0 (which was 3.2v4.2-based), nor even OSR505. A drive
from one of those OSes will just appear to have no names, you must
assign new ones in `divvy`.

>Bela<

Thanks for all the replies....trying to answer everyones questions....

"What is SCO 3.0???" - I don't know what it's supposed to be called,
but a 'uname -a' gives 'V/386 mp386 3.0e1U 3 80386' So, maybe it's
something else?

"Run # dparam /dev/...." - When I run this command, I get "dparam:
not found" I did a search of the system for a file called dparam and
found nothing.

"SCSI or IDE" - Both drives are IDE. The old drive AND the new 5.0.6
drive. I put the old drive on the secondary IDE controller as the
Master drive.


Thanks for all the ideas! so far, no joy. I have limited memory of
SCO setups. I "teethed" on SCO back in the early 90's (around the
time this box was built), but I can't remember crap about it! Thanks
again!

jf