The order in which drives are added in NetVault must correspond precisely with the drive order/geometry of the library. If the alignment is incorrect then NetVault will report errors when moving media.
Because NetVault and the library are not talking about the same drives, errors include the library refusing to unload drive1 that it sees as empty (but NetVault is trying to unload drive2 which contains media), or the library refusing to load media for the same reason.
Typically the changer will then go offline
Symptoms:
* CHGSCSI 24 0 101145 CMD STATUS 'CHECK CONDITION' [2]
CHGSCSI 25 0 101145 CMD SENSE KEY 'ILLEGAL REQUEST' [5] - ASC 3b ASCQ 0e
CHGSCSI 74 0 101145 CMD SENSE INFO 'MEDIUM SOURCE ELEMENT EMPTY '
CHGSCSI 107 0 101145 0x2 = ChgScsiCmd(0x807e860)
CHGSCSI 17 0 101145 Got sense ILLEGAL REQUEST ASC 3b0e from MoveMedia
Moving media RM0019 from Drive failed bacause the drive appeared to be empty.
* CHGSCSI 24 0 115422 CMD STATUS 'CHECK CONDITION' [2]
CHGSCSI 25 0 115422 CMD SENSE KEY 'ILLEGAL REQUEST' [5] - ASC 3b ASCQ 0d
CHGSCSI 74 0 115422 CMD SENSE INFO 'MEDIUM DESTINATION ELEMENT FULL '
CHGSCSI 107 0 115422 0x2 = ChgScsiCmd(0x807e860)
CHGSCSI 17 0 115422 Got sense ILLEGAL REQUEST ASC 3b0d from MoveMedia
Moving media RM0001 from SLOT 19 to Drive 1 failed because the drive appeared to be full.
WORKAROUND 1
Use a methodical approach to document which drive belongs in which bay; empty all drives and then load each drive through NetVault. Note which drive in NetVault corresponds to which physical drive in the library.
Then delete the device and re-add the library so that the drives match in NetVault. As a precaution, enable 'Do not open a device if the serial number has changed' once the configuration has been confirmed
This issue can also be caused by a tape stuck in the gripper.
WORKAROUND 2
Make sure that the drives are added in order in NetVault.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center