1http://poochiereds.net/svn/lvm2/ 2 3This is the lvm2create_initrd script written by Miguel Cabeca, with some small 4modifications by myself. 5 6Here are some other requirements and tips for using it: 7 81) this script uses busybox on the initrd image, hence busybox needs to be 9installed when you create your initrd. 10 112) Make sure /etc/lvm/lvm.conf is set up correctly before running this. In 12particular, if you're using LVM on RAID, make sure that you have a filter that 13excludes the RAID component devices (this may not be necessary with the latest 14patch by Luca Berra, but it doesn't hurt). 15 163) This initrd image does not support modules. If you need to plug in any 17kernel modules during the initrd phase, then you'll need to hand-modify the 18image. 19 204) The generated initrd image supports an 'lvm2rescue' mode as well. If you add 21the parameter 'lvmrescue' on the kernel command line, it will run a shell at 22the end of the initrd 'init' script. This can be helpful when trying to fix a 23corrupt root volume or root LVM2 volume group. 24 255) No userspace md tools are installed, so if you're using LVM on RAID, then 26you'll probably want to mark your RAID partitions as type 'fd' so that the 27kernel will start them automagically (or hand-modify the image). 28 296) I'm not sure if devfs will work with this or not. udev, however does work, 30and is recommended. Because the dm-* devices use dynamically allocated major 31and minor numbers, kernel upgrades and the like can renumber your devices. To 32fix this, you need to run a 'vgscan --mknodes' prior to fscking and mounting 33your rootfs. Doing this with a static /dev creates a problem though -- you 34will be modifying the root filesystem before it has been fsck'ed. udev gets 35around this by mounting a ramdisk over /dev, but you'll probably need to add 36a startup script that creates devices in /dev. The lvm2udev script in this 37directory is an example of such a beast. 38 39-- 40Jeffrey Layton <jtlayton@poochiereds.net> 41