Data is written sequentially. Disk 2 is only utilized once Disk 1 is entirely full.
If you want, I can:
Original ldmtool fails if the LDM database is partially overwritten. The patched version adds --repair-jbod to rebuild the volume layout from remaining disk labels. jbod repair tools patched
Patching closes security holes but also kills many “grey area” repair methods. If you rely on JBOD tools for data rescue, don’t update blindly — and always keep a known-good backup of older binary versions.
Standard hardware RAID controllers with localized firmware are unaffected. However, any system relying on host-based diagnostic scripts, automated disk-wiping tools, or software partition repair utilities must be verified against vendor patch notes. Action Plan for Storage Administrators Data is written sequentially
When a linear JBOD array fails, the partition table or the Logical Volume Manager (LVM) metadata usually becomes corrupted. Because data is not striped across drives like RAID 0, files residing entirely on healthy disks are completely salvageable. However, if the metadata sector linking the drives is damaged, the operating system will label the entire pool as "RAW" or "Uninitialized."
Have you checked the of the individual drives? Share public link The patched version adds --repair-jbod to rebuild the
Recent updates have introduced "smart assembly" patches that can virtually reconstruct a spanned volume even if the metadata is shredded. DiskInternals RAID Recovery™ (v2026 Patched) : Now includes a specialized JBOD wizard