Data Recovery Case File · Desktop Externals · The Log, Translated

Exit code 8 over an odd noise: reading a First Aid report the way a bench does — and recovering the photo library it couldn't verify

The enquiry's core was a document: the complete Disk Utility First Aid log, pasted verbatim, from a 2TB WD My Book that had fallen and now made "an odd noise." The log's arc, familiar to any Mac owner who's watched one scroll: repairing file system… performing fsck on the journaled HFS+ volume… checking the extents overflow file, checking the catalogue file… the volume could not be verified completely… file system check exit code is 8… file system verify or repair failed. Operation failed. Her target was specific — an iPhoto library — and her instinct to capture the log was better than she knew, because read correctly, over the fall and the noise, that report says more about hardware than filesystems. Line by line, then the recovery.

DeviceWD My Book Essential 2TB — fell; now produces an abnormal noise; primary target an iPhoto library
Supplied evidenceFull First Aid log: fsck_hfs run on a journaled (case-sensitive) HFS+ volume; verification incomplete; exit code 8; repair failed
Fault classImpact-degraded mechanics presenting upward as filesystem errors — the log auditing paperwork through a wounded reader
Equipment usedlaminar flow bench (impact inspection; donor parts) · ACE Lab PC-3000 Express + Data Extractor (imaging; HFS+ reconciliation)

The log, line by line — and the context it couldn't see

First Aid's transcript is honest but context-blind, so supply the context it lacked: a drop, then a noise. "Performing fsck_hfs" — the Mac's filesystem checker walking the volume's structures, which means reading, extensively, from a drive that had just been mechanically wounded; every subsequent line is filtered through that reader. "Checking extents overflow… checking catalogue" — the audit visiting HFS+'s central paperwork, the busiest structures on the disk. "Could not be verified completely" — the crucial line, and note what it doesn't say: not "the structures are wrong" but "I couldn't finish checking" — the sound, in log form, of reads failing beneath the audit. "Exit code 8" — fsck's formal verdict of corruption found and not repaired, which over healthy hardware means damaged paperwork, and over a dropped, noisy drive mostly means unreadable paperwork: the checker can't distinguish a torn page from a page the reader couldn't fetch. And "repair failed… restoring the original state" — mercifully, the tool declining to write much into a situation it couldn't parse. The bench translation of the whole document: the filesystem's condition is unknown because the mechanism under it is failing; treat the drive, then re-ask. The one line to act on wasn't in the log at all — it was the odd noise, which is the signal to stop running audits entirely: fsck's exhaustive reading is a marathon assigned to an injured runner.

The recovery — and why a photo library must come back whole

Under laminar airflow the fall's bill was assessed and paid — the impact-degraded mechanics addressed with donor attention — and the PC-3000 imaged the full 2TB at post-impact tempo, the busy central structures First Aid had stumbled through captured patiently and near-completely. On the image, the HFS+ volume was reconciled — and exit code 8's true meaning resolved, as the context predicted, into paperwork that was overwhelmingly intact once it could actually be read, needing only modest repair where the fall's damage had genuinely landed. Then the target, handled as the structure it is: an iPhoto library isn't a folder of pictures but a package — originals, edits, thumbnails and the database binding them — and it was extracted as a coherent whole, then verified the only way that counts: opened in the application, albums browsing, photos rendering, edits attached. Delivered on new media alongside the rest of the volume, with the log she'd supplied returned annotated — her document, translated.

Outcome

The photo library whole and opening, the volume substantially recovered, a First Aid transcript converted from alarming to explanatory — and two habits this page hands every Mac owner. Capture the log, don't obey it: pasting First Aid's output verbatim, as she did, hands a bench real evidence — but "repair failed" over a drive with symptoms is a referral, not an instruction to run it again; repeat passes just re-assign the marathon. And context outranks codes: the same exit code 8 means different diseases over healthy and wounded hardware, and the two facts First Aid never knew — the fall, the noise — were worth more than every line it printed. She supplied all three together. That's the model enquiry, and this was its reward.

First Aid failing on a drive with a history

One run maximum — then stop: fsck reads exhaustively, and over a dropped or noisy drive each pass is a full workout for failing mechanics. Copy the log verbatim (screenshots work) and note the context the tool can't see: falls, noises, what changed. Decline erase-and-restore suggestions; "can't verify" mostly means "can't read," and the paperwork is usually fine once the reader is treated. Photo libraries especially: they're packages, not folders — plan on whole-structure recovery, verified in the app.

First Aid failed and the drive's making noises?
Send the log and the story — call Bristol Data Recovery on 0117 332 1137; we'll treat the reader, then the pages.
Request a quote online →

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.

Call us — 0117 332 1137
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →