Arch Linux

Description:

symptoms :
- kernel panic when booting on the non-fallback image
- boot OK when booting on fallback image

this bug occurs in rare but accurate situations :
- root filesystem needs a module to get mounted (reiserfs in my case)
- all such filesystems are on devices witch names include "fd"
("/dev/mapper/nvidia_bafgafdap#" in my case because it is on a raid array)

reason and fix we could found out (thanks tuxce for your help) :
- my partitions are discarded as floppy disks by the "autodetect" hook when looking for filesystems because their names include "fd"
- editing "/lib/initcpio/install/autodetect" line 16 by changing "... grep -v -e loop -e ram -e fd..." with "... grep -v -e /loop -e /ram -e /fd..." fixes this bug
(needs to rebuild the boot image with mkinitcpio after this edit)

related topics on forums :
- original topic on the French forum :
http://forums.archlinux.fr/topic2802.html
- topic with a summary on the English forum :
http://bbs.archlinux.org/viewtopic.php?id=58060

strange things about this bug :
- I have another small base archlinux on my system (only the base group + the dmraid package)
- this system was installed on November 18th
- this system was never upgraded
- this system produced a working non-fallback boot image during installation
- this system produces non-working non-fallback boot image today
(bug bug occured on Novembre 30th because the boot images wheres rebuild because of a kernel upgrade)

possibly related bugs :
every strange and rare boot bug on systems with "exotic" hard disk configuration
(where "fd" can be included on device names)
Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce: