Isolate System Application Faults; Take Corrective Action For 2U Enclosures - Quantum QXS Series Hardware Installation And Maintenance Manual

Isolate system application faults

System application faults generally fall into two categories: drive and disk group faults or controller module
(CM) cache faults.
In the case of a faulty CM or power loss, the system memory flushes to embedded MultiMediaCard (eMMC).
During the process of writing to eMMC, only those components used in the flush process receive super-
capacitor power. The system memory flush typically takes 60 seconds.
In the case of a faulty CM or a power loss, the cache memory flushes to nonvolatile memory . During the
process of writing the cache to nonvolatile memory, only those components uses in the flush process receive
super-capacitor power while the Cache LED momentarily flashes. The cache memory Normalized Total Time
to Flush (NTTF) typically takes less than 11 seconds. After the flush, the system uses the remaining super-
capacitor power to refresh cache memory.
To isolate system application faults:
1. If a drive or disk group is at fault, determine the cause, then take one of the following actions:
a. If the drive is marked as failed, then replace the drive.
b. If the disk group is not rebuilding, add a spare drive to alter the disk group state.
c. If you have a quarantined disk group, contact Technical Support.
2. If a CM fault condition occurs, discover the status of the Hardware fault LED and if it is on, replace the CM.
If it is flashing, wait for the CM to come online.
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 tested, 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 tested, 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, reseat the HBA.
i. If the SAS host port activity LED still flashes amber, replace the HBA and reconnect the cable.
j. If the fault condition persists, replace the CM.
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.

Take corrective action for 2U enclosures

After you follow the process above and isolate the fault to an area of the storage enclosure or to a particular
module, use the following chart to determine the type of corrective action you should take.
84 Chapter 9 Hardware installation and configuration issues