Hi Dush, On 02/11/2015 02:56 PM, Dush wrote: > Hi, > > I have a RAID 5 composed by 4x 500Go hdd but for some days, it's 'inactive'. > > I'm not raid expert and I prefer asking before doing an unrecoverable mistake... > > Is it possible to fix this raid (md126)? > Is it possible to recover data on it? Probably. Very good report, btw. > Do I have a disk to change or it's "just" a desynchronization between disks? One disk is now truly a spare (/dev/sdd3), which suggests you already tried to '--add' it and didn't get anywhere. Step one: collect some forensics for later. syslog or dmesg containing your failure events. Can be trimmed to just device and md stuff. "smartctl -x /dev/sdX" for each drive involved in the arrays. Then, we'll try the simple stuff. Make sure the array is stopped with: mdadm --stop /dev/md126 Then, force assemble it without sdd: mdadm --assemble --force --verbose --run /dev/md126 /dev/sd[bce]3 If that works, mount it and catch a backup of critical files. Then add your /dev/sdd3 back to the array and let it rebuild: mdadm --add /dev/md126 /dev/sdd3 It may not make it through the rebuild if you have the common timeout mismatch problem.[1] Show the dmesg and smartctl data (pasted inline is preferred) and we'll see. Phil Recent typical case: [1] http://marc.info/?l=linux-raid&m=142353387024935&w=1 -- 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
