...

...

On Tue, Sep 19, 2006 at 11:23 PM, in message <FEF375A836207347A500D2F7F65DA0665A21B9@exchange2k3.BHT.local>, "Lewandowski, Kelly" <KLewandowski@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

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