Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,815 questions
Replacing/Repairing a failed drive in 2-node Hyper-V S2D Cluster.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 78%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
Justin Buckley
0
Reputation points
Hello! I'm working with a 2-node Windows Server 2022 Hyper-V S2D Cluster (we'll call the nodes HV1 and HV2). There are 8 x 4TB NVMe drives per server, and 2 CSVs (two-way mirror/CSVFS_ReFS) used for VM data storage.
HV1 had a physical disk lose connection and was subsequently auto-retired. The storage pool (fixed) and both CSVs are shown to be healthy and online.
I have a replacement drive on hand, but I'd like to also attemp to re-seat the existing failed/retired drive in case it was actually just a connection issue. How do I safely go about this, while also keeping the cluster up and running?
Sign in to answer