How to configure an external hard drive

[logixhel]

OK, I'm a novice at this too - sorry. I have a system that's lost all it's data - the backups are no good either. My only chance is a data backup that was taken to an external/removeable hard drive on a nightly basis.
I know I need to mount this, but when I go into SCOADMIN I'm only given the floppy or cd drive as an option.
What do I need to do ?
I ran an hwconfig and output it to a file without the hard drive connected and then ran it again after a shutdown and reboot with the hard drive connected and hoped the diff would show me what I needed to know, but it didn't.
I think I'm way off track now ...........
Sorry, but I'm really stuffed now, any help would be great - thanks

 

[PHV]

external/removeable hard drive
An USB drive ?
Anyway, which version of SCO unix ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[logixhel]

This is a SCSI external drive,not a USB drive
SCO Unix 5

 

[edfair]

Have there been hardware changes made since the backup?

How about posting the last boot information in /usr/adm/messages so we can get an idea of what you are dealing with. this assuming you have that file and can access it.

Do you know how the backup was accomplished?



Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[logixhel]

OK I'll start again, as I appear to have lost people.

I have a server that has had a new internal hard drive installed and SCO Unix re-installed as the original internal drive crashed. As such the information relating to the removable SCSI hard drive on the system and it's partitions have been lost (by re-installing unix).

How do I get the system to see the removeable hard drive with data on it ?

 

[PHV]

mkdev hd

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[motoslide]

You will need to provide "mkdev hd" with some information, and some caution. The first time you run that command, you will need to give it the SCSI Driver name, Adapter #, Bus #, SCSI ID, and LUN. The first pass of that command will add support for the device in the kernel. This requires a reboot before it will be available.
Then you run the command a second time, furnishing the same information. It will know that the kernel is already updated, and proceed to the process where you can create the partition and divvy entries. This is where you must be very careful. You want to preserve the existing Partition table. You also don't want to change things in "Divvy", except to create names for the filesystems (if they are blank). Make sure "New FS" is set to "NO". Make notes of the filesystem names, which you will use later to mount those volume.

If the filesystem name is "d1150" (often the default), you can mount it like so:
# mount/dev/d1150 /usr2 (assuming /usr2 exists)

For more information, seek out this article on SCO's knowledge base:

http://www.sco.com/ta/104863

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[edfair]

As a precaution I check the divvy table independently before I run the second mkdev.

Look at /dev for nodes HD1* to verify that the drive added correctly. Should also show in tail /usr/adm/messages as the results of the system coming up with it enabled in the kernel. You can "divvy /dev/hd10" (if that is the drive) and see the names associated with the divisions on that drive. You can change them and install them using divvy or at the 2nd invocation of mkdev HD.

You can mount the drive as soon as you have the kernel link and the division names in /dev but probably need to create the mount points as the standard install only has one intended for use. From the root of the drive it is mkdir and the name you want to give the mount point.

You have a choice of mounting from command line or scoadmin. Using scoadmin creates a lost+found directory and gives a couple of other things.

I normally change the division names on my hard drives to match the name of the mount point. Saves confusion down the line.

At the command line it is mount /dev/divvyname /mountpoint

And to take it away it is umount /mountpoint


Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[edfair]

This is a backup drive you are mounting, so it needs to go where the backup drive went, not where your data went.

Then you create your data location and restore from the backup location.

You may find that the data should be reinstalled to a separate division on your root drive. Some are set up like that. If that is what you need, you would reinstall it interactively to create the division.

Ed Fair
Give the wrong symptoms, get the wrong solutions.