Table 4 Status Of Disk Drive Or Array, Based On Front Panel Fault-Application Led; Table 5 Status Of Cm, Based On The Green Cache Led And Reboot - Seagate Exos CORVAULT Hardware Installation And Maintenance Manual

To troubleshoot system application errors:
1. If a drive or array is at fault, determine the cause and take the related recommended action.

Table 4 Status of disk drive or array, based on front panel Fault-Application LED

LED state Cause
Off
On
2. If a CM fault condition occurs, discover the status of the Cache LED and take the related recommended action. The
asterisk (*) indicates a fault condition.

Table 5 Status of CM, based on the green Cache LED and reboot

CACHE LED state
Off
Fast flash every 0.1 seconds
Slow flash every second
Off
Fast flash every 0.1 seconds
Slow flash every second
3. Determine the cause of a SAS port host-side or CM-side connection fault.
a. Halt all input and output from the host to the storage enclosure.
b. Verify there is no activity on the SAS host port activity LED for that data port. If there is, halt all applications that
access the storage enclosure.
c. Confirm the Cache LED is off, indicating there is no cached, unwritten data.
d. Reseat the host cable after inspecting it for damage to the cable and connectors.
e. After reconnection, if the fault condition persists, move the host cable to a port with a known good link status to
isolate the issue to the external data path or the CM data port.
f. After reseating the host cable, if the fault condition persists, replace the host cable with a known good one.
g. Verify that the host bus adapter (HBA) is fully seated and the PCI slot is powered on and functioning.
h. If the fault condition persists, replace the CM.
i. If the fault condition persists, reseat the HBA.
j. If the SAS host port activity LED still flashes amber, replace the HBA and reconnect the cable.
4. For still unaddressed issues, proceed to the next section and take the recommended corrective action, based on the
symptom. This may mean obtaining a replacement FRU of the same type before replacing the faulty module.
60 Chapter 6 Hardware installation and configuration issues
System application logic initiated by CM functioning normally None.
Disk drive marked as leftover or failed
Disk drive in a critical array and not rebuilding
Disk drive in a failed array
CM Cause
boots?
System flushing data from cache
Yes
System in self-refresh mode
System flushing data to nonvolatile memory
No*
Hardware failure
Recommended action
Clear metadata on the leftover disk drive, then
remove the disk drive with the fault.
Add a spare disk drive to alter the array state.
Contact Technical Support.
Recommended action
If this behavior persists, proceed to
Step 3.
Replace the CM.