Just ideas...

If tar works and TSM doesn't, that could indicate your ELEMENT addresses are
wrong.
That is, TSM thinks /dev/rmtx is drive 1, so it mounts the tape in drive 1,
but AIX is looking for the tape on drive 0.
Do a Q DRIVE * F=D, make sure the element addresses are correct.

The other thing I have seen cause weird I/O errors is the driver for the
HBA.
I am clueless about Solaris hardware, but I know that on Windows, the HBA
drivers are separate code and are not provided with IBMTAPE.  Check to make
sure you have the latest level of driver for the HBA, AND that it is set up
for point-to-point or switched fabric, not artitrated loop.

Good luck!


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steve Hartland
Sent: Friday, July 23, 2004 9:10 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Problem with 3582 on Solaris 9


Hi all
        I am having a bit of an arm wrestle getting TSM to write to LTO2
drives in a 3582 library. Config as follows:

TSM 5.2.2.0 (also tried 5.2.0.0)
Solaris 5.9
Direct fibre attached to 2 drives.
Drive firmware 38D0 (latest on web)
IBMtape (latest on web dated 19 May)

Problem description:
When trying to label tape, library mounts tape in drive, rewinds tape, and
unloads it without appearing to write to it. TSM reports I/O error with KEY,
ASC and ASCQ all zero. TSM then reports that the volume has been labeled and
even checks it in. q libv shows volser present as scratch. Backup attempt
fails exactly the same as label libv attempt.
Drive entries in output of dmesg command seem to be correct. Have tried all
8 /dev/rmt options eg. 0st,0stc, etc. All fail
Have also tried with and without the TSM Device Driver.
Even tried configuring drive as manual and manually load tape. Still fails.

The strange thing is that write and read back using TAR command works fine
on both drives.

Hair being depleted.

Any ideas

Regards,

Steve Hartland
Lechabile Storage Solutions
0824645461