On Thu, Feb 18, 2016 at 1:03 PM, d c <c866e866e@xxxxxxxxx> wrote: > Ben, > > You are correct, sdd2 was tied up. This must have been caused by my > experimenting on mounting md0. > > [root@server ~]# cat /proc/mdstat > Personalities : [raid6] [raid5] [raid4] > md0 : inactive sdd2[2](S) > 48194880 blocks > . . . > > I rebooted the system and now both sdd2 and sde2 show "clean" with a > mdadm --examine. > > But I still can not assemble the raid: > > mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2 > mdadm: cannot open device /dev/sde2: Device or resource busy > mdadm: /dev/sde2 has no superblock - assembly aborted Donald - Try "mdadm --stop /dev/md0" before --assemble. Even though md0 is inactive, it still locks its component partitions. I don't see /dev/sde2 in the truncated output of /proc/mdstat - is it possible it's being used for something else other than the md0 array? -- 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
