----- "Aaron Metzger" <ametzger@xxxxxxxxxxxxx> wrote:
> Dale Bewley wrote:
> >> Do I need to make a custom boot/initrd script or am I on the wrong
>
> >> track? Ideas are welcome.
> >
> > Does your initrd contain dm-snapshot.ko?
> >
> > # cat initrd-2.6.21-2950.fc8xen.img | gunzip | cpio -vt | grep
> snapshot
> > -rw------- 1 root root 34608 Nov 27 08:43
> lib/dm-snapshot.ko
> >
> Dale:
>
> No, it does not.
>
> Is the solution as simple as adding it?
> If so, what is the procedure to correctly create/build a custom
> initrd?
If mkinitrd doesn't include what you want (in my case it doesn't know to include raid1 and raid456 modules) you can include it by hand. Example:
VER=`uname -r`
INITRD=/boot/initrd-${VER}.img
if [ -f $INITRD ]; then
mv $INITRD $INITRD.bak
mkinitrd --with=raid1 --with=raid456 $INITRD $VER
else
echo "Can not find $INITRD"
echo "Are you really fixing kernel ${VER}?"
fi
--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
