The Client
Adaeze Chinonso is a civil engineer working as a consultant in Kano. She has spent the past three years building a documentation library for her practice — AutoCAD drawings, structural calculation spreadsheets, project photographs, client correspondence, and the accumulated institutional knowledge of a growing consulting practice. All of it lived on a single desktop PC in her home office. None of it was backed up anywhere else.
She knew she should back up. She had meant to back up. She had a portable hard drive sitting next to the machine that she used occasionally, when she remembered. On the night of March 14, 2026, she remembered that she hadn't backed up in eleven weeks when she came downstairs to find her PC dead, a burning smell in the room, and a blackened patch on the power strip where the surge had entered.
She called us at 7am the following morning. She was, in her words, "trying not to panic." We told her there was reason for measured hope, and to bring the machine to us before touching anything.
The Challenge
A power surge damage assessment is a triage exercise. When high-voltage power enters a PC through an unprotected outlet, it typically travels through the power supply first — the PSU takes the brunt and often dies. But depending on the surge magnitude and path, it can also damage the motherboard, storage devices, and GPU. The hard drive — where the data lives — may be intact, partially damaged, or completely destroyed, depending on exactly where the surge energy dissipated.
Adaeze's machine arrived at our workshop. We began disassembly and assessment immediately. The power supply was completely dead — visibly burnt internal components. The motherboard showed damage on the VRM circuit near the power input — a board replacement would be needed. The GPU appeared physically intact. The 2TB Seagate HDD — the critical component — showed no visible damage and no burn marks on the PCB.
The question was whether the platters and read heads inside the drive were intact. We connected it as a secondary device to a protected diagnostic machine. It spun up. It was recognised. The partition table was intact. We could see the folder structure.
The Consultation
We called Adaeze with the first update: the drive appeared intact and readable. We would attempt a full image copy to a new drive before trying to access any individual files — this is standard data recovery protocol. Attempting to read files directly from a potentially damaged drive risks further damage if the drive has bad sectors. Imaging the entire drive first creates a safe working copy.
The imaging process took nine hours. Sector read errors appeared in approximately 0.3% of the drive — meaning 99.7% of the data was cleanly readable. Those errors were clustered in the Windows system files, not in the data partition where her project files lived. When the image completed, we mounted it and navigated to her project folders.
Everything was there. Three years of AutoCAD drawings. Client files. Calculations. All 47GB of her project archive, intact and accessible.
The Recovery and Rebuild
We moved all recovered data to a new 4TB drive immediately. We also copied it to a USB drive so Adaeze could take it home that day — she did not need to wait for the full machine rebuild to have her data back. That handoff happened the afternoon of day two. She cried, briefly, when she confirmed all her project folders were present.
We then rebuilt the machine properly. Rather than simply replacing the failed components with equivalent parts, we recommended a full modern rebuild — the original machine was five years old and the motherboard was no longer supported by the manufacturer. Repairing it to the same specification seemed like a poor use of the opportunity.
Rebuilt workstation — ₦2.8 million:
- CPU: Intel Core i7-13700 — substantial upgrade from the original i5-8500
- RAM: 32GB DDR5
- GPU: NVIDIA RTX 3060
- Storage: 1TB NVMe (OS) + 4TB HDD (project files, mounted in rubber vibration-dampened tray)
- UPS: APC Smart-UPS 1500VA — pure sine wave, AVR, network-connected for shutdown management
- Surge protection: Legrand surge arrester installed at the wall socket, in addition to the UPS
We also configured Backblaze Personal Backup on the machine — 2TB of her project data backs up to cloud storage nightly, automatically, without requiring her to remember. First backup completed the day of delivery. She now has three copies of every project file: local NVMe, local HDD, and cloud.
The Result
Adaeze lost nothing. Eleven weeks of work that she had mentally written off during the 18 hours between the surge and us confirming the data was intact — all of it recovered. The rebuilt machine is faster than her original by a significant margin. AutoCAD loads from the NVMe in under 4 seconds.
More importantly, she has a backup infrastructure that runs without her active involvement. She has confirmed the cloud backup is running every week by checking the Backblaze dashboard. "I check it every Monday morning now," she told us. "It's like checking that the front door is locked. I just need to know it's there."
The UPS has activated three times since installation in Kano's variable power environment. Not one activation became a problem.
Key Takeaway
Data recovery from surge damage is possible — but it is not guaranteed, and the outcome depends heavily on how quickly you stop trying to use the damaged machine. Every attempt to boot a drive with potential platter damage risks further physical damage. The correct response to a surge event is: power off everything, do not attempt to turn the machine back on, and get it to a professional immediately. Speed matters. Panic does not.
The more important lesson is the one before the crisis: there is no excuse for a single-copy backup strategy in 2026. Cloud backup services cost less per month than a cup of coffee. Losing three years of work to a power surge is a preventable tragedy, and the prevention costs almost nothing.
Worried about your data protection or power resilience? Talk to our team before the problem happens. We design backup and power protection into every build.