probiers ma mit dem hier ... ist zwar für den 9650 ohne SE aber ev mit kleinen anpassungen geniessbar.

#!/bin/bash # VMware ESXi 4.0.0 ISO patch script 20090704 # - integrates 3ware 9650SE driver # - integrates better wget and rsync from vm-help.com # - activates unsupported (!!) SSH server # # by Philipp Wollermann 
 # uses ideas from Varazirs mkesxiaio.sh: http://varazir.mine.nu/esxi/ # Requirements: # # tested with Ubuntu Linux 8.04 # please do "apt-get install unzip bzip2 mkisofs" # Usage: # # 1) Get the following files and put them in a directory with this shell script: # # VMware-VMvisor-Installer-4.0.0-171294.x86_64.iso # (-> https://www.vmware.com/go/get-free-esxi/) # # ESX_ESXi_4.0_driver-GUID78f4117c3d57443485d1c9c989d80909.iso # (-> http://www.3ware.com/KB/article.aspx?id=15548) # # simple.map (you can extract that from an installed ESXi 4.0, see below) # # 2) Start the script from the directory where you placed all the files. # Hint: # # I don't know if the simple.map can be redistributed, so for now you have to # extract it yourself: # # Get VMware Workstation or Fusion (something else like VirtualBox may also work) # Install ESXi as a virtual machine (see http://communities.vmware.com/docs/DOC-6590) # When the install is finished and you see the yellow management screen, press Alt-F1 # Enter "unsupported", press ENTER, when asked for a password, just press ENTER # Copy the simple.map to your Linux workstation using: # # scp /etc/vmware/simple.map 123.123.123.123:/root # Todo: # # - Find out how to unpack the sys.vgz files, so the simple.map can be extracted #   automatically. set -e set -u RPWD=`pwd` # Check if the script is run as a super-user if [ ! $( id -u ) -eq 0 ]; then   echo "Must have super-user rights to run this script."   exit 0 fi # Clean-up echo "Preparing ..." umount esx-cd || /bin/true umount esx-dd || /bin/true umount esx-3ware || /bin/true rm -f ESXi-custom.iso rm -rf $RPWD/esx-cd $RPWD/esx-build $RPWD/esx-oem $RPWD/esx-image $RPWD/esx-dd $RPWD/esx-3ware $RPWD/esx-3ware-unzip # Create folders mkdir -p $RPWD/esx-cd $RPWD/esx-build $RPWD/esx-oem $RPWD/esx-image $RPWD/esx-dd $RPWD/esx-3ware $RPWD/esx-3ware-unzip # Copy files from ISO echo "Extracting ISO ..." mount -o loop VMware-VMvisor-Installer-4.0.0-171294.x86_64.iso $RPWD/esx-cd cp -a $RPWD/esx-cd/* $RPWD/esx-build/ umount $RPWD/esx-cd # Unzip 3ware driver mount -o loop ESX_ESXi_4.0_driver-GUID78f4117c3d57443485d1c9c989d80909.iso $RPWD/esx-3ware cd $RPWD/esx-3ware-unzip unzip $RPWD/esx-3ware/offline-bundle/offline-bundle.zip umount $RPWD/esx-3ware ar x vmware-esx-drivers-scsi-3w-9xxx-400.2.26.08.035vm40-1.0.4.00000.x86_64.vib tar xfz data.tar.gz # Create oem.tgz staging folder echo "Creating oem.tgz staging area ..." mkdir -p $RPWD/esx-oem/etc/vmware $RPWD/esx-oem/bin $RPWD/esx-oem/usr/lib/vmware/vmkmod # Create new inetd.conf with enabled SSH echo "Creating new inetd.conf ..." cat > $RPWD/esx-oem/etc/inetd.conf > $RPWD/esx-oem/etc/vmware/simple.map # Copy 3ware driver into vmkmod directory ... echo "Copying 3w-9xxx.o driver ..." cp $RPWD/esx-3ware-unzip/usr/lib/vmware/vmkmod/3w-9xxx.o $RPWD/esx-oem/usr/lib/vmware/vmkmod/ # Download wget and rsync package if not already downloaded cd $RPWD if [ ! -e SSH_FTP_oem_1.3.tgz ]; then   echo "Downloading wget/rsync from vm-help.com ..."   wget -q http://www.vm-help.com/esx/esx3i/Cus...TP_oem_1.3.tgz fi # Extract wget and rsync echo "Integrating wget and rsync ..." cd $RPWD/esx-oem tar xfz $RPWD/SSH_FTP_oem_1.3.tgz bin/wget bin/rsync # Build oem.tgz echo "Building oem.tgz ..." cd $RPWD/esx-oem tar czf $RPWD/esx-build/oem.tgz * # Add oem.tgz to isolinux.cfg echo "Patching isolinux.cfg ..." sed -i 's/install.tgz/install.tgz --- oem.tgz/g' $RPWD/esx-build/isolinux.cfg # Extract & delete the image echo "Extracting image ..." tar -xzf $RPWD/esx-build/image.tgz -C $RPWD/esx-image rm $RPWD/esx-build/image.tgz # Unpack the compressed DD file echo "Unpacking dd file ..." cd $RPWD/esx-image/usr/lib/vmware/installer/ esx_ddf=(*.bz2) bunzip2 ${esx_ddf[0]} esx_ddf=(*.dd) # Check the number of sectors esx_sector=$(fdisk -ul ${esx_ddf[0]} 2>>/dev/null | awk '/bytes/ {print $9}') # Check where the 5th partition starts esx_number=$(fdisk -ul ${esx_ddf[0]} 2>>/dev/null | awk '/dd5/ {print $2}') # Calculate offset of 5th partition in dd file esx_offset=$(($esx_sector*$esx_number)) # Mounting the 5th partition of the DD file to esx-dd echo "Mounting 5th partition of the DD file (offset: $esx_offset) ..." mount -o loop,offset=$(($esx_sector*$esx_number)) $esx_ddf $RPWD/esx-dd/ # Copy the custom oem file to the mounted dd file echo "Copying oem.tgz into dd file ..." cp $RPWD/esx-build/oem.tgz $RPWD/esx-dd/oem.tgz # Unmount the dd file umount $RPWD/esx-dd # Compressing the dd file echo "Compressing dd file ..." bzip2 -9 $esx_ddf # Rebuilding image.tgz echo "Rebuilding image ..." cd $RPWD/esx-image tar czf $RPWD/esx-build/image.tgz * echo "Building new ISO ..." # Build new ISO cd $RPWD/esx-build mkisofs -o $RPWD/ESXi-custom.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -input-charset utf-8 ../esx-build rm -rf $RPWD/esx-cd $RPWD/esx-build $RPWD/esx-oem $RPWD/esx-image $RPWD/esx-dd $RPWD/esx-3ware $RPWD/esx-3ware-unzip echo "Finished!" exit 0

Welch ein Zufall^^
Ich habe aktuell auch ein Projekt am Laufen, bei dem ein VMware ESXi 5.1 kompatibler PCIe 1x RAID Controller gefordert war. Nach einer ausgiebigen Recherche habe ich einen LSI 3ware 9650SE-2LP als 1. Kandidaten beschafft. Dies vor allem weil der Hersteller expliziten ESXI Support anpreist, und ich in zwei unabhängigen Foren Bereichte fand, wonach diese Lösung auch wirklich funktioniert.
Zur Treiber Integration bin ich dort auf folgende Lösung aufmerksam gemacht worden, die meiner Ansicht nach recht viel einfacher ist, als die hier beigezogene, über die ich auch irgendwo gestolpert bin.

Von V-Front gibt es den ESXi-Customizer, aktuell in der version 2.7.1 http://www.v-front.de/p/esxi-customizer.html Das Ganze ist Freeware und läuft unter WIndows.
Alles was man dann noch braucht ist das original Installer ISO von VMware (VMware-VMvisor-Installer-5.1.0-799733.x86_64.iso) sowie den treiber vom LSI Controller. Konkret wird die *.vib Datei aus dem Treiberpacket benötigt (scsi-3w-9xxx-2.27.08.036-1OEM.500.0.0.472560.x86_64.vib).

Im übersichlichen GUI wählt man die Pfade zu den Grunddaten aus und drückt "Run!". Kurze Zeit später hat man ein gepatchtes *.iso File das man dann auf dem bootfähigen USB Stick oder traditionell mit einer CD dem PC zuführen kann. Die ESXi Installation hat tadellos geklappt.

Allerdings aheb ich aktuell noch andere Probleme mit dieser Lösung...
Das Board ist ein "Intel Desktop Board DN2800MT" http://www.intel.com/p/en_US/s…s/dsktpboards/db-dn2800mt
Das Problem ist, dass ich ESXi zwar auf dem RAID 1 installieren, danach aber nicht von diesem booten kann (no boot device found). Dies unabhängig von den Boot Einstellungen im BIOS. Wenn ich die RAID Karte in einem anderen PC anschliesse bootet das Ganze ohne Probleme.
Ich vermute deshalb dass das Board bzw das BIOS hier das Hauptproblem ist ... Ich habe da noch einige Ideen die ich noch ausprobieren muss.

Stunden später
Da ich hier http://communities.intel.com/message/178468 jemanden gefunden habe der nicht nur das gleiche problem sondern auch den gleichen Setup hat, hab ich das Ganze gleich man in Englisch verfasst.

Hello goofy79

I have basically the same setup as you. Specifically I am using the following hard-/software:
Mainboard: Intel DN2800MT, BIOS version 0165 (MTCDT10N.86A.0165.EB.EXE) released on 14.01.2013.
HDD Controller: LSI 3ware 9650SE-2LP, configured as RAID 1.
DVD Drive: Connected on USB port.
Software Platform: VMware ESXi 5.1.0 Release 799733 (with driver modification).

Workaround (short):
Remove additional drives from the onboard SATA ports.
Do a normal VMware ESXi installation on the RAID 1 volume.
Let the CD-Drive connected to the system.
Put the VMware ESXi installation CD into the drive.
Start the system and wait until the first screen of the ESXi Installer (blue) appers.
Select manually "Boot from local disk" within the given timeframe.
The system will boot into the completed ESXi installation. Enjoy.

Sadly this selection must be made manually on every boot. Maybe this steps can be made unattended. See below.

Explanation and trials I did:
First I made a VMware ESXi installer ISO which includes the LSI 3ware 9650SE driver. Then I started the regular installation from a CD. the RAID 1 was recognised successfully and the basic installation was successful. After the first reboot I had a BIOS error that there is no bootable device. I have checked the boot settings in the BIOS. I recognised that the "boot device priority" listing order never change, even if you select the "Hard Disk Drives" or something else. It seams that this is a bug from the BIOS and it follows always the same order which is Optical device > Removable Device > Hard Disk device > Network.
The same problem is recognisable with the Hard Drive Order when there are additional Drives connected to the onboard SATA ports. The BIOS always tries to boot from the onboard ports first - which actually works properly.
But ... it seams that the BIOS never tries to boot from the 3ware RAID controller (which is correctly listed in the BIOS).
I have additionally tested a random non RAID SATA controller which I had nearby - With the same result.

Just for additional testing, I started to install a Windows 7. Interestingly, the Installation was properly found again after the first reboot and was continued. The reason for this interesting happening was, that I did not removed the Windows DVD from the drive. As we know the Windows installer waits some seconds to press any key to start the installation process. If no key is pressed, it proceeds to boot from the HDD by default. After the DVD was removed, the system was not able to boot from the RAID, as known from the ESXi trial - Until the DVD was put back in. But this shows that is basically possible to boot into a successfully finished installation which gave me hope.

ESXi installed again ... Windows DVD placed in the drive ... But not as expected, Windows started an installation without asking me to press any key to start the installation. Apparently Windows starts the installation automatically (without a choice) if it detects something which is not Windows on the HDD.
Then I put the ESXi CD back in to the drive ... As expected the system was booting from the CD. In the first screen (blue) of the ESXi installer allows to select "Boot from local disk" which I chose. The system will boot into the completed ESXi installation. Enjoy :-). This will not work if there are additional drives connected to the onboard SATA ports because of the not changeable HDD.

Next steps:
Sadly the selection must be made manually on every boot - Which is not the kind of solution I am looking for.
On one hand I don't like to have a CD drive which is connected all the time just for the boot up - An USB flash memory would be better. On the other hand the boot process should work unattended - It is a server.
To boot from an USB flash memory should work, because removable devices are tried to boot directly after the CD-Drive.
The unattended process should also be possible. The boot loader looks very similar to Grub and the ESXi-Customizer (http://www.v-front.de/p/esxi-customizer.html) which I have used to integrate the 3ware driver into the VMware ISO has supplemented the boot menu with some additional notes about the ESXi-Customizer. If it is, as I think, similar to Grub, it should be possible to change the order of the commands and set the "Boot from local disk" as default on top.

Maybe also Intel is able to provide a fix for this problem, which would definitively the best solution.

Kind regards
Gurit

Zitat von rittmeister

Hört sich schwer nach einer Inkompatibilität an. Offiziell wird dein Mainboard vom RAID-Controller ja auch nicht unterstützt.

Wird denn dein RAID-Controller im BIOS POST angezeigt?

Hast Du schon mal folgendes probiert:
- Alle anderen Bootdevices deaktivieren - ausser natürlich Hard Disk
- Controller auf dem Mainboard in einen anderen Slot

Da VMware ESXi und auch der RAID Controller eher für den professionellen Bereich gedacht sind, ist es nicht verwunderlich dass dieses Desktop Board auf keiner Compatibility List auftaucht.
Diese Kombination habe ich eigentlich auch nur aus dem Strom-Spar Gedanken gewählt, da das Ganze wie auch der Vorgänger als erweiterter NAS Ersatz dienen soll.

Ich habe wie gesagt aber auch mal noch so nen 0815 SATA/IDE Controller in den Slot gesteckt, den ich gerade noch rumliegen hatte. Auch hier war es nicht möglich ohne Umwege über eine Boot CD ab einer HDD an diesem Controller zu booten. Auch wenn man den Controller entfernt und mit den onboard SATA Anschlüssen arbeitet werden die im BIOS gemachten Einstellungen nicht übernommen. Entsprechend wird immer die selbe Geräte reihenfolge abgerbeitet.
Einen anderen Slot kann ich leider nicht probieren, da das Board nur einen hat.