Hi Robin, On 2013-02-08, Robin Hill <robin@xxxxxxxxxxxxxxx> wrote: > "mdadm --remove failed" would probably be best. There's also > "mdadm --remove missing" which is the other option in these > circumstances. I apologize: I should have mentioned that I had already tried --remove failed. I tried --remove missing, but that didn't help either: # mdadm /dev/md127 --remove failed mdadm: hot remove failed for 8:96: Device or resource busy # mdadm /dev/md127 --remove missing mdadm: 'missing' only meaningful with --re-add I know the disk is dead, so I don't want to re-add it. The error from --remove failed is basically the same as --remove /dev/sdg except with the major:minor numbers instead of the device file name. When I do a --remove failed (or --remove /dev/sdg), I also get this error in dmesg: md: cannot remove active disk sdg from md127 ... That seems to imply that, while the disk is marked "faulty spare rebuilding" in the array, the array is not totally willing to give it up. --keith -- kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx -- 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
