Veritas-bu

[Veritas-bu] What's required to run DLT tape drive with the l atest firmware from STK

2002-01-02 12:14:09
Subject: [Veritas-bu] What's required to run DLT tape drive with the l atest firmware from STK
From: Kevin_Trotman AT AFCC DOT com (Trotman, Kevin)
Date: Wed, 2 Jan 2002 11:14:09 -0600
Yes, I've had this problem a lot. But I think your problem is something is
wrong with your SCSI bus. I don't have problems with opening my robotic
control device. Maybe you have two problems here.

Has anyone seen this problem though? I've been dealing with this for months.

On two of our 9710 robots we upgraded to 101, then to 106 code on the
drives. The 101 code cause cleanings that were too frequent, causing
read/write errors over time and other problems. Since upgrading to 106,
however, the write errors have gotten much worse and I've experienced
dismount failures. I'm not sure if this is due to the 101 code re-aligning
the drive heads or if this is from the 106 code?? I had to have STK replace
two of the drives because they got really bad. The new drives came standard
with 106 in firmware and do not seem to exhibit the same behavior as much
(not as much as the ones that are giving me a fit anyway). But I'd like to
know if anyone else has had similar problems. Its hard to get STK to own up
to a problem here and do anything about it.

However, just a note. Your sense key errors on the robot may denote another
problem with robotics control.

KBT


-----Original Message-----
From: Andrew Shinkarev [mailto:shinkara AT pprd.abbott DOT com]
Sent: Wednesday, January 02, 2002 10:11 AM
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] What's required to run DLT tape drive with the
latest firmware from STK


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
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] What's required to run DLT tape drive with the l atest firmware from STK, Trotman, Kevin <=