Hi Jiri Jiri Srain wrote:
Hi Mike!
Dne pondělí 30 květen 2005 09:59 jste napsal(a):
Jiri
I think this is a major problem for all machines with more than one HBA. autoinst would work or not depending on the PCI ID which makes it quite unpredictable (i.e. you'd have to check PCI slot ordering and adapt accordingly before starting installation).
It is not for all of them, only for some. It may happen that the modules are loaded in the same order as they are saved to sysconfig - but this is unpredictable.
this is exactly the problem I have. If we wanted to upgrade a number of machines from SLES8 to SLES9 we'd have to check each and every one of them on the hardware level.
SLES10 seems a bit too far on the horizon. This is the first system we're trying to install using autoyast with SLES9.
It is not issue of autoinstallatino only - plain installatino is affected as well.
but there at least you have the option of checking the initrd before you boot. I tried with adding "boot confirm true" (can't remember the exact syntax) in autoinst.xml but that option didn't seem to have any effect as the machine booted automatically right after installation finished. I would be happy if I had the chance to alter the MKINITRD and create a correct initrd _before_ the initial reboot, as we're not really looking for fully-automated setups. Any idea on why this might not work?
Wouldn't it be possible to just add the detected modules _after_ the ones explicitely defined in the info file? This way all the modules needed for the installation get loaded and any additional (detected) modules as well.
Wouldn't it be possible to set the modules to info file in the different order? This should solve the problem for this particular machine.
not really. The number of devices on the qla2300 might change over time and then I'd have to use scsidev or devlabel to get consistent device names. We haven't figured out yet which one of the two (scsidev or devlabel) to use. Hitachi (SAN) wants us to go with devlabel, SuSE with scsidev. I'd prefer to have / on /dev/sda3 on all the machines.
It is not possible to add all modules which are in info file to initrd - because it would put there a lot of modules which are not needed.
Where does the MKINITRD variable get set? Which file would I have to look into to tweak it myself?
/usr/share/YaST2/modules/Initrd.ycp, after modifying it needs to be recompiled by 'ycpc -c Initrd.ycp'.
thanks for the pointer. I'll look into it tomorrow when I'm on site.
Mike
Jiri Srain wrote:
Hi!
To /etc/sysconfig/kernel, the modules are written in the order the respective adapters are detected. The order the modules were loaded for installation is not used. The reason was that the list of modules needed for installation contains moduels which are not needed in inird of the running system (eg. network card if installing from network).
I want to fix it at least for SLES10 (to try to keep the order of the modules during first stage but not modules which are not needed into initrd)
Dne sobota 28 květen 2005 00:26 Michael Steinmann napsal(a):
I'm having problems with SLES9 SP1 autoinst on a machine with two qla2300 and one megaraid controller.
In my info file I've got: insmod: megaraid insmod: qla2300
and the drivers load in that order, giving me /dev/sda on the first disk on the megaraid controller which is what I want.
But, autoinst would always add the qla2300 to the beginning of the MKINITRD variable in /etc/sysconfig/kernel before building the initrd. As the qla2300 gets added at the *beginning* this leads to a initrd linuxrc that always loads qla2300 before megaraid. When the machine boots using the initrd built by autoinst the devices are not in the same order as during the install.
When qla gets loaded via info file, the MKINITRD looks like this: "qla2300 megaraid qla2300"
when it doesn't get loaded by 'insmod: qla2300' in info file: "qla2300 megaraid"
Why would autoinst insist on putting qla2300 in the initrd? And why at the beginning of the list?
Shouldn't the order the modules get added to the initrd honor the order given in the info file?
Mike