Question

Difficulty: Very hardStorage Drives and RAID Array Issues

A network administrator is troubleshooting an enterprise database server utilizing a hardware RAID 10 array composed of four NVMe solid-state drives. During peak transaction periods, the server logs file system write timeouts, yet the hardware RAID controller reports the overall volume status as 'Optimal' and all individual member disks as 'Online'. Drive health telemetry reveals that one specific SSD in Span 0 is experiencing severe thermal throttling and logging a high count of uncorrectable S.M.A.R.T. media errors. Which of the following is the most appropriate action to take to address this issue while protecting system availability and data integrity?

  1. Force the degrading NVMe drive offline via the RAID controller interface, replace the physical drive, and initiate an array rebuild.Answer
  2. B
    Reformat the volume containing the degraded drive using the RAID controller management utility to clear write timeouts.
  3. C
    Break the RAID 10 array and convert it to a RAID 0 striped array to bypass hardware-level parity checks and restore write speed.
  4. D
    Delete the degraded array configuration and recreate the RAID 10 volume from scratch before restoring from a backup.

Answer

Force the degrading NVMe drive offline via the RAID controller interface, replace the physical drive, and initiate an array rebuild.
When a drive in a RAID array experiences severe S.M.A.R.T. errors and thermal throttling, it can cause system-wide I/O timeouts even if the RAID controller has not yet marked the drive as failed. Manually marking the degrading drive offline via controller management, replacing the disk, and running an array rebuild is the standard procedure to isolate the faulty drive and restore full array fault tolerance without data loss.

Step-by-Step Solution

1
Analyze drive telemetry and RAID controller state
Identify that the hardware controller sees the array as 'Optimal' because the drive has not suffered a hard total failure, but high S.M.A.R.T. errors and thermal throttling cause intermittent I/O timeouts.
Hardware RAID controllers do not always automatically mark drives with soft S.M.A.R.T. errors as failed until hard error thresholds are crossed.
2
Take proactive recovery action on the failing drive
Manually set the specific NVMe drive in Span 0 to an offline state using the RAID controller management utility.
Setting the drive offline removes the source of latency and I/O write timeouts from the active array span.
3
Replace the faulty hardware drive and rebuild
Replace the faulted NVMe drive with a healthy drive and initiate the mirror rebuilding process.
This restores full fault tolerance to Span 0 without deleting or reformatting active volumes.

Key Concept

Handling Predictive Failure and Soft Errors in Hardware RAID Arrays
Rate this question