Clone a Failing Server Hard Drive Without Reinstalling Complete Rescue Guide

Do not clone on a guess. Two minutes of checking tells you whether the disk surface is failing or something cheaper is wrong. Open CrystalDiskInfo (or your RAID/HBA tool) and look at the raw values of 05 (Reallocated Sectors), C5 (Current Pending) and C6 (Uncorrectable). On a healthy drive all three are zero. Any rising number means the surface is wearing out. Also check Event Viewer, System log, for disk errors (Event ID 7, 51 or 153) repeating over days.

One warning before you touch anything else: do not run chkdsk /r, a surface scan or a defragmenter on a suspect drive. Those tools force the drive to read and write every sector — exactly the stress that pushes a weak drive over the edge. Copy the data off first; run diagnostics afterwards, on the copy.

You need three things ready before the server goes down:

1. A healthy target drive — same size as the source or larger. Smaller is possible only when used space fits with room to spare (there is a full guide on this site for the smaller-SSD case).
2. A bootable cloning USB — the rescue is run from bootable media, not from inside the Windows that lives on the dying drive. Free bootable cloners such as Clonezilla or Rescuezilla, and Windows tools of the Hasleo Backup Suite class, all do this job; the video demonstrates the full route on screen.
3. A written note of the current setup — drive letters, share names, static IP, and which services must come back. Two minutes of notes save an hour of guessing later.

A clone copies whatever state the disk is in at that moment. If a database is mid-write while the copy runs, the copy holds a torn, half-written database. So before cloning:

1. Tell users the server is going down and close their sessions.
2. Stop database services (SQL Server, MySQL, accounting software services) and any backup jobs.
3. The cleanest clone of all is an offline clone — server shut down, boot from the cloning USB, copy disk to disk. Nothing is writing, so the copy is perfectly consistent.

If this server is a domain controller, read the cautions page on this site before booting the clone — a DC has extra rules (never let the old and new copies run together).

Boot from the cloning USB and start a disk-to-disk clone, source = the failing drive, target = the new drive. Double-check those two selections by size and model name — selecting the wrong direction overwrites the patient with the blank disk, and there is no undo.

1. If the tool offers a rescue / ignore-errors mode, use it: it copies all the healthy areas first and only retries the damaged spots at the end, instead of grinding on the first bad sector for hours.
2. Let it run. On a failing drive the copy slows down hard around the damaged areas — that is normal. Note the reported unreadable sectors; those files are already damaged on the original too.
3. Do not interrupt a clone halfway to "check something". A half copy is useless; a completed copy with some bad sectors is a working server.

When the clone finishes, shut down and disconnect the old drive completely before the first boot from the new one. Two drives with identical disk signatures and the same Windows installation must never boot together — Windows can shuffle drive letters, and on a domain controller two copies on one network is a genuine disaster.

1. Boot with only the new drive attached. First boot may be slow; let it settle.
2. Check the essentials: drive letters correct, shared folders visible, server services started, users can log in and open files.
3. Open the files that sat in the damaged areas if you know them — a file that fails to open was already lost on the old drive, not broken by the clone.