August 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Updating installation
by Harald Finnås 10 Aug '04

10 Aug '04

I've been trying to autoinstall from the 9.1 DVD for a while now, but I've given up on this due to all the bugs I've run into. In an attempt to have more control over the source, I've decided to set up and installation server instead so that I may update all the stuff that's missing in the .dtd files etc. My question is if someone out there has updated .dtd files that works with most of the xml code yast2 generates, or do I have to figure out what's missing myself? Regards, Harald

1 0

Conflicting package
by Krieger-Juhnke, Kai 09 Aug '04

09 Aug '04

Hello list, does anyone knows how to install a conflicting package (i.e. a device-driver, which is included in an older version in the kernel-package) using autoyast? Manually, this job would be done using rpm -i --force <package-file>. Unfortunately, as I want to update the device-driver for the nic, I cannot use a post-installation-script, because at that time the system as allready rebooted. Thanks for any hints, > Kai Krieger-Juhnke > > VOLKSWAGEN BANK GMBH > Postfach I-SBS > Schmalbachstr. 1 > > D-38112 Braunschweig > > Tel.: +49 531 212-2098 > FAX: +49 531 212-72098 > email: K.KRIEGER-JUHNKE(a)VWFSAG.DE > >

2 1

autoyast with suse 9.1
by Todd Merritt 09 Aug '04

09 Aug '04

I've read the documentation at http://www.suse.de/~nashif/autoinstall/9.1/html/, and several other sites I found explaining how to create an autoyast.xml file from a complete installation. The instructions for 9.1 don't specify what rpms need to be installed and when I run yast2 autoyast I get: No such client module autoyast I tried installing the modules I found referenced from documents on 8.x (yast-config-autoinst), but I still get the same message. Can somebody point me in the right direction ? Thanks, Todd

5 5

LVM on Raid-1 using same disks problem
by Tomas Baublys 06 Aug '04

06 Aug '04

Hello, I have the same problem mentioned some times since 2002 in the list, unfortunately I did not found an answer which works for me. I am installing SLES8 through autoyast with software raid and LVM on it. Software Raid contains two partitions (sda3 and sdb3) as I can not use whole disks. The machine is a pSeries p690 LPAR so a PrepBoot partition is required on each disk. The installation worked fine for the first time, repeating the installation on the same disks produced an error: can not create md0 device and can not create system volume group- volume group already exists. I am using <initialize config:type="boolean">true</initialize> in each drive section And <destroy_old config:type="boolean">true</destroy_old> in lvmgroup. I guess the problem is related to the persistent superblock used by software raid and VGDA on the disk used by LVM. I also tried using a prescript: dd if=/dev/zero of=/dev/sda bs=1MB count=3 dd if=/dev/zero of=/dev/sdb bs=1MB count=3 # this does not works: blockdev --rereadpt /dev/sda blockdev --rereadpt /dev/sdb For network boot on pSeries I am using SUSE SLES8 SP3 Kernel with the builtin commandline: ./mkzimage_cmdline -a -1 -c -s "insmod=e100 insmod=e1000 hostip=9.156.175.22 netmask=255.255.255.0 install=nfs://9.156.175.8/software/Linux/PPC/SLES8/unpacked/CD1 autoyast=tftp://9.156.175.8/tftpboot/autoyast_tb.xml" install.tb Unfortunately I can overwrite the begining of the disk, but rereading the partition table fails (disc is in use message in the log). Is there any trick how to reread the partition table or to get rid of the persistent Superblock and VGDA before the installation starts? Now, I need to start installation, read the error messages about raid and lvm, restart installation and it works fine running second time. It also works fine on a new LPAR. Any help is welcome.. Mit freundlichen Gruessen / Best regards, Tomas Baublys IBM Certified Advanced Technical Expert (CATE) pSeries and AIX pSeries Technical Sales Support JS20 Technical Focus Group Systems Sales, Central Region here is my autoyast control file: root@csm:/tftpboot> cat autoyast_tb.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>munich.de.ibm.com</domain> <hostname>p690-lpar2</hostname> <nameservers config:type="list"> </nameservers> <searchlist config:type="list"> <search>ibm.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast></broadcast> <device>eth0</device> <ipaddr>9.156.175.22</ipaddr> <module>e100</module> <netmask>255.255.255.0</netmask> <network>9.156.175.0</network> <options></options> <remote_ipaddr></remote_ipaddr> <startmode>onboot</startmode> <wireless>no</wireless> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>9.156.175.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> <scripts> <chroot-scripts config:type="list"/> <post-scripts config:type="list"> <script> <filename>postinstalltasks.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ /sbin/lilo dd if=/dev/sda1 of=/dev/sdb1 mkdir /mnt/sp3 mount 9.156.175.8:/software/Linux/PPC/SLES8/unpacked/Fixpack3-CD1 /mnt/sp3 rpm -Fvh /mnt/sp3/ppc/update/SuSE-SLES/8/rpm/ppc/kernel-ppc64-2.4.21-111.ppc.rpm /usr/bin/installation_sources -e -a nfs://9.156.175.8:/software/Linux/PPC/SLES8/unpacked/Fixpack3-CD1 ]]> </source> </script> </post-scripts> <pre-scripts config:type="list"> <script> <filename>eliminator.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ vgchange -an vgremove system pvchange -ax mount -t nfs 9.156.175.8:/software/Linux/PPC /mnt /mnt/mdadm --zero-superblock /dev/sda /mnt/mdadm --zero-superblock /dev/sdb /mnt/mdadm -S /dev/md0 umount /mnt vgscan vgchange -an vgreduce system -a -v vgchange -a y system lvremove -f /dev/system/usrlv lvremove -f /dev/system/swaplv lvremove -f /dev/system/usrlv lvremove -f /dev/system/homelv lvremove -f /dev/system/* vgchange -a n system vgremove system dd if=/dev/zero of=/dev/sda bs=1MB count=3 dd if=/dev/zero of=/dev/sdb bs=1MB count=3 # klappt erst nach reboot blockdev --rereadpt /dev/sda blockdev --rereadpt /dev/sdb ]]> </source> </script> </pre-scripts> </scripts> <files config:type="list"> <config_file> <file_path>/etc/lilo.conf</file_path> <file_contents> <![CDATA[ # lilo von autoyast default=linux timeout=100 boot=/dev/sda1 activate image = /boot/vmlinuz label = linux root = /dev/sda2 # initrd = /boot/initrd append = "" ]]> </file_contents> </config_file> <config_file> <file_path>/root2/etc/lilo.conf</file_path> <file_contents> <![CDATA[ # sdb lilo von autoyast default=linux timeout=100 boot=/dev/sdb1 activate image = /boot/vmlinuz label = linux root = /dev/sdb2 # initrd = /boot/initrd append = "" ]]> </file_contents> </config_file> <config_file> <file_path>/etc/ntp.conf</file_path> <file_contents> <![CDATA[ # ntp config von autoyast server 192.53.103.103 server 192.53.103.104 ]]> </file_contents> </config_file> </files> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>XGULujbJ2KVmI</user_password> <username>root</username> </user> </users> </configure> <install> <bootloader> <location>ppc_chrp</location> <prep_boot_partition>/dev/sda1</prep_boot_partition> </bootloader> <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Berlin</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <language>de_DE</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> <mouse> <id>none</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <use>all</use> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">65</partition_id> <size>7.8MB</size> </partition> <partition> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,data=ordered</fstopt> <label>ROOT</label> <mount>/</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <size>2GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <raid_name>/dev/md0</raid_name> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> </partitions> </drive> <drive> <device>/dev/sdb</device> <use>all</use> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">65</partition_id> <size>7.8MB</size> </partition> <partition> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,data=ordered</fstopt> <size>2GB</size> <label>ROOT2</label> <mount>/root2</mount> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <raid_name>/dev/md0</raid_name> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> </partitions> </drive> </partitioning> <raid config:type="list"> <raid_device> <device_name>/dev/md0</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_type>raid1</raid_type> <lvm_group>system</lvm_group> <mount /> <format config:type="boolean">false</format> </raid_device> </raid> <lvm config:type="list"> <lvm_group> <destroy_old config:type="boolean">true</destroy_old> <lvm_name>system</lvm_name> <pesize>16M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>usrlv</lv_name> <lv_size>1GB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/usr</lv_mount> </lv> <lv> <lv_name>swaplv</lv_name> <lv_size>512MB</lv_size> <lv_mount></lv_mount> </lv> <lv> <lv_name>varlv</lv_name> <lv_size>512MB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/var</lv_mount> </lv> <lv> <lv_name>varloglv</lv_name> <lv_size>512MB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/var/log</lv_mount> </lv> <lv> <lv_name>optlv</lv_name> <lv_size>512MB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/opt</lv_mount> </lv> <lv> <lv_name>homelv</lv_name> <lv_size>512MB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/home</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> <software> <base>Minimal</base> <packages config:type="list"> <package>tripwire</package> <package>rsync</package> <package>xntp</package> <package>raidtools</package> <package>vim</package> <package>autoyast2-installation</package> </packages> </software> </install> </profile>

1 0

Problems with autoinstall sles9
by Sohst, Martin 05 Aug '04

05 Aug '04

Hi all, I'm trying to autoinstall SLES9 via NFS My problem is, that after all packages have been loaded, and the first reboot starts the system does not configure itself. Especially network settings are not done which prevents any post install script to run. How can this be fixed ? Also I'm trying to autoinstall a HP ProLiant DL360 with SLES9 but the kernel and initrd in boot/loader (CD1) do not work. I guess the cciss driver is missing. (i'm using a suse9.1 kernel to install) Martin

1 0

[suse-autoinstall] problem with resolv.conf
by m.frerichs 05 Aug '04

05 Aug '04

Hallo, I 'm trying to install the file /etc/resolv.conf on a linux 9.1 client with autoinstallation. My xml-file looks like this: 1) <configure> <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <domain>zam.kfa-juelich.de</domain> <hostname>zam724</hostname> <nameservers config:type="list"> <nameserver>134.94.80.2</nameserver> <nameserver>134.94.80.3</nameserver> <nameserver>134.94.100.7</nameserver> </nameservers> <searchlist config:type="list"> <search>zam.kfa-juelich.de</search> <search>kfa-juelich.de</search> <search>fz-juelich.de</search> </searchlist> </dns> <scripts> <post-scripts config:type="list"> <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source> .... During executing post.sh-script I listed /etc/resolv.conf. It is installed with searchline and nameserver , but without line " domain zam.kfa-juelich.de" 2) to prevent several daemons from changing resolv.conf I inserted: <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>XNTPD_INITIAL_NTPDATE</sysconfig_key> <sysconfig_path>xntp</sysconfig_path> <sysconfig_value>134.94.80.2</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>MODIFY_RESOLV_CONF_DYNAMICALLY</sysconfig_key> <sysconfig_path>/etc/sysconfig/network/config</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> </sysconfig> .... --> /etc/sysconfig/network/config is installed with line MODIFY_RESOLV_CONF_DYNAMICALLY="no" a) /etc/resolv.conf is linked to a file mounted readonly by nfs in post.sh which is valid to all our clients , without 2) --> link is overwritten, resolv.conf is changed by dhcpd , pay attention to length 0 of /etc/resolv.conf.saved.by.dhcpcd zam724:~ # ls -l /etc/reso* -rw-r--r-- 1 root root 1321 Aug 5 12:42 /etc/resolv.conf -rw-r--r-- 1 root root 125 Aug 5 12:20 /etc/resolv.conf.install -rw-r--r-- 1 root root 0 Aug 5 12:42 /etc/resolv.conf.saved.by.dhcpcd b) /etc/resolv.conf is installed as a link to a file mounted ro by nfs in post.sh and with 2) :MODIFY_RESOLV_CONF_DYNAMICALLY="no" --> When system boots for the first time, there are the following errormessages on screen and /etc/resolv.conf becomes an empty file!!!!! grep resolv /var/log/* boot.msg:Cleaning up using /sbin/modify_resolvconf: boot.msg:touch: cannot touch `/etc/resolv.conf': No such file or directory boot.msg:Deleted the following stale backups: removed `/etc/resolv.conf.saved.by.yast2' boot.msg:sed: can't read /etc/resolv.conf: No such file or directory boot.msg:cat: /etc/resolv.conf: No such file or directory messages:Aug 4 11:24:15 linux modify_resolvconf: Service yast2 modified /etc/resolv.conf. See info block in this file messages:Aug 4 11:25:59 linux modify_resolvconf: Service yast2 tried to modify resolver configuration, but it messages:Aug 4 11:25:59 linux modify_resolvconf: was not modified due to MODIFY_RESOLV\NAMED_CONF_DYNAMICALLY=no messages:Aug 4 11:44:50 linux modify_resolvconf: Service dhcpcd tried to modify resolver configuration, but it messages:Aug 4 11:44:50 linux modify_resolvconf: was not modified due to MODIFY_RESOLV\NAMED_CONF_DYNAMICALLY=no Thanks for your answers and improvements +----------------------------------------------------------------------+ | Marianne Frerichs | | Zentralinstitut fuer Angewandte Mathematik | | Forschungszentrum Juelich GmbH | | D-52425 Juelich | | Phone: +49 02461 61-6432 | | Email: M.Frerichsfz-juelich.de Fax: +49 02461 61-6656 | +----------------------------------------------------------------------+

2 1

AutoYaST messages: How do you set the default response and timeout for the yesno_message tag?
by Chris Partridge 03 Aug '04

03 Aug '04

Hi, I am just beginning to use the autoinstall with SLES 9-RC5 and I noticed the reference profile generates a tag for "yesno_messages" with the same defaults as the other message tags. But I don't think it's really doing anything. I have a few windows pop up during installation (confirm a driver installation, continue detecting NIC) and I want those to timeout and continue. How do I do that? Here is the tag I have right now: <yesno_messages> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </yesno_messages> Chris

2 1

users
by Todd Merritt 02 Aug '04

02 Aug '04

I'm trying to use autoyast with suse 9.1, I seem to be stuck on creating user accounts. I'm just trying to have the base system accounts created during the install, but I get an group file with only +::: and a password file with +::::, and I'm not configuring nis. I tried just not putting any users in, but then I got no root password, if I have it create root, it creates it like a normal user account. Two questions, what am I doing wrong, and how do I configure autoyast to NOT configure the machine as a nis client ? I'd be happy to sent the config file if needed. Thanks, Todd

1 0

Installing with Fibre attached drive onto local scsi device
by Aaron Amauba 02 Aug '04

02 Aug '04

Sorry if this question has already been addressed here on the lists. I am new to the SAN enviornment and am haveing a difficult time installing SLES8 onto a machine while it is attached to the SAN. At installation time (I use autoyast via NFS) the fibre attached LUN is being seen first and is being assigned /dev/sda. How do I force the local scsi device to be seen as /dev/sda? I looked in linuxrc in initrd, but it wasnt a script. Thanks in advance. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 1

autoyast soundcard detection and configuration
by jan terje tønnessen 02 Aug '04

02 Aug '04

Hi ! Trying to set up suse91 autoyast. I can't figure out how to set that the soundcard shall be autodetected and configured. Have tried something like <sound> <autoinstall config:type="boolean">true</autoinstall> </sound> /JT

1 0