• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

ESXi - No Network Adapter error

A

aznguile972

Weaksauce
Joined
Apr 21, 2012
Messages
88
This is my first ever server build. Here are the specs:

Mobo: SuperMicro X10SLM-F-O (1150)
CPU: Intel Xeon e3-1240v3
RAM: 8GB 1600 Kingston ECC Unbuffered
HDD: 250GB Samsung 840 SSD
PSU: 430W Corsair CX430

So, here's my problem. After much research, it seemed like installing Windows Server 2012 in a virtualized environment is a good idea. And so, I tried to install ESXi 5.1 through IPMI. It looks like everything is running fine until I get this error message: "No network adapters were detected." and prompts me to reboot.

After doing some research on the issue, I found this link: http://www.supermicro.com/support/resources/OS/OS_Certification_SuperServer.cfm?show=SELECT&form=1U

I noticed that every system with my motherboard is not compatible with ESXi. Does this mean I can't install ESXi or is there a way for me to get the drivers installed to the image before installation?
 
Or...go buy a cheap supported NIC. You'll want several NICs anyway. Then install and just add the driver.
 
NetJunkie said:
To create a customer ESXi image w/ new drivers you'll need to use the Image Builder.

http://blogs.vmware.com/vsphere/2012/04/using-the-vsphere-esxi-image-builder-cli.html
Click to expand...

Nice, I've never used image builder or seen that tutorial. I wonder if that's all that's done to the HP/Dell/etc. customized isos.

Image builder seems like the better way to go, but if you want to try something quick you could download a 4.0 or 4.1 ESXi image and see if that'll install. I had a whitebox that wouldn't install 5.0 or 5.1 (no storage driver iirc), but would install 4.1 and then upgrade to 5.x without issue. I assume the system was using a driver that was no longer included in the 5.x builds. No guarantee it'll work (it probably won't).
 
markwo said:
Nice, I've never used image builder or seen that tutorial. I wonder if that's all that's done to the HP/Dell/etc. customized isos.

Image builder seems like the better way to go, but if you want to try something quick you could download a 4.0 or 4.1 ESXi image and see if that'll install. I had a whitebox that wouldn't install 5.0 or 5.1 (no storage driver iirc), but would install 4.1 and then upgrade to 5.x without issue. I assume the system was using a driver that was no longer included in the 5.x builds. No guarantee it'll work (it probably won't).
Click to expand...

I've used the image builder its excellent.

HP and Dell ISO are essentialy modified by the same thing.
 
I'm not sure what I'm doing wrong here. I keep getting an error on both "creating a new image profile" or "cloning an existing image profile" step. Here is the error message I am getting:

New-EsxImageProfile : Cannot conver 'System.String' to the type 'System.Management.Automation.SwitchParameter' required by parameter 'NewProfile'
At line:1 char:1
+ New-EsxImageProfile
+ ~~~~~~~~~~~~~~~~
+ Category Info : InvalidArgument: ( : ) [New-EsxImageProfile], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgument, VMware.ImageBuilder.Commands.NewImageProfile

Sorry, I'm such a newb when it comes to this stuff. :confused:

Edited:
I was able to finally get the custom image to work. I downloaded a copy of an image using the information from this post: http://communities.vmware.com/message/1826641#1826641
And then, put that file as part of my custom image and it worked perfect.

Next step...hope it recognizes my network adapter. At least the i210-AT network adapter. I couldn't find anything for the i217-LM adapter though.

**Note to self for next server build:
1. Check HCL
2. Get boards with matching network adapters

Thanks for all of your help. I hope my next post will be that I have ESXi up and running.
 
Last edited:
What NIC does your board have? If it's Realtek or Marvell (hopefully Supermicro isn't stupid enough to use either of those), then get a real Intel NIC. If it's Intel or Broadcomm, I can't see why it wouldn't be detected, unless ESXi has outdated drivers and you have a relatively new LAN chip...
 
dandragonrage said:
What NIC does your board have? If it's Realtek or Marvell (hopefully Supermicro isn't stupid enough to use either of those), then get a real Intel NIC. If it's Intel or Broadcomm, I can't see why it wouldn't be detected, unless ESXi has outdated drivers and you have a relatively new LAN chip...
Click to expand...

That board uses the Intel 210 chip, which Esxi does not provide support for yet cause they are stupid slow at updating there driver support. You are going to see most newer Intel server boards will be using this chip. Intel announced it with drivers to software vendors some time ago.
 
I disabled the LAN Option ROM for both network adapters in the BIOS and was able to install ESXi last night. w00t w00t! That's about as far as I could get last night. Will keep everyone posted. Next step: Installing Windows Server 2012. Would 100GB partition on the SSD be plenty for Server 2012?

Vader said:
http://www.servethehome.com/install-vmware-esxi-5x-intel-i210-intel-i350-ethernet-adapters/
Click to expand...
This looks like the same process as I went through with PowerCLI, but simplified in an application. Wish I would have known before I figured out the hard way...:D

_d3_ said:
>> http://www.vm-help.com/forum/viewtopic.php?f=24&t=4391 for i217.
Click to expand...
Hmmm. I wonder if I need to reinstall ESXi to make sure the 2nd network connection works or can I just install the driver after the fact.
 
_d3_ said:
You can install vib packages.
http://kb.vmware.com/selfservice/mi...nguage=en_US&cmd=displayKC&externalId=2008939
Click to expand...

Thanks. Will definitely try this out tonight.

Had something weird happen to me last night. I get home from work and turn on my server, I get 5 beeps (supposedly means bad memory) and won't boot ESXi. I was unable to IPMI remotely into the server so I had to setup a monitor and keyboard to it. Once I got to BIOS, IPMI shows "Not Working". Tried changing settings around and even reset CMOS to no avail. Finally, as a last resort, I moved the RAM from slot 1 to slot 3. BAM! Booted up with no issues and IPMI is functional again. Switched it back to slot 1 and it worked fine.

I'm wondering if I either have a bad motherboard or bad memory and whether or not I should RMA it before something gets worse. Does anyone have suggestions on how to properly test the memory or the board to make sure I don't have something faulty?

To be honest, (**knocking on wood**) I've been fortunate that everything I've ever bought, hardware-wise, has never been faulty or DOA. Except a Seagate Barracuda that quit on me, after 4 years or so, back in early 2000. They had a 5 year warranty so they RMA'd with no questions asked.
 
You must log in or register to reply here.
Back
Top