Overland Storage ARCvault Series Service Manual page 38

Autoloader/library
Hide thumbs Also See for ARCvault Series:
Table of Contents

Advertisement

Section 3
FSC
Message
3002 "Picker Tach Errors"
3011 "Bin Fetch Failure"
3012 "Bin Stow Failure"
3013 "Drive Fetch Failure"
3014
"Drive Stow Failure"
3016
"Drive Status Failure"
301B "Drive Communication Error"
301C "Drive Get General Status Fail"
301E
"Drive Unload Fail"
3020 "Undefined Config"
3035 "Drive Unload Prevented"
3041
"Loader Received Invalid Cmd"
3045 "Loader Invalid Drive Number in
Cmd"
3051 "No Cartridges In Library"
3052 "Too Many Cartridges"
3053 "Need 3 Cartridges Minimum"
3054 "Need 1 Drive Minimum"
3055 "Memory Allocation Error"
305b "Diag Fetch, Drive not loaded"
3–4
Table 3-1: FSC/ERP Cross-Reference
ERP Description
1
The library picker motor has reported excessive
tach errors.
6
The library failed to fetch a cartridge from a slot
and all retries were exhausted.
6
The library failed to stow a cartridge to a slot and all
retries were exhausted.
7
The library failed to fetch a cartridge from a drive
and all retries were exhausted.
7
The library failed to stow a cartridge to a drive and
all retries were exhausted.
2
The library was not able to get status from the drive
serial (ADI) interface during the normal status
check.
2
The library was not able to communicate with the
drive ADI.
2
The drive did not return the general status packet
over the ADI.
8
The drive did not successfully unload a cartridge
when the library issued the eject command over
the ADI.
2
The library firmware detected an invalid
configuration during a diagnostic operation. This
error usually indicates an internal hardware
problem.
5
The library was unable to eject the cartridge from
the drive to scan its barcode during an inventory
because the drive is in a prevent media removal
state. The prevent media removal state is set by a
host SCSI command to the drive.
1
The library loader firmware process detected an
invalid internal command.
1
The library loader firmware process detected an
invalid drive number in an internal command.
4
A cartridge cycle diagnostic was attempted with no
media in the library.
4
A cartridge cycle diagnostic was attempted with no
empty slots in the library.
4
A drive cycle diagnostic was attempted with too few
cartridges in the library.
4
A drive cycle diagnostic was attempted but no
drives were detected.
1
The library firmware detected an internal memory
allocation error.
6
The drive cycle diagnostic attempted to fetch a
cartridge from the drive and detected the drive in
an unexpected not loaded state.
10400025-101 10/2006

Advertisement

Table of Contents
loading

Table of Contents