+++ This bug was initially created as a clone of Bug #651585 +++
I am seeing symptoms similar to the initial error but after adding the appropriate debug I found that the BusLogic module was not being loaded.  With the debug console configured I can do a "modprobe BusLogic" and then exit, to allow the the lvm to find my disks and finish the boot.  This happen at some point while I was running FC13 and ever upgrading to FC14 it is still broken.  I have ried many things at this point with no easy fix.  Right now if I boot FC14 with the debug console for dracut I can finish the boot.

The only kernel that boot with no intervention is 2.6.34.7-56 from FC13 the 2.6.35.10-74 for FC14 will only do it if I do the manual modprobe.  How it got this way is a question and with all the the "fixes" I have tried at this point I am not sure where I discovered the issue.  My initial issue was it could not find the root for LVM to work and then I discovered the driver for the disk was not there.

This configuration is now in a VM with VMWare fusion so I can back it up and retry different things.  I was attempting to force the kernel module BusLogic.ko to load but I do not know why it stopped or if doing so will kill something later.

--- Additional comment from gmiller.com on 2011-01-22 12:36:36 EST ---

Upgraded to latest dracut:

dracut-generic-006-6.fc14.noarch
dracut-tools-006-6.fc14.noarch
dracut-network-006-6.fc14.noarch
dracut-006-6.fc14.noarch
dracut-fips-006-6.fc14.noarch

rebuilt initramfs:


[root@gmillerLinux recover]# cat rebuild_initramfs.sh 
echo "backing up current /boot/initramfs-$(uname -r).img starting"
mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-backup.img
echo "backing up current /boot/initramfs-$(uname -r).img complete"
echo "rebuild of current /boot/initramfs-$(uname -r).img starting"
dracut /boot/initramfs-$(uname -r).img $(uname -r)
echo "rebuild of initramfs /boot/initramfs-$(uname -r).img complete"
[root@gmillerLinux recover]# 

booted machine and the system fails to find the device root

--- Additional comment from gmiller.com on 2011-01-22 12:41:22 EST ---

Created attachment 474747 [details]
dmesg output during boot

Here is the contents of dmesg that I see during the boot failure that drops me to the debug command prompt.  Also the output of the "modprobe BusLogic" needed to get my drives recognized, and then the output after "exiting" the debug command prompt and the completion of the boot.

--- Additional comment from harald on 2011-01-25 09:58:49 EST ---

(In reply to comment #32)
> Created attachment 474747 [details]
> dmesg output during boot
> 
> Here is the contents of dmesg that I see during the boot failure that drops me
> to the debug command prompt.  Also the output of the "modprobe BusLogic" needed
> to get my drives recognized, and then the output after "exiting" the debug
> command prompt and the completion of the boot.

seems like the BusLogic driver does not support module autoloading, and has to be fixed... you might want to add "rdloaddriver=BusLogic" to the kernel command line.

--- Additional comment from gmiller.com on 2011-01-25 12:00:10 EST ---

This stopped working after kernel 2.6.34.7-56.fc13 so I thought it was something else other than driver change but I will try what suggest.

--- Additional comment from gmiller.com on 2011-02-22 15:48:18 EST ---

The "rdloaddriver=BusLogic" makes not difference so I am open to other suggestions. :-(  Is there a special way to reference the driver "BusLogic.ko" or "scsi/BusLogic.ko" ??

--- Additional comment from harald on 2011-02-23 02:48:36 EST ---

(In reply to comment #35)
> The "rdloaddriver=BusLogic" makes not difference so I am open to other
> suggestions. :-(  Is there a special way to reference the driver "BusLogic.ko"
> or "scsi/BusLogic.ko" ??

Is the driver included in the initramfs image at all?

# lsinitrd /boot/initramfs-<kernel version>.img | grep BusLogic

--- Additional comment from gmiller.com on 2011-02-23 07:31:52 EST ---

yes, if I do the "modprobe BusLogic" I can load it by hand and then continue the boot. Is the syntax of the driver name something other than "BusLogic" ?

--- Additional comment from harald on 2011-02-23 07:50:23 EST ---

"rdloaddriver=BusLogic" on the kernel command line should really work!

We should really open a new bug for this...