Red Hat Bugzilla – Bug 472989
3ware 8006-2 LP raid card won't boot
Last modified: 2008-12-30 15:56:07 EST
Description of problem:
Fedora 10 machine x86_64 with 3ware 8006-2 LP raid card won't boot after installing. Is the driver for this card gone missing from the kernel ????
if the driver were missing, it wouldn't have managed to get through the install at all. (The installer and the final image use the same kernel).
It should be using the 3w-xxxx driver I think, which is definitly built in the rpm.
What might be failing however, is the initrd creation. Peter?
Yes, F10 initrd does not wait long enough for the disk scans to complete, with many scsi and raid cards. 3w-xxxx is confirmed to be a problem in bug #466071 comment #46, and has one workaround there too. Boot a rescue shell, chroot, rebuild initrd with the scsi_wait_scan module, then reboot.
bug #466534 comment #20 has a list of the 10 or so other dupe bugs that have been accumulating for a while, if you want more details.
First of all apologies for not responding to this bug for so long, we've been
swamped with other stuff. We understand this is a rather critical bug.
We've prepared an mkinitrd image, which should fix the not waiting long enough issue. I've put detailed instructions on how to test this in bug 466607 comment 57.
Can you please test if this fixes the issues with 3w-xxxx cards?
Rather than building a new initrd I simply updated my /boot/grub/grub.conf so that the parameter is provided to the kernel via its command line. Here's an example:
title Fedora (220.127.116.11-159.fc10.x86_64)
kernel /vmlinuz-18.104.22.168-159.fc10.x86_64 ro root=/dev/VolGroup00/RootLV rhgb quiet scsi_mod.scan=sync
Of course, I had to boot the rescue (or run Knoppix) to be able to edit my /boot/grub/grub.conf file.
This approach has the advantage that the additional parameter is carried forward by the kernel update process when a new kernel rpm comes out.
By the way, I'm running with a 3ware Inc 9650SE
Ok, so its the same issue, closing this is a dup of 466607 then.
*** This bug has been marked as a duplicate of bug 466607 ***