September 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

SLES 10 and disk to disk autoyast installation
by Wenk, Moritz 27 Sep '06

27 Sep '06

Hello, I am trying to autoinstall SLES 10 in HD mode (disk to disk). It worked for SLES 9 but does not any longer with SLES 10. The problem is that YaST tries to mount my source partition when formating the other partitions and this fails because the source partition is alerady mounted. This is my partition schema: sda1: ext3 16GB sda2: swap sda3: fat32 16BG The third partition does contain the installation source. This is the autoyast partition plan: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <is_evms_vg config:type="boolean">false</is_evms_vg> <is_lvm_vg config:type="boolean">false</is_lvm_vg> <use>1,2</use> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> <fsopt>defaults,acl</fsopt> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>16gb</size> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>512mb</size> </partition> </partitions> </drive> </partitioning> And the kernel command line for autoyast: install=hd://sda3/suse AutoYaST=file:///autoyast.xml The autoyast file (autoyast.xml) is contained in the initrd. Kernel and initrd are booted from sda3. This worked for SLES 9 with a little trick (unmounting /mounts/extra in a pre-install script). Any ideas how to get the disk to disk autoyast installation working for SLES 10? Regards, i. A. Moritz Wenk Specialist Product Engineering & Development Corporate Technology Software MAXDATA Systeme GmbH Elbestraße 12-16 D-45768 Marl Telefon: +49 (0) 2365 952-2715 Telefax: +49 (0) 2365 952-2279 E-Mail : moritz.wenk(a)maxdata.de http://www.maxdata.com

2 2

merge scripts
by Arvid Walter 27 Sep '06

27 Sep '06

Hi, I cannot merge scripts: --snip-- <?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> <classes config:type=list> <class> <class_name>Repositories</class_name> <configuration>apt-suse10.xml</configuration> </class> </classes> <scripts> <init-scripts config:type=list> <script> <source> <![CDATA[#!/bin/sh apt-get install nagios-plugins ]]> </source> </script> </init-scripts> </scripts> </profile> --snap-- --snip-- <?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> <signature-handling> <accept_unsigned_file config:type=boolean>true</accept_unsigned_file> </signature-handling> </general> <add-on> <add_on_products config:type=list> <listentry> <media_url>nfs://10.x.x.x/usr/local/Unattended/vmware/suse/</media_url> <product>VMware-server</product> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> <software> <packages config:type=list> <package>VMware-server</package> <package>gcc</package> <package>gcc-c++</package> <package>xorg-x11-libs</package> <package>fontconfig</package> <package>freetype2</package> <package>compat</package> <package>kernel-source</package> <package>xinetd</package> <package>wget</package> <package>patch</package> </packages> </software> <scripts> <init-scripts config:type=list> <script> <network_needed config:type=boolean>true</network_needed> <source> <![CDATA[#!/bin/sh echo -n Switching multicast dns off if [ ! $(grep mdns /etc/host.conf) ]; then echo mdns off >> /etc/host.conf; fi echo done echo -n Changing service number 902 to 904 cp /etc/services /etc/services.backup awk '{res=gsub(^902/, \t904/, $2); print $0 }' /etc/services.backup > /etc/services echo done echo -n Configure vmware server ... /usr/bin/vmware-config.pl default EULA_AGREED=yes rm -f /etc/vmware/not_configured echo done echo Installing the vmware web interface cd /tmp/ wget http://10.x.x.x/vmware/VMware-mui-current.tar.gz tar zxvf VMware-mui-current.tar.gz cd vmware-mui-distrib echo -n Applying patches wget http://10.x.x.x/vmware/vmware-install.pl.p0 patch -p0 < vmware-install.pl.p0 echo done echo -n Installing and configuring vmware server web interface ... perl vmware-install.pl --default EULA_AGREED=yes echo done echo -n Preparing xinetd insserv xinetd echo done]]> </source> </script> </init-scripts> </scripts> </profile> --snap-- Both xmls are beeing merged using the nagios part only. How can i use more than one script.

2 1

RE: [suse-autoinstall] Disk detection order
by Marlier, Ian 26 Sep '06

26 Sep '06

> -----Original Message----- > From: Karsten Künne [mailto:kuenne@rentec.com] > Sent: Friday, September 22, 2006 10:55 AM > To: suse-autoinstall(a)suse.com > Cc: Marlier, Ian > Subject: Re: [suse-autoinstall] Disk detection order > > On Friday 22 September 2006 10:11, Marlier, Ian wrote: > > Hey, all -- > > > > This is returning to an old question for me, as I've started creating > > 10.1 installation profiles now that the zypp/zmd issues seem to be > > fixed. > > > > I'm trying to install onto a server with the following: > > - 2 x 80GB SATA, on a Silicon Image controller, exported as JBOD. > > - 3 x 250GB SATA, on a 3ware 9550 controller, exported as a single RAID > > 5 > > > > I'm creating a software RAID 1 on the 80GB drives, and using that as the > > root partition. The RAID5 being partitioned for LVM, though not > > allocated yet. > > > > When autoyast starts the install, it autodetects the installed hardware > > (in, I think, alphabetical order?). The 3ware RAID array is detected as > > /dev/sda, and the two SiI disks as /dev/sdb and /dev/sdc > > > > When the install is complete and the system reboots, this order has > > switched; the SiI disks are /dev/sda and /dev/sdb, and the 3ware RAID is > > /dev/sdc. > > > > You have to load the modules for your controllers in the right order. Put > them > into the <initrd_modules> section in your profile in the proper order, the > 3ware module first and then the other one. Well, I'm hoping to have the 3ware RAID as /dev/sdc, so I have my initrd_modules section set up this way: <initrd_modules config:type="list"> <initrd_module> <module>amd74xx</module> </initrd_module> <initrd_module> <module>sata_sil</module> </initrd_module> <initrd_module> <module>3w_9xxx</module> </initrd_module> <initrd_module> <module>processor</module> </initrd_module> <initrd_module> <module>thermal</module> </initrd_module> <initrd_module> <module>fan</module> </initrd_module> <initrd_module> <module>jbd</module> </initrd_module> <initrd_module> <module>ext3</module> </initrd_module> <initrd_module> <module>raid1</module> </initrd_module> </initrd_modules> But it looks like it doesn't apply to the autoinstall process; the detection order is correct after the first installed boot, but not during the install process itself...

3 2

Trouble on OpenPBS server for Sles10.0 x86_64
by hp9 25 Sep '06

25 Sep '06

Hello, I installed bother server and nodes. But I can not configure OpenPBS server. The trouble is the follow: ------------------------------------------------------------- funmat:~ # qmgr -c "set server scheduling=true" qmgr obj= svr=default: Unauthorized Request funmat:~ # qmgr Max open servers: 4 Qmgr: create queue qdefault qmgr obj=qdefault svr=default: Unauthorized Request ----------------------------------------------------------- Anyone has experience to configure OpenPBS in SUSE? Thanks, hongbin

1 0

Troubles installing SLES10 from a FreeBSD Server
by Beat Rubischon 25 Sep '06

25 Sep '06

Hello! I try to set up SLES10 from a NFS installation source based on a Panasas storage system. From the software point of view, the Panasas is a FreeBSD 4 NFS server and offers the following RPC services: program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100005 3 udp 1009 mountd 100005 3 tcp 1023 mountd 100005 1 udp 1009 mountd 100005 1 tcp 1023 mountd 100003 3 udp 2049 nfs 100003 3 tcp 2049 nfs 100021 1 udp 996 nlockmgr 100021 3 udp 996 nlockmgr 100021 4 udp 996 nlockmgr 100021 1 tcp 1021 nlockmgr 100021 3 tcp 1021 nlockmgr 100021 4 tcp 1021 nlockmgr 100024 1 udp 988 status 100024 1 tcp 1020 status An final installed SLES10 is able to mount the shared filesystems, but not the installer. In the initrd is a /lbin/mount (Busybox?) which tries the wrong protocol (NFSv4?) and fails: mount("172.16.9.1:/cluster", "/mnt", "nfs", MS_MGC_VAL|MS_RDONLY, "\4") = -1 EPROTONOSUPPORT (Protocol not supported) Surprisingly, the installation from a stoneage RedHat only supporting NFSv2/v3 over UDP just works. Is there any possibility to replace the mount command in the initrd? Or have a look at the sources to get further information? Beat -- \|/ Beat Rubischon <beat(a)0x1b.ch> ( 0^0 ) http://www.0x1b.ch/~beat/ oOO--(_)--OOo--------------------------------------------------- Meine Erlebnisse, Gedanken und Traeume: http://www.0x1b.ch/blog/

1 0

AW: [suse-autoinstall] SLES 10 and disk to disk autoyast installation
by Wenk, Moritz 25 Sep '06

25 Sep '06

Hi, it is the same error code, but for me it is the partition containing the sources (the SLES CDs) that autoyast tries to mount. -----Ursprüngliche Nachricht----- Von: Niall Calvert [mailto:niall@calvert.cn] Gesendet: Freitag, 22. September 2006 18:29 An: Wenk, Moritz; suse-autoinstall(a)suse.com Betreff: RE: [suse-autoinstall] SLES 10 and disk to disk autoyast installation I've also been trying also to get disk-to-disk install working, also with EVMS volumes; do you get a similar error message to the following: Failure occurred during following action: Mount /dev/sda1 to /boot System error code was -3003 mount -t reiserfs /dev/sda1 /mnt/boot mount: /dev/sda1 already mounted or /mnt/boot busy Best regards Niall -----Original Message----- From: Wenk, Moritz [mailto:Moritz.Wenk@maxdata.com] Sent: 22 September 2006 14:15 To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] SLES 10 and disk to disk autoyast installation Hello, I am trying to autoinstall SLES 10 in HD mode (disk to disk). It worked for SLES 9 but does not any longer with SLES 10. The problem is that YaST tries to mount my source partition when formating the other partitions and this fails because the source partition is alerady mounted. This is my partition schema: sda1: ext3 16GB sda2: swap sda3: fat32 16BG The third partition does contain the installation source. This is the autoyast partition plan: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <is_evms_vg config:type="boolean">false</is_evms_vg> <is_lvm_vg config:type="boolean">false</is_lvm_vg> <use>1,2</use> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> <fsopt>defaults,acl</fsopt> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>16gb</size> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>512mb</size> </partition> </partitions> </drive> </partitioning> And the kernel command line for autoyast: install=hd://sda3/suse AutoYaST=file:///autoyast.xml The autoyast file (autoyast.xml) is contained in the initrd. Kernel and initrd are booted from sda3. This worked for SLES 9 with a little trick (unmounting /mounts/extra in a pre-install script). Any ideas how to get the disk to disk autoyast installation working for SLES 10? Regards, i. A. Moritz Wenk Specialist Product Engineering & Development Corporate Technology Software MAXDATA Systeme GmbH Elbestraße 12-16 D-45768 Marl Telefon: +49 (0) 2365 952-2715 Telefax: +49 (0) 2365 952-2279 E-Mail : moritz.wenk(a)maxdata.de http://www.maxdata.com -- 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] SLES 10 and disk to disk autoyast installation
by Niall Calvert 22 Sep '06

22 Sep '06

I've also been trying also to get disk-to-disk install working, also with EVMS volumes; do you get a similar error message to the following: Failure occurred during following action: Mount /dev/sda1 to /boot System error code was -3003 mount -t reiserfs /dev/sda1 /mnt/boot mount: /dev/sda1 already mounted or /mnt/boot busy Best regards Niall -----Original Message----- From: Wenk, Moritz [mailto:Moritz.Wenk@maxdata.com] Sent: 22 September 2006 14:15 To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] SLES 10 and disk to disk autoyast installation Hello, I am trying to autoinstall SLES 10 in HD mode (disk to disk). It worked for SLES 9 but does not any longer with SLES 10. The problem is that YaST tries to mount my source partition when formating the other partitions and this fails because the source partition is alerady mounted. This is my partition schema: sda1: ext3 16GB sda2: swap sda3: fat32 16BG The third partition does contain the installation source. This is the autoyast partition plan: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <is_evms_vg config:type="boolean">false</is_evms_vg> <is_lvm_vg config:type="boolean">false</is_lvm_vg> <use>1,2</use> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> <fsopt>defaults,acl</fsopt> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>16gb</size> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>512mb</size> </partition> </partitions> </drive> </partitioning> And the kernel command line for autoyast: install=hd://sda3/suse AutoYaST=file:///autoyast.xml The autoyast file (autoyast.xml) is contained in the initrd. Kernel and initrd are booted from sda3. This worked for SLES 9 with a little trick (unmounting /mounts/extra in a pre-install script). Any ideas how to get the disk to disk autoyast installation working for SLES 10? Regards, i. A. Moritz Wenk Specialist Product Engineering & Development Corporate Technology Software MAXDATA Systeme GmbH Elbestraße 12-16 D-45768 Marl Telefon: +49 (0) 2365 952-2715 Telefax: +49 (0) 2365 952-2279 E-Mail : moritz.wenk(a)maxdata.de http://www.maxdata.com -- 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] Auto installation SLES9 SP2
by Lewandowski, Kelly 22 Sep '06

22 Sep '06

Hello again, I have fixed the version mismatch for the bcraid.ko problem. I now see the disks even though they are not seen correctly. I created an autoyast file to see if it works. Every thing works for the automated install. The problem: The disk drives are seen as individual drives vs the raid 1 or raid 5 that is set via the Broadcom cards bios. When I initiate the install, modules are loaded up, SLES loads sata_svw.ko, then loads bcraid.ko. ** In the autoyast file I have taken out the sata_svw module ** Autoinstall starts and installs SLES on an individual drive instead of the raid. I did a manual install (cd's and floppy) watching the loading of the modules. The Broadcom is loaded at the top. When the manual install is done we change the (using YaST /etc/sysconfig editor) System>kernel>INITRD_MODULES by deleting the sata-svw. Question: How do I change / modify the boot sequence to load the bcraid.ko module before or instead of the sata_svw.ko module. If this involves remaking the initrd file (witch I think it might not sure) can someone enlighten me on the procedures for this. Thanks, Kelly Lewandowski -----Original Message----- From: Lewandowski, Kelly [mailto:KLewandowski@breecehill.com] Sent: Wednesday, September 20, 2006 8:48 AM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Auto installation SLES9 SP2 Thanks Yan, We are slated to upgrade when we have enough cycles to thoroughly test a new version against our platform. Our server also has a tape library, with an LTO-3 tape drive, and 10 tape cartridges. Front half of the box is a library, back half is a server with sata drives, and a DVD-RW. All cards in the server are half height cards to keep it at 4U. When I use the driver image on a manual install (CD's and usb floppy) the drivers that I have work fine. I will run through another manual install and verify. Thanks, Kelly Lewandowski -----Original Message----- From: Yan Fitterer [mailto:yfitterer@novell.com] Sent: Wednesday, September 20, 2006 1:52 AM To: Lewandowski, Kelly; suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Auto installation SLES9 SP2 The overall process / setup seems sound. Looks like a classic case of version mismatch between bcraid.ko and running kernel. The binary module must be built for exactly the kernel version that it is used with. Either the kernel that runs during install isn't the one you expect, or the kernel module hasn't been built for quite the same version. Check the exact version of the kernel that's running during install (making sure it _is_ indeed the SP2 version, in case of install source problem). Then verify that the bcraid module you're using has been build for that very same version. Why are you using SLES9 SP2 anyway? That's old, outdated, and insecure - given the number of security updates that have been released since. Do verify that the bcraid driver hasn't been built for an SP3 (or later...) kernel. There should be no incompatibility issues with updating to SP3 (+ latest patches). Yan >>> On Tue, Sep 19, 2006 at 11:23 PM, in message <FEF375A836207347A500D2F7F65DA0665A21B9(a)exchange2k3.BHT.local>, "Lewandowski, Kelly" <KLewandowski(a)breecehill.com> wrote: > Hello all, > > > > I have been tasked by my manager to create a SLES auto installation > process for our 2 server products. > > > > We are using SLES 9 SP2. > > > > The 2 servers: > > > > 7210 Intel motherboard running a P4 processor with a BroadCom BC4852 > SATA Raid card. (8 SATA drives) > > 7520 Intel Motherboard running dual Xeon processors with a BroadCom > BC4852 SATA RAID card. (8 SATA drives) > > > > I have tried many of the suggestions on this list but nothing seems to > fully work. > > So any suggestions would be appreciated. The steps and setup of what I > have done are listed below. > > > > This is for the 7520 Xeon only. I am trying to get one system to work > first. > > > > 1. Setup > > a. 1 windows 2003 server running DHCP > b. 1 SLES9 SP2 2.6.5- 7.191- default running the tftp server > and nfs server. > c. 1 new Xeon server ready to image. 35 G RAID 5 across all > 8 drives. > > 2. Steps > > a. SLES server set up for tftp boot. > > /tftpboot Files are: initrd linux pxelinux.0 ./pxelinux.cfg/default > > default file: > > > > label linux > > kernel linux > > append initrd=initrd install=nfs://xxx.xxx.xxx.xxx/install/SLES9x64 > vga=0x0314 > > > > b. SLES server set up for NFS. 64 bit cd's plus server > pack cd's created via YaST > > /install/SLES9x64 > > c. BroadCom driver image dd'd to floppy then copied over > into the sp2/cd1/linux/suse/x86_64/install/update.tar.gz. Also copied > over ./modules/bcraid.ko > d. Control file is the one right off the cd's. Have not > used YaST to create one as of yet as I needed to make sure everything > loaded manual method first. > > 2. Problems > > a. new system boots. Gets its ip and location of the boot > file from the DHCP server. Installation begins. Accept the agreements. > Accept the languages. When it gets to the checking for hard disks it > comes back with none. > b. Errors on tty3 are as follows. > > Dud 100: Service Pack 2 > > insmod - f /modules/bcraid.ko > > insmod: error inserting '/modules/bcraid.ko': - 1 invalid module format > > c. Errors on tty4 are as follows. > > kernel: bcraid: disagrees about version of symbol struct_module > > > > Questions: > > I have tried using both the - smp- 64 and the - default- 64 from Broadcom. > Both show the same errors as above. > > > > Thanks, > > > > Kelly Lewandowski > > > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Disk detection order
by Marlier, Ian 22 Sep '06

22 Sep '06

Hey, all -- This is returning to an old question for me, as I've started creating 10.1 installation profiles now that the zypp/zmd issues seem to be fixed. I'm trying to install onto a server with the following: - 2 x 80GB SATA, on a Silicon Image controller, exported as JBOD. - 3 x 250GB SATA, on a 3ware 9550 controller, exported as a single RAID 5 I'm creating a software RAID 1 on the 80GB drives, and using that as the root partition. The RAID5 being partitioned for LVM, though not allocated yet. When autoyast starts the install, it autodetects the installed hardware (in, I think, alphabetical order?). The 3ware RAID array is detected as /dev/sda, and the two SiI disks as /dev/sdb and /dev/sdc When the install is complete and the system reboots, this order has switched; the SiI disks are /dev/sda and /dev/sdb, and the 3ware RAID is /dev/sdc. I would like for the behavior to be consistent, one way or the other, but I can't seem to figure out how to force it to be. (In an ideal world, the 3ware RAID would be /dev/sdc during install and after initial boot.) Anyone have any suggestions, or pointers to documentation that I may have missed? I've been trying to keep track through Uwe's (many and wonderful!) improvements to autoyast, but may have missed something along the way... TIA! - Ian

2 1

firewall config vs apache config
by Rich 21 Sep '06

21 Sep '06

i am performing an autoinstall of sles 10 with a control file. it seems that firewall config in http-server conflicts with firewall settings that instruct to open access for http service. if <firewall> section has http as an allowed service, but <http-server> has <firewall config:type="boolean"> set to false (or missing), port 80 is not opened. is this the intended behaviour or have i missed something ? -- Rich

1 0