Principles
- Never write to the source. Don't mount it read-write, don't let your OS "repair" it, don't run chkdsk or fsck. Use a hardware write-blocker if you have one.
- Image the whole device, not a partition:
/dev/sdb, not/dev/sdb1. The partition table, boot code and gaps between partitions are part of the history. - Keep it raw. Don't compress or convert. Share the plain
.img/.dd/.raw. - Hash immediately and record the hash with your notes.
Connecting the drive
IDE/PATA and SATA drives connect easily through a USB adapter or dock. Prefer one that passes through the full capacity (some cheap IDE adapters truncate large drives or misreport geometry). SCSI drives need a SCSI controller; MFM/RLL and floppy media are best imaged at the flux level with tools like Greaseweazle or KryoFlux, then converted to a sector image.
On Linux, stop desktop auto-mounting before plugging the drive in. On macOS, disable auto-mount with
sudo defaults write /Library/Preferences/SystemConfiguration/autodiskmount AutomountDisksWithoutUserLogin -bool false
or use Disk Arbitration tools; on Windows, use a write-blocker or diskpart's
attributes disk set readonly.
Identifying the device
# Linux
lsblk -o NAME,SIZE,MODEL,SERIAL,TRAN
sudo hdparm -I /dev/sdX # model, firmware, LBA count (IDE/SATA)
sudo smartctl -a /dev/sdX # health, power-on hours
# macOS
diskutil list
Double-check the device name. Imaging the wrong disk in the wrong direction destroys data.
Imaging a healthy drive with dd
sudo dd if=/dev/sdX of=DRIVE.img bs=1M conv=noerror,sync status=progress
conv=noerror,sync keeps going past read errors and pads unreadable blocks with zeros so
offsets stay correct. With a large bs one bad sector zeroes the whole block, so on
anything with errors use ddrescue instead. On macOS, use /dev/rdiskN (the raw device) for
speed. dc3dd works like dd and also hashes and logs as it goes:
sudo dc3dd if=/dev/sdX of=DRIVE.img hash=sha256 log=DRIVE.log
Failing drives: GNU ddrescue
ddrescue copies the easy areas first, then returns to bad areas, and records progress in a map file so you can stop and resume:
sudo ddrescue -d -n /dev/sdX DRIVE.img DRIVE.map # pass 1: skip the slow bits
sudo ddrescue -d -r3 /dev/sdX DRIVE.img DRIVE.map # pass 2: retry bad areas 3×
Please include the .map statistics (rescued, bad areas) in your preservation notes. A partially recovered image is still valuable; say so.
Windows and forensic tools
FTK Imager (free) can create raw (dd) images: File → Create Disk Image → Physical Drive → Raw (dd), with "verify images after they are created" enabled. Leave the fragment size at 0 so you get a single file. Guymager on Linux does the same with a GUI. E01 output isn't accepted yet: choose raw.
Computing the SHA-256
sha256sum DRIVE.img # Linux
shasum -a 256 DRIVE.img # macOS
Get-FileHash DRIVE.img -Algorithm SHA256 # Windows PowerShell
Paste the 64-character hash into the submission form. We recompute it on the archive's copy; if the two don't match, something changed in transit and we'll ask you to check your image.
Sharing the image as a torrent
Images are far too large to upload to a website, so DriveArchive is a private BitTorrent tracker. You make a torrent of the image and keep seeding it; the archive's seedbox downloads it from you, and after review everyone with access downloads from all seeders. Your personal tracker URL is shown in the submission form and on your Download credit page.
mktorrent -p -l 24 -a 'https://tracker.drivearchive.org/announce?passkey=…' DRIVE.img
- Private (
-p, or the "private torrent" box in qBittorrent, Transmission or Deluge): clients then only talk to our tracker, never DHT or peer exchange. - One file: the image itself, not a folder.
- Piece size:
-l 24is 16 MiB, good for anything over ~100 GB; smaller images can use the default. - Open the .torrent in your client so it starts seeding, then upload the .torrent in the submission form. Keep seeding at least until your submission shows that the archive has a complete copy.
- Every drive of yours that is published earns download credit equal to its size, to spend on other drives.
Documenting the drive
- Photograph the label (model, serial, date code, jumper settings). You can redact the serial.
- Note where you got it, when, and anything the seller said about its past.
- Note the tools, adapter and command you used, and any errors.
- Before submitting, consider whether the drive may contain personal information. If you think it does, submit it as private or ask for reviewer guidance.