openSUSE Autoinstall September 2006

autoinstall@lists.opensuse.org

33 participants
53 discussions

WG: [suse-autoinstall] reboot after install
by Maurer, Andreas 08 Sep '06

08 Sep '06

Hello Simon, forceboot only forces the boot :) the reboot is done by: <reboot config:type="boolean">true</reboot> andreas ________________________________ Von: Simon Crute [mailto:scrute@novell.com] Gesendet: Do 07.09.2006 14:12 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] reboot after install Hi, I'm trying to get my autoyast setup to reboot after the install has finished, and then run the initscript scripts after the first boot. I've got the following section. <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">true</forceboot> <second_stage config:type="boolean">true</second_stage> </mode> <mouse/> ... </general> but it's still not rebooting after an install. This causes me problems because the install kernel is a -default one, but I'm building -smp systems, so the initscrupt (which configures the sound card, and the display) fails cos there are no -default modules there, only -smp ones -- Simon Crute IS&T Bracknell Novell UK Ltd -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

4 12

Partitioning problem: /boot auto-added
by Frank Steiner 08 Sep '06

08 Sep '06

Hi, I'm trying to install SuSE 10.1 on a system with one SCSI disk. I used a profile to keep all existing partitions: /dev/sda1 / ext3 /dev/sda2 swap swap /dev/sda3 /var ext3 /dev/sda4 /export reiserfs The profile worked with SLES9, now fails with 10.1. While debugging I tried the same profile but toll AY to create all 4 partitions, just to see what comes out of it. Amazingly, AY creates this partitioning scheme: /dev/sda1 / ext3 /dev/sda2 /var ext3 /dev/sda3 extended partition /dev/sda5 swap swap /dev/sda6 /export reiserfs /dev/sda7 /boot ext2 A complete mess, of course (note that also swap and /var are swapped with the partition no.). Looking at y2log I find this: Partitions.ycp: BootCycl lba_support false Partitions.ycp: BootCycl /proc/xen/capabilities $[] Partitions.ycp: BootCycl lba_support false autoinstall/autoaprt.ycp: boot added automagically... So it looks like AY thinks that I need a special boot partition, which is nosense, of course. What can I do? Is this some known bug, or do I need to send the full y2log? The partitioning profile is below... cu, Frank <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>/</mount> <partition_nr config:type="integer">1</partition_nr> <size>20gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>/var</mount> <partition_nr config:type="integer">3</partition_nr> <size>4gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>swap</mount> <partition_nr config:type="integer">2</partition_nr> <size>2gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>/export</mount> <partition_nr config:type="integer">4</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> -- 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: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

2 8

reboot after install
by Simon Crute 07 Sep '06

07 Sep '06

Hi, I'm trying to get my autoyast setup to reboot after the install has finished, and then run the initscript scripts after the first boot. I've got the following section. <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">true</forceboot> <second_stage config:type="boolean">true</second_stage> </mode> <mouse/> ... </general> but it's still not rebooting after an install. This causes me problems because the install kernel is a -default one, but I'm building -smp systems, so the initscrupt (which configures the sound card, and the display) fails cos there are no -default modules there, only -smp ones -- Simon Crute IS&T Bracknell Novell UK Ltd

1 0

problems with language settings.
by Simon Crute 07 Sep '06

07 Sep '06

HI All, I'm having problems setting the language settings. I'm using this fragment of XML that's being pulled in via a rule. (basically, import a custom file depending on which domain the client is in) This fragment was created by yast2 autoyast. I just added the <general>tags round it. <?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"> <general> <keyboard> <keyboard_values> <capslock config:type="boolean">false</capslock> <delay></delay> <discaps config:type="boolean">false</discaps> <numlock></numlock> <rate></rate> <scrlock config:type="boolean">false</scrlock> <tty>tty1 tty2 tty3 tty4 tty5 tty6 tty8 tty9 tty10 tty11 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty20</tty> </keyboard_values> <keymap>english-uk</keymap> </keyboard> <language> <language>en_GB</language> <languages>en_US,en_GB</languages> </language> <timezone> <hwclock>UTC</hwclock> <timezone>Europe/London</timezone> </timezone> </general> </profile> However, the compleated system ends up with a US keyboard.... Interestingly, shortly after loading the xml fragment, the log file has 2006-08-17 17:01:55 <3> 192.168.21.139(3453) [Interpreter] Profile.ycp:118 Can't convert value '$["language":"en_GB", "languag es":"en_US,en_GB"]' to type 'string' in it. so, is it a bug, or user error ? ;-) -- Simon Crute IS&T Bracknell Novell UK Ltd

2 1

AutoYaST IP and partitioning problems
by Peter Ludikovsky 07 Sep '06

07 Sep '06

Good morning! I have some problems using AutoYaST to test the automatic installation I made from within VMware. But first things first. My target is to generate a bootable DVD that should be used to "reset" testing servers. The installation should run as quietly and automatic as possible from inserting the DVD and powering up the system to a complete system with Samba & Oracle. The configuration files can be retrieved at http://www.badongo.com/file/1308770 While the used linuxrc.config & info files should tell AutoYaST to use a static IP address (using VMwares emulated AMD PCnet32 card) it always tries to fetch information from a DHCP server, which is not present, or skips this step all together without BOOTP fallback. This is a major problem since the autoinstall directives should be fetched by HTTP. As soon as the installation proceeds past this it stops short at partitioning. I already tried using fresh disks (remember, still in VMware) and disks that had all required partitions written but to no avail. Is this a general problem with VMware or did I find a glitch? I would really like to be able to continue my test within VMware since I don't want to stress out the hardware now and have it break too soon. Regards, Peter

2 4

RAID1 md-device with "missing"-device
by Tob_Sch＠gmx.de 07 Sep '06

07 Sep '06

Hi, which entries in autoyast.xml do I need to configure a raid1 device with 2 devices, where one of these should be (at the beginning / installation time) a missing device. Sometimes, after the installation, I want to add a second HD and make a "mdadm -a". => so the functionality of "mdadm -C /dev/md0 -l raid1 -n 2 /dev/hda1 missing" and "mdadm -C /dev/md1 -l raid1 -n 2 /dev/hda2 missing" in autoyast is required Because, I didn't find anything about missing devices in the autoyast documentation, I tried to only change "/dev/hdb" to "missing", but that's not working... (see below) : : : <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>256M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>missing</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>256M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </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> <filesystem_id config:type="integer">131</filesystem_id> <chunk_size>4</chunk_size> <mount>/boot</mount> <format config:type="boolean">true</format> <filesystem config:type="symbol">xfs</filesystem> </raid_device> <raid_device> <device_name>/dev/md1</device_name> <lvm_group>vg00</lvm_group> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_type>raid1</raid_type> <filesystem_id config:type="integer">142</filesystem_id> <chunk_size>4</chunk_size> </raid_device> </raid> : : : Thanks in advance. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

2 1

error in create_update_source.sh + fix
by Stan Novogroudski 06 Sep '06

06 Sep '06

Please fix it: in create_update_source.sh line 101 use if ! [[ "$VALUE" -eq "SHA1" ]]; then instead of if ! [[ "$VALUE" =~ "SHA1" ]]; then Operator =~ is used in Perl, not in shell. After this fix is create_update_source.sh working. Best regards. Stan

3 2

init-scripts without network config
by Paul DiSciascio 06 Sep '06

06 Sep '06

init-scripts don't seem to work if there is no network config in SLES 10. So i added a network section to my autoinst.xml. The problem with this is that the default for eth0 is dhcp, which is not allowed on my network, so i set bootproto to "none", which had absolutely no affect. So I removed the /etc/sysconfig/network/ifcfg-eth0-* file in my init-script and rebooted. The problem with this solution is that /etc/hosts and /etc/resolv.conf are already modified by the installer by this point (i would like that to not happen.) Is there a better way besides setting bootproto to "none" that will make the network subsystem come up, but with no devices configured? Or failing that, is there a way to make init-scripts work without the network dependency? Thanks, Paul

2 1

Preload modules before hardware detection? (wrong scsi order)
by Frank Steiner 05 Sep '06

05 Sep '06

Hi, similar post was sent in July with title "Problem with the order of disks", where Michael Schulz had the same problem we have: SCSI controllers are detected in the wrong order, so that the disk that should be /dev/sda ends up as /dev/sde. This used to work with SuSE 9.0 where we loaded the module for the first controller with "insmod gdth" passed to linuxrc (we are using pxeboot). Now, with 10.1, the init process of YA starts a "Hardware detection" *before* loading the modules defined in the info file or passed to the command line. This makes the insmod option for linuxrc more or less superfluous and removes any control over the order in which modules are loaded during the AY boot. Here, it makes the fc modules load before the scsi modules, thus moving our scsi disk to /dev/sde. Is it possible to disable automatic hardware detection or load the modules before the hardware detection? Or could I try thinks like renaming the init binary in the initrd and install my own script there that's just modprobe gdth exec init.suse Of course, I would prefer a method without changing the initrd if possible... 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: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 8

OpenSUSE 10.1 Online update in autoyast
by Ian Grant 01 Sep '06

01 Sep '06

Does anyone have XML for OpenSUSE 10.1 to cause autoyast to do an online update at install time? I am hoping this is better than the farce we have to go through at the moment to run it after the autoyast install: it has to be run, interactively, four times to get the security/recommended updates done. Failing that, does anyone know how to run it from the command line so it doesn't need somoeone to press keys?

6 7

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall September 2006