Red Hat Bugzilla – Bug 454663
mkinitrd missing scsi_wait_scan
Last modified: 2008-12-09 15:00:30 EST
Description of problem: Recent mkinitrd no longer adds these lines to the init script: modprobe scsi_wait_scan rmmod scsi_wait_scan also does not appear to be pulling in scsi_wait_scan at all. This breaks booting on scsi. Version-Release number of selected component (if applicable): mkinitrd-6.0.54-1.fc10 testing 6.0.55 now but based on the changelog it does not appear this is fixed. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I confirmed mkinitrd-6.0.55-1.fc10 does still have this issue.
This is because scsi_mod is now built-in and that was what we used to key needing scsi_wait_scan
ah, good catch. I could flip this back to =m if there's no better way. Strikes me as somewhat fragile to do it this way, though I admit I haven't got any better ideas.
I guess we could try to do some form of determination based on symbols used in the module, but then we have to be doing nm on modules. Or we could use the modules.block file and seeing if the driver is listed there
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Created attachment 326229 [details] Correct variable name There is some code in there to wait for scsi to stop scanning it doesn't use the module but it would work if the variable name was consistent.
Created attachment 326270 [details] Corrected all variable names Last suggested patch made things worse this one makes all variables the same name.
*** This bug has been marked as a duplicate of bug 470628 ***