Hello quys

 

I'm building my own esxi server.

HW is as follows:

Supermicro X9SCM-F

Intel Xeon E3-1230 V2

And i have 2 IBM M1015 cross-flashed to IT mode.

 

I'm currently running ESXI 5.1 (the latest version as of now)

 

The first couple of virtual servers are running but I have problems with the unraid server, more specifically setting the m1015 to passthrough.

It seems to me that vSphere can't see them.

 

Is it just my eyes or aren't the m1015 not visible.

Could the reason be a incorrect cross flash, if so is there an way to test if the system can see them. Or could it be something else.

 

Also I have my parity drive a (Seagate Barracuda 7200.14 ST3000DM001, 3TB) directly hooked up to a sata port on my MB, how should i pass it through to the unraid vm. My normal datastorages are also directly connected to the MB.

 

Thanks upfront for any advise you can give me.

 

 

Hello quys

 

I'm building my own esxi server.

HW is as follows:

Supermicro X9SCM-F

Intel Xeon E3-1230 V2

And i have 2 IBM M1015 cross-flashed to IT mode.

 

I'm currently running ESXI 5.1 (the latest version as of now)

 

The first couple of virtual servers are running but I have problems with the unraid server, more specifically setting the m1015 to passthrough.

It seems to me that vSphere can't see them.

 

Is it just my eyes or aren't the m1015 not visible.

Could the reason be a incorrect cross flash, if so is there an way to test if the system can see them. Or could it be something else.

 

Also I have my parity drive a (Seagate Barracuda 7200.14 ST3000DM001, 3TB) directly hooked up to a sata port on my MB, how should i pass it through to the unraid vm. My normal datastorages are also directly connected to the MB.

 

Thanks upfront for any advise you can give me.

Did you turn on VT-d in the motherboard BIOS?

Yes VT-d is enabled

 

I went back to all the bios intruction in the atlas tread it says the following.

In the advanced tab: PCIe/PCI/PnP Configuration

Set PCI ROM Priority to "EFI Compatible ROM"

(NOTE: for Ver 2.0a BIOS this is replaced with "Disable OPROM for slots 7&6" set them to "Disabled")

 

But I can't find this setting in my bios. Could this be the cause?

There should be two settings to turn on passthrough correctly.  One is what you mention above.  The other is labeled something like "Intel® Virtualization Technology" in the bios.  Also did you power off and then back on after changing them.  The manual mentions that for the field I looked up so it might also be needed for the VT-d setting as well.

There should be two settings to turn on passthrough correctly.  One is what you mention above.

 

Bob which setting do you mean the vt-d setting or pci setting?

There should be two settings to turn on passthrough correctly.  One is what you mention above.

 

Bob which setting do you mean the vt-d setting or pci setting?

I mentioned it in my post.  I looked up in the X9SCM-F manual in the bios settings and it mentions "Intel® Virtualization Technology" setting - but I didn't see a graphic of the screen so I couldn't post that.  Look at the manual for "Intel® Virtualization Technology" phrase.

There should be two settings to turn on passthrough correctly.  One is what you mention above.

 

Bob which setting do you mean the vt-d setting or pci setting?

I mentioned it in my post.  I looked up in the X9SCM-F manual in the bios settings and it mentions "Intel® Virtualization Technology" setting - but I didn't see a graphic of the screen so I couldn't post that.  Look at the manual for "Intel® Virtualization Technology" phrase.

 

I think you mean this setting it is enabled in my bios.

 

I think if this wasn't on my other vm's shouldn't work at all.

There should be two settings to turn on passthrough correctly.  One is what you mention above.

 

Bob which setting do you mean the vt-d setting or pci setting?

I mentioned it in my post.  I looked up in the X9SCM-F manual in the bios settings and it mentions "Intel® Virtualization Technology" setting - but I didn't see a graphic of the screen so I couldn't post that.  Look at the manual for "Intel® Virtualization Technology" phrase.

 

I think you mean this setting it is enabled in my bios.

 

I think if this wasn't on my other vm's shouldn't work at all.

Correct on all counts.  After changing the VT-d setting did you power off the computer and then power it back on?  The manual mentions needing to do that for the "Intel® Virtualization Technology" setting - didn't check if the same requirement was needed for VT-d.  I don't use my X9SCM-F MB currently but I never had a problem with it detecting the M1015 cards before - just a x1 PCIe 1.0 tuner card after a bios update.  Buy chance did you skip the bios flash to speed up boots?  If so you might try that - but I'm almost certain it shouldn't make a difference.

I have already skipped the bios of the m1015.

 

I already had reset and shutdown my computer. Just did it again and removed the power to be sure, no joy.

 

Is there some way to test the controllers. Maybe by booting directly to unraid instead of using esxi?

I have already skipped the bios of the m1015.

Don't expect a problem with this or it would have been reported before now but I flashed the bios on MY M1015s so that I can see the drives upon booting.  That appears to be a difference between your M1015s and mine based on your post.

I already had reset and shutdown my computer. Just did it again and removed the power to be sure, no joy.

 

Is there some way to test the controllers. Maybe by booting directly to unraid instead of using esxi?

That would be my suggestion.  Just put the unRAID flash as the boot instead of ESXi flash.  See if unRAID picks up the drives then.  I have 6 cards - 5 working - toasted one - so that would be an unfortunate problem if it happened to yours.

well i think i have found the problem when I boot directly into unraid I don't see any drives either. So the problem isn't in esxi.

I will start testing the controllers I hope they aren't bricked or anything.

 

Edit:

Well i can tick something else of the list.

I took the cards out of my computer and into another and booted to unraid. It then detected the drives connected to the controller correctly.

 

So only thing left is the mobo I think is will clear the cmos and try again.

 

Edit2:

I have returned the bios settings to factory default. This should have the same effect as removing the cmos battery right? Or does that do something extra?

Then booted directly into unraid so no esxi still no drives from the m1015.

 

I'm running the latest bios ver 2.0b I guess i'm not the only one that uses that? Is there any kind of jumper on the mobo that can cause behavior like this?

 

I use 2.0b and have M1015's in the first 3 slots - no issues here.  I wonder if you have a bad motherboard

I will try update mobo bios again, i have spotted some similar problems online with incorrect bios update. So i will try that and that will be my last hope I think otherwise I will have to get a new mobo maybe.

It's probably worth calling Supermicro about - their support is very good.

Success!!!

 

After a new bios flash to ver2.0a esxi sees my controllers now. I think my previous bios flash went wrong.

 

btw I found a handy tool to update your bios. Below you can download a live cd which you can mount through ipmi so you can remotely update your bios.

 

http://forums.servethehome.com/processors-motherboards/851-new-project-supermicro-ipmi-2-0-bios-update-live-cd.html

Hey there's an idea, I'll update my M1015/X9SCM tools (linked in my sig) into an .iso that we can use like this.  Good to hear you got it sorted!

I'd be curious if you guys get this to work.  I am getting the Error 65 on my X8DTH-iF that some users are getting in that thread.

 

John

Hey there's an idea, I'll update my M1015/X9SCM tools (linked in my sig) into an .iso that we can use like this.  Good to hear you got it sorted!

 

Good plan. Would like an all in one tools/utilities ISO.