ADSM-L

Re: MSL6030 TSM write failure

2006-03-15 00:26:33
Subject: Re: MSL6030 TSM write failure
From: Kurt Beyers <Kurt.Beyers AT DOLMEN DOT BE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 15 Mar 2006 06:24:31 +0100
Jim,
 
It looks indeed to be a HW problem with the library (which is brand new, so 
that cancels option 1 and 2). I was just surprised that the tapes could be 
labelled as data is wrtten to them then too.
 
But apperantly the HW issues only pop-up when you start sending the backup 
data, which are larger then a label of course.
 
thanks,
Kurt

________________________________

Van: ADSM: Dist Stor Manager namens JN
Verzonden: di 3/14/2006 18:53
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: Re: [ADSM-L] MSL6030 TSM write failure



Hi Kurt,

   In my experience, the errors that you are seeing are primarily caused by
one of three problems:

1)  The tape drive is dirty and needs to be cleaned
2)  The tape cartridge is bad and needs to be destroyed
3)  The Tape drive has a physical problem that needs to be fixed via
replacement or maintenance.

   I hope one of these solutions works for you.



   Jim

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Kurt Beyers
Sent: Tuesday, March 14, 2006 1:01 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] MSL6030 TSM write failure

Hello,

A quick (?) question. My setup is the following:

TSM 5.3.2 server with a MSL6030 SCSI attached library (2 HP-Ultrium 3
drives).

The library has been defined in TSM and the labelling of the tapes went
fine. However a migrate of the diskpool towards the LTOPool fails with the
following messages:

ANR0984I Process 42 for MIGRATION started in the BACKGROUND at 08:45:30.
ANR2110I MIGRATE STGPOOL started as process 42.
ANR1000I Migration process 42 started for storage pool DISKPOOL manually,
highMig=90, lowMig=0, duration=No.
ANR8337I LTO volume HK3722L3 mounted in drive DRIVE1 (mt1.0.0.5).
ANR1340I Scratch volume HK3722L3 is now defined in storage pool LTOPOOL.
ANR0513I Process 42 opened output volume HK3722L3.
ANR8302E I/O error on drive DRIVE1 (mt1.0.0.5) with volume HK3722L3
(OP=WRITE,
Error Number=1117, CC=208, KEY=0B, ASC=47, ASCQ=03,
SENSE=70.00.0B.00.00.00.00.10.00.00.00.00.47.03.00.00.00.00.00.00.00.00.,
Description=Command aborted).  Refer to Appendix D in the 'Messages' manual
for
recommended action.
ANR1411W Access mode for volume HK3722L3 now set to "read-only" due to write
error.
ANR0515I Process 42 closed volume HK3722L3.

What am I missing here? The library configuration in TSM is as follows:

-The TSM device driver is used and the library is detected by the
tsmdlst.exe program as follows:

Tivoli Storage Manager -- Device List Utility
Licensed Materials - Property of IBM
5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
Computer Name:      TSM-server
OS Version:         5.2
OS Build #:         3790
TSM Device Driver:  TSMScsi - Running
2 HBAs were detected.
Manufacturer        Model          Driver      Version            Firmware
Description
----------------------------------------------------------------------------
------------------------------------
QLogic Corporation  QLA2340        ql2300.sys  9.0.2.11 (w32 IP)  3.03.12
QLogic QLA2340          Fibre Channel Adapter
QLogic Corporation  QLA2340        ql2300.sys  9.0.2.11 (w32 IP)  0.00.00
QLogic QLA2340          Fibre Channel Adapter
TSM Name     ID   LUN  Bus  Port SSN                   WWN               TSM
Type  Device Identifier
----------------------------------------------------------------------------
------------------------------------
lb0.0.0.5    0    0    0    5    -                     -
LIBRARY   HP      MSL6000 Series  0507
mt1.0.0.5    1    0    0    5    -                     -                 LTO
HP      Ultrium 3-SCSI  G24W
mt2.0.0.5    2    0    0    5    -                     -                 LTO
HP      Ultrium 3-SCSI  G24W
Completed in: 0 days, 0 hours, 0 minutes, 1 seconds.

-The library is defined in TSM with:

tsm: SRV-SPGR-BACKUP_SERVER1>q library f=d
Library Name: MSL6030
Library Type: SCSI
WWN: 00900D06254B8000
Serial Number: 2U2527002X
AutoLabel: No
Reset Drives: No
Last Update by (administrator): ADMIN

tsm: SRV-SPGR-BACKUP_SERVER1>q drive f=d
Library Name: MSL6030
Drive Name: DRIVE1
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2
Element: 480
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 50060B000034589E
Serial Number: HU105252G0

Library Name: MSL6030
Drive Name: DRIVE2
Device Type: LTO
On-Line: Yes
Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM
Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2
Element: 481
Drive State: EMPTY
Volume Name:
Allocated to:
WWN: 50060B000034586E
Serial Number: HU105252FH

tsm: SRV-SPGR-BACKUP_SERVER1>q path f=d
Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: MSL6030
Destination Type: LIBRARY
Library:
Node Name:
Device: LB0.0.0.5

Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: DRIVE1
Destination Type: DRIVE
Library: MSL6030
Node Name:
Device: mt1.0.0.5

Source Name: SRV-SPGR-BACKUP_SERVER1
Source Type: SERVER
Destination Name: DRIVE2
Destination Type: DRIVE
Library: MSL6030
Node Name:
Device: mt2.0.0.5

thanks,
Kurt

<Prev in Thread] Current Thread [Next in Thread>