RAID & NAS · bench notes · RDG-2025-2064
Out of the Box, and Invisible to Windows.
A Seagate Personal Cloud in Lower Earley vanished off the family's network. Their neighbour, an IT man by trade, did the sensible things — pulled the disk, docked it over USB, and gave Windows whatever driver the forums reckon opens Linux partitions
. No change. The disk itself shows up fine. There is simply nothing on it to open.
Next came an offer to initialise the thing, which he sensibly declined. Older material had all been moved elsewhere long ago; these last eighteen months had not been.
Same fault on yours? Tell us what it is doing.
0800 6890668
What actually caused it.
His own work had already ruled one suspect out: the filesystem was sound. Two others remained. Consider the disk itself. Some sectors reply instantly. Others stall, and keep stalling, and an ordinary desktop has no strategy for that — it waits, abandons the read, and pronounces the disk empty. Then consider how the appliance stacks things up. A domestic NAS does not put something as plain as ext4 straight onto the platters. Its own partitioning goes down first, a volume manager sits on top of that, and the filesystem lives inside the pair. Perfectly good sectors can therefore reach a Windows driver that can make nothing of them.
What this one needed on the bench.
How every job runs →| Bench tools | Its part in this job | Why it is here |
|---|---|---|
| DeepSpar Disk Imager 4 | Carried on reading through the stalls that had beaten both of his machines | It maps the heads before anything is taken off, keeps to one platter side per pass, and stays in charge of the resets, the timeouts and the power |
| UFS Explorer RAID Recovery | Unpicked every layer standing between the platters and the folders this household used | Puts the array back together, then unpicks whatever volume manager the NAS laid over it |
| R-Studio Technician | Compared what the rebuilt shares held against what the household expected to find in them | Handles almost any file system, and puts an array back together off the images |
What the bench did.
Repeat his test, but on lab hardware
His findings all reappeared on the bench, this time with numbers attached. Some reads took a few milliseconds. Others took close to thirty seconds. Quick and slow were mixed across the surface in no pattern anybody could work out. An operating system will make two or three attempts at a disk behaving like that, and both of his machines had stopped precisely there.
Imaging hardware that does not stop at the first stall
Timeouts were shortened deliberately, and each stall answered with a reset rather than a wait. Much of the surface proved sound, which let the pass move along at a fair rate. Difficult ground was noted and left for later, then collected at the end, by which point nothing readable was still exposed.
Unpick the layers in the order the appliance laid them
Everything from there happened on the image, working in the sequence the appliance itself had used: partition table, then volume manager, then ext4. Done that way round, the shares came back in the shape the family recognised, eighteen months of photographs that exist nowhere else sitting exactly where they had always been.
What went back.
An ordinary external drive carried those eighteen months back, to stand beside the years already safe. Not one step the neighbour took did any harm: read-only throughout, and it saved us ground we would otherwise have had to cover. What this one wanted was imaging hardware plus a decode taken layer by layer, and no piece of software was ever going to manage it alone. That house keeps two copies of everything now.
If this sounds like yours, start here.
More RAID & NAS work, written up.
If that sounds like yours, stop there.
Post it in as it is, switched off. Looking costs nothing, and you get one fixed figure in writing before any chargeable work begins — £250 + VAT for a card or stick, £300 + VAT for a single drive, from £500 + VAT for RAID and NAS. On most jobs, nothing is charged unless your data comes back.