Casebook entry · NAS & RAID · EDR-2025-2914
Out of the Cloud Box, Still Unreadable.
When a Tiverton household's Seagate Personal Cloud dropped off the home network, the eldest son did what any sensible forum suggests: disk out, into a USB dock, and Windows fitted with a driver that is supposed to open Linux disks
. The verdict never changed — it sees the disk but there's nothing to open
. The older years had copies elsewhere; the last eighteen months of family photographs existed here only.
Sound familiar? Talk to us.
0800 6890668
In plain English.
His process was sound, and it usefully narrowed the field: Linux formatting was never the obstacle. Two things stood behind it instead. The disk was answering some reads and hanging on others, which starves any software running on a normal PC. And a home-cloud box does not simply format its disk in ext4 — it wraps its own partitioning and volume management around the Linux underneath, so a desktop driver can stare at perfectly healthy sectors and still meet nothing it recognises as openable.
The tools this job took.
See how your case runs →| System | The part it played | Why we rate it |
|---|---|---|
| DeepSpar Disk Imager 4 | Held the copy together through stalls that had beaten every desktop tool | Images by head map — timeouts, resets and power-cycling managed per head |
| UFS Explorer RAID Recovery | Decoded the appliance's private stacking of partitions and volumes | Reads NAS volume managers as the layered systems they are, not one flat array |
| R-Studio Technician | Matched the rebuilt library against the family's memory of what it held | Handles most filesystems; dependable RAID reassembly |
On the bench.
Confirm what the kitchen-table testing suggested
Bench tests told the same story from a better vantage point: reads that returned instantly sat beside reads that hung for half a minute, scattered without pattern. An operating system gives a drive like that a few polite retries and then abandons it — which is precisely what the dock-and-driver attempts had been running into.
A copy taken by kit that won't give up
The imager kept every timeout short and met each stall with a reset rather than a surrender, so the healthy majority came over quickly. Stubborn stretches were logged and skipped on the first pass, then revisited at the end, once nothing easy remained at risk.
Unwrap the appliance's layers until photographs appear
The image was then opened the way the box itself would have opened it: partition scheme first, the appliance's volume management next, and only then the ext4 filesystem folded inside. Read in that order, the shares stood up in their proper shape — and the eighteen months with no copy anywhere were sitting where they had always been.
How it ended.
The missing year and a half of photographs rejoined the rest of the library on a plain external drive. His experiments, being read-only, had cost nothing and told us plenty — the imaging hardware and the layer work did what no download was ever going to do.
More like this in the casebook.
More from RAID & NAS.
Sound like your drive?
Every case here points the same way: power the device down, take the free diagnosis, then make your decision.