1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

TS3200 Drive error, not sure what's going on

Discussion in 'Tape / Media Library' started by Stefanina, Dec 19, 2016.

  1. Stefanina

    Stefanina Newcomer

    Joined:
    May 4, 2016
    Messages:
    4
    Likes Received:
    0
    My library interface for the TS3200 shows a drive error, TSM drive status is unknown, but I can't find any error codes. A dump of the library logs came up empty.
    the interface gives this:
    Status [​IMG] Error
    Cartridge In Drive Slot 19 (SFC044L5)
    Drive Error Code No Error
    Cooling Fan Active [​IMG]
    Drive Activity Unknown
    Port A Status Logged out
    Encryption Status
    Encryption method Application
    Key path Default by method
    BOP policy Disabled
    Density reporting Other

    TSM reports this:
    Library Name: TPL-K02
    Drive Name: LTO5_DRIVE_1
    Device Type: LTO
    On-Line: Yes
    Read Formats: ULTRIUM5C,ULTRIUM5,ULTRIUM4C,ULTRIUM4,ULTRIUM3C,ULTRIUM3
    Write Formats: ULTRIUM5C,ULTRIUM5,ULTRIUM4C,ULTRIUM4
    Element: 256
    Drive State: UNKNOWN
    Volume Name:
    Allocated to:
    WWN: 2001000E1114F960
    Serial Number: 1068084013

    I am running TSM 6.3.3 on Win server 2008R2
    It looks like I last upgraded the firmware on the TS 3200 around 11/25/15

    I'm sure I will have to post more info. I was handed this over after incomplete traing, and of course this happens when work is on a two week holiday break.
     
  2.  
  3. Houssam

    Houssam ADSM.ORG Member

    Joined:
    Aug 19, 2016
    Messages:
    12
    Likes Received:
    0
    try to make a tsmdlst and see if device name has changed, you have to update the path maybe.
     
  4. Stefanina

    Stefanina Newcomer

    Joined:
    May 4, 2016
    Messages:
    4
    Likes Received:
    0
    No, no changes to the device names or paths. The only changes to things at all in the past month has been to add two new nodes.
    The only things is that the library sent a cleaning request during the weekend while I was not at work, then the drive errored the next day.
    TSM does not manage the cleaning, the library sends to requests directly.
     
  5. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,232
    Likes Received:
    322
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Are you getting any errors in TSM while accessing the library or drives?
    If necessary, try this:
    halt TSM
    shutdown OS
    power off library
    power on library
    boot up the OS (TSM will start automatically)

    Check the activity log once it up again to see if there were errors initializing the library
     
    Stefanina likes this.
  6. Stefanina

    Stefanina Newcomer

    Joined:
    May 4, 2016
    Messages:
    4
    Likes Received:
    0
    I already did that when the error first occurred. I can see the volume in the drive, but I can't see a way to get it out of the drive. Nor will TSM or the library itself move it.

    I did get this on the last library reboot:
    0001 16.12.23 12:11:10.37 LIB/ERR<80 63 00 00 2B 00 00 00 00 00 00 00 FF 04
    01 FF FF FF 02 53 46 43 30 34 34 4C 35 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 > ME: invalid cartridge
    0002 16.12.23 12:07:28.29 TRC/CST<84 13 01 37 > Drive Warn or Crit Tape Alert flag
    0003 16.12.23 12:07:28.29 TRC/CST<84 13 01 27 > Drive Warn or Crit Tape Alert flag
    0004 16.12.23 12:07:28.29 TRC/CST<84 13 01 1E > Drive Warn or Crit Tape Alert flag
    0005 16.12.23 12:06:53.73 TRC/CST<84 13 01 14 > Drive Warn or Crit Tape Alert flag
    0006 16.12.23 12:06:53.72 TRC/CST<82 01 > Drive Cleaning request
    0007 16.12.23 11:47:45.27 LIB/ERR<80 F5 95 4D 2B 06 00 00 00 00 00 00 FF 04
    01 FF 02 13 02 53 46 43 30 34 34 4C 35 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 > HE: drive unload timeout
    0008 16.12.23 10:10:53.04 TRC/CST<84 09 04 27 > Drive Warn or Crit Tape Alert flag
    0009 16.12.23 10:10:53.04 TRC/CST<84 09 04 14 > Drive Warn or Crit Tape Alert flag
    0010 16.12.23 10:10:53.04 TRC/CST<84 09 04 06 > Drive Warn or Crit Tape Alert flag
    0011 16.12.23 10:10:53.03 TRC/CST<84 09 04 03 > Drive Warn or Crit Tape Alert flag
    0012 16.12.23 10:10:53.03 TRC/CST<82 04 > Drive Cleaning request
     
  7. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,232
    Likes Received:
    322
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    If you have a tape stuck in the drive, you need to place a hardware call with your library.
     
    Stefanina likes this.
  8. Stefanina

    Stefanina Newcomer

    Joined:
    May 4, 2016
    Messages:
    4
    Likes Received:
    0
    I put in a call to IBM, it turns out the drive itself has gone bad. It took the tech quite a while to unwind the tape and I got to see how the drive physically works, which was neat.
    The drive is now replaced, and turns out I did remember how to set the path and bring it online.
     

Share This Page