CompTIA Server+ (SK0-005)TroubleshootingMedium

A server is configured with a RAID 1 array for its operating system and critical data. The server administrator receives a notification that one of the drives in the RAID 1 array has failed. The server remains operational. Which of the following is the MOST appropriate next step for the administrator to take?

  1. AImmediately replace the failed drive with a new, identical drive while the server is running.
  2. BWait for the second drive in the RAID 1 array to fail before taking action.
  3. CShut down the server, replace the failed drive, and then power on.
  4. DPerform a full system backup before replacing the failed drive.
Show answer & explanation

Correct answer: A. Immediately replace the failed drive with a new, identical drive while the server is running.

RAID 1 provides redundancy, meaning the server can continue operating with one failed drive. Many RAID controllers support hot-swapping, allowing a failed drive to be replaced while the server is running without downtime. This is the most efficient and common procedure for a single drive failure in a redundant array.

Why the other options are wrong

  • B. Waiting for the second drive to fail would lead to complete data loss and server downtime, defeating the purpose of RAID 1.
  • C. Shutting down the server for a hot-swappable drive replacement causes unnecessary downtime and is not required for RAID 1 single drive failures.
  • D. While backups are always important, the IMMEDIATE first step in a RAID 1 single-drive failure is to replace the drive to restore redundancy, especially if hot-swappable.

RAID 1 Single Drive Failure

In a RAID 1 (mirroring) array, one drive can fail without causing data loss or interruption to server operation due to data redundancy.

  • Server remains operational with one failed drive.
  • Redundancy is lost until the drive is replaced.
  • Hot-swapping is often supported to replace the drive without downtime.

Memory trick: One drive down? RAID 1's crown: hot-swap it, no server frown!

More Troubleshooting questions