linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Jim Santos <iluvgadgets@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: "Missing" RAID devices
Date: Tue, 21 May 2013 11:31:29 -0400	[thread overview]
Message-ID: <519B9351.4050708@turmel.org> (raw)
In-Reply-To: <CAGPLN=viGgdw0MM18tiNxwjNadg0cj8xjntW3ne1qMNkfgocaA@mail.gmail.com>

Hi Jim,

On 05/21/2013 08:51 AM, Jim Santos wrote:
> Hi,
> I recently upgraded my 2 disk RAID-1 array from 1.5TB to 2TB disks.
> When I started I had 10 MD devices. Since the last partition was
> small, I removed the filesystems and deleted the associated RAID
> device. The I created two new devices and split the extra 500 GB
> between them. Everything was good until I rebooted. Now two of the
> raid devices are 'gone'.

[snip /]

> Notice the Preferred Minor numbers. It looks like the two new RAID
> devices took over the devices with the highest minor numbers.

Preferred minors are only used when assembling with kernel internal
auto-assembly (deprecated), which only works on meta-data v0.90, and
only if an initramfs is not present.  Boot-time assembly is otherwise
governed by the copy of mdadm.conf in your initramfs.

You appear to have failed to update your initramfs.  This is complicated
by your failure to avoid mdadm's "fallback" minor numbers that are used
when an array is assembled without an entry in mdadm.conf.

> I don't know what I did to get into this situation, but could really
> use some help getting out of it.

mdadm is called by modern initramfs boot scripts to assemble raid
devices as they are encountered.  If the given device is not a member of
an array listed in mdadm.conf, mdadm picks the next unused minor number
starting at 127 and counting down.  Mdadm must have found the members of
your new arrays before it found members of the arrays your old
mdadm.conf listed for md127 and md126.

Any time you update your mdadm.conf in your root filesystem, you must
remember to regenerate your initramfs so mdadm has the correct
information at boot time (before root is mounted).

To minimize future confusion, I recommend you renumber all of your
arrays in mdadm.conf starting with minor number 1.  Then update your
initramfs.  Then reboot.

Your fstab uses uuids (wisely), so you don't need any particular minor
numbers.  So you can and should avoid the minor numbers mdadm will use
as defaults.

HTH,

Phil

  reply	other threads:[~2013-05-21 15:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 12:51 "Missing" RAID devices Jim Santos
2013-05-21 15:31 ` Phil Turmel [this message]
2013-05-21 22:22   ` Jim Santos
2013-05-22  0:02     ` Phil Turmel
2013-05-22  0:16       ` Jim Santos
2013-05-22 22:43       ` Stan Hoeppner
2013-05-22 23:26         ` Phil Turmel
2013-05-23  5:59           ` Stan Hoeppner
2013-05-23  8:30             ` keld
2013-05-24  3:45               ` Stan Hoeppner
2013-05-24  6:32                 ` keld
2013-05-24  7:37                   ` Stan Hoeppner
2013-05-24 17:15                     ` keld
2013-05-24 19:05                       ` Stan Hoeppner
2013-05-24 19:22                         ` keld
2013-05-25  1:42                           ` Stan Hoeppner
2013-05-24  9:23                   ` David Brown
2013-05-24 18:03                     ` keld
2013-05-23  8:22           ` David Brown
2013-05-21 16:23 ` Doug Ledford
2013-05-21 17:03   ` Drew
     [not found]     ` <519BDC8C.1040202@hardwarefreak.com>
2013-05-21 21:02       ` Drew
2013-05-21 22:06         ` Stan Hoeppner

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=519B9351.4050708@turmel.org \
    --to=philip@turmel.org \
    --cc=iluvgadgets@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).