From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Tomasz Nowak <tnowak@netventure.pl>
Subject: Re: [linux-lvm] Errors after adding new md pv (boot only?)
Date: Thu, 24 Feb 2011 10:50:47 +0000 [thread overview]
Message-ID: <4D663807.9010802@redhat.com> (raw)
In-Reply-To: <ik41em$6rl$1@dough.gmane.org>
On 02/23/2011 10:24 PM, Tomasz Nowak wrote:
> md: ... autorun DONE.
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
>
> ------------------------ and here come the problem -----------------------
>
> Scanning logical volumes
> Reading all physical volumes. This may take a while...
> Couldn't find device with uuid qeDW2q-nq5b-Yh5U-5sKY-7Rkd-1UXh-LAxL8j.
> Found volume group "vg0" using metadata type lvm2
> Activating logical volumes
> Couldn't find device with uuid qeDW2q-nq5b-Yh5U-5sKY-7Rkd-1UXh-LAxL8j.
> 8 logical volume(s) in volume group "vg0" now active
> Creating root device.
> Mounting root filesystem.
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Setting up other filesystems.
> Setting up new root fs
> no fstab.sys, mounting internal defaults
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
The initramfs doesn't know about your new array so it's not activating it during
early boot (before mounting root). This leads to the partial LV errors since the
tools will not allow an incomplete LV to be activated without manual
intervention (but at least it doesn't cause the boot to fail completely ;).
You need to rebuild your initramfs (mkinitrd on CentOS 5.5) to include the
configuration for the newly defined MD array.
Something like:
mkinitrd /boot/initrd-$(uname -r).img $(uname -r)
Regards,
Bryn.
next prev parent reply other threads:[~2011-02-24 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 22:24 [linux-lvm] Errors after adding new md pv (boot only?) Tomasz Nowak
2011-02-24 10:50 ` Bryn M. Reeves [this message]
2011-02-24 11:54 ` [linux-lvm] [SOLVED] " Tomasz Nowak
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=4D663807.9010802@redhat.com \
--to=bmr@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=tnowak@netventure.pl \
/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).