We got Solaris 7 with NB_34_1 patch level.
We recently got upgraded DLT7000 tape drives in
our STK L700 to rev level 106 (276A) and start getting problems.
I've got 2 tape downed tape drives with the error messages:
Jan 1 20:32:58 uback-ap9-1 unix: WARNING: /pci@1f,4000/fibre-channel@2/st@1,0
(st14):
Jan 1 20:32:58 uback-ap9-1 Error for Command: write
Error Level: Fatal
Jan 1 20:32:58 uback-ap9-1 unix: Requested Block: 385
Error Block: 385
Jan 1 20:32:58 uback-ap9-1 Error for Command: write
Error Level: Fatal
Jan 1 20:32:58 uback-ap9-1 unix: Vendor: QUANTUM
Serial Number: qe 5 i M
Jan 1 20:32:58 uback-ap9-1 unix: Sense Key: Hardware Error
Jan 1 20:32:58 uback-ap9-1 unix: Requested Block: 385
Error Block: 385
Jan 1 20:32:58 uback-ap9-1 unix: ASC: 0x15 (<vendor unique code 0x15>),
ASCQ: 0x1, FRU: 0x0
Jan 1 20:32:58 uback-ap9-1 unix: Vendor: QUANTUM
Serial Number: qe 5 i M
Jan 1 20:32:58 uback-ap9-1 unix: Sense Key: Hardware Error
Jan 1 20:32:58 uback-ap9-1 unix: ASC: 0x15 (<vendor unique code 0x15>),
ASCQ: 0x1, FRU: 0x0
Jan 1 20:34:39 uback-ap9-1 tldcd[3721]: Processing UNMOUNT, TLD(6) drive 6,
slot 397, barcode 003177 , vsn
003177
Jan 1 20:34:39 uback-ap9-1 tldcd[3289]: TLD(6) opening robotic path
/dev/sg/c2t1l2
Jan 1 20:34:39 uback-ap9-1 tldcd[3289]: TLD(6) initiating MOVE_MEDIUM from
addr 505 to addr 1396
Jan 1 20:34:39 uback-ap9-1 tldcd[3289]: TLD(6) key = 0x0, asc = 0x0, ascq =
0x0, NO ADDITIONAL SENSE INFORM
ATION
Jan 1 20:34:39 uback-ap9-1 tldcd[3289]: TLD(6) Move_medium error: CHECK
CONDITION
Jan 1 20:34:39 uback-ap9-1 tldcd[3289]: TLD(6) closing/unlocking robotic path
Jan 1 20:34:39 uback-ap9-1 tldd[3717]: DecodeDismount(): TLD(6) drive 6,
Actual status: Robotic dismount fa
ilure
Jan 1 20:34:39 uback-ap9-1 tldd[3717]: TLD(6) drive 6 (device 5) is being
DOWNED, status: Robotic dismount
failure
Anyone seen it before?
Thanks,
--
----
Andrew Shinkarev
Network Systems Specialist
Abbott Laboratories
(847) 9387559
shinkara AT pprd.abbott DOT com
|
