Arch Linux

Description:

/bin/fstype in the initcpio returns filesystems that do not correspond to kernel filesystem modules. /sbin/modprobe in line 54 of /lib/initcpio hooks/filesystems gives and error, but it's tossed to /dev/null instead of being handled. this produces a kernel panic after the hand-off to kinit.

see http://bbs.archlinux.org/viewtopic.php?id=55842 for detailed diagnosis.

i don't see a use-case where this isn't caused by user error (not setting $cryptdevice on the kernel command-line), but handling the error would be more helpful than allowing it to cause a kernel panic.

perhaps something like:

if /sbin/modprobe -q ${FSTYPE} >/dev/null 2>&1; then
kinit_params="${kinit_params} rootfstype=${FSTYPE}
else
err "There is no kernel module for filesystem ${FSTYPE} on specified root device ${root}"
echo "Dropping to a recovery shell... type 'exit' to reboot"
echo "NOTE: klibc contains no 'ls' binary, use 'echo *' instead"
echo ""
echo "If your root device is a logical volume on and encrypted block device"
echo "you *must* specify \"cryptdevice=/dev/encryptedBlockDevice:dm-crypt_mapping\""
echo "at the kernel command-line"
PS1="ramfs$ " /bin/sh -i
msg "Rebooting..."
/bin/reboot
fi

Additional info:

mkinitcpio 0.5.19-1

Steps to reproduce:

http://bbs.archlinux.org/viewtopic.php?id=55842

(wee... edge cases are fun!!!)