On Dec 6, 2005, Andre Noll wrote:
Don't we need /dev/console as well?
About the example script:
==============================================
#!/bin/sh
echo 'Auto-assembling boot md array'
mkdir /proc
mount -t proc proc /proc
if [ -n "$rootuuid" ]
then arg=--uuid=$rootuuid
elif [ -n "$mdminor" ]
then arg=--super-minor=$mdminor
else arg=--super-minor=0
fi
echo "Using $arg"
mdadm -Acpartitions $arg --auto=part /dev/mda
cd /
mount /dev/mda1 /root || mount /dev/mda /root
umount /proc
cd /root
exec chroot . /sbin/init < /dev/console > /dev/console 2>&1
=============================================
(a) mkdir, mount, umount won't be found. 'busybox mkdir /proc'
etc. does the job though. Or, create symlinks.
(b) Does mdadm --auto=/dev create the /dev directory? If if does
not, the script has to create it. Otherwise, the mdadm manpage should
mention this ;)
(c) Documentation/filesystems/ramfs-rootfs-initramfs.txt recommends to
mount --move . /
before the final chroot.
I'm not very initrd savvy; and I'm having a heck of a time making the
initramfs instructions in mdadm work. Does anyone have a working example of
them?
I'm attempting to use the following 'init' file -- based on some of the
observations that Andre made.
#!/bin/sh
/bin/busybox echo "Auto-assembling boot md array..."
/bin/busybox mkdir /proc
/bin/busybox mount -t proc proc /proc
/bin/busybox echo "Using /dev/md_d0..."
/bin/mdadm -A /dev/md_d0 --auto=part /dev/sdb1
cd /
/bin/busybox mount /dev/md_d0p1 /root
/bin/busybox umount /proc
cd /root
exec /bin/busybox chroot . /sbin/init < /dev/console > /dev/console 2>&1
I've added a /dev directory to the init.cpio.gz as well. It seems like I may
have some cart before the horse syndrome tho, as mdadm cannot find
/dev/sdb1... which I'm assuming is because udev hasn't started.
Help!
-- David M. Strang
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
