Data Recovery Case File · NAS & Network Storage · Discovery and Service Are Separate
The Unit Is Answering, So the Failure Is Above the Network
His enquiry describes a device that is present and unhelpful. A dual-drive network unit that worked until recently, where "I can see the drive on my network — just when I try to open it I keep getting connection failure." Being visible and refusing connections are two different layers reporting different things, and the combination places the fault inside the unit rather than anywhere on the way to it.
| Media | Dual-drive network storage unit — responding to network discovery; file service connections failing; internal volume state undetermined |
| Reported situation | Dual-drive network unit in normal service until recently · unit visible on the network · connection attempts to shares failing · no access to content · contents required |
| Fault class | File service failure above a functioning network stack — internal volume mount failure the leading cause; member disk condition to be established |
| Equipment used | Network visibility accepted as elimination of connectivity causes · service failure interpreted as internal volume state · no factory reset or reinitialisation permitted · members removed and imaged individually write-blocked · array assembled offline from images |
The decode: what visibility proves, and what opening a share requires
What appearing on the network establishes: the unit has power, its network interface works, it has an address, and it is responding to the discovery traffic that makes devices appear. Its operating system has started and its networking is functioning — a considerable amount confirmed in one observation.
Why that eliminates a whole family of causes: cables, switches, addressing, and the unit being dead are all ruled out. People spend a long time on those, and his single observation removes them.
What opening a share requires beyond that: the file service must be running, and it must have a mounted volume to serve. Those are separate from networking entirely — a unit can be perfectly reachable while having nothing to offer.
So what a connection failure means here: the unit answered the network and refused the request. It is not unreachable; it is declining, which is what a file service does when it has no volume behind it.
Why that is the leading explanation: a network unit whose internal volume fails to mount comes up normally in every visible respect. It powers, joins the network, appears in listings, and serves nothing — because the storage layer beneath the service did not come up.
Why that points at the disks rather than the unit: the electronics are demonstrably working, since they are running an operating system and talking to the network. What has not worked is the storage, which on a dual-drive unit means one or both members, or the arrangement between them.
What must be established about the configuration: whether the two disks mirrored each other or were combined. If mirrored, one surviving member holds everything; if combined, both are needed. That decides the whole scope and is readable from the unit or from the disks themselves.
What must not happen: no factory reset, and no acceptance of any offer to reinitialise or recreate the volume. Both are presented as remedies for exactly this symptom, and both write to the disks. If the unit offers to check or repair the volume, that too should be declined until the members have been imaged.
On the bench
Network visibility was accepted as elimination of connectivity causes — a unit responding to discovery having power, a functioning interface, an address and a running operating system, which removes cabling, addressing and device failure together. Service failure was interpreted as internal volume state, a file service declining connections when it has no mounted volume to serve despite the unit being reachable. No factory reset or reinitialisation was permitted, and members were imaged individually before offline assembly.
The outcome
Network visibility accepted as elimination, the service failure read as an internal volume state, and members imaged individually before any assembly. 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: visible and refusing are two layers. Appearing on the network proves power, interface, address and a running system — so the failure is above all of that, and a service with no mounted volume declines connections exactly like this.
Network unit you can see and cannot open
Don't factory reset it, and refuse any offer to reinitialise, recreate or repair the volume — all of those are presented as remedies for this exact symptom and all of them write to your disks. Your observation has already done useful work: appearing on the network proves the unit has power, a working interface, an address and a running operating system, which eliminates cabling, addressing and a dead device together. Opening a share needs more than that — a file service with a mounted volume behind it — so a connection failure from a visible unit usually means the storage didn't come up. Find out whether the disks mirrored each other.
Don't reset it — call Oxford Data Recovery on 01865 593000; visibility accepted as elimination, service failure read as internal volume state, members imaged individually before offline assembly.
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.