Skip to main content

FQXST0008W : A disk group is down, a disk group failed, or a disk group reported that it has no life remaining.

A disk group is down, a disk group failed, or a disk group reported that it has no life remaining.

Severity​

Critical

Serviceable with log​

No

Automatically Notify Support​

No

User Action​

  • If a disk that was part of a disk group is down:
    1. If the specified disk failed for one of these reasons: excessive media errors, imminent disk failure, possible hardware failure, disk is not supported, too many controller-recoverable errors, illegal request, or due to being degraded, replace the disk with one of the same type (SAS SSD, enterprise SAS, or midline SAS) and the same or greater capacity. For continued optimum I/O performance, the replacement disk should have performance that is the same as or better than the one it is replacing.
    2. If the specified disk failed because a user forced the disk out of the disk group, RAID-6 initialization failed, or for an unknown reason:
      1. If the associated disk group is offline or quarantined, contact Support.
      2. Otherwise, clear the metadata for the disk to reuse the disk.
    3. If the specified disk failed because a previously detected disk is no longer present:
      1. Reinsert the disk or insert a replacement disk of the same type (SAS SSD, enterprise SAS, or dline SAS) and the same or greater capacity as the one that was in the slot. For continued optimum I/O performance, the replacement disk should have performance that is the same as or better than the one it is replacing.
      2. If the disk then has a status of leftover (LEFTOVR), clear the metadata to reuse the disk.
      3. If the associated disk group is offline or quarantined, contact Support.
  • If reconstruction of a disk group failed:
    1. If the associated disk group is online, clear the specified disk's metadata so that the disk can be re-used.
    2. If the associated disk group is offline, the CLI trust command may be able to recover some or all of the data in the disk group. However, trusting a partially reconstructed disk may lead to data corruption. See the CLI help for the trust command. Contact technical support for help to determine if the trust operation applies to your situation and for help to perform it.
    3. If the associated disk group is offline and you do not want to use the trust command, perform these steps:
      1. Delete the disk group (remove disk-groups CLI command).
      2. Clear the specified disk's metadata so the disk can be re-used (clear disk-metadata CLI command).
      3. Replace the failed disk or disks. (Look for other instances of event 8 in the event log to determine which disks failed.)
      4. Re-create the disk group (add disk-group CLI command).
  • If an SSD that was part of a disk group has reported that it has no life remaining, replace the disk with one of the same type (SAS SSD, enterprise SAS, or midline SAS) and the same or greater capacity. For continued optimum I/O performance, the replacement disk should have performance that is the same as or better than the one it is replacing.