From: Ram Ramesh <rramesh2400@gmail.com>
To: Linux Raid <linux-raid@vger.kernel.org>
Subject: How to delay mdadm assembly until all component drives are recognized/ready?
Date: Tue, 9 May 2017 22:13:57 -0500 [thread overview]
Message-ID: <243ef080-c32f-f423-3a98-af70194f994b@gmail.com> (raw)
Today, I noticed that my RAID6 md0 was assembled in degraded state with
two drives in failed state after a pm-suspend and restart. Both of these
drives were attached toSAS9211-8I controller. The other drives are
attached to motherboard. I have not had this on a normal boot/reboot.
Also, in this particular case, mythtv recording was going on when
suspended and therefore as soon as resumed that used this md0.
Upon inspection, it appears (I am not sure here) that mdadm assembled
the array even before the drives were ready to be used. All I had to do
was to remove and re-add them to bring the array back to "good" state. I
am wondering if there is a way to tell mdadm to wait for all drives to
be ready before assembling. Also, if there is something that I can add
to resume scripts that will help, please let me know.
Kernel: Linux zym 3.13.0-106-generic #153-Ubuntu SMP
mdadm - v3.2.5 - 18th May 2012
Failed drives are HGST NAS and WD Gold with less than a year of usage.
So I doubt they are bad drives by any means.
Ramesh
next reply other threads:[~2017-05-10 3:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 3:13 Ram Ramesh [this message]
2017-05-16 4:15 ` How to delay mdadm assembly until all component drives are recognized/ready? Ram Ramesh
2017-05-16 21:25 ` NeilBrown
2017-05-16 23:49 ` Ram Ramesh
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=243ef080-c32f-f423-3a98-af70194f994b@gmail.com \
--to=rramesh2400@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.