Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

All of a sudden a lot read/write errors

Status
Not open for further replies.

Venzent

Technical User
Feb 15, 2007
13
NL
TSM Server 5.3 on Windows 2000, 3584 Library.

Completely out of the blue my TSM server is giving a lot of read/write errors on several volumes on several drives. I can not conclude any logical in the source of this problem, that's going for 3 days now, starting each day at the reclaimation process, here's a part of the logged errors.
Where or how to look any deeper to the problem?

TSM alert for TSM1 at 7/18/2008 2:09:53 PM
7/18/2008 2:04:25 PM ANR8302E I/O error on drive DRIVE0 (mt1.0.0.6) with volume 000428L1 (OP=WRITE, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.01.30.30.30.34.32.38.4C.00.00.00.0D.1C.EF,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:04:36 PM ANR8302E I/O error on drive DRIVE1 (mt3.0.0.7) with volume 000183L1 (OP=WRITE, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.01.30.30.30.31.38.33.4C.00.00.00.05.92.E8,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:05:27 PM ANR8302E I/O error on drive DRIVE3 (mt2.0.0.7) with volume 000186L1 (OP=WRITE, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.03.30.30.30.31.38.36.4C.00.00.00.0D.FC.C6,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:05:54 PM ANR8302E I/O error on drive DRIVE5 (mt1.0.0.7) with volume 000182L1 (OP=WRITE, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.03.30.30.30.31.38.32.4C.02.00.01.1E.6E.C3,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:05:54 PM ANR8302E I/O error on drive DRIVE5 (mt1.0.0.7) with volume 000182L1 (OP=OFFL, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.03.30.30.30.31.38.32.4C.02.00.01.1E.79.C3,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:05:56 PM ANR8469E Dismount of LTO volume 000182L1 from drive DRIVE5 (mt1.0.0.7) in library 3584LIB failed.
7/18/2008 2:06:26 PM ANR8302E I/O error on drive DRIVE1 (mt3.0.0.7) with volume 000190L1 (OP=WRITE, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.01.30.30.30.31.39.30.4C.00.00.00.07.5F.E8,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:06:26 PM ANR8302E I/O error on drive DRIVE1 (mt3.0.0.7) with volume 000190L1 (OP=OFFL, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.01.30.30.30.31.39.30.4C.00.00.00.07.68.E8,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:06:28 PM ANR8469E Dismount of LTO volume 000190L1 from drive DRIVE1 (mt3.0.0.7) in library 3584LIB failed.
7/18/2008 2:08:20 PM ANR8302E I/O error on drive DRIVE0 (mt1.0.0.6) with volume 000188L1 (OP=WRITE, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.01.30.30.30.31.38.38.4C.00.00.00.0C.96.EF,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:09:01 PM ANR8302E I/O error on drive DRIVE3 (mt2.0.0.7) with volume 000198L1 (OP=WRITE, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.03.30.30.30.31.39.38.4C.00.00.00.0D.05.C6,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:09:01 PM ANR1023W Migration process 139 terminated for storage pool DISKPOOL_3 - excessive write errors encountered.
7/18/2008 2:09:01 PM ANR8302E I/O error on drive DRIVE3 (mt2.0.0.7) with volume 000198L1 (OP=OFFL, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.03.30.30.30.31.39.38.4C.00.00.00.0D.10.C6,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:09:03 PM ANR8469E Dismount of LTO volume 000198L1 from drive DRIVE3 (mt2.0.0.7) in library 3584LIB failed.
7/18/2008 2:09:17 PM ANR8302E I/O error on drive DRIVE5 (mt1.0.0.7) with volume 000191L1 (OP=WRITE, Error Number=1235, CC=0, KEY=0B, ASC=4E, ASCQ=00,~SENSE=70.00.0B.00.00.00.00.1C.00.00.00.00.4E.00.00.00.10.47.00.00.00.03.30.30.30.31.39.31.4C.00.00.00.33.15.C3,~Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action.
7/18/2008 2:09:33 PM ANR8779E Unable to open drive mt3.0.0.6, error number=1235.
7/18/2008 2:09:33 PM ANR8779E Unable to open drive mt3.0.0.6, error number=1235.
7/18/2008 2:10:06 PM ANR8381E LTO volume 000348L1 could not be mounted in drive DRIVE4 (mt3.0.0.6).
7/18/2008 2:10:06 PM ANR1401W Mount request denied for volume 000348L1 - mount failed.

 
If you have problems with DRIVE0, you may have a problem with the library itself. Do you have access to your LTO GUI? That might be a good place to look.

Check your Paths, and maybe your physical connections. If you recently replaced a drive or if the WWN's have chnaged all your paths could be messed up.

Another thing - less likely, but possible - Drive cleaning?

Just a couple thoughts..

 
Drive0 was replaced a couple of weeks ago, could this be the problem? It's been running fine for several weeks since the replacement, can errors occour like this suddenly show up after running fine for weeks?
 
Hmm.. unlikely... you may want to verify all the wwn's to make sure 'q drive f=d' and 'q path f=d' marry up to each other. Get a list of the WWN's from the TSM server itself to compare, since it will hold the true WWN's. also, check the actlog startd=7/18/2008 startt=00:00:00 endt=2:15:00 to see if there are any other messages that relate.

If you have access to the LTO GUI, I use this alot when there are problems - usually it will have the answer if something is faulty.. if it looks clean, the problem is most likely in TSM or on the TSM Server itself.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top