A QNAP RAID 5 reconfigured as RAID 0 in the management interface. The array reported itself as new, the redundancy that had protected it no longer existed, and every patient record the practice held was on the other side of it.
← All case files · from £500 + VAT
A veterinary practice ran patient records, imaging, appointments and billing on a six-bay QNAP configured as RAID 5. During a settings change the array was reconfigured as RAID 0 — a single confirmation, and the RAID 5 the practice had relied on for years no longer existed as far as the unit was concerned.
The QNAP presented six drives as a new RAID 0 volume with nothing on it. The practice stopped immediately rather than continuing to set the unit up, which is the reason this recovered.
creating a new array lays down fresh RAID descriptors. It does not erase six disks — that would take many hours rather than the moment it actually took.
the data and its parity were still physically present on the platters in their original positions, addressed by a description that had been replaced.
no bad sectors of consequence, no head or motor symptoms — this was entirely a logical problem.
no files copied to the new volume, which mattered more than anything else on this list.
The distinction that decides these jobs is between overwriting a description and overwriting content. A reconfiguration does the first. What does the second is what happens afterwards — every file written to the new array lands on top of the old one.
All six drives were imaged read-only before any analysis, and everything afterwards ran against those copies. The original RAID 5 geometry was then derived from the data itself rather than from any stored configuration: stripe size established by looking for structural repetition across members, drive order tested against known file-system structures until reassembly produced coherent metadata rather than noise, and parity rotation confirmed by verifying that reconstructed stripes resolved correctly.
With the layout proven, the RAID 5 was reassembled virtually from the images — entirely outside the QNAP, whose own firmware now described a different array altogether. The file system was rebuilt from the assembled volume.
Everything. Patient treatment records, case histories, diagnostic images, appointment schedules and billing data all recovered with folder structure intact, and returned on fresh storage.
Records were checked by opening them in the practice management software rather than merely counting files — a clinical record that lists correctly but will not load in the system it belongs to is not a recovery.
Changing a RAID level is not a conversion, it is a re-creation. The interface presents it as a setting; underneath, the unit writes a new array description over the old one and expects you to start again. The data survives that moment — and stops surviving as soon as anything is written to the new volume.
So the response matters more than the mistake. Stop, write nothing, and power the unit down. Keep the disks in bay order. RAID, NAS and server recovery starts from £500 +VAT after a free 48-hour diagnostic, and where clinical or personal data is involved we sign a data processing agreement as standard.
Drop the drive at our Oxford Science Park reception, or post it to us — it costs nothing to find out what happened. You get a written figure from the fixed bands before any work begins.