Appearance
To recover data from legacy media, read it at the lowest level your hardware allows, capture that raw signal before interpreting it, and retry errors without ever forcing a fragile disk. For floppies that means a flux-level controller such as a Greaseweazle or Kryoflux; for hard drives and optical discs it means a recovery-aware imager like ddrescue. Decode the file system from the raw capture afterwards, never from the failing original. This guide takes you through the practical defaults and the mistakes that turn a recoverable disk into a lost one.
Why read at the flux level?
Standard drives interpret a disk as they read it, and if the format is non-standard, copy-protected or marginal, they simply report failure. A flux-level controller records the raw magnetic transitions instead, leaving interpretation to software you can swap and improve later. That is why flux is both a recovery technique and a preservation format: you keep the signal, not just one tool's reading of it.
What hardware should you set up?
For magnetic media, a Greaseweazle or Kryoflux board bridges a genuine floppy drive to USB. Match the drive to the media: a 5.25-inch drive for those disks, 3.5-inch for the later ones, and confirm the drive's jumpering. For hard drives use a forensic write blocker; for optical discs, a good external drive and patience. Photograph and label every disk before you touch it; that photo is the start of provenance and a record of physical condition.
How do you capture a floppy safely?
Take multiple revolutions so the software can reconstruct weak sectors, and write to a flux format such as SCP or KryoFlux raw:
bash
# Greaseweazle: read a 3.5-inch DD disk, 5 revolutions per track, to flux
gw read --revs 5 --tracks "c=0-79:h=0-1" jones_disk03.scp
# Then decode the flux to a usable file-system image
gw convert jones_disk03.scp jones_disk03.imgCapture first, decode second. If the decode fails, you still hold the flux and can try a different decoder without re-reading the fragile original.
How do you recover a failing hard drive?
Never run a verifying imager straight at a dying drive; use ddrescue, which skips ahead and logs unreadable regions in a mapfile so it can retry them later:
bash
# Pass 1: fast, no scraping, grab everything readable
ddrescue -n /dev/sdb legacy.img legacy.map
# Pass 2: retry hard sectors a few times
ddrescue -d -r3 /dev/sdb legacy.img legacy.mapThe mapfile is preservation metadata in its own right, documenting exactly which bytes could not be read.
Which tool for which medium?
| Medium | Recommended tool | Capture format |
|---|---|---|
| 3.5"/5.25" floppy | Greaseweazle / Kryoflux | SCP / raw flux |
| Zip, Jaz, LS-120 | Native drive + ddrescue | Raw image |
| Hard disk drive | Write blocker + ddrescue | Raw / EWF |
| CD-R / DVD-R | Quality drive + ddrescue | ISO image |
| Tape (DAT, LTO) | Matching drive + dd | Raw stream |
When a disk resists, slowing the read and increasing retries usually recovers more than brute force, which can finish the disk off for good.
What about physically degraded disks?
Mould, dust and binder hydrolysis are common in old media. Gentle, appropriate cleaning sometimes rescues a disk, but it can also destroy it, so for valuable items document the condition, capture what reads, and weigh a specialist over improvisation. Heat-sensitive tape may need careful conditioning before a single safe pass.
What do you keep afterwards?
Retain the flux or raw image as the master, the decoded file-system image, the extracted files, and a recovery log noting the drive, controller, settings, number of passes and the error map. Because the flux master can be re-decoded as tools improve, it is the artefact that protects you against today's software being the limit of today's recovery.
Key Takeaways
- Read at the lowest level available and capture raw signal before decoding.
- Use a Greaseweazle or Kryoflux for floppies; ddrescue for drives and discs.
- Take multiple revolutions or passes to reconstruct weak areas.
- Capture first, decode second, so the original is read as little as possible.
- Slow reads and more retries usually beat brute force on fragile media.
- Keep the flux master; it can be re-decoded as software improves.
Frequently Asked Questions
What hardware do I need to read old floppies?
A flux-level controller such as a Greaseweazle or Kryoflux connected to a working floppy drive. These read the raw magnetic flux, so they can recover disks and formats that a standard USB floppy drive cannot even mount.
Why capture flux instead of just copying files?
Flux imaging records the raw magnetic signal before any format interpretation, so you can re-decode it later with better software, recover copy-protected or non-standard disks, and preserve evidence of the physical encoding.
How do I handle a disk that gives read errors?
Image it with a recovery tool that retries and logs bad areas, such as ddrescue for drives or multiple-revolution reads on a Greaseweazle for floppies. Capture what you can first, then retry the gaps; never force repeated reads on a fragile disk.
Can I recover data from old optical discs like CD-Rs?
Often yes, even when they will not mount. Tools such as ddrescue combined with a quality drive can read past minor rot, and for badly degraded discs a slower drive and multiple passes recover more than a fast one.
Should I clean a mouldy or dusty disk before reading?
Gentle, appropriate cleaning can be the difference between a readable and an unreadable disk, but it carries risk. For valuable or visibly damaged media, document the condition and consider a specialist rather than improvising.
What do I keep once recovery succeeds?
Keep the flux or raw image, the decoded file-system image, and any extracted files, plus a log of the drive, tool, settings and error map used. The flux image is the master because it can be re-decoded as software improves.