Clone a Hard Drive That Won’t Boot: Full Guide

Yes, you can clone a hard drive that won’t boot, provided the drive is still physically recognized by your computer (in BIOS/UEFI or as a secondary drive). The cloning process copies all data sector-by-sector, bypassing the operating system, so a non-booting drive is often the most common reason to clone. This guide explains how to do it safely, what tools you need, and how to handle common obstacles.

Why a Drive Won’t Boot (But Can Still Be Cloned)

A drive that fails to boot usually has one of several issues: a corrupted boot loader, missing system files, a damaged partition table, or a failing physical component. If the drive spins up and appears in the BIOS or as a secondary drive in another system, the data is often still intact. Cloning works at the block level, reading every sector regardless of file system health, so it can copy a drive that Windows or macOS refuses to start from.

Common scenarios where cloning is the right fix:

• Windows shows “Bootmgr is missing” or a blue screen during startup.
• macOS shows a folder with a question mark or stops at the Apple logo.
• You upgraded hardware and the old drive won’t boot in the new machine.
• The drive has bad sectors but still responds to read commands.

If the drive makes clicking sounds, is not detected at all, or has severe physical damage, cloning may not work. In those cases, professional data recovery is the only option.

What You Need Before You Start

Cloning a non-booting drive requires a few essentials:

• A working computer (Windows, Mac, or Linux) with a free SATA port, USB port, or an external drive dock.
• A destination drive with at least the same capacity (or larger) than the source drive. It will be completely overwritten.
• An adapter or enclosure if the source drive is not internal (e.g., a USB-to-SATA cable for a 2.5″ laptop drive).
• Cloning software that can run from a bootable USB or from the working OS. Many tools offer free trials or free editions.

If the source drive is your primary drive in a dead computer, you can remove it and connect it to a second computer as a secondary drive. If you only have one computer, you can boot from a live Linux USB and clone from there, avoiding the need to install anything on the broken system.

How to Clone a Non-Booting Drive (Step-by-Step)

The general process is the same regardless of the tool you choose. Here’s a safe method using a bootable Linux USB (like Ubuntu) with the dd command, which is built-in and free:

1. Create a bootable USB with a Linux ISO (e.g., Ubuntu) using another computer. Tools like Rufus or balenaEtcher can do this.
2. Boot from the USB on the machine with the failing drive. Choose “Try Ubuntu” to load the live environment.
3. Identify the drives by opening a terminal and running lsblk. The source drive (e.g., /dev/sda) and the destination drive (e.g., /dev/sdb) will be listed. Double-check sizes and models to avoid overwriting the wrong drive.
4. Clone the drive with the command: sudo dd if=/dev/sda of=/dev/sdb bs=64K conv=noerror,sync status=progress. This copies every sector, including bad ones (marked as errors but skipped).
5. Wait until the command finishes. For a 1TB drive, this can take several hours. Do not interrupt it.
6. Shut down, remove the source drive, and boot from the destination drive. If the clone was successful, it should boot normally.

If you prefer a graphical interface, tools like Clonezilla (also bootable) or Macrium Reflect Free (runs from Windows PE) offer guided wizards. The principle is the same: select source, select destination, confirm, and wait.

Choosing the Right Cloning Method

There are two main cloning approaches: sector-by-sector (raw) and file-based (logical). For a non-booting drive, sector-by-sector is usually the safest because it copies the boot sector, partition table, and all data exactly. File-based cloning (like using Windows Backup or some commercial tools) only copies files and may miss the boot loader, which would not fix the boot problem.

Consider these factors when choosing a method:

• Bad sectors: Use a tool that can skip bad sectors (like dd with conv=noerror) to avoid hanging.
• Partition layout: If the destination drive is larger, you may want to expand partitions after cloning. Tools like GParted can do that.
• Operating system: Some tools only work with Windows or macOS. Check compatibility.
• Time: Sector-by-sector clones take longer because they read every sector, even empty ones. File-based clones are faster but may not preserve bootability.

For most users, a bootable Clonezilla or a Linux live USB with dd is the most reliable and free option.

Common Problems and How to Avoid Them

Cloning a non-booting drive can hit snags. Here are the most frequent issues and fixes:

• Drive not detected: Check connections, try a different SATA cable or USB port. If the drive is not spinning, it may be dead.
• Wrong drive selected: Always verify with lsblk or the tool’s disk list. Overwriting the wrong drive will destroy data.
• Clone hangs on bad sectors: Use conv=noerror,sync in dd to skip unreadable blocks. Some tools have a “skip bad sectors” option.
• Destination drive too small: The destination must be at least as large as the source’s used capacity, but ideally equal or larger. If it’s smaller, cloning will fail.
• Boot still fails after clone: This can happen if the boot loader was not copied correctly or the BIOS boot order is wrong. Check that the destination drive is set as the first boot device.
• File system errors: After cloning, run chkdsk (Windows) or fsck (Linux) on the destination to fix any logical issues.

Safety and Data Protection Tips

Cloning is a safe process if you follow basic precautions. The most important rule: never clone to a drive that contains data you want to keep. The destination drive will be completely erased. Always double-check the source and destination drive letters or device names.

Other safety measures:

• Back up any important data on the destination drive before starting.
• Use a UPS (uninterruptible power supply) if cloning a desktop, to avoid power loss mid-clone.
• If the source drive is physically failing, consider making a disk image first (a single file) instead of cloning directly, so you can retry without stressing the drive.
• Do not interrupt the clone process. If you must stop, restart from scratch.
• After cloning, verify the destination by booting from it before wiping the source drive.

Alternatives to Cloning

If cloning seems too risky or the drive is too damaged, consider these alternatives:

• Disk imaging: Create a compressed image file of the entire drive (e.g., with Clonezilla or dd). This is safer for failing drives because you can retry reads.
• File recovery: If you only need specific files, use recovery software like PhotoRec or TestDisk to extract them without cloning the whole drive.
• Repair the boot: If the drive is readable, you might fix the boot loader using Windows Recovery Environment or a Linux live USB, avoiding a full clone.
• Professional data recovery: For physically damaged drives, send them to a cleanroom service. This is expensive but often the only way to get data back.

Frequently Asked Questions

Can I clone a hard drive with bad sectors?

Yes, but you need a tool that can skip bad sectors, like dd with conv=noerror or Clonezilla’s “-rescue” mode. The clone may have missing data in those areas, so verify the result. If the bad sectors are in critical system files, the clone may not boot.

How long does it take to clone a non-booting drive?

It depends on the drive size and speed. A 1TB HDD can take 3-6 hours with a USB 3.0 connection. SSDs are faster, often under an hour. Using a direct SATA connection is quicker than USB.

Do I need to install the clone software on the broken computer?

No. You can boot from a live USB (Linux or Clonezilla) and run the software from there, without touching the broken drive’s operating system. This is the safest approach.

Can I clone a larger drive to a smaller one?

Only if the used space on the source is smaller than the destination’s capacity. Some tools can shrink partitions during cloning, but it’s risky. It’s better to use a destination drive of equal or larger size.

Will cloning a non-booting drive fix the boot problem?

If the problem is software-based (corrupted boot files, bad sectors in system areas), cloning to a healthy drive often fixes it. If the issue is hardware (failing motor, damaged controller), cloning may not help because the source drive cannot be read reliably.

Is it safe to clone a drive that is making clicking noises?

No. Clicking often indicates mechanical failure. Attempting to clone can cause further damage. Turn off the drive and seek professional data recovery instead of risking total data loss.

Related

• Hyper-V vs VMware: Key Differences Explained
• See If Someone Viewed Your Facebook Invitation
• Stop Windows 11 Adding Keyboard Layouts