May 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] initrd module load order not following info file
by Michael Steinmann 16 Jun '05

16 Jun '05

Jiri Srain wrote: > Hi Mike! > > Dne pondělí 30 květen 2005 10:26 jste napsal(a): > >>Jiri Srain wrote: >> >>>Dne pondělí 30 květen 2005 09:59 jste napsal(a): > > >>>>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. > > > Don't know, pass the question to the list. > > >>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? > > > No, no idea. I didn't know about this option before. That's (or rather was) the option in autoinst.xml: <install> <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">false</forceboot> </mode> According to autoyast documentation here http://www.suse.de/~nashif/autoinstall/9.1/autoyast.pdf it has been dropped for SuSE9.1/SLES9. >>>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. > > > If you just want to update sysconfig and recreated initrd before the reboot, > the probably easiest would be to add to /usr/share/YaST2/clients/inst_finish > just after bootloader is installed eg. > > Popup::Message (_("Update the inirdd now")); > > This will show you message after bootloader is saved and you can switch to the > console to change anything you want to. > > Just remember that you have to change the file in the installation system > (which is stored on CD1 in /boot/root). It is cramfs image. that sounds like a good workaround, thanks.

3 2

Re: [suse-autoinstall] initrd module load order not following info file
by Michael Steinmann 30 May '05

30 May '05

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 > >

1 0

initrd module load order not following info file
by Michael Steinmann 30 May '05

30 May '05

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

2 1

Problem with swap space on Suse 9.1 installation
by Paulo Coelho 29 May '05

29 May '05

Hello, I’m trying to install Suse 9.1 on a very old machine (a Pentium 133Mhz w/ 48Mb of RAM and two Maxtor hard drives, one with 1.2Gb and another with 1.5Gb) Since my CD-ROM doesn’t seem to read recordable CDs, I’ve been trying a network installation (I’ve downloaded the installation directory into another PC on my LAN that’s acting as FTP server). I’ve created the three boot floppy disks and I’m booting my machine from floppy. I can configure my network card using the appropriate modules disk. When I first tried to install, it told me there was not enough memory and had to create some swap space. I then used the rescue disk to try to do something about it. I used fdisk and set up these partitions: /dev/hda1 – Linux /dev/hda2 – Linux Swap /dev/hdc1 – Linux Then I did a mkswap –c /dev/hda2 and the swapon /dev/hda2 The swap has 280Mbytes. I rebooted the machine and started the installation process. Once again it said I had to create swap space, and I went to a console terminal and did the swapon /dev/hda2 command – no errors. This seamed to have worked, because it started to download the installation image. It was all going well until it needed to use the swap space. I can see activity on the hard drive, but the download stops and the installation hangs. No error messages that I can see. Can anyone help me on this one? I have very little experience with Linux, I’m probably doing something wrong… Thank you! Paulo -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.2.0 - Release Date: 27-05-2005

1 0

RE: [suse-autoinstall] Network Installation Problems
by Paul Anthony Rae (QC/EMC) 27 May '05

27 May '05

As it turns out it was a corrupted control.xml in the source tree. Thanks to those who sent their suggestions and advice! Paul -----Original Message----- From: Paul Anthony Rae (QC/EMC) [mailto:Paul.Anthony.Rae@ericsson.com] Sent: May 19, 2005 5:33 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Network Installation Problems Well I am still battling with this issue. I still get big red "Error in Installation" trying to do an autoinstall over the network. Possible issues: 1) I have no DNS server on my little private network where I am attempting the install. Is this a problem? 2) Control file validity checks out ok, but maybe there is something busted? What kinds of problems might lead to 'Error in Installation" just after control file download, assuming the control file is sane? Below is the last version of the control file I have been using. Any weirdnesses I am missing? Paul <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <runlevel> <default>3</default> </runlevel> </configure> <install> <general> <clock> <hwclock>UTC</hwclock> <timezone>US/Pacific</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> </mode> <mouse> <id>ignore</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>13.9GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/usr</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount>Swap</mount> <partition_id config:type="integer">131</partition_id> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">131</partition_id> <size>12GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>acl</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/opt</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <size>6GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </yesno_messages> </report> <software> <addons config:type="list"> <addon>Base-System</addon> <addon>YaST2</addon> </addons> <base>Minimal</base> </software> </install> </profile> -----Original Message----- From: Paul Anthony Rae (QC/EMC) [mailto:Paul.Anthony.Rae@ericsson.com] Sent: May 10, 2005 11:32 AM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Network Installation Problems Quite sure. The distro I have is 9.0 enterprise, I have checked and double checked. Also I was able to complete an interactive network installation just fine so I haven't the foggiest what is going wrong when I try to get it to auto-install. Is the request for driverupdate triggered by the control file? Is it possible somehow the control file I have generated is asking for it, or needs to be set to ignore it or somesuch? It's the only thing I can think of, but I can't see anything in the control file that clues me in to what is happening. Paul -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: May 9, 2005 6:20 PM To: Paul Anthony Rae (QC/EMC) Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Network Installation Problems On 9 May, Paul Anthony Rae (QC/EMC) wrote: > The problem seems to be that it's trying to download "driverupdate" from the > source directory, but no such file exists. After it can't find that file > the Installation stops with "Error in Installation". Are you sure you're not booting from the sp1 cd's linux kernel and initrd files? I don't think I've ever seen a non-sp installer look for the driverupdate file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Excluding a package, or proper dependency resolution
by Dax Kelson 25 May '05

25 May '05

I'm having a problem of having two conflicting packages being installed. Both "imap" and "cyrus-imapd". Apparently "imap" is coming from either "base" one of the "addons" listed, and then when I manually specify cyrus-imapd as a "package" the conflict occurs. How can I still use my defined list of "addons", yet not have imap installed? Here is my config snippet: <software> <base>default</base> <addons config:type="list"> <addon>Basis-Devel</addon> <addon>Basis-Sound</addon> <addon>Fonts</addon> <addon>Games</addon> <addon>Gnome</addon> <addon>Gnome-Devel</addon> <addon>Hacker</addon> <addon>Java</addon> <addon>Kde</addon> <addon>Kde-Desktop</addon> <addon>Kde-Devel</addon> <addon>Kernel-Devel</addon> <addon>LAMP2</addon> <addon>LDAP-Server</addon> <addon>Laptop</addon> <addon>Latex</addon> <addon>Min</addon> <addon>Mobile</addon> <addon>Multimedia</addon> <addon>Network</addon> <addon>Office</addon> <addon>SuSE-Documentation</addon> <addon>Tcl-Development</addon> <addon>Voip</addon> <addon>X11</addon> <addon>Xen</addon> </addons> <packages config:type="list"> <package>autoyast2-utils</package> <package>SDL-devel</package> <package>finger-server</package> <package>mozilla-mail</package> <package>ncftp</package> <package>pdksh</package> <package>talk-server</package> <package>telnet-server</package> <package>postgresql-server</package> <package>lvm2</package> <package>cyrus-imapd</package> </packages> </software> A workaround is to just "rpm -e imap" in a postinstall script, but I was hoping for a cleaner solution. Thanks in advance. Dax Kelson Guru Labs

2 1

Re: [suse-autoinstall] SLES8 Retrieving Controlfile via http
by Daniel Fitzner 25 May '05

25 May '05

I use as bootcd the sles8 sp3 cd, so normally this could not be the problem. thx and best regards --- Uwe Gansert <ug(a)suse.de> schrieb: > On Tuesday 24 May 2005 13:44, Daniel Fitzner wrote: > > > I checked the logfile and the following entries > should be a hint for the > > problem: > > okay, I see. > > > 2005-05-24 04:26:42 <1> linux(1397) [ag_curl] > CurlAgent.cc(Execute):252 > > Data: 2005-05-24 04:26:42 <1> linux(1397) > [ag_curl] > > CurlAgent.cc(Execute):253 Output: > /tmp/YaST2-01397/autoinst.xml 2005-05-24 > > 04:26:42 <3> linux(1397) [Interpreter] :0 Couldn't > find an agent to handle > > '.get_mac' 2005-05-24 04:26:42 <3> linux(1397) > [Interpreter] > > the .get_mac agent came with a service pack. I think > it's SLES8 Service Pack > 3. So you have to use that one and not a plain > SLES8. > > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 > Nürnberg, Germany > e-mail: uwe.gansert(a)suse.de, Tel: > +49-(0)911-74053-0, > Fax: +49-(0)911-74053-476, Web: http://www.suse.de > > > -- > To unsubscribe, e-mail: > suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: > suse-autoinstall-help(a)suse.com > > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

2 1

Interactive option checked BEFORE scripts?
by Jesse Keating 25 May '05

25 May '05

I'm using the modified.xml method of dynamic autoinstall control files. One of the things I wanted dynamic was the interactive or not choice, controlled by: <mode> <confirm config:type="boolean">false</confirm> If this was set to true, it should be interactive. I have this being set in modified.xml, however it does not take effect. Is this option checked BEFORE the pre-scripts run? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 2

Integrating scsi modul in autoyast installation
by FITZ MAILING 24 May '05

24 May '05

Hello guys, maybe someone of you tried the same, like I am doing now since 1 week. I have a server with a scsi controller, that is not supported by the standard kernel of suse. If I a the modul manual at the installation everything works. But I want to use autoyast. The FAQ of autoyast points to http://ftp.softnet.tuc.gr/pub/linux/suse/people/hvogel/Update-Media-HOWTO/U… for this. So I created the directory linux/suse/i386-sles8 with the subdirectories install and module in my HTTP-Repository and also at my bootcd (SLES8 SP3), but nothing works, the module could not be loaded. Any hints or suggestions how to deal with this problem??? thanks ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

3 2

Re: [suse-autoinstall] SLES8 Retrieving Controlfile via http
by Uwe Gansert 24 May '05

24 May '05

On Tuesday 24 May 2005 13:44, Daniel Fitzner wrote: > I checked the logfile and the following entries should be a hint for the > problem: okay, I see. > 2005-05-24 04:26:42 <1> linux(1397) [ag_curl] CurlAgent.cc(Execute):252 > Data: 2005-05-24 04:26:42 <1> linux(1397) [ag_curl] > CurlAgent.cc(Execute):253 Output: /tmp/YaST2-01397/autoinst.xml 2005-05-24 > 04:26:42 <3> linux(1397) [Interpreter] :0 Couldn't find an agent to handle > '.get_mac' 2005-05-24 04:26:42 <3> linux(1397) [Interpreter] the .get_mac agent came with a service pack. I think it's SLES8 Service Pack 3. So you have to use that one and not a plain SLES8. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de

1 0