How to mount a MO Driver (HP C1716T) device so I can read the info on disks

I am so close to getting this to work I am about to scream! (well, maybe I won't)

I now have the following situation:

I have sucessfully installed SunOS 4.1.1. and have SunView running.

Also I have an ancient driver I found on the internet user group here;
http://tecfa.unige.ch/pub/documentation/technical-hints/Sun-Unix/Install-Tahiti-MO-Drive.text

At long last I was able to get the driver in UUencoded format (finally figured out to send the text to myself in an email, with UUencodeing turned on)

I did finally get the driver files on my SparcStation II; The Lord bless me they worked!!

NOW -- I am stuck again. I cannot seem to reach the author of this famed driver, but I believe he lives in Colorado, and is 45. His name is Timothy Sesow. (rat hole)

I need to figure out the following:

I now have a device created nicely for me, which is so5a, so5b... so on to so5h.

That means there are partitions to these disks or something. I am not sure how I would mount this so I can look at the data on the disks.

REMEMBER: The disks are Magneto-Optical, and have data on them, so I cannot format them, but I may need to create a file system or something so I can read what data ALREADY exists on them. I am really not sure what I will find, but they were used to store the city of UKIAH's city records at one time 8-10 years ago.

I do know that they were mounted in a similar fasion to how I am trying to mount them today.

Other clues: I have already tried the following:

# mount /dev/so5a /modrive

It fails on this error:

mount: /dev/so5a on /modrive: No such device or address
mount: giving up on:
      /modrive

Othere clues:

I tried it on the rest of  a - h (so5a, so5b, etc...) and it gives the same error.
There are devices in the /dev directory. You get the following if you issue: # ls so*

s05  so5a   so5b  so5c  so5d  so5e  so5f  so5g  so5h


Above all, I am on a deadline. I need resolution to this ASAP. I am already 3 mos into this project and I need to bring it to a close this week. (by months end)

If you have any things for me to try, by all means PLEASE do suggest it. (or ask me for more details about the situation)

Thanks!

splendidsysAsked:
Who is Participating?
 
moduloConnect With a Mentor Commented:
PAQed - no points refunded (of 500)

modulo
Community Support Moderator
0
 
shivsaCommented:

if the driver does not provide standard functionality with mount.
I think u have to use mo_mount or something like that. read this document, in the end there are these utilities.

http://www.sunmanagers.org/archives/1994/0038.html
0
 
shivsaCommented:
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Hanno P.S.IT Consultant and Infrastructure ArchitectCommented:
usually with SunOS 4.x the device ending with "c" stands for the whole "disk". The others are the different "slices" or "partitions", numbers from "a" to "h"
0
 
gheistCommented:
and on removable media you need to mount so0c, not so0a ...
and never partition and ignore anything it says about labeling media...
anyway first check if you can dd if=/dev/so0c of=/dev/null count=1 (ie if device is ok)
0
 
splendidsysAuthor Commented:
Okay to kill/retire this question. Solution was to send M.O. Disks to Data-RECOVERY site in OKLAHOMA. Data was recovered and task completed.
0
 
gheistCommented:
"If you have any things for me to try"

there are no way for you to drop it. Everyone answered.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.