From: Scott Tablett <scott.tablett@netgis.com>
To: linux-raid@vger.kernel.org
Subject: Expanding partitions -> missing md on kernel load
Date: Tue, 20 Jan 2015 23:40:28 -0500 [thread overview]
Message-ID: <54BF2DBC.5000809@netgis.com> (raw)
Migrated two drive RAID 1 array (1.2 metadata) to larger drives (larger
gpt partitions)
Followed steps on https://raid.wiki.kernel.org/index.php/Growing
Before using mdadm --grow, the system reliably booted for months,
automatically discovering, mounting md.
Noticed one of next two steps involved fsck. I understand fsck should
be performed on unmounted filesytem. So, changed to runlevel 1 with
init 1 and unmount md.
Ran mdadm --grow --size=max on unmounted md. Command exited normally.
Ran fsck and resize2fs. Commands exited normally. Mounted md and
verified file system contents.
Did same steps for another md and restarted services with CTL+D. Noticed
resync taking place using Disk Utility. After resync completed, NFS
service froze, so decided to test reboot.
The two Expanded md (/var and /home) are no longer automatically
assembled by kernel. The md can be assembled by using mdadm --assemble.
Is there a way to get the two Expanded md to auto assemble again?
Tried using mdadm --create with one drive, but could not mount md (error
message). Guessing it needs formatting after --create?
reply other threads:[~2015-01-21 4:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54BF2DBC.5000809@netgis.com \
--to=scott.tablett@netgis.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).