Case record · NAS & RAID · SDR-2025-1103
RAID Five, Racing the Clock.
The phone call was pure logistics: RAID 5 on a four-bay NAS
, disks already out of the chassis, and we can drive them over this afternoon
. Their tender had to be submitted by Monday morning. Before committing, they wanted a straight answer on cost and how long
— no salesmanship.
Seeing the same thing yourself?
0800 6890668
The translation.
A deadline alters the timetable, not the technique. Imaging is the one stage that stays: rebuilding straight off the customer's own disks to save a few hours puts the array itself at risk, and if a member dies partway through there is no second run. On a job against the clock, time is won by working in parallel — every disk on an imager at once instead of one after another — and by working out the geometry while those copies are still running, so nothing sits waiting.
Kit used on this job.
What happens in a case →| Platform | Its role in this case | Why we use it |
|---|---|---|
| Atola TaskForce 2 | Every member imaged at the same time — the largest single saving on offer | Images several drives in parallel — it turns a week on an array into a few days |
| PC-3000 Portable PRO | Firmware-level work taken to the disks instead of the disks to the bench | Identical firmware-level reach, in a box that goes to the disks |
| UFS Explorer RAID Recovery | Worked out stripe size, disk order and parity rotation from the copies | Understands how NAS volume managers really work, instead of a flat array |
In the lab.
All of them on imagers together
Every member went onto imaging hardware together as soon as they landed. Doing a multi-disk array one drive after another is what stretches three days into a week; enough imagers to run them side by side decides whether Friday is met or excused.
Work out the geometry as the copies run
The array's parameters came off metadata in the first images to finish, rather than waiting on the rest — stripe size, disk order, parity rotation and delay, each one checked against real data patterns instead of trusted to whatever the controller normally does.
Rebuild it, then check the things the firm needs soonest
The volume was assembled virtually over the images and its filesystem read. Checking followed the firm's own priorities — the shares they had flagged for Monday were verified first, so we could tell them those were safe before the rest had finished validating.
The result.
The rebuilt volume checked out and went back inside the weekend window. The practice started Monday on its own files — done quickly, with no stage left out to manage it, and the position reported at the end of each stage rather than promised at the start.
Similar cases on the index.
Also from NAS & RAID.
Does this sound like your own drive?
The rule holds as in every case above: switch it off, and let a free diagnosis come before any decision.