Data Recovery Case File · Mac & Apple Ecosystem · Good Diagnosis, One Write
Verbose Startup Told Him the Truth and the Check Wrote to It
His enquiry describes competent work with one consequential step in it. A 2013 desktop that will not boot and "appears to be the drive after running a verbose mode startup. I was able to run a filesystem check from single user mode, but that also failed. I assume you would need the hard drive removed." The verbose startup was free and told him everything; the filesystem check was not free, and it is worth knowing why.
| Media | Internal hard drive from a 2013 all-in-one desktop — host failing to complete start-up; filesystem check attempted from a minimal environment without success |
| Reported situation | Machine failing to boot · verbose start-up performed by the owner indicating a storage fault · minimal-environment access obtained · filesystem check executed and failing · owner anticipating drive removal · contents required |
| Fault class | Filesystem or drive-level failure with a repair attempt having intervened — post-check state to be established before reconstruction |
| Equipment used | Post-check state established before any reconstruction · drive removed and read independently of the machine · imaged write-blocked before further work · pre-check structures located from surviving copies on the image · files validated by opening |
The decode: one diagnostic that costs nothing and one that does not
What a verbose start-up gives you: the messages the machine normally hides behind its logo. Every stage of the boot process reports as it happens, and where it stops is where the problem is. It writes nothing, changes nothing, and costs nothing — it is purely a matter of watching a process that was happening anyway. For anybody trying to establish whether a fault is storage or something else, it is the single most informative free step available.
What it told him: that the failure is at the drive. That is a real diagnosis, arrived at properly, and it is more than most enquiries contain.
What a filesystem check does, and this is the part that is not free: it reads the filing structures, determines whether they are internally consistent, and repairs them where they are not. Repair means writing. Where entries cannot be reconciled, it resolves the inconsistency by removing them — because a coherent filesystem missing some files is usable and an incoherent one is not.
Why running it was completely reasonable: it is the standard remedy, it is what that environment exists for, and on a drive with a damaged filesystem and healthy hardware it frequently works. Nothing about the decision was wrong — the tool simply has a cost that its name does not convey, and "check" sounds like an inspection rather than an intervention.
Why its failure is informative anyway: a check that cannot complete generally indicates either damage beyond what it can reconcile, or a drive that is not returning data reliably enough for it to work. The second possibility matters more, because running a repair against a drive with read failures means it was working from partial information.
So the first thing established now: what the check reported and how far it got, because the drive's state afterwards is not its state before. Filesystems keep backup copies of key structures away from the primary set, and a repair typically rewrites the primary while leaving the duplicates — which is what a reconstruction reads.
Why his assumption about removal is right: a machine of that generation carries an ordinary internal drive, so it comes out and reads independently. The machine's condition stops mattering entirely.
The general note worth keeping: verbose start-up before anything else. It is free, it is fast, and it frequently answers the only question that matters.
On the bench
The post-check state was established before any reconstruction — a filesystem check resolving inconsistency by removing entries it cannot reconcile, so the drive's condition after it differs from its condition before, and a check run against a drive with read failures works from partial information. The drive was removed and read independently of the machine, that generation carrying ordinary internal storage. It was imaged write-blocked before further work, with pre-check structures located from surviving copies on the image.
The outcome
The post-check state established, the drive read independently of the machine and pre-check structures recovered from their surviving copies. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: your verbose start-up was the right move — it writes nothing and shows exactly where the boot stops. The filesystem check is a different kind of tool: "check" sounds like inspection, and it repairs by removing entries it cannot reconcile.
Diagnosing a machine that won't boot
Run a verbose start-up first — it shows the messages normally hidden behind the logo, reports every stage as it happens, and where it stops is where the fault is. It writes nothing and costs nothing, which makes it the most informative free step available. Be more careful with a filesystem check, though. The word "check" suggests an inspection, and the tool actually repairs: it reads the filing structures, decides whether they're consistent, and resolves inconsistency by removing entries it can't reconcile. On a drive that's also returning read errors, it works from partial information. If you've already run one, find out what it reported before anything else is attempted.
Stop there — call Guildford Data Recovery on 01483 901310; post-check state established before any reconstruction, drive read independently of the machine, pre-check structures recovered from their surviving copies.
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.