What you need
- The drive, and a note of what's printed on its label (make, model, capacity).
- An adapter. A USB-to-SATA/IDE adapter or dock lets you connect a bare drive. Older 3.5" drives need the adapter's separate power supply. Laptop-size IDE drives use a smaller 44-pin connector, so check your adapter supports it.
- Ideally, a write-blocker. A hardware write-blocker sits between the drive and your computer and physically stops anything being written. It's the safest option, but not essential if you're careful.
- Free space at least as large as the whole drive (not just the used space). An 80 GB drive makes an 80 GB image.
- A free imaging tool: FTK Imager, or ddrescue (via WSL or a Linux live USB).
Windows' "helpful" prompts
When you plug in an old drive, Windows may try to be helpful. Don't let it. Every one of these writes to the drive and can destroy exactly the history you're trying to preserve:
- "You need to format the disk in drive E: before you can use it." Click Cancel. This usually just means Windows doesn't understand the old filesystem.
- "Do you want to scan and fix?" or anything mentioning chkdsk: close it, don't fix.
- Disk Management "Initialize Disk" dialog: click Cancel.
- Don't open files on the drive in Explorer before imaging; even browsing can update timestamps or create thumbnail files.
To make Windows treat the disk as read-only, you can use diskpart from an administrator
prompt after finding the disk number (see below):
diskpart
list disk
select disk 2
attributes disk set readonly
exit
Replace 2 with your old drive's number, and double-check it. This is a software setting, so it's less certain than a hardware write-blocker, but it's much better than nothing. Use attributes disk clear readonly afterwards.
Finding the right disk
Windows numbers physical disks: PhysicalDrive0 is usually your system disk. Open PowerShell and list the disks before and after plugging in the old drive; the new entry is the one you want.
Get-Disk | Format-Table Number, FriendlyName, Size, PartitionStyle
Check the name and size against the drive's label. If anything is unclear, stop and unplug other external drives until only one candidate is left. Choosing the wrong disk is the most common way beginners lose data.
Imaging with FTK Imager
FTK Imager is a free forensic imaging tool for Windows (available from Exterro after a short registration).
- Run FTK Imager as administrator.
- Choose File → Create Disk Image…
- Select Physical Drive as the source (not "Logical Drive", which only copies one partition) and pick the disk you identified, e.g.
\\.\PHYSICALDRIVE2. - Under Image Destination(s), click Add… and choose Raw (dd). DriveArchive accepts raw images only, not E01.
- Fill in the evidence details if you like (they become notes; leave out anything personal), then choose a destination folder and a file name.
- Set Image Fragment Size to
0so you get a single file instead of many pieces. - Tick Verify images after they are created, then click Start.
When it's done, FTK Imager shows the hashes it computed and writes a small text log next to the image. Keep
that log with your notes. If the image comes out as drive.001, that's fine: it's a raw image and
you can rename it to drive.img.
Alternative: ddrescue
If the drive is making odd noises, is very slow or shows read errors, stop and use GNU ddrescue instead. It copies the healthy areas first and keeps a map so it can resume. It's a Linux tool, and there are two easy ways to run it from a Windows PC:
Option 1: a Linux live USB
Boot from a USB stick with a Linux distribution such as Ubuntu or a rescue-focused one. Nothing gets installed on your PC. Then follow the commands in the imaging guide:
lsblk -o NAME,SIZE,MODEL,SERIAL # find the drive, e.g. /dev/sdb
sudo ddrescue -d -n /dev/sdb drive.img drive.map
sudo ddrescue -d -r3 /dev/sdb drive.img drive.map
Option 2: WSL with usbipd
The Windows Subsystem for Linux can't see USB devices by default, but the free usbipd-win tool can pass a USB adapter through to it. In an administrator PowerShell:
usbipd list # find the BUSID of your adapter
usbipd bind --busid 2-3
usbipd attach --wsl --busid 2-3
Then, inside WSL (for example Ubuntu):
sudo apt install gddrescue
lsblk -o NAME,SIZE,MODEL,SERIAL
sudo ddrescue -d -n /dev/sdb drive.img drive.map
Some cheap adapters don't work well over usbipd. If it's unreliable, use a live USB instead.
Computing the SHA-256
The SHA-256 hash is the image's fingerprint. In PowerShell:
Get-FileHash .\drive.img -Algorithm SHA256
For a big image this takes a while. Copy the 64-character value from the Hash column; you'll paste it into the contribute form. Don't modify, mount or rename-and-edit the image afterwards, or the hash will no longer match.
What's next
- Unplug the drive and store it safely; you shouldn't need it again.
- Write down what tool and adapter you used and any errors you saw.
- Think about privacy: does the drive likely contain someone else's personal data? If so, or if you're unsure, plan to submit it as private.
- Now create a private torrent of the image so the archive can download it.