SL3000- Llibrary Goes to Down State in SAMFS Due to Drive Load Failure Reporting Sense Key = 04, ASC = 53, ASCQ = 00 (Doc ID 1614360.1)

Last updated on NOVEMBER 27, 2022

Applies to:

Symptoms

SL3000 library goes to down state in SAMFS due to drive load failure reporting Sense Key = 04, ASC = 53, ASCQ = 00

Move retry failure between 2371 (Cell)  to 1005 (drive) but subsequent move was done properly.

2013/12/25 20:04:07 5177 [3047:20] transport.c:521 time Move cartridge: from 2371(asis) to 1005: time 18 seconds
2013/12/25 20:04:07 1010 [3047:20] scsi_cmd.c:1273 Error: SCSI error: Fatal hardware error.
2013/12/25 20:04:07 0000 [3047:20] dev_log.c:304 all cdb - a5 00 00 00 09 43
2013/12/25 20:04:07 0000 [3047:20] dev_log.c:306 all       03 ed 00 00 00 00
2013/12/25 20:04:07 0000 [3047:20] dev_log.c:331 all sense - 70 00 04 00 00 00 00 0c 00 00
2013/12/25 20:04:07 0000 [3047:20] dev_log.c:333 all         00 00 53 00 00 40 00 00 00 00
2013/12/25 20:04:07 1008 [3047:20] misc.c:210 all Changing state to DOWN
2013/12/25 20:04:07 5207 [3047:20] transport.c:611 Error: Move cartridge from 2371(asis) to 1005 fails - retries exhausted
2013/12/25 20:04:07 0000 [3047:20] dev_log.c:304 all cdb - a5 00 00 00 09 43
2013/12/25 20:04:07 0000 [3047:20] dev_log.c:306 all       03 ed 00 00 00 00
2013/12/25 20:04:07 0000 [3047:20] dev_log.c:331 all sense - 70 00 04 00 00 00 00 0c 00 00
2013/12/25 20:04:07 0000 [3047:20] dev_log.c:333 all         00 00 53 00 00 40 00 00 00 00
2013/12/25 20:04:07 5179 [3047:20] transport.c:622 detail Move cartridge complete: from 2371(asis) to 1005
2013/12/25 20:12:57 5049 [3047:15] media_move.c:208 detail Move cartridge: from 1003(asis) to 2142
2013/12/25 20:13:29 5049 [3047:16] media_move.c:208 detail Move cartridge: from 1004(asis) to 2370
2013/12/25 20:14:17 5049 [3047:14] media_move.c:208 detail Move cartridge: from 1002(asis) to 2141

Library log shows library hardware error as below. (Time is not synchronised in SAMFS system)

2013-12-25T18:11:28.433,   1.1.2.1.2,    root,   scsi0,        move, 3435601, error, 3955, "Error from device Code: 605 - Drive media error", Data=<response sequence="1031981" final="true"><command>load</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6415</resultCode><resultText><!|CDATA|drive 1,1,2,1,2: load FAILED with mediaError: CartLabel R00303L4||></resultText><operationalState>605</operationalState></resultStatus><currentCleanUsage>0</currentCleanUsage><maxCleanUsage>0</maxCleanUsage><faultSymptomCode>0000</faultSymptomCode></result></response>

2013-12-25T18:11:28.446,   1.1.2.1.2,    root,   scsi0,        move, 3435601, error, 3337, "Drive load failed due to media error - on failed load", volumeLabel=R00303L4

2013-12-25T18:11:33.303,      0.0.0.0.0, 1000,      scsi-engine,                 ,   info, 1202, 0000, "task = 0x3b9019e0, senseKey = 0x4, asc = 0x53, ascq = 0, bitPtr = 0, bpv = 0, command = 0x1, sksValid = 0, fieldPtr = 0"

HBC trace shows the same error on the same drive.

!2013-12-25T18:11:33.288,   1.0.0.0.0,    root, default,odi-operation,      0, trace, 0000, Error Number string = 3337
!2013-12-25T18:11:33.288,   1.0.0.0.0,    root, default,odi-operation,      0, trace, 0000, ScsiAppOdiInterface::translateResultCode() impResultcode = 3337
!2013-12-25T18:11:33.288,   1.0.0.0.0,    root, default,odi-operation,      0, trace, 0000, OdiPliInterfaceImp::translateResultCode(): impResultcode = 3337
!2013-12-25T18:11:33.288,   1.0.0.0.0,    root, default,odi-operation,      0, trace, 0000, pliErrorNumber = 3337 _resultCode = 1415
!2013-12-25T18:11:33.299,   1.0.0.0.0,    root, default,  scsi-engine,      0, trace, 0000, ScsiTask::setStatusAndSense()errCode = 45300
!2013-12-25T18:11:33.300,   1.0.0.0.0,    root, default,  scsi-server,      0, trace, 0000, SmcMoveMedium::doNext(): move failed

Changes

 No change has been applied.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.