Red Hat Bugzilla – Bug 69776
kickstart with bootnet.img does not find SCSI disks
Last modified: 2007-04-18 12:44:28 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (compatible; Konqueror/3.0.0-10; Linux) Description of problem: when using bootnet.img to do a kickstart installation, then the installer will not load the aic7xxx module; when doing a graphical install with the same diskette, then aic7xxx is loaded automatically Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. create boot disk from bootnet.img 2. boot SCSI system with this disk 3. start with "linux ks" (or with "linux ks=floppy" if a ks.cfg has been copied to it) Actual Results: ERROR: no valid devices were found on which to create new filesystems Expected Results: successfull installation; with RH 7.2 this did work without any problems Additional info: when doing a standard installation instead of "kickstart", then everything works fine (with the same boot floppy)
Created attachment 67004 [details] the kickstart file I used
Found the problem: this was not a bug in loading the SCSI driver, but I forgot to update my kickstart file. It still did point to an image of RedHat 7.2 instead of 7.3. But the error message "no valid devices were found on which to create new filesystems" was very confusing! Now I corrected the pointer and everything works fine. I.e. the only bug is showing a misleading error message.
This is why current releases now double-check a timestamp file and verify that they match if it exists on both images. Unfortunately, we can't change legacy behavior of the boot disks. And the message is completely valid that we don't have any block devices to install to.