From: Moshe Yudkowsky <moshe@pobox.com>
To: linux raid <linux-raid@vger.kernel.org>
Subject: Re: using update-initramfs: how to get new mdadm.conf into the /boot? Or is it XFS?
Date: Mon, 04 Feb 2008 19:23:41 -0600 [thread overview]
Message-ID: <47A7BA9D.3070501@pobox.com> (raw)
In-Reply-To: <47A798EA.40002@pobox.com>
I wrote:
> Now it's failed in a different section and complains that it can't find
> /sbin/init. I'm at the (initramfs) prompt, which I don't ever recall
> seeing before. I can't mount /dev/md/root on any mount points ("invalid
> arguments" even though I'm not supplying any). I've checked /dev/md/root
> and it does work as expected when I try mounting it while in my
> emergency partition, and it does contain /sbin/init and the other files
> and mount points for /var, /boot, /tmp, etc.
>
> So this leads me to the question of why /sbin isn't being seen. /sbin is
> on the device /dev/md/root, and /etc/fstab specifically mounts it at /.
> I would think /boot would look at an internal copy of /etc/fstab. Is
> this another side effect of using /boot on its own partition?
The answer: I managed to make a mistake in the configuration of grub, in
/boot/grub/menu.lst. I'd changed root= from /dev/md/root to
/dev/md/boot -- but I really need to include the *root* location, which
does not change, vs. the boot location, which is not relevant.
--
Moshe Yudkowsky * moshe@pobox.com * www.pobox.com/~moshe
"The central tenet of Buddhism is not 'Every man for himself.'"
-- Wanda
prev parent reply other threads:[~2008-02-05 1:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 20:59 using update-initramfs: how to get new mdadm.conf into the /boot? Or is it XFS? Moshe Yudkowsky
2008-02-04 21:08 ` Robin Hill
2008-02-04 21:09 ` maximilian attems
2008-02-04 21:53 ` Moshe Yudkowsky
2008-02-07 21:24 ` Bill Davidsen
2008-02-07 21:48 ` Bill Davidsen
2008-02-04 22:25 ` Robin Hill
2008-02-04 22:59 ` Moshe Yudkowsky
2008-02-05 1:23 ` Moshe Yudkowsky [this message]
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=47A7BA9D.3070501@pobox.com \
--to=moshe@pobox.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 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.