Data Recovery Case File · NAS & Network Storage · Ask for the Delivery Format
What a Recovery Hands Back Should Be Chosen Before the Work Rather Than After
His enquiry asks for something more specific than his content, and he is right to. A failed network unit of an earlier generation holding a music collection, where he wants the data recovered "in such a format that it can then be transferred onto a newer unit." Delivery format is a decision, and stating it before the work begins is the difference between a usable result and a second project.
| Media | Single-drive network storage unit of an earlier generation — failed and inaccessible; content to be migrated to a current-generation replacement unit |
| Reported situation | Older single-drive network unit holding a music collection · unit failed and content inaccessible · replacement unit of a current generation intended · recovery sought in a form suitable for transfer to the replacement · guidance on cost requested |
| Fault class | Unit failure with drive condition unestablished — native volume format requiring interpretation; deliverable format determined by the intended destination |
| Equipment used | Destination platform established before the deliverable was defined · drive removed and read independently of the unit · imaged write-blocked at the block level before any interpretation · native volume format interpreted from the image · content delivered as a plain directory tree with structure and timestamps preserved |
The decode: why the format question matters, and what to ask for
Why a recovery does not automatically produce something portable: the drive holds a volume in the unit's own format. Older network units use filesystems that current machines and current units do not read natively, so an untouched drive handed back is no more usable than it was.
What the right deliverable is here: a plain directory tree on ordinary media. Files and folders in a format any machine reads, which a new unit ingests by simple copying — no interpretation, no import tool, no conversion.
Why that is better than transferring the drive itself: a newer unit will not adopt an older one's volume. Placing the old drive into new hardware generally results in an offer to prepare it, which is the destructive outcome.
What should be preserved alongside the files: the folder structure and the timestamps. A music collection is organised by its directory arrangement, and content delivered as a flat pile of files is technically complete and practically useless.
Why timestamps deserve a specific mention: they are easily lost in a copy and hard to restore afterwards. Asking for them to be preserved costs nothing at the time and cannot be retrofitted.
What else is worth specifying: the format of the destination media. A drive prepared for one platform may not be readable on another, and the new unit's own requirements should decide it.
Why the age of the unit is a practical rather than technical obstacle: older network filesystems are well documented. Interpreting them from an image is routine, and the unit's failure has no bearing on it once the drive is read directly.
Why the unit itself need not be diagnosed: the objective is the content. Whether the enclosure, its supply or its software failed is irrelevant — and repairing it would not be worth doing given a replacement is intended.
What determines the cost: the drive's condition rather than the unit's. A drive that images cleanly is a straightforward job; one with unreadable regions is not, and that is established by assessment.
What must not happen meanwhile: no fitting the old drive into the new unit to see what happens. That is the single action most likely to end this, and it is the obvious thing to try.
On the bench
The destination platform was established before the deliverable was defined — older network units holding volumes in formats neither current machines nor current units read natively, so an untouched drive is no more usable than before, while a newer unit shown an older one's volume generally offers to prepare it. Content was delivered as a plain directory tree with structure and timestamps preserved, timestamps being easily lost in copying and not retrofittable.
The outcome
The destination platform established before the deliverable was defined, the drive read independently of the unit, and content delivered as a plain directory tree. 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: asking for the format up front is the right instinct. A new unit will not adopt an old one's volume — what it will take is an ordinary folder tree it can simply copy in.
Recovering from one network unit to move onto another
Say what the destination is before the work starts, and ask for three things specifically: a plain directory tree on ordinary media that any machine reads, the folder structure preserved, and the timestamps preserved — that last one costs nothing at the time and can't be retrofitted. Don't fit the old drive into the new unit to see what happens, since a newer unit shown an older one's volume will generally offer to prepare it. The old unit itself needn't be diagnosed at all; cost follows the drive's condition rather than the enclosure's.
Don't fit the old drive into it — call Manchester Data Recovery on 0161 871 0788; destination established before the deliverable is defined, drive read independently, content delivered as a plain directory tree.
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.