Also check micro code levels on the tape drives. Have them brought up to the latest level.
Check compatibility between the microcode levels on the drive and the O/S fileset level. You will have to contact the manufacturer for this. You may need to update the fileset. Also make sure that TSM is compatible with the current micro-code level. You may need to upgrade TSM. Good luck Jan -----Original Message----- From: George Lesho [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 3:29 PM To: [EMAIL PROTECTED] Subject: Re: sense errors This sense code indicates a medium error where the format was corrupted. This error is usually associated with a TSM volume where someone did other than TSM recordings (dd, Veritas, tar, etc) George Lesho System/Storage Admin AFC Enterprises "Johnn D. Tan" <[EMAIL PROTECTED] To: [EMAIL PROTECTED] L.EDU> cc: (bcc: George Lesho/Partners/AFC) Sent by: "ADSM: Subject: sense errors Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 04/18/02 03:31 PM Please respond to "ADSM: Dist Stor Manager" Does anyone have any ideas on the following errors that showed up in our TSM activity log? We have TSM 4.1.3 server running on AIX 4.3.3ML9, connected to a SpectraLogic HVD 64000/Gator (with Sony SDX-500C drives). We've sent the sense code info to Tivoli as well as SpectraLogic, but they point at each other or general "SCSI" problems. We've already swapped out the cables, the terminators, even one of the SCSI cards. We've cleaned the drives, changed the filters, re-connected the cables, etc. Even though all of the below are on DRIVE1, it actually happens to all six of our drives eventually. I checked the TSM Messages manual, and it's not that helpful. ***** I'm writing not so much to get a definitive answer (as that's obviously something specific to our site & setup), but more for other clues or leads that I could investigate. Maybe Tivoli, SpectraLogic, and our own group have all been looking in the wrong direction. ***** By the way, we get these on a more-or-less regular basis, like one set of three (such as below) per week or every other week. Thanks for any leads. johnn 04/18/02 07:43:55 ANR8302E I/O error on drive DRIVE1 (/dev/mt0) (OP=READ, CC=306, KEY=03, ASC=31, ASCQ=00, SENSE=F0.00.03.00.00.80.00.14.00.00.00.00.31.00.00.00.CE- .00.00.00.00.B8.01.4D.20.50., Description=Drive or media failure). Refer to Appendix B in the 'Messages' manual for recommended action. 04/18/02 07:56:40 ANR8302E I/O error on drive DRIVE1 (/dev/mt0) (OP=READ, CC=306, KEY=03, ASC=31, ASCQ=00, SENSE=F0.00.03.00.00.80.00.14.00.00.00.00.31.00.00.00.CE- .00.00.00.00.EC.01.4C.60.70., Description=Drive or media failure). Refer to Appendix B in the 'Messages' manual for recommended action. 04/18/02 08:06:17 ANR8302E I/O error on drive DRIVE1 (/dev/mt0) (OP=READ, CC=306, KEY=03, ASC=31, ASCQ=00, SENSE=F0.00.03.00.00.80.00.14.00.00.00.00.31.00.00.00.CE- .00.00.00.01.24.01.46.68.00., Description=Drive or media failure). Refer to Appendix B in the 'Messages' manual for recommended action. ********************************************************************** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action or reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. **********************************************************************
