From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] / on LVM2
Date: Mon Dec 9 05:09:02 2002 [thread overview]
Message-ID: <20021209120102.D18845@sistina.com> (raw)
In-Reply-To: <200212062032.11584.mweiss@grenoble.cnrs.fr>; from mweiss@grenoble.cnrs.fr on Fri, Dec 06, 2002 at 08:32:11PM +0100
Markus,
we don't support root on LVM2 yet :(
On SuSE what you want to do that still _and_ have an LVM2/device-mapper
emergency boot media at hand if something goe wrong it goes along
these (untested!) lines:
- have device-mapper and LVM2 tools installed
- in case you want to go with the device-mapper module:
- add dm-mod to your /etc/sysconfig/kernel
- build/install a kernel qith dm-mod
- run mkinitrd
- add "modprobe dm-mod" etc. to the created initrd:
- gzip -dc /boot/initrd>initrd.wrk
- mount -oloop /boot/initrd.wrk /mnt
- echo -e "lvm vgscan\nlvm vgchange -ay" >> /mnt/linuxrc
- cp -p /sbin/lvm /mnt/sbin
- cp -sp /lib/libdevmapper* /mnt/lib
- umount /boot/initrd.qrk
- gzip -c /boot/initrd.wrk>/boot/initrd
- lilo
- rm /boot/initrd.wrk
On Fri, Dec 06, 2002 at 08:32:11PM +0100, Markus Weiss wrote:
>
> Hello everbody,
>
> I ran into a problem testing LVM2 on my system.
> I have / on LVM, and booting into kernel 2.5.50 (with dm compiled in,
> libdevmapper and LVM2-tools installed) fails, because the kernel cannot mount
> the root fs. I have tried building an initrd using SuSE's mk_initrd and
> lvmcreate_initrd, but I get the same problem.
>
> Do these scripts have to be modified in any way to work with LVM2 ?
> (something like calling devmap_mknod.sh at some point ?)
>
> Thanks for any advice,
>
> Markus
>
> PS:
> Please cc me, as I'm not subscribed
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2002-12-09 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 13:32 [linux-lvm] / on LVM2 Markus Weiss
2002-12-09 5:09 ` Heinz J . Mauelshagen [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=20021209120102.D18845@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.com \
/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.