From: Sachin Garg <sgarg.bugreporter@gmail.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Desperate: mdadm fails to assemble raid saying devices are busy.
Date: Sat, 21 Sep 2013 10:32:05 -0400 [thread overview]
Message-ID: <523DADE5.8050604@gmail.com> (raw)
Hi,
I am on Arch Linux. I have a 4 device RAID 5 of which 1 device is no longer
working. I am unable to assemble the raid.
The active devices are:/dev/sda2, /dev/sdb1, /dev/sdc2
The errors I get are like:
# mdadm -Avf /dev/md127
mdadm: looking for devices for /dev/md127
mdadm: no RAID superblock on /dev/dm-6
mdadm: no RAID superblock on /dev/dm-5
mdadm: no RAID superblock on /dev/dm-4
mdadm: no RAID superblock on /dev/dm-3
mdadm: no RAID superblock on /dev/dm-2
mdadm: no RAID superblock on /dev/dm-1
mdadm: no RAID superblock on /dev/dm-0
mdadm: /dev/sdc2 is busy - skipping
mdadm: no RAID superblock on /dev/sdc1
mdadm: no RAID superblock on /dev/sdc
mdadm: /dev/sdb1 is busy - skipping
mdadm: no RAID superblock on /dev/sdb
mdadm: no RAID superblock on /dev/sda3
mdadm: /dev/sda2 is busy - skipping
mdadm: no RAID superblock on /dev/sda1
mdadm: no RAID superblock on /dev/sda
I would like to know what is making these devices busy. I do not see any
indication from lsof or from the device mapper that these devices are being
used. I have even changed the initramfs and the fstab etc. to prevent this
array from being started at boot time - still unable to assemble it.
This array contains my /home and I do not know how to recover it.
Help please ...
Thanks,
Sachin
next reply other threads:[~2013-09-21 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 14:32 Sachin Garg [this message]
2013-09-21 17:44 ` Desperate: mdadm fails to assemble raid saying devices are busy Roger Heflin
2013-09-23 14:44 ` Sachin Garg
2013-09-23 15:43 ` Mikael Abrahamsson
2013-09-23 19:49 ` (Solved) " Sachin Garg
2013-09-24 2:09 ` Mikael Abrahamsson
2013-09-22 6:29 ` Mikael Abrahamsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=523DADE5.8050604@gmail.com \
--to=sgarg.bugreporter@gmail.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).