RAID 0 Photos Are Visible After Rebuilding, but Every Recovered JPG Fails
Being able to list photo filenames from a reconstructed RAID 0 array is not proof that the image bytes are assembled correctly. If every exported JPG is unreadable, check the reconstruction parameters and the completeness of each disk image before scanning again.
In this r/datarecovery LaCie 2big RAID 0 case, one of two 6TB members failed. The owner imaged both disks, guessed a 128KB stripe size, and could see photos in DMDE, but none opened. A scheduled NAS backup had also stopped working.
Verify the Member Images Before Rebuilding the Array
An image file that has the same nominal size as the original disk can still contain unread sectors or missing regions. Check the OpenSuperClone log and actual successful-read percentage for both members; GNU ddrescue's mapfile documentation illustrates why image length and copied sectors are different facts.
Do not write a new RAID configuration, initialize the disks, or repeatedly read a failing member to test guesses.
Recheck Stripe, Order, and Offset
RAID 0 has no parity: missing portions of one member can damage files spanning those stripes. Even with good images, the wrong member order, stripe size, or starting offset may produce plausible filenames but corrupt extracted content.
Test small known JPEG samples under independently verified parameters using recovery software that supports virtual RAID reconstruction. If those still fail, assess whether the images have missing data and consider a specialist before more physical reads. The existing RAID recovery FAQ gives the broader limitations, not proof this particular array is reconstructable.