Data Recovery Case File · NAS & Network Storage · Do Not Repair the Box
When the Enclosure Fails, the Drives Are Still the Data and the Box Is Not
This enquiry asks whether to repair a unit or buy a new one, and the honest answer is neither. A four-bay network enclosure that reported one drive faulty, then failed during an attempted recovery — "all the disk lights went out, the display is either not working or flickering, and I can't communicate by connection or network." The unit has become the problem and it is not the objective: the content is on the drives inside it.
| Media | Four-bay network storage enclosure — one member reported faulty, enclosure subsequently unresponsive with drive indication absent, display intermittent and no communication over any interface |
| Reported situation | Network storage unit reporting a fault on one member drive · recovery attempted through the unit · attempt failing · all drive indicators extinguishing · display not functioning or flickering intermittently · no communication over direct connection or network · advice sought on repair or replacement |
| Fault class | Enclosure failure following a member fault — unit electronics implicated; member drives holding content independently of the enclosure's condition |
| Equipment used | Enclosure condition separated from member condition before any repair or replacement was considered · unit powered down and members removed for independent assessment · every member imaged individually write-blocked · array parameters and member order derived from the members themselves · array assembled offline and filesystem interpreted from the images |
The decode: three things the unit is, and only one of them matters
What a network unit actually provides: an enclosure, a controller and a network interface. It powers the drives, joins them into an array, and serves the result over the network — all of which is machinery around the data rather than the data itself.
Where the content lives: on the member drives. Every file written to the unit is written to those drives, and removing them from the enclosure does not alter what they hold.
Why that makes repairing the unit unnecessary: the objective is the content and the content is elsewhere. A repaired enclosure would let him reach his files through the network again, which is a convenience rather than a requirement.
Why buying a new unit does not help either: a replacement will not adopt the array. Fitting the drives into different hardware generally produces an offer to prepare them, which is the destructive outcome, and units of different makes do not recognise one another's arrangements at all.
Why the two failures are probably connected: a member drawing incorrectly can destabilise the unit that powers it. A drive that failed and then took the enclosure with it is a common sequence, and it explains why everything stopped at once.
What the flickering display indicates: the unit is receiving power and not running. Intermittent indication with no communication points at the enclosure's own electronics rather than at its software.
Why the attempted recovery is worth noting: whatever the unit was doing when it failed, it was working the drives. A recovery operation reads members end to end, and a set with one already-faulty member is being stressed throughout.
What that means for the surviving members: they have been worked hard recently. All should be assessed rather than assumed healthy, because the operation that failed was demanding on every one of them.
What is done instead of any repair: the members come out, each is imaged individually, and the array is assembled offline from those images with parameters derived from the drives. The unit takes no part in it.
What must not happen: no fitting the drives into a replacement unit, and no attempt to revive the enclosure with the drives inside. Both are ways of writing to members that need reading exactly as they stand.
On the bench
The enclosure condition was separated from member condition before any repair or replacement was considered — a network unit providing an enclosure, controller and network interface, all machinery around content that resides on the member drives and is unaltered by their removal. Replacement hardware does not adopt an existing array and generally offers to prepare the drives instead. A member drawing incorrectly can destabilise the enclosure powering it. Every member was imaged individually and the array assembled offline.
The outcome
Enclosure condition separated from member condition, members removed for independent assessment, and the array assembled offline from images. Free assessment, one fixed written figure including VAT, charged per drive, with 50% of parts and labour upfront and the balance only on successful recovery. The decode: neither repairing nor replacing the unit gets your files back. The content is on the drives, removing them changes nothing about what they hold — and a new unit shown them will offer to prepare them.
When the network unit fails rather than a drive
Don't repair the enclosure and don't buy a replacement to put the drives into. Your content is on the member drives and removing them from the box doesn't alter what they hold, so a working unit is a convenience rather than a requirement — while a different unit shown those drives will generally offer to prepare them, which is the destructive outcome. Have all the members assessed rather than just the one reported faulty, since whatever the unit was doing when it failed was reading them end to end and stressing every one.
Don't repair or replace it — call Manchester Data Recovery on 0161 871 0788; enclosure separated from member condition, every member imaged individually, array assembled offline from the images.
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.