SL8500 - Unable to MOUNT a Cartridge (MVC) to RTD Tape Drive

Asset ID:	1-72-2336800.1
Update Date:	2018-05-17
Keywords:

Solution Type Problem Resolution Sure

Solution 2336800.1 : SL8500 - Unable to MOUNT a Cartridge (MVC) to RTD Tape Drive

Applies to:

Sun StorageTek SL8500 Modular Library System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

No slot at address.
01DEC 09:16:49 SLS6634I RTD A213 available for use
01DEC 09:17:00 SLS6894I M A213,MT0355,SL,,VSM2,SWSRDRC,VSM2TB05
01DEC 09:17:00 SLS0662I LMU Response error - 01,000,18,00
01DEC 09:17:00 SLS0698I Req ACS 01 SEQ 02/269 REQ B Mount       VOL MT0355 SRC 01/08:08:00 CEL      TGT 01/01:00:00 DRV A213
01DEC 09:17:00 SLS0699I Response ACS 01 SEQ 02/269 ERR 02/02 Drive Does Not Exist         Ret'd To Src LSM 02
01DEC 09:17:00 SLS0120E Mount of MT0355 on drive A213 - LMU error 65156515 ACS 01
01DEC 09:17:01 OPS1000J ito.colruyt.int: A00310NOPA M=ITO,A=STK;PC03,I=MVS.1OPER PROBLEMEN,P=2,O=PROD,G=OPER,338 SLS6896E Mount of MVC MT0355
01DEC 09:17:01 338 SLS6896E Mount of MVC MT0355 on RTD A213 failed. Enter CANCEL to terminate VTCS request or RETRY to attempt recovery

Changes

Cause

From HSC/ELS message:

The software (HSC/ELS) thinks that there would not be a drive present at the time for the mount request.
01DEC 09:17:00 SLS0699I Response ACS 01 SEQ 02/269 ERR 02/02 Drive Does Not Exist Ret'd To Src LSM 02

The library does see the drive:
2017-12-01T09:31:16.578239, drive-drv-48, getState: requested
2017-12-01T09:31:16.643043, drive-drv-48, drive 1,2,-2,1,1: getState Successful (state = empty, label = , enableLibraryMode = 1, type = T10000c)
2017-12-01T09:31:16.730275, drive-drv-48, getDriveNetData: requested (SeqNo = 7281393)
2017-12-01T09:31:16.793214, drive-drv-48, drive 1,2,-2,1,1: getDriveNetData Successful

Can see in the HBT trace log file that drive was last successfully detected today.
2017-12-07T07:25:36.376060, drive-drv-48, getState: requested
2017-12-07T07:25:36.433041, drive-drv-48, drive 1,2,-2,1,1: getState Successful (state = empty, label = , enableLibraryMode = 0, type = T10000c)
2017-12-07T07:25:36.436906, drive-driveIf, driveifGetStateResponse: sent response
2017-12-07T07:25:36.518072, drive-driveIf, driveifCallbackGetNetData: Received. SeqNo = 7441062
2017-12-07T07:25:36.520917, drive-drv-48, getDriveNetData: requested (SeqNo = 7441062)
2017-12-07T07:25:36.583331, drive-drv-48, drive 1,2,-2,1,1: getDriveNetData Successful
2017-12-07T07:25:40.165390, drive-drv-48, getState: requested
2017-12-07T07:25:40.223058, drive-drv-48, drive 1,2,-2,1,1: getState Successful (state = empty, label = , enableLibraryMode = 0, type = T10000c)
2017-12-07T07:25:40.226929, drive-driveIf, driveifGetStateResponse: sent response
2017-12-07T07:25:40.364133, drive-driveIf, driveifCallbackGetNetData: Received. SeqNo = 7441072
2017-12-07T07:25:40.366936, drive-drv-48, getDriveNetData: requested (SeqNo = 7441072)
2017-12-07T07:25:40.433214, drive-drv-48, drive 1,2,-2,1,1: getDriveNetData Successful

Found in HBC trace log that this drive is assigned to the MediaValidation Pool
Version 1
<drives>
<mvConfigurationVersion>
2
</mvConfigurationVersion>
<drive>
<driveType>
null
</driveType>
<driveState>
null
</driveState>
<address>
1,2,-2,1,1
</address>
<driveTray>
null
</driveTray>
<driveSerialNumber>
null
</driveSerialNumber>
</drive>
</drives>Once this drive is assigned to MediValidation it is dedicated to it!!

Solution

Have customer remove the drive from Media Validation Pool within SLConsole and attempt usage as RTD A213 in VSM environment once again.
Should it still fail, a log snapshot needs to be pulled immediately after the fault and sent support for analysis.

Attachments

This solution has no attachment