Data Recovery Case File · Trust, Practice & Honest Limits · Two Problems, Not One
When the Machine You Work On Stops
Her enquiry was one sentence and carried an urgency the words understate. "My MacBook isn't recognising its OS and I'm eager to retrieve the data from it, as it's my self-employed work laptop." For someone employed, a dead laptop is an inconvenience handled by an IT department. For someone self-employed it is the business stopping — no invoicing, no client files, no email, no way to deliver work that is already late. That changes what a useful answer looks like, because there are two problems here and they have different timescales. Getting the data back and being able to work tomorrow are separate, and treating them as one is what turns a bad week into a bad month.
| Media | MacBook used as a sole business machine — system not loading; business-critical data held with no stated alternative |
| Reported situation | Machine failing to recognise its operating system · sole working machine for a self-employed business · data retrieval required · no alternative machine or access stated |
| Fault class | System volume or boot failure — user data typically intact; business continuity a separate and more urgent problem |
| Equipment used | Continuity routes established alongside the recovery · storage read write-blocked rather than through the machine · working data delivered in priority order early rather than as a single final handover |
The decode: separate the two problems, then solve them in the right order
Why "not recognising its OS" is usually good news: a machine that starts and cannot find or load a system has generally failed at the system volume rather than at the storage. The hardware powered, the firmware ran, the display works. In most of these the user data is entirely intact and sitting on the same drive as the damaged system. That is the likeliest position and it is a straightforward one.
Why continuity comes first even though the data feels more urgent: the practical point. A recovery takes as long as it takes, and waiting for it before doing anything else means every day of that is a day not working. The things that get a self-employed business running again are mostly independent of the failed drive: email is almost always on a server and reachable from any machine or phone; cloud storage, if any was in use, is reachable the same way; accounting and invoicing are usually online services; and client contact details often exist in a phone, a mail archive or previous correspondence. Signing into those from a borrowed or cheap replacement machine can restore most of a working day before the drive is even assessed.
Why the data should not be delivered as one final handover: where a recovery is needed, it is worth asking for the working set first — current client folders, active projects, anything with a deadline — rather than waiting for the complete result. That is a sequencing decision, and naming it costs nothing. Being handed the three folders needed this week, two days before everything else, is frequently the difference between a delayed job and a lost client.
What not to do while under pressure: the temptation is to reinstall the operating system to get working again quickly. On a machine whose user data is intact behind a damaged system, that is the fastest way to lose it — the standard reinstall route offers to erase the drive, sometimes prominently. Get the data off first, and repair afterwards.
The thing to fix afterwards: said plainly because it is the actual lesson. A sole trader with one machine and no backup has a business with a single point of failure, and this will happen again. Once the data is back, a synchronised copy of the working folders costs very little and turns the next occurrence into an afternoon rather than a fortnight.
On the bench
The continuity routes were established alongside the recovery rather than after it, since a business waiting on a bench is a business not trading — mail, cloud storage and online accounting are reachable independently of the failed machine and frequently restore most of a working day immediately. Storage was read write-blocked on native equipment rather than through the machine, taking the boot failure out of the question entirely. The working set was delivered first, in the priority order she named, rather than held back for a single complete handover, and the remainder followed.
The outcome
The continuity routes opened immediately and the working files delivered in priority order ahead of the full recovery. Free assessment, one fixed written figure including VAT; where a drive has to be opened or a chip removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone whose only work machine has stopped: these are two problems and the less obvious one is more urgent — get trading again while the recovery runs, because mail, cloud storage, online accounting and client contacts are all reachable from a borrowed machine and independent of the failed drive; a machine that cannot find its system usually has intact user data behind a damaged system volume; ask for your working set first rather than one final handover; and do not reinstall to get going quickly, because that route offers to erase.
Your only work machine has stopped
Get trading again while the recovery runs — don't wait for it. Most of what a small business needs is reachable without the failed machine: email lives on a server and opens from any browser or phone, cloud storage does the same, invoicing and accounting are usually online services, and client contact details are often in your phone or your sent mail. Signing into those from a borrowed or inexpensive laptop can restore most of a working day within an hour. Then ask for your recovery to be delivered in stages — the current client folders and anything with a deadline first, rather than everything at the end. That single request often makes the difference between a delayed job and a lost client. And don't reinstall the operating system to get going quickly: on a machine whose data is intact behind a broken system, the reinstall route offers to erase it.
Get working first, recover in parallel — call Glasgow Data Recovery on 0141 404 0294; read write-blocked rather than through the machine, working set delivered ahead of the full result.
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.