error installing ESXi 4U1

[uscadmin]

I am trying to install ESXi 4.0 Update 1 on a PE 2950III. I recieve the following error when the installer tries to load

"Booting: MBI=0x000100D8, Entry=0x00100212"

And the install just hangs there. I have read a bunch of other posts all of which suggested that the cause is the CPU not being 64bit, or the hardware not being supported. I have checked the HCL and the 2950III with two XEON 5430's is indeed supported

DELL

PowerEdge 2950-III\

Intel Xeon 54xx Series\

ESX 4.0 U1\, ESX 4.0\, ESXi 4.0 Embedded U1\, ESXi 4.0 Embedded\, ESXi 4.0 Installable U1\, ESXi 4.0 Installable\, ESX 3.5 U4\^[1\

http://www.vmware.com/resources/compatibility/search.php?action=search&deviceCategory=server&productId=1&advancedORbasic=advanced&maxDisplayRows=50&key=&release%5B%5D=34&datePosted=-1&partnerId%5B%5D=23&formFactorId%5B%5D=2&cpuSeriesId%5B%5D=21&filterByEVC=0&filterByFT=0&min_sockets=&min_cores=&min_memory=&rorre=0#notes]^ , ESX 3.5 U3\^[1\

http://www.vmware.com/resources/compatibility/search.php?action=search&deviceCategory=server&productId=1&advancedORbasic=advanced&maxDisplayRows=50&key=&release%5B%5D=34&datePosted=-1&partnerId%5B%5D=23&formFactorId%5B%5D=2&cpuSeriesId%5B%5D=21&filterByEVC=0&filterByFT=0&min_sockets=&min_cores=&min_memory=&rorre=0#notes]^ , ESX 3.5 U2\^[1\

http://www.vmware.com/resources/compatibility/search.php?action=search&deviceCategory=server&productId=1&advancedORbasic=advanced&maxDisplayRows=50&key=&release%5B%5D=34&datePosted=-1&partnerId%5B%5D=23&formFactorId%5B%5D=2&cpuSeriesId%5B%5D=21&filterByEVC=0&filterByFT=0&min_sockets=&min_cores=&min_memory=&rorre=0#notes]^ , ESX 3.5 U1\^[1\

http://www.vmware.com/resources/compatibility/search.php?action=search&deviceCategory=server&productId=1&advancedORbasic=advanced&maxDisplayRows=50&key=&release%5B%5D=34&datePosted=-1&partnerId%5B%5D=23&formFactorId%5B%5D=2&cpuSeriesId%5B%5D=21&filterByEVC=0&filterByFT=0&min_sockets=&min_cores=&min_memory=&rorre=0#notes]^ , ESX 3.5\^[1\

http://www.vmware.com/resources/compatibility/search.php?action=search&deviceCategory=server&productId=1&advancedORbasic=advanced&maxDisplayRows=50&key=&release%5B%5D=34&datePosted=-1&partnerId%5B%5D=23&formFactorId%5B%5D=2&cpuSeriesId%5B%5D=21&filterByEVC=0&filterByFT=0&min_sockets=&min_cores=&min_memory=&rorre=0#notes]^ , ESXi 3.5 Embedded U4\, ESXi 3.5 Embedded U3\, ESXi 3.5 Embedded U2\, ESXi 3.5 Embedded U1\, ESXi 3.5 Embedded\, ESXi 3.5 Installable U4\, ESXi 3.5 Installable U3\, ESXi 3.5 Installable U2\, ESXi 3.5 Installable U1\, ESX 3.0.3\, ESX 3.0.2 U1\

So I took a leap and upgraded to the latest BIOS (v2.6.1) thinking that would somehow help. It did not and I still recieve the same error. Can anyone suggests what might be going on here? I have installed ESX4 on identical hardware without issue, but ESXi just won't play nice. Any thoughts would be greatly appreciated.

Cheers,

GM

[enDemand]

GM...very odd indeed. I can consistently recreate the issue by using a server that doesn't have CPUs supporting 64-bit, but outside of that I haven't seen this before. And yes, the 2950 III should work. Maybe it's some hardware option that you have installed in your server? Also, you may want to look at data execution protection (DEP)...is it enabled or disabled. Don't know if will cause the error, but however it's set in the BIOS, I would flip the switch. I usually run my ESXi servers with DEP enabled (don't know what the Dell default is). I would also try to install the ESX 4 (classis, not "i") to see if it has problems. If you don't already have licenses for it, you can sign up for a free 60-day trial.

[uscadmin]

Well I am actually even more confused now. After following your suggestion regarding the DEP I was still getting the same error so I tried installing ESX 4 and it worked. I have 5 other machines with almost identical configs. They all have the broadcom 2port onboard nic with 2 additional addon broadcom 2 port nics and a dual port Qlogic ISCSI HBA. They all use the same PERC controller and the only thing that is unique to the machine I am having issues with is that it runs a 2.66GHz proc instead of the 3GHz proc on the other 5 machines. I have checked everywhere I can think of for an explaination to my issue but no one seems to be having this issue. I have also tried grabbing a frsh copy of the ESXi .iso to rule out bad media/download and still I run into the same error message with ESXi 4.

Cheers,

GM

[enDemand]

No logical answer that I can think of. Your ESX 4 test results were what I expected. And since ESXi 4 works on the other 5 machines, it should work on the one you're having problems with if they're all the same. CPU speed won't have anything to do with it. If you're up for it, you can try switching CPUs out with those from one that does work. But that's probably more work than is necessary or worth it. That would eliminate the CPU as the problem, though, if you still can't install it. Don't want to make any assumptions...can you post the EXACT CPU model that you have, as reported by Dell's site (plugging in the service code)?

[uscadmin]

Well I am actually even more confused now. After following your

suggestion regarding the DEP I was still getting the same error so I

tried installing ESX 4 and it worked. I have 5 other machines with

almost identical configs. They all have the broadcom 2port onboard nic

with 2 additional addon broadcom 2 port nics and a dual port Qlogic

ISCSI HBA. They all use the same PERC controller and the only thing

that is unique to the machine I am having issues with is that it runs a

2.66GHz proc instead of the 3GHz proc on the other 5 machines. I have

checked everywhere I can think of for an explaination to my issue but

no one seems to be having this issue. I have also tried grabbing a frsh

copy of the ESXi .iso to rule out bad media/download and still I run

into the same error message with ESXi 4.

Cheers,

GM

[uscadmin]

The exact proc info from Dell is:

Processor, 80574K, XDH, E5430 FCLGA6

I am tempted to ask VMware about this since it seems really odd and I do have an existing support contract with them albeit not for this particular server setup.

Cheers,

GM