Description of problem: FC5 correcttly installs to the 660F, the BIOS loads the boot loader, the boot loader brings in the kernel and initrd, then stops after the kernel has loaded with an unable to locate volumegroup00 error. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Install fc5 onto a 660F on an otherwise diskless machine 2.Attempt to boot Actual results: bootloader loads, kernel and ramdisk load, stops with unable to locate volumegroup00 Expected results: Boots correctly to login. Additional info:
Have now booted from the rescue disk and the rescue disk successfully finds the partition and mounts it. Have checked that the qla2200.ko exists on teh image and it does. Will now reboot back to the installed image and see if there are any clues as to why this is happening.
Ok, fixed it. The ql driver must take a period of time to bring the drives online, amended the init script to sleep for 10 seconds (which is probably overly cautious), and all is fine. SOLUTION: insert sleep command into init script
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
(this is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug.