Data Recovery Case File · NAS & Network Storage · A Container Without Contents
A Successful Connection to a Block Target Says Nothing About the Volume Inside It
This enquiry distinguishes two things most accounts merge. A network unit whose block storage target is in an error state, where connecting "is a success" but "no disk is presented" — with the objective being the virtual disk files needed to rebuild the machines they contained. Connection and content are separate layers here, and success at the first says only that the network path works.
| Media | 3TB block storage target on a network unit — target reporting an error state; connection succeeding while no volume is presented to the host; virtual machine disk files sought |
| Reported situation | Network unit hosting a block storage target of 3TB · target reported in an error state · connection from the host succeeding · no disk presented following connection · volume therefore not mountable · virtual machine disk files required to rebuild the machines |
| Fault class | Block target connecting with volume metadata unreadable — container present on the underlying array; virtual disk files recoverable from the container independently of the unit's own presentation |
| Equipment used | Connection success separated from volume presentation before any conclusion was drawn · no repair or re-initialisation permitted on the unit · member drives removed and imaged individually write-blocked · underlying array assembled offline and the container file located within it · virtual disk files extracted from the container and validated by mounting read-only |
The decode: three layers, and which one has failed
What the arrangement actually consists of: layers inside layers. The unit holds an array; the array holds a filesystem; the filesystem holds a large container file; the container holds a volume; the volume holds the virtual disk files — five levels between the drives and the objective.
What connecting to the target proves: the outermost layers work. The unit is running, the network path is good, authentication succeeded and the target responded — genuine progress and nothing about the content.
Why no disk being presented follows a successful connection: the host then asks what volume is inside. It reads the volume's own structures through the connection, and if those cannot be interpreted it presents nothing.
Why that places the fault precisely: above the network and below the connection. The container is reachable and the volume inside it is not readable, which is a filesystem-layer problem in a very specific location.
Why the error state on the target is consistent with that: the unit has noticed something wrong with the container. An error state is the unit reporting that its own checks failed, rather than a statement about the underlying drives.
What that means for the drives, and it is the encouraging part: they may be entirely healthy. A container file is data on a filesystem like any other, and a problem with its contents does not implicate the array beneath.
Why the objective is well chosen: he wants the virtual disk files rather than a working target. Those are ordinary files inside the container, and extracting them does not require the unit to work at all.
Why the work happens away from the unit: members are imaged individually and the array assembled offline. The container is then located as a file and opened as a volume in a controlled environment, with nothing depending on the unit's own presentation.
Why virtual disk files recover comparatively well: they are large and written contiguously. A container holding a small number of very large files fragments far less than a general-purpose volume, so even partial structural damage frequently leaves them intact.
What must not happen: no repair of the target, no re-initialisation and no reconnection attempts. A unit offering to correct an error state will rewrite the container's metadata, which is what is being reconstructed.
On the bench
Connection success was separated from volume presentation before any conclusion was drawn — a successful connection establishing that the unit runs, the network path is good and the target responded, after which the host reads the volume structures inside the container and presents nothing if they cannot be interpreted. That places the fault above the network and below the connection. A container is a file on the array's filesystem, so its contents failing does not implicate the drives. Virtual disk files were extracted from the container and validated by mounting read-only.
The outcome
Connection separated from presentation, no repair permitted on the unit, and the container located within an offline assembly of the array. Free assessment, one fixed written figure including VAT, charged per drive, with 50% of parts and labour upfront where a drive has to be opened. The decode: connecting successfully only proves the path works. The volume inside your container is what cannot be read — which is a filesystem problem in a specific place, and it does not implicate the drives underneath.
A block target that connects and presents nothing
Don't let the unit repair the target or re-initialise it, since correcting an error state rewrites exactly the metadata a reconstruction reads. Separate the layers: a successful connection proves the unit runs and the network path works, after which the host tries to read the volume inside the container and presents nothing when it can't. So the fault sits above the network and below the connection. Your drives may be entirely healthy. Virtual disk files also recover well, being large and written contiguously.
Don't repair it — call Manchester Data Recovery on 0161 871 0788; connection separated from presentation, members imaged individually, container located in an offline assembly of the array.
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.