Case Study — Apple MacBook
Stuck on the Apple logo. Twice, for two different reasons.
A 2011 MacBook came in dead on the Apple logo. The hard drive was failing — and once that was solved, a second, unrelated fault kept the machine from booting anyway.
The case
A MacBook that wouldn't boot, for more than one reason.
This is a common Apple MacBook symptom with an uncommon cause underneath it.
A 2011 MacBook arrived that wouldn't boot at all — stuck on the Apple logo. This is one of the two failure patterns we see most often on MacBooks of this era: either the hard drive itself fails, or a faulty internal hard drive cable causes the drive to drop out or makes OS X slow and unstable. This machine had both problems stacked together — the drive had started developing errors, and a faulty SATA cable had let that corruption run further than it should have.
As with every drive that arrives showing errors, the first step was not to work on it directly. It was imaged with a hardware-based imaging tool, so every recovery step from that point on happened on a copy — never on the only surviving copy of the client's data.
What we did
From imaging to a working Mac.
- 01
Image first
The MacBook's hard drive was cloned with a hardware-based imaging tool before anything else was attempted, so all further work happened on a safe copy rather than the original, still-failing drive.
- 02
Assess the damage
The image showed only a couple of bad sectors, but the file system structure was damaged. DiskWarrior was used to reconstruct most of the data structure — but the MacBook still wouldn't boot, now throwing kernel errors.
- 03
Rule out the drive
An OS X recovery was attempted and still failed on the Apple logo. To take the ageing, cable-troubled hard drive out of the picture entirely, the MacBook was upgraded with a solid state drive and given a fresh install of OS X Mavericks — which booted cleanly.
- 04
Find the real second fault
The moment Apple's Migration Assistant was used to bring the user's data and apps across, the same boot failure returned. A fresh Lion install with the same data migrated in worked fine — pointing to something inside the user account itself, not the hardware, not the OS version. Repeated attempts to carry that account up through Mavericks, then Sierra and El Capitan, all reproduced the same failure on boot.
- 05
Isolate and rebuild
With the drive and the OS both cleared, the fault was the OS X user account. A fresh OS X install went onto the formatted drive, and this time Migration Assistant was used to bring across only the apps and preferences — not the full user account. That worked. The client's personal files — documents and pictures — were then copied in separately, by hand, into the newly created account.
The outcome
A working MacBook, with everything the client needed back.
The MacBook ended up on a solid state drive, running OS X Mavericks with every app working, and with the client's documents and pictures restored. There was no Time Machine backup to fall back on, so every part of this ran through the drive image and hands-on reconstruction rather than a simple restore.
The full process — imaging, file system reconstruction, isolating a user-account fault that survived four separate OS installs, and rebuilding the account cleanly — took around three days from start to finish. The total cost came to approximately £450 including VAT, covering the SSD upgrade alongside the data recovery itself.
The lesson underneath the detail: a boot failure on an ageing MacBook is often more than one problem wearing the same symptom. Treating the drive fault and stopping there would have left this machine unusable.
Power it down and talk to a specialist before trying another reinstall. We'll image it safely first and give you a fixed quote before any recovery work begins.