- Can you just image one disk from the server?
- Not use full y, on a striped or parity RAID: a single member holds only interleaved fragments, every file sliced through, and reads as gibberish (§2). The array must be reassembled from forensic images of every member, using the solved geometry (§4). The exception is a mirror (RAID 1), where one member is a readable whole, but even then the array metadata matters for currency.
- A disk failed and IT put in a new one and rebuilt the array. Is the evidence gone?
- Possibly, and this is the single most damaging thing that can happen (§5, Example 1): a rebuild recalculates and overwrites stripes. Caught early, enough original stripes may survive on forensic images of the members to reconstruct; run to completion, the overwritten data is gone. Stop any rebuild at once, image every member including the failed and replacement disks, and recover on the copies.
- The array has lost two disks. Can it be recovered?
- It depends on the parity: a single-parity array (RAID 5) survives one failure, not two, so two losses put it beyond reconstruction from the survivors alone (§5). A double-parity array (RAID 6) survives two. Where the array is beyond parity, partial recovery of what the survivors cover is attempted, and the estate, backups, replicas, end point s, carries the rest (Example 2, §8).
- Do we have to shut the business server down to preserve it?
- Usually not: live server storage is preserved by snapshots and live forensic acquisition that capture the relevant data while the system keeps running (§6), and by targeted, documented collection of the relevant shares rather than wholesale imaging. Downtime is reserved for where the array itself must be imaged member by member, which is planned to minimise disruption.
- The whole array is huge. Do we really need to image all of it?
- Often not: where it is the documents that matter, targeted collection of the relevant shares, home directories and mailboxes is the proportionate route (§6, guide 20). Full member-by-member reconstruction is reserved for where the array itself is in issue, its deleted data, its structure, or where the file system must be rebuilt. The method is sized to what the dispute actually needs.
- Is a reconstructed array admissible as evidence?
- Yes, when done properly: the members are imaged and hashed, the reconstruction is validated and its geometry and method documented so it can be explained and reproduced by another examiner (§4). A reconstructed logical volume is as sound as any other image; what must be avoided is the undocumented black-box reassembly that cannot be explained, and the rebuild-in-place that alters the original. cflab. u k · e-disc ove r y. u k ©2026 Computer Forensics Lab Ltd ·cflab.uk ·e-discovery.uk ·info@cflab.uk ·+44 (0)20 7164 6915 Page 16 of 18