Case file · NAS & RAID · MKD-2025-4914
Out of the Cloud Box and Still Unreadable.
When an Olney family's Seagate Personal Cloud stopped answering on the network, a neighbour who works in IT did the sensible thing: disk out, into a dock, and Windows fitted with the driver everyone recommends for Linux partitions
. The verdict never shifted — the disk is there, but there is nothing on it to open
. Windows offered to initialise it, and he had the sense to decline. The older years were copied elsewhere. The last eighteen months were not.
Same fault? Start here.
0800 6890668
Without the jargon.
His method was sound, and it ruled something out, which is worth having: Linux formatting was never the obstacle. Two other things were. The disk answered some requests instantly and hung on others, and software on an ordinary PC cannot cope with that — it waits, gives up, and calls the disk empty. Beyond that, a home cloud box does not simply put ext4 on a bare disk. It lays down its own partitioning and volume management first, with the filesystem folded inside, so a desktop driver can be looking at perfectly sound sectors and find nothing it knows how to open.
The kit this job needed.
See how a job runs here →| Kit | Why it was used | What it gives us |
|---|---|---|
| DeepSpar Disk Imager 4 | Kept the copy moving through the hangs that had stopped every tool on his PC | Maps the heads, then images each — resets, timeouts and power cycles controlled |
| UFS Explorer RAID Recovery | Unpicked the layers the box builds between the bare disk and its shares | Unpicks a NAS layer by layer instead of treating it as one flat array |
| R-Studio Technician | Checked the rebuilt shares against what the family remembered putting there | Copes with almost any file system; dependable array rebuilds |
What happened on the bench.
Confirm at the bench what the dock had hinted
Bench tests told the same story with better instruments. Reads that returned in milliseconds sat beside reads that hung for thirty seconds or more, scattered with no pattern to them. An operating system gives a disk behaving that way a handful of polite retries and then writes it off — which is precisely what happened in the dock, twice, on two different machines.
A copy made by hardware with no give-up in it
The imager held every timeout short and answered each stall with a reset rather than an abandonment, so the healthy majority came across quickly. Awkward stretches were noted and skipped on the first sweep, then revisited at the end, once nothing straightforward was still at risk.
Peel the layers back in the order the box built them
The image was opened in the order the appliance itself uses: partition table first, then the box's own volume management, then the ext4 filesystem sitting inside that. Taken that way, the shares came up in the shape the family knew, and the eighteen months held nowhere else were exactly where they had always been.
The outcome.
The missing year and a half went back to join the older photographs, on a plain external disk. The neighbour's tests had been read-only, so they cost nothing and told us plenty. Imaging hardware and a layer-by-layer decode did the work; no download was going to. The phone uploads now go two places.
Other jobs from the casebook.
See also RAID & NAS.
Does that sound like your device?
One lesson runs through the lot: cut the power, let us look for free, then decide with the facts in hand.