3581-L23 with TSM 5.2.2 on AIX

[charlieliu]

My Environment as follow



1. TSM Server is on p630-6C4 attach 3581-L17 (GEN 1)

2. Server oslevel is AIX 5.1.0.0 with 32 bit kernel mode

3. TSM Server code," TSM for AIX 5.2.2.0" with 32bit mode



Everything is ok , and operation is smoothly.





Now , I change the LTO form 3581-L17 (Gen1) to 3581-L23 (Gen2) ,

appear trouble



my procedure as follow:



1. delete all volume in squencial pool (tapepool) , checkout all

library volume , all LTO 1 Tape is Clear on the machine, and no more data preserve

2 delete squencial pool (tapepool), delete Lto device class

3. delete drv path , delete autodrv , delete library path , delete

autolibrary ( everything is clean)

4. shutdown DSMSERV

5. change Autoloader from 3581-L17 to 3581-L23

6. change Atape.bin to Latest version 8.4.6

7. have a 3581-L23 Test , run mksysb to test 3581-L23 operation ( Test

is ok)

8. start DSMSERV Service

9 define autolibrary , define library path , define autodrv , define drv

path

10 define LTO Device Class ( I try the format " Utrium 2 " and "Utrium

2C" )

11 create squencial pool (LTO2pool)

12 Label new LTO2 tape to library , and check in ( all tape is success

show scretch in library )





When I move data form diskpool to LTo2pool for a Testing , trouble

appear Lto2pool auto mounting the scretch Tape , but reject the tape after 3sec



follow is my errorlog from my activelog and my install fileset



--------------------------------------------------------------------------

06/15/04 17:30:31 ANR8336I Verifying label of LTO volume LTO001 in drive LT

O2DRV (/dev/rmt1). (PROCESS: 12)

06/15/04 17:31:14 ANR8468I LTO volume LTO001 dismounted from drive LTO2DRV

(/dev/rmt1) in library LIB3581. (PROCESS: 12)

06/15/04 17:31:15 ANR2017I Administrator ADMIN issued command: DEFINE VOLUME

LTO2POOL lto001 ACCESS=READWRITE (SESSION: 606)

06/15/04 17:31:15 ANR2206I Volume LTO001 defined in storage pool LTO2POOL (

device class LTO2CLASS). (SESSION: 606)

06/15/04 17:31:15 ANR4502W No files have been defined for automatically sto

ring sequential volume history information. (SESSION: 13

1)

06/15/04 17:31:17 ANR1003I Migration retry delay ended; checking migration

status for storage pool DISKPOOL. (PROCESS: 12)

06/15/04 17:31:17 ANR0984I Process 13 for MIGRATION started in the BACKGROU

ND at 17:31:17. (PROCESS: 13)

06/15/04 17:31:17 ANR1000I Migration process 13 started for storage pool DI

SKPOOL. (PROCESS: 13)

06/15/04 17:31:34 ANR2017I Administrator ADMIN issued command: QUERY ACTLOG

(SESSION: 616)

06/15/04 17:31:52 ANR8337I LTO volume LTO001 mounted in drive LTO2DRV (/dev

/rmt1). (PROCESS: 13)

06/15/04 17:31:55 ANR0513I Process 13 opened output volume LTO001. (PROCESS:

13)

06/15/04 17:32:01 ANR9999D pvrntp.c(4936): ThreadId<40> DumpBlock error on

drive LTO2DRV (/dev/rmt1); amtWritten -16731590, bufCurs

or 45625. Callchain of previous message: 0x10016138 outD

iagf <- 0x10100D24 DumpBlock <- 0x10103C0C NtpFlush <- 0

x1062CA40 LtoFlush <- 0x100E625C AgentThread <- 0x10007A

E8 StartThread <- 0xD004B3F0 _pthread_body <- (PROCESS:

13)

06/15/04 17:32:01 ANR1411W Access mode for volume LTO001 now set to "read-o

nly" due to write error. (PROCESS: 13)

06/15/04 17:32:01 ANR0515I Process 13 closed volume LTO001. (PROCESS: 13)

06/15/04 17:32:01 ANR1181E astxn.c582: Data storage transaction 0:1076309 w

as aborted. (PROCESS: 13)

06/15/04 17:32:01 ANR2183W dfmigr.c1976: Transaction 0:1076309 was aborted.

(PROCESS: 13)

06/15/04 17:32:01 ANR1033W Migration process 13 terminated for storage pool

DISKPOOL - transaction aborted. (PROCESS: 13)

06/15/04 17:32:01 ANR0985I Process 13 for MIGRATION running in the BACKGROU

ND completed with completion state FAILURE at 17:32:01.





******************************************************************



I have tested 64 bit mode and appear the same problem

I have patch to TSM Server to 5.2.2.5 but dont resolve



Can anybody help me to check my produce , which step is wrong

or tell me what version or what way to resolve the problem

 

[Izo]

A classic case:



LTO-2 firmware is buggy, as was LTO-1 firmware to begin with.

Make sure you upgrade to the very latest firmware for both loader but in perticular the drive, before doing write operations with the loader.

I highly recommend formatting (e.g. labling or relabling in case of an already labled tape) new, empty or scratch tapes at least once before using them with TSM.

Labling the tapes will make sure data is written with the new firmware algorithms, which in general improves performance, reliability and solves an enormous lot of I/O problems.



Go to this page and obtain the latest firmware:

http://www-1.ibm.com/servers/storage/support/lto/index.html



Good luck, mail me if you do not succeed



BR

Izo

 

[AmosHagay]

Hi There,



I had this Error Before with P630 and LTO2 Drive, Working with TSM,

This Problem solved after i update the Firmware of the Scsi card, that connected to the Tape.





Amos