From mboxrd@z Thu Jan 1 00:00:00 1970 From: Moshe Yudkowsky 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 Message-ID: <47A7BA9D.3070501@pobox.com> References: <47A77CC0.10807@pobox.com> <20080204222521.GB7162@cthulhu.home.robinhill.me.uk> <47A798EA.40002@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <47A798EA.40002@pobox.com> Sender: linux-raid-owner@vger.kernel.org To: linux raid List-Id: linux-raid.ids 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