From: Phil Turmel <philip@turmel.org>
To: "Randall C. Grimshaw" <rgrimsha@esf.edu>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: md prefered minor has been renumbered
Date: Mon, 28 Nov 2016 17:12:39 -0500 [thread overview]
Message-ID: <bccbeb42-82b5-87fc-aa74-11a34b8c9d8d@turmel.org> (raw)
In-Reply-To: <BC4985417D7F7B49B9AB545333BDB61B191FE20C@Exchange-MBX1.esf.edu>
On 11/28/2016 03:34 PM, Randall C. Grimshaw wrote:
> Phil:
> Thank you for responding, it is much appreciated.
> This is a recently assigned system so I must apologize for not having all of the history re fstab.
> But when I try to boot into the 'normal' system it continues to use the new numbering, the mounts fail, (the duplicate md122 obviously fails), and the system panics.
> I suspect the answer will have something to do with the command I googled: mdadm -A --update=superminor /dev/mdNEWNUMBER /dev/sd...
> .. but I have zero experience with it.
> Randall
Use 'blkid' to find out the UUIDs of your filesystems. Replace /dev/mdX
in your fstab with UUID="......"
then "mount -av"
Then you don't care what number shows up, and can resolve it at your
leisure.
Whatever mdadm.conf you end up with, run your distro's utility to get it
into your initramfs. On ubuntu, it is "update-initramfs".
Phil
next prev parent reply other threads:[~2016-11-28 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BC4985417D7F7B49B9AB545333BDB61B191FE1A2@Exchange-MBX1.esf.edu>
2016-11-28 17:26 ` md prefered minor has been renumbered Randall C. Grimshaw
2016-11-28 19:58 ` Phil Turmel
2016-11-28 20:34 ` Randall C. Grimshaw
2016-11-28 22:10 ` Randall C. Grimshaw
2016-11-28 22:12 ` Phil Turmel [this message]
[not found] ` <BC4985417D7F7B49B9AB545333BDB61B191FE29B@Exchange-MBX1.esf.edu>
2016-11-28 23:10 ` Phil Turmel
2016-11-29 1:12 ` Randall C. Grimshaw
2016-11-28 20:02 ` Wols Lists
2016-11-28 20:22 ` Phil Turmel
2016-11-28 20:39 ` Wols Lists
2016-11-28 22:06 ` Phil Turmel
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=bccbeb42-82b5-87fc-aa74-11a34b8c9d8d@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rgrimsha@esf.edu \
/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).