Attention all Unix Lovers - Here's your chance to shine!

Vaity | Jolly Green

[Jolly Green]

I'm embarrassed to admit that I have forgotten most of what I knew about Unix, so maybe some of you guys can help.

I have a client running a manufacturing process with SCO Unix. (Don't ask why.) They had a hard disk crash on the primary disk last week. They have installed the new disk and reinstalled SCO and their application. Some critical data still exists on the secondary drive. They need to mount the drive so they can access the data. I recall that there is a Unix "mount" command, but I don't recall the syntax or even if that is all that is required. (I recall that there is a "man" system that should help me, but I don't have access to that.)

[Jolly Green]

Can a FReeper help me out?

[gov_bean_ counter]

Sorry dude. All I know about unix is VI editor. And I may not be saying that correctly.

[AppyPappy]

man mount

NAME
     mount, umount - mount or unmount  file  systems  and  remote
     resources

SYNOPSIS
     mount  [-p  | -v ]

     mount    [   -F FSType   ]    [   generic_options    ]     [
     -o specific_options ]  [ -O ] special  | mount_point

     mount    [   -F FSType   ]    [   generic_options    ]     [
     -o specific_options ]  [ -O ] special mount_point

     mount -a  [ -F FSType ]  [ -V  ]   [  current_options  ]   [
     -o specific_options ]  [ mount_point ... ]

     umount   [  -V  ]   [  -o specific_options  ]   special    |
     mount_point

     umount -a  [ -V ]  [ -o specific_options  ]   [  mount_point
     ... ]

DESCRIPTION
     mount  attaches a file system to the file  system  hierarchy
     at  the   mount_point, which is the pathname of a directory.
     If  mount_point has any contents prior to the  mount  opera-
     tion, these are hidden until the file system is unmounted.

     umount  unmounts a currently mounted file system, which  may
     be  specified  either  as a  mount_point or as  special, the
     device on which the file system resides.

     mount  and  umount  maintain a table of mounted file systems
     in   /etc/mnttab,  which  is  described in  mnttab(4). mount
     adds an entry to the mount table; umount  removes  an  entry
     from the table.

[Jolly Green]

What a guy!!! Thanks.

[JRandomFreeper]

Is that SCO unix? mntab? It's a different flavor from linux and Solaris and SunOS. Hmmmm.

[Exnihilo]

that stuff looks like chinese written by a drunk chimp high on prozac

HAHAHAHAHA!!!! That was funny!! As a software engineer I can attest to the fact that "man pages" are all like that. Written by someone who is obviously very skilled with computers, but flunked out of 8th grade english.

[AmericaUnited]

Is it SCO Unixware or OpenServer ? Plus you have to know what type of filesystem was on the other drive.

Assuming it was Uniware, do the following:

# prtvtoc /dev/rdsk/c0b0t0d1s0

The "prtvtoc" command will show your the layout of the drive, how many slices. We'll assume just two, with the scond slice being the user's file system.

Then try mounting the filesystem by using the following mount commands for the different possible filesystem types if your don't know. If the magic number in file system header does not match the filesystem type specified, it will complain and just not mount. Try the next one.

mount -F vxfs /dev/dsk/c0b0t0d1s1 /"yourdirectory"

mount -F s5 /dev/dsk/c0b0t0d1s1 /"yourdirectory"

mount -F ufs /dev/dsk/c0b0t0d1s1 /"yourdirectory"

[j_tull]

assuming a reconfiguration boot has been done, then look at /dev/dsk to see what's out there. mount each entry individually [you can eliminate the entries of the root disk from this rotation] with(mount /dev/dsk/c(x)t(x)d(x)s(x) /mnt (or other mount point) then ls /mnt to find your data

[j_tull]

btw, no backup tapes? if you could restore /etc/vfstab, you data disk should would mount at boot time

[zeugma]

My favorite line from MAN pages is...

You can tune a filesystem, but you can't tuna fish.

[eggman]

If you did a reinstall you will need to recreate the device files for the second drive. What you need to do is run mkdev hd defining the device (SCSII/IDE) parameters, reboot, run mkdev hd again to run the fdisk and divvy to define the partitions and filesystems on the disk. The divvy portion of mkdev should show the existing filesystems on the drive. You will just need to enter the name(s) for the partitions which will recreate the /dev links that can be mounted. Just dont let it recreate the filesystems as new. That would wipe out your data. If they are raw partitions that should not be a problem.

Check out AP Lawrence for some additional details and all your other SCO Unix questions.

[Jolly Green]

Awesome, you guys. This should do the trick.

[AmericaUnited]

Just a quick note, #13 applies to SCO Openserver, not SCO Unixware.

[Bush2000]

Why in God's name would you want to "man mount"? It sounds like an abomination...

[AppyPappy]

The same reason someone would want to "chkdsk".

[ArrogantBustard]

I bet you've fdisked many times, in public no less.

[Bush2000]

I bet you've fdisked many times, in public no less.

Nah. I only fdisk in privat

[Bush2000]

The same reason someone would want to "chkdsk".

I don't know, Appy ... "man mount" sounds a bit more gay than "chkdsk" ...