Data Recovery Case File · NAS & Network Storage · The Barrier Is the Software
Nothing Has Failed Except the Way In
His enquiry describes an obstacle rather than a fault. An old network unit unused for years: "it looks like the software to connect with it was redundant after an old version of Windows. It has two drives in it, which I think I set up as a mirror array — can't remember, to be honest. It contains recordings of the services of the church I attend, so it is not 'valuable' but is p"recious. The unit has not broken and neither have the disks — what has expired is a piece of client software, and the recordings do not live inside it.
| Media | Two-bay network storage appliance unused for several years — manufacturer management software no longer supported on current systems; array configuration not recalled; community audio recordings held |
| Reported situation | Appliance unused for several years · manufacturer's connection software no longer running on current operating systems · two drives installed · array configuration believed to be a mirror but not confirmed · recordings of community services held · contents required |
| Fault class | No device fault — access barrier at the management software layer; disks readable directly regardless of client support |
| Equipment used | Both disks removed and imaged write-blocked individually · array configuration determined from on-disk metadata rather than recollection · volume assembled offline from images · appliance filesystem interpreted after capture · contents delivered on current media |
The decode: what the software was for, and why it does not matter
What that client application actually did: found the unit on the network, displayed its status, and offered a way to configure it. It was a convenience layer over a device that was already there. The recordings were never inside the software — they were on the disks, in a filesystem, exactly as they are now.
So what its obsolescence costs him: the ability to administer the unit from a modern computer. That is genuinely inconvenient and it is not a data problem, because the disks come out and are read directly by anything that understands the format. The manufacturer withdrawing support for an application does not reach inside a hard drive.
Why this is worth stating clearly: a great many perfectly good network units are discarded for exactly this reason. The software stops running, the unit becomes unreachable, and people reasonably conclude the contents are locked inside. They are not, and the disks are readable long after the ecosystem around them has gone.
Why not remembering the configuration is fine: the disks themselves record it. Array members carry metadata describing the arrangement, the order and the parameters, and that is read off the disks rather than recalled. His memory is not needed and would not be trusted anyway, since a wrong assumption about the layout is a good way to assemble a volume incorrectly.
Why a mirror would be good news if that is what it is: a mirror holds a complete copy on each disk, so either one alone may contain everything — which makes the case straightforward and gives a second chance if one disk has aged badly.
What the years of storage add: the usual dormancy considerations. Lubricant thickens, heads resting on a platter can adhere, and two disks that were fine when the unit was retired may not both start now. That argues for acting rather than waiting, and for not repeatedly powering the unit to see whether it still works.
On what he called it: not valuable, and precious. That distinction is exactly right and it is the reason most of this archive exists — almost nothing in it had resale value.
On the bench
Both disks were removed and imaged write-blocked individually, the management software's obsolescence being a barrier to administering the unit rather than to reading its disks. Array configuration was determined from on-disk metadata rather than recollection — members carrying a record of the arrangement and order, which a wrong assumption would compromise. The volume was assembled offline from the images, the appliance filesystem interpreted after capture, and contents delivered on current media.
The outcome
Both disks imaged individually, the configuration read from on-disk metadata and the volume assembled offline. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: the software that stopped working was a convenience layer over a device that was already there. Your recordings were never inside it — they are on the disks, in a filesystem, readable long after the application stopped running. And the disks record their own array configuration, so not remembering it costs nothing.
Network unit you can't reach because the software is obsolete
Don't discard it — a great many perfectly good units are thrown away for exactly this reason. The application that stopped working was a convenience layer that found the unit on your network and let you configure it; your files were never inside it. They're on the disks, in a filesystem, and they stay readable long after the manufacturer stops supporting the software. Take the disks out and they can be read directly by anything that understands the format. Not remembering how you configured the array costs nothing either, because the disks carry a record of it. Do act rather than leaving it longer, though: disks that sat unused for years may not all start cleanly, and repeatedly powering the unit to check doesn't help.
The disks are still readable — call Guildford Data Recovery on 01483 901310; both imaged individually, configuration read from on-disk metadata, volume assembled offline onto current media.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.