Call us — 0113 322 3083
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →

Data Recovery Case File · NAS & Network Storage · No Redundancy, Two Warnings

NAS Data Recovery: RAID 0 With a Failed Disk and a Warning on the Second

His enquiry was well observed and slightly self-accusing, and the self-accusation can go. A two-bay NAS: "it recently had a disk failure and an advisory about a predicted failure on the second drive. However they're configured in RAID 0, so I'm unable to access the data on either drive currently." Then, reasonably puzzled: "I'm not sure why it's happened. It wasn't knocked or dropped and doesn't have the power disconnected without being shut down first. I shut it down and disconnected the power yesterday to reorganise my study, and when I plugged it back in I had the issue." Three things to give him. Why his careful shutdown did not cause this. Why a two-bay unit in RAID 0 turns one disk's failure into a total outage. And the reason this case is more urgent than most in the archive: the second drive is already warning, which means the window for a complete recovery is open now and closing.

MediaTwo-bay network storage unit configured as a striped array — one member failed, the second reporting a predicted failure; volume inaccessible
Reported situationUnit shut down correctly and powered off for relocation · failure reported on power-up · no impact or improper shutdown history · both members still physically present
Fault classStriped array with a failed member and a degrading second — no redundancy; complete recovery contingent on imaging both members before the survivor deteriorates further
Equipment usedBoth members removed and imaged individually, write-blocked and in parallel (Atola TaskForce 2) · failing member handled with prioritised timeout-controlled imaging (PC-3000 Express, Data Extractor) · stripe parameters derived from the images and the volume reassembled offline · contents verified and delivered

The decode: the power cycle, the configuration, and the urgency

Why his shutdown did not cause it: the reassurance is genuine and the mechanism is worth understanding. Drives in a network unit typically run continuously for years, spinning at a constant temperature, never stopping. A shutdown and a period without power lets everything cool and come to rest — and the next spin-up is the most demanding moment a hard drive experiences: the motor has to overcome static friction, the bearings must start turning from cold, and the heads must unpark and calibrate. A drive that has been quietly deteriorating while running can complete years of continuous service and then fail to survive its first restart. The power cycle did not damage anything; it revealed a drive that had already reached the end of its margin. Anyone who has restarted a long-running server knows this phenomenon by reputation.

Why RAID 0 turns one failure into total loss: striping splits every file into chunks written alternately across both disks, for speed and to present the combined capacity as a single volume. It carries no redundancy at all — no parity, no mirror. So when one member fails, the volume is not degraded, it is gone: every file is missing alternate pieces. This is worth stating plainly because two-bay home units frequently ship configured this way, or offer it as the default when capacity is the visible selling point, and many owners do not realise their two disks are a single point of failure rather than a safety net. He clearly did understand it — his enquiry says so — but the number of people who discover it at this moment is considerable.

Why this case is urgent: here is the part that matters more than either decode. His second drive is reporting a predicted failure, which means it is still readable and is telling him it will not be for much longer. In a striped array, the surviving member holds half of every file — so it is not a spare, it is half the archive. If it degrades further before it is imaged, the recovery loses ground on both fronts simultaneously. The correct action is therefore immediate and specific: power the unit down, remove both disks, and have both imaged now — the failed one for what it will still yield, and the warning one urgently while it is still cooperative. Waiting to see whether the NAS can be coaxed back is exactly the wrong instinct.

And what must not happen: no rebuild, no initialise, no letting the unit repair itself, and no putting a replacement disk in either bay. On a striped array those operations have nothing useful to rebuild from and can overwrite the very layout a reconstruction depends on.

On the bench

Both members came out of the unit and were treated as two patients with one deadline. They were imaged write-blocked and in parallel on the Atola TaskForce 2, with the warning drive given priority so that its remaining margin was spent on a complete image rather than on further service; the failed member was worked separately on the PC-3000 Express under Data Extractor, prioritised and under tight timeouts to take everything it would still give. Only then, with both copies secured, were the stripe parameters derived from the images — member order, chunk size and offsets established by analysis — and the volume reassembled offline, where a wrong hypothesis costs nothing. The contents were verified by opening and delivered.

The outcome

Both members imaged before either deteriorated further, the stripe reconstructed from the copies, and the contents verified and delivered. 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. Three things worth carrying: a correct shutdown does not cause this — the next spin-up is the most demanding moment in a drive's life, so a power cycle reveals a drive that had already reached its limit rather than damaging a healthy one; a two-bay unit striped for capacity has no redundancy whatsoever, so one failure is a total outage, and many owners do not realise that is how their unit was configured; and a predicted-failure warning on the surviving member makes the case urgent, because in a stripe that member is half of every file, not a spare.

Striped NAS with one disk failed and another warning

Power the unit down and take both disks out now. In a striped array the surviving disk isn't a spare — it holds half of every file — so a predicted-failure warning on it means your window for a complete recovery is closing, and it should be imaged before anything else is attempted. Don't let the unit rebuild, don't initialise anything, don't insert a replacement disk, and don't keep power-cycling to see whether it comes back: on a stripe there is nothing to rebuild from, and those operations can overwrite the layout a reconstruction needs. Label which bay each disk came from. And don't blame your shutdown — drives that have run continuously for years commonly fail on their first restart, because spin-up from cold is the hardest thing a drive ever does. The power cycle showed you a problem that already existed.

Striped NAS down with a warning on the second disk?
Image both today — call Leeds Data Recovery on 0113 322 3083; members removed and imaged in parallel, the warning drive prioritised, stripe reassembled offline from the 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.

0113 322 3083