September 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 05 Mar '08

05 Mar '08

I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Friday, 30 June 2006 12:50 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 29 June 2006 16:45, Manfred Hollstein wrote: > > > If that fails, you have kinternet installed; add that to > the list and it > > should work. > > good point. > <remove-packages> can not break dependencies and so it's very > likely that > there is still a package that needs those packages. > I did a very small installation with no X - so it worked for me. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug > now playing Covenant - Wasteland > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 6

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

Does anyone know if it is possible to use the 'dirinstall' from the command line? For instance i would like to be able to do something like: # yast dirinstall -d /someroot -s mypackages.sel If i do yast -h it says: "Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]" But is there a way to find out what 'module specific parameters' are available for a specific module? Thanks, Teun

3 2

Kernel Options
by discip＠pjm.com 06 Oct '06

06 Oct '06

Is there an easy way to automatically append an option to the default kernel that is installed? Or do I need to hack at this with some perl? Thanks, Paul

2 2

RE: [suse-autoinstall] autoyast freezes
by Marlier, Ian 29 Sep '06

29 Sep '06

> I'm doing an autoyast install with a SuSE 10.0 DVD. > First I have a problem with booting it up. It stops > at setting dhcp. I have three NICs in the box. > It will not work with the Intel(e1000) and couple of > RTL based. > > The only way I managed to boot thing up is trough an > RTL based NIC and by NFS based install. I chose > NFS server and dir, put the autoyast line and system > boots but only after it fails to dhcp on intel NIC. I'm assuming that you're using PXE to pass the install initrd and everything? Assuming so, you might try pausing the PXE process when the Intel NIC is trying to get an IP address, by hitting the "Pause/Break" key on your keyboard. Let it sit for about 30-60 seconds, and then hit space to start the process back up. (This situation -- where the NIC is on a network with DHCP, but doesn't get an address -- can be an indication that negotiation between the NIC and the switch to which it's network is taking a while -- and that the PXE process times out before the link is negotiated and brought up. It's happened with some of my machines, though only in cases where the networking hardware behind them is Cisco)

4 8

RE: [suse-autoinstall] Kernel Options
by GUNREBEN, PETER (Peter) 29 Sep '06

29 Sep '06

Paul, discip(a)pjm.com wrote: > discip(a)pjm.com wrote: > > Is there an easy way to automatically append an option to the > > default kernel that is installed? > > Or do I need to hack at this with some perl?> > > [...] > > Perfect! If autoyast actually created a valid document that > I could validate, or if there was a DTD available, I would > not have these issues. 1) You can use "yast2 autoyast" to generate or edit the XML-Files. Actually the XML-Code I've provided was generated using "yast2 autoyast". 2) There are DTD files available, see /usr/share/autoinstall/dtd/profile.dtd in RPM-Package: autoyast2-installation-2.13.56-3 Peter.

2 1

autoyast freezes
by Babarovic Ivica 28 Sep '06

28 Sep '06

Hi! I'm doing an autoyast install with a SuSE 10.0 DVD. First I have a problem with booting it up. It stops at setting dhcp. I have three NICs in the box. It will not work with the Intel(e1000) and couple of RTL based. The only way I managed to boot thing up is trough an RTL based NIC and by NFS based install. I chose NFS server and dir, put the autoyast line and system boots but only after it fails to dhcp on intel NIC. Ok ... I've managed to somehow install the system with hopefully correct xml setup file. The way I got this file is I first manually installed the system, exported the xml file with autoyast's tools menu and then edited that file untill it finally passed trough. Anyway ... now installation stops at first stage and box just freezes up. It will not reboot. After manually rebooting I get stuck at the grub prompt. I can see that menu.lst file is almost empty. What might be causing this? Best regards, I.B.

1 0

RE: [suse-autoinstall] Kernel Options
by GUNREBEN, PETER (Peter) 28 Sep '06

28 Sep '06

Paul, discip(a)pjm.com wrote: > Is there an easy way to automatically append an option to the > default kernel that is installed? > Or do I need to hack at this with some perl? What about: ================ <bootloader> <activate config:type="boolean">true</activate> <global> <default></default> <embed_stage1.5 config:type="boolean">false</embed_stage1.5> <gfxmenu>/boot/message</gfxmenu> <prompt>1</prompt> <timeout config:type="integer">8</timeout> </global> <loader_device></loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr> <sections config:type="list"> <section> <append> splash=silent showopts ***MYOPTIONS*** </append> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <name>SuSE 10.1</name> <original_name>linux</original_name> <root></root> <type>image</type> <vga></vga> </section> </sections> </bootloader> ================ You can create this also with "yast2 autoyast", of course. Peter.

2 1

Online Update not functioning after autoinstall
by Marlier, Ian 27 Sep '06

27 Sep '06

Hey, all -- Working on autobuilding with SUSE 10.1. I've got a local install source, rsynced from mirrors.kernel.org (I think it was). The installation works fine, but after install, Online Updates doesn't function. The error that I get when trying to configure Online Update is "No products to register". It looks like that error is thrown when the products returned by `/usr/lib64/zmd/query-pool products` don't intersect with Novell's list of supported SUSE products. And yet... [root@(fts0/dbopteron5):~]# /usr/lib64/zmd/query-pool products |product|SUSE-Linux-10.1-FTP|10.1-0|x86_64 [root@(fts0/dbopteron5):~]# and SUSE-Linux-10.1-FTP is one of the products returned by novell's registration server... This does NOT happen if I install manually, using the same local source (that's why I'm sending this here...) Has anyone: - Seen this? - Fixed this? If not, is it a bug with autoyast, or a bug more generally with zmd?

1 0

FW: Autoyast fails when trying to mount /boot with other EVMS Partitions
by Niall Calvert 27 Sep '06

27 Sep '06

I've being trying to identify a solution to an autoinstall problem for several weeks now without success and would appreciate some assistance. I'm trying to install sles10 from media located on a hard-drive partition, which was copied from the installation DVD. The problem does not occur when installing from the DVD using the same autoinst.xml file. I get the following error message after the volumes and boot partition has been formatted: 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 >From spare console I see that nothing is mounted to /boot when the error occurs. However sda1 shows under /dev/evms so I suspect that sda1 is being used by EVMS in error. I tried applying the 'sles10_root_fix_v0.2' that I found on the Autoyast download area however this causes a different error. Thanks in advance for any suggestions on how to fix the problem. Best regards Niall Logs etc below. Grub Boot Config kernel (hd1,0)/boot/x86_64/loader/linux splash=verbose showopts ip=dhcp ramdisk_size=65536 install=hd://sdb3/software/sles10/sles10dvd/. autoyast=device://sdb1/autoinst.xml initrd (hd1,0)/boot/x86_64/loader/initrd Tail of Y2log file 2006-09-10 03:04:53,555 INFO libstorage(3024) - Volume.cc(checkDevice):962 checkDevice:/dev/sda1 ret:0 2006-09-10 03:04:53,555 INFO libstorage(3024) - SystemCmd.cc(SystemCmd):44 Konstruktor SystemCmd Nr:0 2006-09-10 03:04:53,555 INFO libstorage(3024) - Volume.cc(mount):1621 device:/dev/sda1 mp:/mnt/boot 2006-09-10 03:04:53,555 INFO libstorage(3024) - Volume.cc(mount):1626 device:/dev/sda1 mp:/mnt/boot 2006-09-10 03:04:53,555 INFO libstorage(3024) - SystemCmd.cc(execute):160 SystemCmd Executing:"modprobe reiserfs" 2006-09-10 03:04:53,563 INFO libstorage(3024) - SystemCmd.cc(doExecute):305 system() Returns:0 2006-09-10 03:04:53,563 INFO libstorage(3024) - SystemCmd.cc(execute):160 SystemCmd Executing:"mount -t reiserfs /dev/sda1 /mnt/boot" 2006-09-10 03:04:53,572 INFO libstorage(3024) - SystemCmd.cc(addLine):625 Adding Line 1 "mount: /dev/sda1 already mounted or /mnt/boot busy" 2006-09-10 03:04:53,572 INFO libstorage(3024) - SystemCmd.cc(getUntilEOF):591 pid:3902 added lines:1 stderr:1 2006-09-10 03:04:53,572 INFO libstorage(3024) - SystemCmd.cc(doExecute):305 system() Returns:32 2006-09-10 03:04:53,572 INFO libstorage(3024) - SystemCmd.cc(logOutput):636 stderr:mount: /dev/sda1 already mounted or /mnt/boot busy 2006-09-10 03:04:53,572 INFO libstorage(3024) - Volume.cc(mount):1667 ret:-3003 2006-09-10 03:04:53,572 INFO libstorage(3024) - Volume.cc(doMount):1011 ret:-3003 2006-09-10 03:04:53,572 INFO libstorage(3024) - Container.cc(commitChanges):148 ret:-3003 2006-09-10 03:04:53,572 INFO libstorage(3024) - Disk.cc(commitChanges):1618 ret:-3003 2006-09-10 03:04:53,572 INFO libstorage(3024) - Storage.cc(commitPair):3251 err at stage:3 type:1 cont:0 dest:0 name:sda1 2006-09-10 03:04:53,572 INFO libstorage(3024) - Storage.cc(ignoreError):3180 ret:0 2006-09-10 03:04:53,572 INFO libstorage(3024) - Storage.cc(commitPair):3259 stage:3 evms_activate:0 new_pair:0 2006-09-10 03:04:53,573 INFO libstorage(3024) - Storage.cc(commitPair):3272 ret:-3003 2006-09-10 03:04:53,573 INFO libstorage(3024) - Storage.cc(commit):3150 empty:1 2006-09-10 03:04:53,573 INFO libstorage(3024) - Storage.cc(commit):3158 ret:-3003 2006-09-10 03:04:53 <3> linux(3024) [YCP] Storage.ycp:3016 CommitChanges sint ret:-3003 2006-09-10 03:04:53 <1> linux(3024) [YCP] clients/inst_prepdisk.ycp:97 CommitChanges ret:-3003 Partitions / Volumes Sda1 - boot / and Swap lvm2 volumes in same evms container

2 2

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

RE: [suse-autoinstall] Auto installation SLES9 SP2
by Lewandowski, Kelly 20 Sep '06

20 Sep '06

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 > > > >

1 0

installing from driver update package
by jaiber john 20 Sep '06

20 Sep '06

I have a driver update disk in .img format which has a device driver created according to the instructions on chapter 3 of http://mirror.mcs.anl.gov/suse-people/hvogel/Update-Media-HOWTO/Update-Medi…. I want to automate the driver installation for SLES9 SP2. How do I do that? I can re-master the initrd that comes with SLES9 SP2 CD1, insert this .img file into it. What other settings should I follow so that Yast detects it and installs it automatically? If i add driverupdate=1 as a boot parameter, it searches in floppy not what is inside initrd. Thanks -- <Jaiber John>

1 0

Auto installation SLES9 SP2
by Lewandowski, Kelly 20 Sep '06

20 Sep '06

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

2 1

SDK license agreement/SLES10
by Frank Steiner 20 Sep '06

20 Sep '06

Hi, is there a way to get rid of that license agreement popping up for SDK on SLES 10? I configured it as add_on_product and now it gets on my nerves with that agreement stopping the autoinstall :-( 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. *

2 2

RE: [suse-autoinstall] FW: Autoyast fails when trying to mount /boot with other EVMS Partitions
by Niall Calvert 19 Sep '06

19 Sep '06

Hi Uwe, > which partition is that? media is on partition sdb3 formatted as FAT32 (a USB disk) >can you post your partitioning section of the profile? <partitioning config:type="list"> <drive> <device>/dev/system</device> <is_evms_vg config:type="boolean">true</is_evms_vg> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <lv_name>swap</lv_name> <mount>swap</mount> <size>2684354560</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>sys_lx1</lv_name> <mount>/</mount> <size>8053063680</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_EVMS</type> <use>all</use> </drive> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>320753664</size> </partition> <partition> <evms_group>system</evms_group> <filesystem_id config:type="integer">142</filesystem_id> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>10742215680</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> </partitioning> Many thanks Niall -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 18 September 2006 08:18 To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] FW: Autoyast fails when trying to mount /boot with other EVMS Partitions On Wednesday 13 September 2006 01:08, Niall Calvert wrote: > I'm trying to install sles10 from media located on a hard-drive > partition, which partition is that? > which was copied from the installation DVD. The problem does > not occur when installing from the DVD using the same autoinst.xml file. can you post your partitioning section of the profile? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0