Adding a drive 1

[BITSys]

I have followed SCO's technical article 104863 for adding a SCSI disk that has data on it that I do not want destroyed. It seems to have been successful except that I cannot access the data. This drive was the main drive to another system that became unstable (to say the least) so it had boot, swap, root and recover divisions on it.

When the system attempt to mount the drive it reports that it is unable to fsstat it, says it is out of space, runs fsck on the drive and then claims to have mounted it. I know the data is still on the drive, I can put it back in its original system and boot from it but it cannot run in anything other than maintenance mode. That was "part" of the problem that started this mess.

However, when I enter a command like "ls -l /x/u/ssi6" (where /x is the mount point and /u/ssi6 is a folder that contains data) I'm either told that it does not exist or I'm shown the contents on the corresponding drive in the system I'm trying to use to access this drive. Any help would be appreciated more than I can say.

 

[PHV]

The disk hasn't an u filesystem ?

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

 

[BITSys]

No, in this case the /u is just a folder not a file system.

 

[Annihilannic]

Can you see the files under /u on the original system when it's in maintenance mode? Is it possible for you to show us the output of df -kv while in maintenance mode (might involve some old-fashioned writing-down )?

Annihilannic.

 

[edfair]

Maybe I don't understand the problem you are dealing with or the solution but here is how I interpret what you are trying to do. And my experience ends with OS5.0.5 if that makes a difference.

You don't mount the hard drive. You mount filesystems. In your case mkdev hd would create /dev/hd10 through /dev/hd1a, one point there for each division that it identifies plus all. Rebooting makes it accessible.

Then you would run divvy on one of those points which brings up the divvy table in the kernel with blank names but filesystem types and beginning and ending blocks.
You enter the filesystem names you wish to use and apply the table. Names will need to be different than they were, you'll already have boot, root, and recover in the system. I use boot1, root1, and recover1 in those I have mounted.

Once you have the divisions identified you are able to run fsck on them.

Make attachment points, I use boot1 and root1 so there is clear indication of where I am when I question it.

Then a matter of mount /dev/boot1 /boot1 for temporary attachment or mkdev fs and set it up permanently.

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

 

[BITSys]

This problem has been solved. It was user error on my part. A second hard drive is hd10 not hd01. I guess those are the major and minor numbers I've seen errors about but not understood. I was essentially creating a second map to the primary hard drive and not accessing the second hard drive at all. If it helps anyone else hd00 through hd09 are the primary drive. The second drive is hd10 through hd19. The first digit is the major and the second is the minor. Oh well, live and learn.