RAID & NAS · lab notes · HUL-2025-0914
I Took the Disk Out and Windows Saw Nothing.
A Seagate Personal Cloud in Bricknell dropped off the home network. A neighbour who does IT for a living worked through it in a sensible order: the disk out, into a USB dock, then Windows given whatever driver the forums recommend for reading Linux partitions
. Nothing changed. The disk is plainly there. What is not there is anything to open.
Windows put up its offer to initialise, which he turned down, correctly. Older files had been copied elsewhere years ago. The last eighteen months had not.
Sounds like yours? Ring us.
0800 6890668
What causes it.
His work had already cleared the obvious culprit. The filesystem was sound. Two other things were not. Take the drive itself first. Some sectors come back at once. Others hang and never answer, and a desktop PC has no plan for that. It waits, drops the read, and reports an empty disk. Then there is how the appliance stacks things up. A home NAS box puts nothing as plain as ext4 on the platters. It writes its own partitioning, adds a volume manager over that, and keeps the filesystem inside the two. A Windows driver can be reading good sectors and make sense of none of it.
The tools this one needed.
The steps we follow →| The gear | What this one did | Why we have it |
|---|---|---|
| DeepSpar Disk Imager 4 | Carried on reading through the stalls that had halted both his computers | Grades each head first, reads one surface at a time, and keeps resets, timeouts and power under control |
| UFS Explorer RAID Recovery | Took apart each layer between the platters and the folders the family knew | Puts the array back together, then unwinds the volume layers a NAS lays over it |
| R-Studio Technician | Checked the rebuilt shares against what the household said should be there | Handles almost any file system, and puts RAID sets back together |
The stages.
Repeat his test, this time on lab hardware
The bench found what he had found, with numbers against it. Some reads came back inside a few milliseconds. Others sat there for close to thirty seconds. Fast and slow were mixed together over the whole surface, in no order we could work out. An operating system gives a disk like that two or three tries and then quits. Both of his machines did exactly that.
Imaging hardware that refuses to quit
Timeouts were cut short on purpose. Every stall was met with a reset rather than a wait. That let the good part of the surface, which was most of it, transfer at a fair rate. Awkward areas were noted and left alone at first, then picked up at the end, once nothing readable was still exposed.
Undo the layers in the order the box laid them
Everything after that was done on the image, in the sequence the appliance had used: partition table, then the volume manager, then ext4. Worked through that way, the shares came back in the layout the family recognised, and eighteen months of photographs held nowhere else sat exactly where they had always sat.
How it finished.
Those eighteen months went back on a plain external drive, alongside the older years. The neighbour had done no damage at all. Every step he took was read-only, and it cut down what we had to look at. The answer here was imaging hardware, and a decode worked one layer at a time. Software alone was never going to get there. The phones in that house now copy to two places.
What people read after this.
Other RAID & NAS cases.
Is yours doing the same?
Turn it off. Send it to us. The diagnosis comes first. It says which files are still readable and which are not.