September 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

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

Anyone has experence on x86_64 autoyast installation?
by hp9 19 Sep '06

19 Sep '06

I have very bad experience to install SLES10.0 x86_64 on 64bits machine. Though I can do it manually. But I can not install it by AUTOYAST, because AUTOYAST always install i586 but x86_64! Anyone has experence on x86_64 autoyast installation?

3 2

RE: [suse-autoinstall] SuSE 10.1: Could not find the SUSE Linux Installation Source
by GUNREBEN, PETER (Peter) 19 Sep '06

19 Sep '06

GUNREBEN, PETER wrote: > > I have problems to get the autoyast installation (SuSE 10.1) > up and running with some new computers (K8N-DRE, 2xOpteron > 275). The main error message is "Could not find the SUSE > Linux Installation Source". The onboard NICs are Broadcom > 5721and I'm using the tg3 driver. I can see on console 3 that > there is a problem with the nfs mount. However, I can mount > this directory via nfs (from console 9) without any problems. > Any help or idea is highly appreciated. I'm desperately > searching for a solution. I just got a hint from Lee per E-Mail to add netwait=5 to the kernel command line. This solved the problem. Many thanks to Lee. Peter.

1 0

SuSE 10.1: Could not find the SUSE Linux Installation Source
by GUNREBEN, PETER (Peter) 19 Sep '06

19 Sep '06

Hi, I have problems to get the autoyast installation (SuSE 10.1) up and running with some new computers (K8N-DRE, 2xOpteron 275). The main error message is "Could not find the SUSE Linux Installation Source". The onboard NICs are Broadcom 5721and I'm using the tg3 driver. I can see on console 3 that there is a problem with the nfs mount. However, I can mount this directory via nfs (from console 9) without any problems. Any help or idea is highly appreciated. I'm desperately searching for a solution. ======== Console 3 ======== got info from file:/info hostname: 135.246.30.241 netmask: 255.255.254.0 broadcast: 135.246.31.255 gateway: 135.246.30.1 server: 135.246.75.102 nameserver: 135.246.31.80 Ok, that seems to have worked. :-) Ok, that seems to have worked. :-) Ok, that seems to have worked. :-) Looking for a network server... Trying to activate eth0 setting up localhost...done eth0 activated nfs: trying to mount 135.246.75.102:/raid0/SuSE/10.1 Starting portmap. mount: nfs mount failed, server says: unknown error -1 Ok, that didn't work; see if we can activate another network device... No further network cards found; giving up. Automatic setup not possible. ======== Console 3 ======== Peter.

1 0

RE: [suse-autoinstall] SLES10 Archive Selection: My autoyast alway install i586 but x86_64
by hp9 18 Sep '06

18 Sep '06

My autoyast alway install i586 but x86_64 in its process. Who know the reason about that? Thank you lots. The follow is my scripts: ------------------------------ <?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"> <bootloader> <activate config:type="boolean">true</activate> <global> <embed_stage1.5 config:type="boolean">true</embed_stage1.5> <lines_cache_id>0</lines_cache_id> <prompt>1</prompt> <stage1_dev>/dev/sda1</stage1_dev> <timeout config:type="integer">8</timeout> </global> <initrd_modules config:type="list"> <initrd_module> <module>piix</module> </initrd_module> <initrd_module> <module>ata_piix</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_modules> <loader_device>/dev/sda1</loader_device> <loader_type>grub</loader_type> <location>boot</location> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"> <section> <append>showopts</append> <initial>1</initial> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>1</lines_cache_id> <name>SUSE Linux 10.0</name> <original_name>linux</original_name> <root>/dev/sda1</root> <type>image</type> <vga>0x31a</vga> </section> <section> <append>showopts ide=nodma apm=off acpi=off noresume edd=off 3</append> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>2</lines_cache_id> <name>Failsafe -- SUSE Linux 10.0</name> <original_name>failsafe</original_name> <root>/dev/sda1</root> <type>image</type> <vga>normal</vga> </section> </sections> </bootloader>

1 0

RE: [suse-autoinstall] SLES10 Archive Selection: My autoyast alway install i586 but x86_64
by hp9 18 Sep '06

18 Sep '06

My autoyast alway install i586 but x86_64 in its process. Who know the reason about that? Thank you lots.

1 0