← Back to Runtime Software

RAID Reconstructor is Runtime's dedicated RAID-parameter analyzer, not a general recovery suite and not a bundled feature of GetDataBack Pro. It exists to solve one specific problem — determining the unknown geometry of a RAID 0 or RAID 5 array from its member disks — and hands off the resulting reconstructed image to a separate filesystem-recovery tool such as GetDataBack or Captain Nemo.

What it actually solves

When a RAID array's original controller, configuration or documentation is gone, the member disks alone don't say how they were combined. RAID Reconstructor analyzes the member disks or disk images to determine unknown start sector, block (stripe) size, drive rotation order and drive order — the parameters needed to reassemble the array's logical address space correctly. That analysis is the product's entire job; it does not itself recover files or navigate a file system.

RAID scope and array-size limits

Current official documentation confirms RAID 0 and RAID 5 specifically — not RAID 1, 6, 10 or nested/custom layouts. Documented member-count ranges are 2–16 drives for RAID 0 and 3–16 drives for RAID 5, with one missing member tolerated for RAID 5 thanks to parity. Broader RAID-level coverage, larger arrays, or nested layouts should not be assumed — those are the kind of case a broader tool such as UFS Explorer RAID Recovery or R-Studio is built to cover instead.

Source handling and output

RAID Reconstructor accepts either physical member disks or image files as input, and can direct its reconstructed output to a virtual image, an image file, or a physical destination drive. That flexibility matters for a difficult case: the member disks can be imaged first and the actual parameter analysis run against the images, keeping the original media untouched during the analysis itself.

Source safety

Runtime documents RAID Reconstructor as read-only with respect to the source members — parameter analysis and reconstruction don't write back to the original disks. As with any tool, that doesn't remove the physical read stress of scanning an already-unstable member drive; imaging a failing member before analysis is still the safer order of operations.

What comes after: filesystem recovery is a separate step

RAID Reconstructor's output is a reassembled block device or image — it doesn't browse files, recover deleted items, or interpret the file system on top of the array. Runtime's own documentation expects filesystem recovery and file access to continue in GetDataBack Pro or Captain Nemo once the array geometry has been solved. Don't expect RAID Reconstructor to behave like a complete recovery product on its own — it's the first of two steps.

Important limitations

RAID Reconstructor is a narrow, single-purpose tool: RAID 0/5 only, no broader RAID-level or NAS-vendor-storage-stack support, and no filesystem-level recovery capability of its own. For an unknown array outside RAID 0/5, a nested or vendor-specific NAS layout, or a case that needs RAID analysis and filesystem recovery in one product, a broader integrated tool is the better fit — RAID Reconstructor's value is specifically in solving unknown geometry for a straightforward RAID 0 or RAID 5 array before handing off to a separate recovery step.

Features verified September 2026 directly from Runtime Software's own RAID Reconstructor help documentation. Current pricing and licensing terms are not detailed in the sources reviewed for this listing — check runtime.org for the current price before buying.