On Wed, 4 Feb 2004 bdoctor@xxxxxxxxx wrote: > Both stage 1 and stage2 have kernel modules for devices. Think of stage 2 > as the extended hardware detection. if the kernel modules in stage 2 do not > match Stage 1, you will get this message. So -- you can either fix this by > downrevving (if you up revved) stage 1, or doing the same if that is where > you made the change - both module versions must match exactly. > > -brad > > > I am attempting to build a RedHat AS 2.1 Update 2 (2.4.9-e.24) boot.iso disk > > with the 1.18k megaraid driver included in it to install on many Dell PE > > 1750s with the Perc 4/Di RAID cards. I know there are some driver disks > > available for the megaraid driver, but driver disks just add too much > > complexity for the sometimes non-technical staff that has to do the final > > install of these servers. > > > > Whenever I use my new boot disk, I get the following error message: > > > > "The second stage of the install which you have selected does not match the > > boot disk which you are using. I am going to reboot your system now." > > > > Does anyone have any idea where this is coming from? Or how Anaconda > > determines a match between boot and 2nd stage media? It seems to come > > shortly after the netstg1.img file is downloaded to the 1750 being built. > > (virtual console output at the end of this message). FWIW, Jeremy said a few days ago either on one of the Fedora lists or on IRC (I do not remember which) that the check is simply a date match. The boot image date must match the date on the 2nd stage image. The bottom line here is if the boot image and the 2nd stage image are not a matched set your install WILL fail in weird ways. He also stated that implementing this check has eliminated a whole host of weird bugs. :-) I would suspect that If you know that the boot image you are trying to boot from matches the 2nd stage image, you could just touch both files to set the correct date. HTH, Tom
