Windows 2000 Server (mirrored system volume): Volume C (boot/system) is mirrored to dynamic Disk 1. Disk Management now shows Volume C = Failed Redundancy and Disk 1 = Missing. Reactivating Disk 1 does not restore health. What is the correct next action to reestablish mirroring safely?

Introduction / Context:
Fault tolerance with software mirroring (RAID-1) in Windows 2000 uses dynamic disks. If a mirror partner is “Missing,” and reactivation fails, treat that side as unavailable. Proper repair is to remove the failed mirror member, replace the physical disk, and then mirror the healthy side to the new disk so the array can resynchronize cleanly and safely.

Given Data / Assumptions:

• System/boot volume C: is mirrored.
• Disk 1 status = Missing; reactivation unsuccessful.
• Goal: restore redundancy without risking the good copy.
• Windows 2000 Disk Management is the tool in use.

Concept / Approach:
When a mirror member is irrecoverable (Missing and not reactivating), the safe path is: remove the broken mirror leg (leaving C: healthy on the remaining disk), replace the failed hardware, convert/initialize the new disk as dynamic, and then add the mirror back so Windows rebuilds from the good copy to the replacement.

Step-by-Step Solution:
Right-click the mirrored volume and select Remove Mirror for the Missing side.Physically replace Disk 1; initialize it in Disk Management and convert to dynamic.Right-click C: and choose Add Mirror; select the new Disk 1.Allow synchronization to complete; verify status becomes Healthy (Mirrored).

Verification / Alternative check:
Event Viewer logs and Disk Management status should show a rebuild in progress. After completion, test boot paths if mirror was the system/boot volume.

Why Other Options Are Wrong:
Automatic regeneration after simple replacement (no remove/add): Not reliable; Disk Management requires explicitly removing and re-adding the mirror target.

Manually copying files to recreate a mirror: Not how software RAID-1 works; use Add Mirror to rebuild.

Rescan/delete data on Disk 1: Unnecessary and risky; removing the mirror and re-adding is the supported process.

None of the above: Incorrect because the remove-replace-add workflow is correct.

Common Pitfalls:
Pulling the wrong disk, trying to force reactivation repeatedly, or attempting to clone files rather than letting the mirroring engine rebuild block-by-block.

Final Answer:
Remove the mirror on Disk 1, replace Disk 1, then add the mirror back to the new Disk 1