July 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Segmentation Faults on autoinstall
by Kevin Stallard 20 Jul '04

20 Jul '04

I'm getting the following errors after the package installation steps of my autoinstall. ("Executing autoinstall scripts in the installation env") -- Segmentation fault at /mounts/instsys/use/share/YaST2/clients/ inst_finish.ycp:214 /usr/lib/YaST2/bin/YaST2: line 424: 780 Segmentation Fault y2base "$modulename" $moduleargs ncurses -- Checking /var/log/YaST2/y2log gives the following... -- clients/inst_finish.ycp:174 x11_installed: <false> clients/inst_finish.ycp:205 stopping SCR clients/inst_finish.ycp:207 SCR handle1 closed clients/inst_finish.ycp:207 There is no default SCR now clients/inst_finish.ycp:213 Restarting SCR on /mnt clients/inst_finish.ycp:214 Can't create component 'chroot=/mnt:scr' -- I don't know what is causing this, and I have even less idea how to fix it. Any suggestions on where to look next? -K -- Kevin Stallard <kstallard(a)lancope.com>

1 0

Setting up swap and lprng printers with autoyast
by Henrik Schmidt 20 Jul '04

20 Jul '04

Since cloning a partition setup with the autoyast GUI isn't possible I tried to do it by hand. I want 1 GB swap on /dev/hda1, 20 GB / on /dev/hda2 and the rest as /home on /dev/hda3. Setting it up with autoyast will result in the config down below and the error message 'could not set up swap partition on /dev/hda1' during install. Only thing I added was the <partition_nr> part but it also fails without it. Is see more configuration problems arising as I want to use lprng, not cups. How do I configure printers with autoyast2 GUI without using cups ? I guess its not possible ? Please point me to some complete autoyast documentation. All I have now is the 66 page AutoYaST pdf which is very scarse and I don't want to swamp the mailing list with my newbie questions. Here is the config.xml part which will fail to set up swap : <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <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">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>1gb</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>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>20gb</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>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

2 1

Driver Disk
by Martin Möser 20 Jul '04

20 Jul '04

Hi all, does anyone know how to make a Driver Disk accessible for autoyast CD-installation? Is there a possibility to put it on the CD in order to not have an extra floppy? Thanks, Martin

2 3

Create Reference Profile problems
by Henrik Schmidt 20 Jul '04

20 Jul '04

First question : I want to install 16 identical clients with PXE boot and autoyast. I installed one with DVD and tried to clone its setup with autoyast and 'Create Reference Profile'. I expected to get the complete setup including Software, Partitions, Graphics Card, Monitor, Network Devices, Sound etc. Not so :( I'm missing Partitioning (says Total of 0 drives), Sound (not configured yet), Network Card (not configured yet) as well as Graphics Card and Monitor. Parts working are Software, Boot Loader and General Options. Am I missing something ? Note that I did NOT check the Basic Resources checkboxes for Partitioning, Boot Loader and Software so I expected to get an exact copy of settings. Second question : Regardless of the problem mentioned above I tried to see wether the network PXE install will work. I successfully managed to setup DHCP, TFTP and NFS and the client is starting to install. Problem is yast in auto install mode asked for manual acception of the setup to start installation. How can I skip this to get a fully automated install without user intervention ? Thanks for a great setup tool. Hope I can manage to overcome these hurdles to do complete auto installs in the future. Third question : Will future versions of SuSE break compatibility of 9.1 configurations for PXE autoinstall ? What are the steps to configure a 9.1 client for autoinstall of 9.2 with the same setup as used for 9.1 ? Is it just adopting config.xml to suit new/different software packages ? Thanks Henrik Schmidt -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

1 0

Custom user scripts
by Ralf Neugebauer 20 Jul '04

20 Jul '04

Hello, I have got two questions about using custom user scripts: 1. Is it only possible to copy the configuration file into the xml file? I think it's more useful to write only the path and filename to a externel configuration file I want to copy to the new system. Is this possible? 2. Which interpreters are possible to use? Only shell and perl? Is it also possible to use python? -- Thx for your help Ralf Neugebauer Fachhochschule Osnabrück Albrechstr. 30 49076 Osnabrück Tel. (0541) 969-3673 Fax. (0541) 969-3671 eMail R.Neugebauer(a)et.fh-osnabrueck.de

1 0

SLES9 Multiple Source Net Install
by Aaron McSorley 19 Jul '04

19 Jul '04

Is there a document that describes how to set up a multiple source network install for SLES9. There is one for SLES8 at http://www.suse.de/~nashif/autoinstall/multiplesource.html but this method doesn't seem to work with SLES9.

2 2

Problems at the end of my autoinstall
by Kevin Stallard 19 Jul '04

19 Jul '04

I'm seeing these two errors in my log, but I'm not sure how to investigate further. 2004-07-19 13:47:26 <3> linux(780) [INTERPRETER] clients/inst_finish. ycp:214 Can't create component 'chroot=/mnt:scr' and 2004-07-19 13:47:25 <1> linux(780) [YCP] clients/inst_rpmcopy:146 failed ["sdscsyslogd"] * Note: sdscsyslogd is a custom package that I'm including with my autoinstall. The file is present in the suse/i586 directory and in the appropriate files in suse/setup/descr. Any bit of help, as always, is appreciated. Thanks for all of the kind responses I've received so far to my other queries. -K -- Kevin Stallard <kstallard(a)lancope.com>

1 0

Pb's in creating a custom distribution
by HORNY Jean-Marc 19 Jul '04

19 Jul '04

Hello, I need a solution creating a custom distribution, which can be installed "without" any confirmation on several servers. We have the SLES9, and i try to do this whith AutoYast2. At this time, i don't have enough information / documentation to do what i want : My actual problems are : 1-My control file seems not be able to allow me to use LVM partitioning on a client server, 2-Many configuration parameters may be detected at the installation time ( such as type of network cards ), and not specified in this file, 3-The final distribution must fit on a CD, and i don't find a way to create only the distribution i have defined with the control file .... Has anyone an example with such a similar demand,ideas, procedures, or scripts samples ..? <file:///Q:/Jmarc/Informatique/ordi5.gif> Thank's for help. Jmarc. HORNY Jean-Marc 03 88 65 44 51 Jhorny(a)unedic.fr +----------------------------------------------------------------+ | Ce courrier ainsi que les fichiers joints sont confidentiels. | | Si vous avez recu ce courrier par erreur, veuillez en informer | | l'administrateur du systeme : exp-iris(a)unedic.fr | | --------- | | Ce message confirme que le courrier a passe le controle | | antivirus du relais de messagerie Internet avec succes. | +----------------------------------------------------------------+

2 1

Workaround for the <location>nfs:// bug
by Frank Steiner 16 Jul '04

16 Jul '04

Hi, as I posted earlier, <location>nfs:// </location> does not work for chroot scripts, since autoyast mounts the directory specified in <location> at /mnt, where the installed system was already mounted. Thus, autoyast cannot copy the chroot scripts into the installed system... Here's a workaround: - assume we have the scripts in /rpm/autoyast/9.1/scripts/ where /rpm/autoyast/9.1/ is our autoyast directory with rules/ subdir etc. - you should have "autoyast=nfs://192.168.0.1/rpm/autoyast/9.1" defined, e.g. in the info file on on the append line in pxelinux.cfg. If you don't install over nfs and don't have such a line, it doesn't make sense to get the chroot scripts via nfs... - the autoyast line will cause the variable "$autoyast" to be defined with the value defined above in the environment where the chroot scripts run. Thus, we just write a little chroot script which mounts the scripts dir to some different directory: <scripts> <chroot-scripts config:type="list" > <script>  <filename>prepare-post.sh</filename> <source><![CDATA[ #!/bin/bash mkdir /mnttmp || exit 1 # mount the autoyast dir from the server. we just splitt the # value "autoyast=nfs://..." along the / characters mount `echo $autoyast| cut -d/ -f 3-3`:/`echo $autoyast| cut -d/ -f 4-` /mnttmp || exit 1 # now you can access all of your scripts in /mnttmp. E.g.m copy # them to /mnt/var/adm/autoinstall/scripts like AY would do it, # or execute them directly from the /mnttmp dir. umount /mnttmp ]]> </source> </script> </chroot-scripts> </scripts> Thus, you can keep all of your chroot scripts in normal files (which makes it easier to debug) and still get them via nfs, until the bug in autoyast is fixed. You can also work with some other variables like the "install" variable or "Server" etc. Have fun :-) cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: -4054 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

1 0

Boot from a scsi disk: Part II (Anas: there is a bug in AY)
by Frank Steiner 16 Jul '04

16 Jul '04

Hi, unfortunately, the "Boot from a scsi disk" I posted before is still not enough to boot from a scsi disk. Here's what happens: - autoyast automatically detects the scsi controllers in the system. In one of my systems there are a icp vortex and a adaptec controller. - when writing the bootloader config, autoyast inserts the scsi modules for the detected controllers at the beginning of the INITRD_MODULES line in /etc/sysconfig/kernel - unfortunately, *only* the scsi controller modules are inserted, *not* the scsi_mod module. This results in an initrd trying to load e.g. the gdth and the aic7xxx modules without loading scsi_mod first (sd_mod is loaded automatically). Thus, the first boot attempt after the installation ends up with unknown symbols in sd_mod, gdth and aic7xxx, and the scsi disk to boot from cannot be activated and the kernel panics. - adding scsi_mod to the initrd modules in the bootloader profile, does not work. When you specify <bootloader> <initrd_modules config:type="list"> <initrd_module> <module>scsi_mod</module> <module_args></module_args> </initrd_module> </initrd_modules> </bootloader> that does add the scsi_mod modules to the INITRD_MODULES value, but this step is done before the bootloader module runs, and so it inserts the scsi controller modules *before* the scsi_mod, thus the initrd still tries to load gdth/aic7xxx *before* the scsi_mod. - the solutions is to specify the scsi_mod *and* the scsi controller modules in the <bootloader> section in the right order,i.e., <initrd_module> <module>scsi_mod</module> <module_args></module_args> </initrd_module> <initrd_module> <module>gdth</module> <module_args></module_args> </initrd_module> This will finally end up with the INITRD_MODULES line "aic7xxx gdth scsi_mod aic7xxx gdth" where the last three entries come from the <bootloader> specification. Then, the mk_initrd script does some kind of sorting and inserts the scsi_mod as first module, resulting in a clean boot from the scsi disk. Anas: I think that autoyasts bootloader configuration module should automatically insert "scsi_mod" as first module, when it has autodetected and inserted any scsi controller module. Or to insert the modules the user specifies on the <bootloader> section at the head of the INITRD_MODULES list. cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: -4054 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

1 0