From: Phil Turmel <philip@turmel.org>
To: shaun.reich@kdemail.net
Cc: Shaun Reich <predator106@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Raid5 boot failure after grow
Date: Wed, 20 Jul 2011 13:16:39 -0400 [thread overview]
Message-ID: <4E270D77.2090609@turmel.org> (raw)
In-Reply-To: <CADVynFDJO3_87ub-qfKK-0JWOB0nYK5P7=Au7fhcd+LEQkP=OA@mail.gmail.com>
On 07/20/2011 12:39 PM, Shaun Reich wrote:
> Do you happen to know how to rebuild it when I can't boot into it?
> I've tried booting into a livecd, mounting the raid volume and the
> /boot, running 'dracut --mdadmconf "initramfs-$(uname -r).img" $(uname
> -r)', copying the generated initramfs into the separate /boot
> partition, and making grub try to boot it, but it simply is not
> working.
I'm not familiar with Fedora, so I don't know what tools it has on the liveCD. Look for a tool that will mount everything for you then put you in a chroot. Then run the appropriate update-initramfs utility within the chroot.
> It seems to be because it's actually using the livecd's kernel and
> mods, which is rather unfortunate and would probably be why it is
> unable to boot. I've also tried simply doing it from the livecd (with
> the proper mdadm.conf) and then copying that file (from the livecd),
> into /boot. That at least gets me from a blank blinking cursor, to a
> message about a failed modprobe attempt for /lib/modules, prior to
> falling back to a shell.
>
> Ideas?
HTH,
Phil
next prev parent reply other threads:[~2011-07-20 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 22:43 Raid5 boot failure after grow Shaun Reich
2011-07-19 23:07 ` Phil Turmel
2011-07-20 16:39 ` Shaun Reich
2011-07-20 17:16 ` Phil Turmel [this message]
2011-07-21 10:06 ` Nikolay Kichukov
2011-07-21 15:18 ` Shaun Reich
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=4E270D77.2090609@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=predator106@gmail.com \
--cc=shaun.reich@kdemail.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.