From: Jake Thomas <thomasj10@georgefox.edu>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Device Unusable At Startup
Date: Sun, 12 Aug 2012 23:45:53 -0700 [thread overview]
Message-ID: <CACO8virEMpQU9+AmAAUkPVe=rG9cEJ-uPMLus1v-zX=dPORX3A@mail.gmail.com> (raw)
In-Reply-To: <20120813102020.172d3a93@notabene.brown>
Neil, you wouldn't believe it! I got it working!
Here's what I did:
I got to the Grub menu, hit "e" to temporarily edit my menu entry, and
added "break=premount" to the kernel (linux) line. This causes Linux
to drop you to a recovery shell before the real root is mounted (still
in the initial ramdisk). From there I did "mdadm -R /dev/md127". That
started /dev/md127. Then I entered "exit" to continue the booting
process.
Once fully booted, /dev/md127 no longer was active, even though I got
it active in the pre-mount environment.
From a "regular" (after the real root is mounted) environment, I ran
"sudo mdadm -R /dev/md127". This resulted in:
mdadm: failed to run array /dev/md127: Invalid argument
Then I restarted without doing a break, and "sudo mdadm -R /dev/md127"
resulted with the same error as last time.
Then I re-created the raid device with:
sudo mdadm --stop /dev/md127
(note that the file /dev/md127 still exists, it's just stopped, which
I find interesting.)
sudo mdadm --create /dev/md127 --level=1 --raid-devices=2 /dev/sda2 missing
Then I stopped all devices:
sudo mdadm --stop /dev/md127
(I only had that one device. I probably could have done "sudo mdadm
--stop /dev/md* if I really wanted to wipe them all out, if I had
more.)
Then I renamed mdadm to mdadm.moved:
sudo mv /sbin/mdadm /sbin/mdadm.moved
Then I restarted:
sudo shutdown -r 0
And my ramdisk hybrid raid device was up and running after startup!
One time I didn't stop /dev/md127 and restarted. That corrupted it.
I remade it, and as long as I stopped the device before shutdown, I was good.
Going into the pre-mount environment does not seem to be needed to
make it _NOT_ corrupted, but I wanted to tell the story how it was.
I changed fstab to use the raid device for /usr (specifying by uuid!),
added "/sbin/mdadm.moved --stop /dev/md*" very early in
/etc/rc.shutdown, and added "/sbin/mdadm.moved /dev/disk/by-uuid/[uuid
of my hybrid md device] -a /dev/ram0" to /etc/rc.local.
And now it works!
Yey!!!! Thanks so much Neil Brown and Mr. Green and all y'all!
Super Cheers,
Jake
next prev parent reply other threads:[~2012-08-13 6:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 23:59 Device Unusable At Startup Jake Thomas
2012-08-13 0:20 ` NeilBrown
2012-08-13 6:45 ` Jake Thomas [this message]
2012-08-13 6:51 ` Jake Thomas
-- strict thread matches above, loose matches on Subject: below --
2012-09-27 23:47 Jake Thomas
2012-09-28 11:11 ` Jan Ceuleers
2012-09-28 12:12 ` Jake Thomas
2012-09-28 16:24 ` Jan Ceuleers
2012-08-12 22:17 Jake Thomas
2012-08-12 22:39 ` NeilBrown
2012-08-05 7:13 Jake Thomas
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='CACO8virEMpQU9+AmAAUkPVe=rG9cEJ-uPMLus1v-zX=dPORX3A@mail.gmail.com' \
--to=thomasj10@georgefox.edu \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).