linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Expanding partitions -> missing md on kernel load
@ 2015-01-21  4:40 Scott Tablett
  0 siblings, 0 replies; only message in thread
From: Scott Tablett @ 2015-01-21  4:40 UTC (permalink / raw)
  To: linux-raid

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?

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-01-21  4:40 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-21  4:40 Expanding partitions -> missing md on kernel load Scott Tablett

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).