StoreEver Tape Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

Ultrium-3 autoloader has NO_HW listed for device state

mailtest
Occasional Visitor

Ultrium-3 autoloader has NO_HW listed for device state

HI
I'm experiencing some problems lately with an HP StorageWorks Ultrium-3 autoloader 1/8 tape device on an HP-UX 11.31 PA-RISC rxxxx based system..the tape device's state is showing `NO_HW`..

ioscan -P health -H shows the device online..no problems reported..
# ioscan -P health -H 0/1/1/1.0x5.0x1000000000000
Class I H/W Path health
===============================
lunpath 4 0/1/1/1.0x5.0x1000000000000 online

ioscan -fn:
tape 0 0/1/1/1.5.0 stape NO_HW DEVICE HP Ultr
ium 3-SCSI
/dev/rmt/0m /dev/rmt/c3t5d0BEST
/dev/rmt/0mb /dev/rmt/c3t5d0BESTb
/dev/rmt/0mn /dev/rmt/c3t5d0BESTn
/dev/rmt/0mnb /dev/rmt/c3t5d0BESTnb
autoch 0 0/1/1/1.5.1 schgr NO_HW DEVICE HP 1x8
autoloader
/dev/rac/c3t5d1



the following are the most recent entries in the syslog file:

Aug 17 09:36:43 cshp1 vmunix:
Aug 17 09:36:43 cshp1 vmunix: C8xx: c8xx_isrUDC: Unexpected Disconnect -- lbolt:
8566518, dev: 0xcb034004 (c3t4d0), io_id: 0x1566bd
Aug 17 09:36:44 cshp1 vmunix: C8xx: isrEscape Controller at 0/1/1/1.
Aug 17 09:36:44 cshp1 vmunix: C8xx: lsp is NULL on Selection Time-out -- lbolt:
8566547, bus: 3
Aug 17 09:36:44 cshp1 vmunix: lbp->state: 30008
Aug 17 09:36:44 cshp1 vmunix: lbp->offset: ffffffff
Aug 17 09:36:44 cshp1 vmunix:
Aug 17 09:36:44 cshp1 vmunix: lbp->nominalOffset: 358
Aug 17 09:36:44 cshp1 vmunix: lbp->Cmdindex: 1d
Aug 17 09:36:44 cshp1 vmunix: lbp->siop_Cmdindex: 1c
Aug 17 09:36:44 cshp1 vmunix: lbp->last_nexus_index: 1d
Aug 17 09:36:44 cshp1 vmunix: lbp->nexus_index: 1e
Aug 17 09:36:44 cshp1 vmunix: uCmdSent: 1d00dd00 uNexus_offset: 4005d6
78
Aug 17 09:36:44 cshp1 vmunix: last lbp->puStatus [00000000c714d658]:
Aug 17 09:36:44 cshp1 vmunix: 0003007d 0003007d 0003007d 0003007d
Aug 17 09:36:44 cshp1 vmunix: next lbp->puStatus [00000000c714d668]:
Aug 17 09:36:44 cshp1 vmunix: From most recent interrupt:
Aug 17 09:36:44 cshp1 vmunix: ISTAT: 02, SIST0: 00, SIST1: 04, DSTAT:
00, DSPS: 00000000
Aug 17 09:36:44 cshp1 vmunix: lsp: 0x0000000000000000
Aug 17 09:36:44 cshp1 vmunix: 0003007d 0003007d 0003007d 0003007d
Aug 17 09:36:44 cshp1 vmunix: DSAtbl->host_iocb_index: 1d
Aug 17 09:36:44 cshp1 vmunix: DSAtbl->host_iocb_addr: 4005df40
Aug 17 09:36:44 cshp1 vmunix: scratch_lsp: 0x0000000000000000
Aug 17 09:36:44 cshp1 vmunix: c8xx_iocb [ffffffff90010b00]:
Aug 17 09:36:44 cshp1 vmunix: 1d00df40 ff005400 40059000 9f043e80
Aug 17 09:36:44 cshp1 vmunix: 00000009 4005df20 00000006 4005df2c
Aug 17 09:36:44 cshp1 vmunix: Pre-DSP script dump [ffffffff90010220]:
Aug 17 09:36:44 cshp1 vmunix: 74358000 00000000 80840000 00000660
Aug 17 09:36:44 cshp1 vmunix: e1640004 90010b08 7a5c0100 00000000
Aug 17 09:36:44 cshp1 vmunix: Script dump [ffffffff90010240]:
Aug 17 09:36:44 cshp1 vmunix: 1e000000 00000010 878b0000 000002a8
Aug 17 09:36:44 cshp1 vmunix: 1a000000 00000018 e27c0004 4005e000
Aug 17 09:36:44 cshp1 vmunix: NCR chip register dump for: 0x400200a
Aug 17 09:36:44 cshp1 vmunix: 00: SCNTL3: 9f SCNTL2: 80 SCNTL1:
00 SCNTL0: da
Aug 17 09:36:44 cshp1 vmunix: 04: GPREG: 0f SDID: 04 SXFER:
3e SCID: 47
Aug 17 09:36:44 cshp1 vmunix: 08: SBCL: 00 SSID: 85 SOCL:
00 SFBR: 00
Aug 17 09:36:44 cshp1 vmunix: 0c: SSTAT2: 0a SSTAT1: 0e SSTAT0:
00 DSTAT: 00
Aug 17 09:36:44 cshp1 vmunix: 10: DSA: 90010b00
Aug 17 09:36:44 cshp1 vmunix: 14: MBOX1: 00 MBOX0: 00 ISTAT1:
00 ISTAT: 02
Aug 17 09:36:44 cshp1 vmunix: 1c: TEMP: 90010350
Aug 17 09:36:44 cshp1 vmunix: 24: DCMDDBC: 1e000000
Aug 17 09:36:44 cshp1 vmunix: 28: DNAD: 4005df30
Aug 17 09:36:44 cshp1 vmunix: 2c: DSP: 90010248
Aug 17 09:36:44 cshp1 vmunix: 30: DSPS: 4005df20
Aug 17 09:36:44 cshp1 vmunix: 34: SCRATCHA: ff075400
Aug 17 09:36:44 cshp1 vmunix: 38: DCNTL: a1 DWT: 00 DIEN:
7f DMODE: 4c
Aug 17 09:36:44 cshp1 vmunix: 3c: ADDER: 9006e168
Aug 17 09:36:44 cshp1 vmunix: 40: SIST1: 00 SIST0: 04 SIEN1:
97 SIEN0: 8f
Aug 17 09:36:44 cshp1 vmunix: 44: GPCNTL: 2f MACNTL: 00 SWIDE:
00 SLPAR: 00
Aug 17 09:36:44 cshp1 vmunix: 48: RESPID1: 00 RESPID0: 80 STIME1:
10 STIME0: ec
Aug 17 09:36:44 cshp1 vmunix: 4c: STEST3: 80 STEST2: 00 STEST1:
0c STEST0: 76
Aug 17 09:36:44 cshp1 vmunix: 50: RESV50: 00 RESV51: c0 SIDL1:
00 SIDL0: 00
Aug 17 09:36:44 cshp1 vmunix: 54: CCNTL1: 01 CCNTL0: 01 SODL1:
00 SODL0: 7d
Aug 17 09:36:44 cshp1 vmunix: 58: RESV58: 00 RESV59: 00 SBDL1:
00 SBDL0: 00
Aug 17 09:36:44 cshp1 vmunix: 5c: SCRATCHB: 00040001
Aug 17 09:36:44 cshp1 vmunix: 60: SCRATCHC: 00000027
Aug 17 09:36:44 cshp1 vmunix: 64: SCRATCHD: 40059000
Aug 17 09:36:44 cshp1 vmunix: 68: SCRATCHE: 90010dfc
Aug 17 09:36:44 cshp1 vmunix: 6c: SCRATCHF: 40058500
Aug 17 09:36:44 cshp1 vmunix: 70: SCRATCHG: 9f043e80
Aug 17 09:36:44 cshp1 vmunix: 74: SCRATCHH: 4005d678
Aug 17 09:36:44 cshp1 vmunix: 78: SCRATCHI: 0a019f1f
Aug 17 09:36:44 cshp1 vmunix: 7c: SCRATCHJ: 1d00df40
Aug 17 09:36:44 cshp1 vmunix: bc: SCNTL4: 80
Aug 17 09:36:44 cshp1 vmunix:
Aug 17 09:36:44 cshp1 vmunix: C8xx: Resetting SCSI -- lbolt: 8566647, bus: 3 pat
h: 0/1/1/1
Aug 17 09:36:44 cshp1 vmunix: C8xx: Reset detected -- lbolt: 8566647, bus: 3 pat
h: 0/1/1/1
Aug 17 09:36:44 cshp1 vmunix:
#

before I contact HP support for service on this tape device I wanted to see if there was something that can be done manually to reset the device or if the above syslog entry shows the scsi controller ( probably on the tape device) is problematic meaning a support call is necessary.

Thanks
Rob
4 REPLIES
Torsten.
Acclaimed Contributor

Re: Ultrium-3 autoloader has NO_HW listed for device state

NO_HW means it is no longer there.

Try to power cycle the loader, check cable, terminator etc. ...

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
mailtest
Occasional Visitor

Re: Ultrium-3 autoloader has NO_HW listed for device state

Thanks
I've tried all of that, even got a new tape device from HP, still seeing 'no hw'..changed cables even...

I think I need to disable/enable the new device with scsimgr ?
Torsten.
Acclaimed Contributor

Re: Ultrium-3 autoloader has NO_HW listed for device state

Slowly ... what is changed now?

Became the loader ready?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Michael Leu
Honored Contributor

Re: Ultrium-3 autoloader has NO_HW listed for device state

Just a guess, if the serial number changed you need to do the 'scsimgr replace_wwwid' dance.

Check with
scsimgr get_attr -H -a serial_number
if the S/N ist correct and grep syslog for entries with
vmunix: Evpd inquiry page 83h/80h failed