George, Thank you for staying with me. I tried both commands you sent to me, but still does not work. Here is my session: [root@server ~]# mdadm --stop /dev/md0 mdadm: error opening /dev/md0: No such file or directory [root@server ~]# [root@server ~]# mdadm --assemble --force /dev/md0 /dev/sdd2 /dev/sde2 mdadm: cannot open device /dev/sde2: No such file or directory mdadm: /dev/sde2 has no superblock - assembly aborted thank you, donald On Fri, Feb 19, 2016 at 3:43 PM, George Rapp <george.rapp@xxxxxxxxx> wrote: > On Fri, Feb 19, 2016 at 9:40 AM, George Rapp <george.rapp@xxxxxxxxx> wrote: >> On Thu, Feb 18, 2016 at 1:03 PM, d c <c866e866e@xxxxxxxxx> wrote: >>> >>> 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? >> > Sorry for replying to myself, but I noticed something further down in > the thread. Because the event counts on /dev/sdd2 and /dev/sde2 are > different, you may need to add --force to your mdadm --assemble > command. > > -- > 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
