topic Re: Connecting MO unit in Operating System - HP-UX

Connecting MO unit

romano r — Fri, 23 Aug 2002 06:33:01 GMT

Hello,
I'm trying to connect a MO unit (Maxoptix T6-5200) to a 715 box. I find the same problem even in HP-UX10.20 than 11i: running diskinfo, mediainit,... the result is: "can't access /dev/dsk/c.... I/O error". The jumper settings seems ok (as suggested by the manufacturer).

thanx
Romano

Re: Connecting MO unit

Paula J Frazer-Campbell — Fri, 23 Aug 2002 06:43:02 GMT

Hi

If iocan can "See" the disk then most likly it is the jumper settings.

Might be trial and error, I would start with default first.

Paula

Re: Connecting MO unit

Stefan Schulz — Fri, 23 Aug 2002 09:01:03 GMT

Hi Romano,

if you get an I/O error on a removable disc it's most likely the writeprotect setting.

Check if your MO which is in the drive is set write protected.

You could also try to mount it read only. This should work. But it sounds like you would like to write to them.

Hope this helps

Regards Stefan

Re: Connecting MO unit

Frank Slootweg — Fri, 23 Aug 2002 09:19:09 GMT

If you still need help, then please post (the hardware address of the MO unit) and the output from:

ioscan -fn -H ....
diskinfo /dev/rdsk/...

"mediainit": Don't use that until you have proven to yourself that it is needed. See the thread "How/when (not) to use mediainit?"
(<>). While that does not specifically cover MO disks, it is still applicable, *unless* you have a MO disk which you *know* (not think) is not-LLF-ed.

Re: Connecting MO unit

romano r — Fri, 23 Aug 2002 10:23:33 GMT

HI Frank here the outputs:
#ioscan -fn -H 2/0/1.3.0
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 3 2/0/1.3.0 sdisk CLAIMED DEVICE MaxoptixT6-5200
/dev/dsk/c0t3d0 /dev/rdsk/c0t3d0
#diskinfo /dev/rdsk/c0t3d0
SCSI describe of /dev/rdsk/c0t3d0:
vendor: Maxoptix
product id: T6-5200
type: direct access
size: 0 Kbytes
bytes per sector: 0
#mount /dev/dsk/c0t3d0 /mo_unit
/dev/dsk/c0t3d0: Device busy
#diskinfo /dev/dsk/c0t3d0
diskinfo: can't open /dev/dsk/c0t3d0: I/O error

HI Stefan,
I've to write on it, anyway even setting write protection nothing change.

Hi Paula,
I'm gonna play with jumpers...

thank you
Romano

Re: Connecting MO unit

Vincent Farrugia — Fri, 23 Aug 2002 10:29:55 GMT

Hello,

Both diskinfo and mediainit require the use of the RAW device file (/dev/rdsk/c0t3d0). That is why it is giving you errors when you try to run them using the block device file (/dev/dsk/c0t3d0).

See man diskinfo and man mediainit for details.

HTH,
Vince

Re: Connecting MO unit

Frank Slootweg — Fri, 23 Aug 2002 10:42:44 GMT

Because you get *some* result from diskinfo(1M), you can assume that the driver, interface, cable, controller are OK. (The diskinfo information comes from the controller in the MO drive.)

Because diskinfo says
> size: 0 Kbytes
> bytes per sector: 0
there is some problem with the *media*.

What do you know about the media? Is it hardware compatible with *this* drive? Is it formatted? If not, can you format it elsewhere (As I said, please do not use mediainit(1M), at least not yet.).

Re: Connecting MO unit

Ulrich Deiters — Mon, 26 Aug 2002 07:52:16 GMT

If your MO was turned off at boot time, do an "ioscan", because HP-UX will otherwise not be able to see the device. If you use a fresh MO disk, create a file system on the raw device first:
/usr/sbin/newfs -F hfs -L /dev/rdsk/cXtYd0 .

Re: Connecting MO unit

Michael Lampi — Mon, 26 Aug 2002 23:58:53 GMT

I'd try mediainit using the raw device file (/dev/rdsk/c...). The media is probably not formatted.

Otherwise, since you can obtain status information via diskinfo, I agree that the SCSI cabling is probably just fine.