December 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

[suse-autoinstall] configuring grub
by Thomas Holzapfel 12 Dec '05

12 Dec '05

Hi, I'm using autoyast to install SuSE 10.0 on a set of systems. I want to configure grub, which works fine using SuSE 9.3. I want to - set the boot loader location to the boot sector of my boot partition - activate the boot loader partition - set the boot menu timeout - set the vga mode - set the kernel parameters like resume and splash=verbose The corresponding part of my config file is <bootloader> <loader_type>grub</loader_type> <location>custom</location> <loader_device>/dev/sda1</loader_device> <activate config:type="boolean">true</activate> <repl_mbr config:type="boolean">false</repl_mbr> <global config:type="list"> <global_entry> <key>timeout</key> <value config:type="integer">5</value> </global_entry> </global> <sections config:type="list"> <section> <append>selinux=0 resume=/dev/sda8 splash=verbose showopts</append> <initial>1</initial> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>0</lines_cache_id> <name>SuSE Linux 10.0</name> <original_name>linux</original_name> <root>/dev/sda6</root> <type>image</type> <vga>794</vga> </section> ... </sections> </bootloader> I'm using the following directive to check the result of my config file <mode> <confirm config:type="boolean">true</confirm> </mode> Autoyast ignores the directives <location> and <loader_device>, instead MBR is selected as the boot loader location. The timeout setting in the global section is also ignored. I think all global settings are ignored. At last, in the section settings the directive <vga>794</vga> is set to blank and the splash=verbose option is replaced by splash=silent! Only activating the boot loader partition is set right. Any ideas, what's going wrong? Thanks, -- Thomas Holzapfel Lehrstuhl und Institut fuer Wasserbau und Wasserwirtschaft RWTH Aachen

2 1

Failure to auto-install 9.3/10.0 using same XML file....
by UNIX-admin 12 Dec '05

12 Dec '05

Hi everyone, I've been having one of those days, and I would like to know if anyone else has seen the same problems I have been experiencing... I have a Linux server running 9.2, serving installation sources via http for SuSE 9.2, 9.3, and 10. Using a 9.2 DVD, I can quite happily install a new system over the network using the following (IPs changed to protect the not-so-innocent, 10.20.30.59 is serving the sources via Apache): initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/9.2 autoyast=http://10.20.30.59:/conf/infra.xml However, if I use *EXACTLY* the same xml configuration file but this time using a 9.3 DVD... initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/9.3 autoyast=http://10.20.30.59:/conf/infra.xml it fails (as far as I can make out) with an "out of swap space" error. I of course then tried increasing swap, but received the same error, albeit I think a bit further along than before. Its hard to say for sure because it still fails installing the kernel source rpm, just not at the exact same point. Swap is now twice the size of core memory. I then tried (again using *EXACTLY* the same xml file) to install 10: initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/10.0 autoyast=http://10.20.30.59:/conf/infra.xml It got further, but the system appeared to completely hang about 25 seconds from completing the package install. I was unable to get any response at all. The hardware is a brand-new DL380-G4 with 2Gb RAM. The 9.2 installation source server has not been patched to the absolute latest (but why would this matter - I'm only using it to share the installation media, right?). I should also point out I suffer from the old problem with the network timeout due to spanning tree on the switches (don't think it has any bearing on the issue though). The DVDs are straight out of the box, and are the professional versions. The xml config file is nothing fancy - just sets up the partitioning, defines package selection, and runs a post-install script. I searched the net, and trawled through the archives (oh for a search facility ;-) ), but I couldn't find anything. Could someone please point me in the right direction? Thanks! Colin.

4 5

[suse-autoinstall] keeping partitions
by Thomas Holzapfel 12 Dec '05

12 Dec '05

Hi, I'm using autoyast to install SuSE 10.0 on a set of systems. Keeping partitions seems to be a problem. The partitiontable looks like Disk /dev/sda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 4 32098+ 83 Linux /dev/sda2 5 1279 10241437+ 7 HPFS/NTFS /dev/sda3 1280 2554 10241437+ 7 HPFS/NTFS /dev/sda4 2555 14593 96703267+ f W95 Ext'd (LBA) /dev/sda5 2555 2558 32098+ 83 Linux /dev/sda6 2559 3323 6144831 83 Linux /dev/sda7 3324 4088 6144831 83 Linux /dev/sda8 4089 4216 1028128+ 82 Linux swap /dev/sda9 4217 8041 30724281 83 Linux /dev/sda10 8042 13141 40965718+ 7 HPFS/NTFS /dev/sda11 13142 14593 11663158+ c W95 FAT32 (LBA) What I want to do is to keep all the partitions, just to format the boot- and root- partition of the new system (/dev/sda1 , /dev/sda6) and to set some mount points. In a first attempt the relevant part of my config file was <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext2</filesystem> <partition_nr config:type="integer">1</partition_nr> <mount>/boot</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">ext2</filesystem> <partition_nr config:type="integer">5</partition_nr> <mount>/export/suse/9.3/boot</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <partition_nr config:type="integer">6</partition_nr> <mount>/</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">reiser</filesystem> <partition_nr config:type="integer">7</partition_nr> <mount>/export/suse/9.3/root</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">reiser</filesystem> <partition_nr config:type="integer">9</partition_nr> <mount>/local</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">fat</filesystem> <partition_nr config:type="integer">11</partition_nr> <mount>/transfer</mount> </partition> </partitions> </drive> </partitioning> In the "Create partition plans" stage I got the error message "Error while configuring partitions. Try again." After a series of try and error, nearly all works fine with the following modifications in the config file: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext2</filesystem> <partition_nr config:type="integer">1</partition_nr> <mount>/boot</mount> </partition> ...  ... </partitions> </drive> <use>1</use> </partitioning> Using the directive above to set the mount point of partition nr 5 results in the same error message "Error while configuring partitions. Try again." Any ideas to fix that problem rather than setting the mount point manually? Is it possible to prevent autoyast from setting the mount points to ntfs-partitions? -- thanks, Thomas Holzapfel Institut fuer Wasserbau und Wasserwirtschaft RWTH Aachen

3 5

32-bit binaries on 64-bit machines
by Thorbjörn Jemander 09 Dec '05

09 Dec '05

Hello, some time ago I found a message on this list that explained how to disable the 64-bit check in the early start-up process. However, no matter how I look now, I can't find it. So, how do I force the 32-bit binares to be installed, despite that I install on a 64-bit machine? (automacically) Thanks in advance, ________________________________________________ Dr. Thorbjörn Jemander, Senior RT/Systems Expert Enea Epact AB, Teknikringen 8, Linköping, Sweden thje(a)enea.se +46 13 465 58 67 www.enea.com

1 1

where to store the config?
by fisch 07 Dec '05

07 Dec '05

Hi, I have a problem, I have to make an autoyast install (SuSE 10.0) for clients that do not have floppy, cd and network. I only have an external USB-DVD and an USB-stick. I tried to store the autoyast.xml on the USB-stick but Yast can not access it. I am confused because of the situation: /dev/sda -> SATA harddisk /dev/sdb -> USB-Stick I give the bootoption: autoyast=/dev/sdb1/autoyast.xml Yast shows the error: Can't find /dev/sdb1/autoyast.xml when I change into tty I am able to mount /dev/sdb1 and can access the autoyast.xml what's going wrong? Is it possible to "remaster" the install-dvd and store the autoyast.xml there? bye fisch

2 1

RE: [suse-autoinstall] Failure to auto-install 9.3/10.0 usingsame XML file....
by Yan Fitterer 07 Dec '05

07 Dec '05

> Or are you saying what I need to do is generate xml config files for > each distribution and then use rules to select the appropriate ones > (implying that the config files generated are different in some way > between each distribution)? Yes. You can avoid duplication of identical elements by using classes (if you feel fancy). Yan

1 0

Re: [suse-autoinstall] Failure to auto-install 9.3/10.0 using same XML file....
by Yan Fitterer 07 Dec '05

07 Dec '05

Using rules, it is possible to have a single "install system" (i.e. a set of xml config files) that works for different versions with different configs. As a starting point, you should look at: http://www.suse.de/~ug/autoyast_doc/rulesandclass.html Hint: create a rule that detects the OS version being installed (see installed_product and/or installed_product_version attributes), and select a profile based on that.

1 0

Re: [suse-autoinstall] Failure to auto-install 9.3/10.0 using same XML file....
by Hans-Joachim Ehlers 07 Dec '05

07 Dec '05

Hi, i had a similar problem with Suse 9.3 and installation via http. For a minimum installation via http i needed 2 GB of swap space so depending on your software selection it might be much more. For testing i would do one of the following - increase swap to 8GB - use an NFS installation I think in the docu is also something mentioned about copy the software first to the disk before installing it. hth Hajo >>> UNIX-admin <UNIX-admin(a)m151.uklinux.net> 06/12/05 22:13 >>> Hi everyone, I've been having one of those days, and I would like to know if anyone else has seen the same problems I have been experiencing... I have a Linux server running 9.2, serving installation sources via http for SuSE 9.2, 9.3, and 10. Using a 9.2 DVD, I can quite happily install a new system over the network using the following (IPs changed to protect the not-so-innocent, 10.20.30.59 is serving the sources via Apache): initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/9.2 autoyast=http://10.20.30.59:/conf/infra.xml However, if I use *EXACTLY* the same xml configuration file but this time using a 9.3 DVD... initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/9.3 autoyast=http://10.20.30.59:/conf/infra.xml it fails (as far as I can make out) with an "out of swap space" error. I of course then tried increasing swap, but received the same error, albeit I think a bit further along than before. Its hard to say for sure because it still fails installing the kernel source rpm, just not at the exact same point. Swap is now twice the size of core memory. I then tried (again using *EXACTLY* the same xml file) to install 10: initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/10.0 autoyast=http://10.20.30.59:/conf/infra.xml It got further, but the system appeared to completely hang about 25 seconds from completing the package install. I was unable to get any response at all. The hardware is a brand-new DL380-G4 with 2Gb RAM. The 9.2 installation source server has not been patched to the absolute latest (but why would this matter - I'm only using it to share the installation media, right?). I should also point out I suffer from the old problem with the network timeout due to spanning tree on the switches (don't think it has any bearing on the issue though). The DVDs are straight out of the box, and are the professional versions. The xml config file is nothing fancy - just sets up the partitioning, defines package selection, and runs a post-install script. I searched the net, and trawled through the archives (oh for a search facility ;-) ), but I couldn't find anything. Could someone please point me in the right direction? Thanks! Colin. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] documentation of XML control file anywher e?
by Gunreben, Peter (Peter) 06 Dec '05

06 Dec '05

Paul, > From: Paul Beltrani > On 12/5/05, Gunreben, Peter (Peter) <pgunreben(a)lucent.com> wrote: > > [...] > > > Is there some place where I can find the exact details of all > > > the tags and attributes used by the autoyast xml control file? > > > > http://www.suse.de/~ug/ > ... > > Perhaps I've missed something. Where at that site is a list of the > resources/properties that may be specified in the control file? There's not really a list, but you can find the resources in the chapters 4-6 in: http://www.suse.de/~ug/autoyast_doc/index.html However, a complete list of xml tags would be a good idea. Uwe? Peter.

2 1

Partitioning problems doing RAID + LVM on SL 10.0
by Gavin Carr 06 Dec '05

06 Dec '05

Hi, I'm having all kinds of problems trying to get a RAID1 + LVM partitioning scheme working on SL10.0. I'm wanting this: /dev/sda: swap auto raid1a 100MB raid2a 100MB raid3a 100MB raid4a max /dev/sdb: swap auto raid1b 100MB raid2b 100MB raid3b 100MB raid4b max RAID: md0: raid1a + raid1b, /boot md1: raid2a + raid2b, /boot2 md2: raid3a + raid3b, /boot3 md3: raid4a + raid4b, LVM physical volume LVM: volume group /dev/system: /dev/md3 logical volumes: / ext3 5GB /data ext3 200GB i.e. an LVM physical volume on a RAID1 partition. The partitioning fragment of my autoyast config looks like this: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md3</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md3</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">0</partition_nr> <mount>/boot</mount> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <mount>/boot2</mount> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <mount>/boot3</mount> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <lvm_group>system</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">3</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>root1</lv_name> <mount>/</mount> <size>5gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>data</lv_name> <mount>/data</mount> <size>200gb</size> </partition> </partitions> <pesize>32M</pesize> <use>all</use> </drive> </partitioning> This validates against the DTDs with xmllint, and it _almost_ works under autoyast. Here's the Partitioning confirmation output: Create extended partition /dev/sda1 (232.8 GB) Create swap partition /dev/sda5 (1.0 GB) Create partition /dev/sda6 (101.9 MB) with id=8E Create partition /dev/sda7 (101.9 MB) with id=8E Create partition /dev/sda8 (101.9 MB) with id=8E Create partition /dev/sda9 (231.5 GB) with id=8E Create extended partition /dev/sdb1 (232.8 GB) Create swap partition /dev/sdb5 (1.0 GB) Create partition /dev/sdb6 (101.9 MB) with id=FD Create partition /dev/sdb7 (101.9 MB) with id=FD Create partition /dev/sdb8 (101.9 MB) with id=FD Create partition /dev/sdb9 (231.5 GB) with id=FD Create software RAID /dev/md0 (101.9 MB) for /boot with ext3 Create software RAID /dev/md1 (101.9 MB) for /boot2 with ext3 Create software RAID /dev/md2 (101.9 MB) for /boot3 with ext3 Create software RAID /dev/md3 (231.5 GB) Create volume group system Create logical volume /dev/system/data (200.0 GB) for /data with ext3 Create logical volume /dev/system/root1 (5.0 GB) for / with ext3 The problem is that somehow it comes up with the wrong partition type /dev/sda[6-9] partitions, making them LVM partitions (8E) instead of RAID partitions (FD), it's added all the /dev/sda partitions to the /dev/system volume group, and the raid partitions only contain the /dev/sdb members, and so raid volume creation fails. Does this look like an error in my config somewhere, or a bug? If I correct these problems by hand, everything works. In addition, if I try and initialise the drives I get even more bizarre problems - the /dev/sda partitions disappear altogther. I've been deleting the partition tables by hand to get it this far. This is x86_64 on sata drives, in case that matters. Thanks a lot for any clues/ideas. Been banging my head against this for a day and a half now ... Cheers, Gavin

3 3