On Sat, Jan 28, 2017 at 6:33 PM, Roman Mamedov <rm@xxxxxxxxxxx> wrote: > On Sat, 28 Jan 2017 18:29:32 -0500 > George Rapp <george.rapp@xxxxxxxxx> wrote: > >> Attempting to re-add /dev/sdg4 to the array fails on a busy device: >> >> # mdadm --manage /dev/md4 --re-add /dev/sdg4 >> mdadm: Cannot open /dev/sdg4: Device or resource busy > > You need to remove it first > > mdadm --remove /dev/md4 /dev/sdg4 > > or > > mdadm --remove /dev/md4 faulty > > But honestly I am not sure if simply removing and re-adding will bring your > reshape back to its working order at this point. > > Also you should figure out why did it fail in the first place. Check > SMART, check dmesg further back rather than a few lines only. Maybe the disk > needs a replacement, not just a blind re-add. Perhaps not surprisingly, the --remove command also hung. /dev/sdg4 apparently suffered an uncorrectable read error. Entire dmesg output (2172 lines) is at https://app.box.com/s/7brp7c53a51zw4ez5to0m12oc5hxeq92 for your reference. Since none of the mdadm commands will respond, I'm thinking we need to reboot the machine at this point to do any more diagnostics. Thanks for your quick replies! -- George Rapp (Pataskala, OH) Home: george.rapp -- at -- gmail.com LinkedIn profile: https://www.linkedin.com/in/georgerapp Phone: +1 740 936 RAPP (740 936 7277) -- 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
