No, just assemble with --force. >The other idea I have in mind is to - after a backup - recreate the >array using the initial configuration (raid-level 5, num-devices 3, >etc), and hope that the array can pick itself up again. > >Any thoughts much appreciated - thanks for helping out :) This is the last alternative, when you're sure the 2 disks are fine. Then just re-create the array replacing the /dev/3rd-drive by the word "missing". This won't change the data, it'll just re-write the superblocks. Then do read-only fsck -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html ======= If the data is really important, and worth a few thousand dollars or more, then try calling a company that specializes in data recovery. If it was me, then I would go pick up a few extra disks, boot to a CDROM LINUX image, and make raw block copies of the disks on the RAID and then try to reconstruct with the copies of the data. No going back if the recovery software doesn't work. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
