VmWare ESXi v5.5 - unable to allocate 2nd datastore on Cisco UCS 220 M4S

We recently purchased a Cisco UCS C220 M4S server to use as a VMware ESXi v5.5 host.  We configured the RAID as follows:
Group 0: 2 drives RAID 1
Group 1: 4 drives RAID 5
Controller:  Cisco 12G SAS Modular Raid
We installed VMware on Group 0, (lets call it datastore1).  Problem now is when trying to create a second datastore (datastore2), we receive the following error:  
     An error occurred during host configuration, create vmfs datastore:  Operation failed, diagnostics report.  Unable to create filesystem, please see VMKernel log for more details.  No such file or directory.  Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "" failed.

I looked through the vmkernel log, but I'm not sure what I'm looking for.

I can provide more details upon request.

Thank you,
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mr TorturSystem EngineerCommented:
did you use the custom ESXi iso for Cisci server or only the generic vanilla iso from VMware ?
I used these servers a few times on vpshere 5 and I remember not having issue with local datastore creation.
trinity2007Author Commented:
We used Custom ESXi ISO for the cisco server, that I downloaded from Cisco.  We have 3 other 220 M3 models, which I was able to configure with no issue.  Could it be the RAID controller on the M4?  this is a Cisco 12G SAS Modular Raid controller, where the 220 M3's had the LSI controller.
Thank you,
Mr TorturSystem EngineerCommented:
I think this could help :

Maybe you just need to wipe your RAID 5 logical disk before creating datastore..
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

trinity2007Author Commented:
Tried 2 options:
1. From the UCS Raid Management:  Wiped the RAID 5 logical disk, still received error.  
2. Used a Win2012 disk, diskpart utility to remove the GPT, format, still received error.
We do have Cisco support, so we may end up opening a ticket with them.
Mr TorturSystem EngineerCommented:
bad news, sorry to hear that.
I think you should try my second link to wipe it out under esxi commandline.
trinity2007Author Commented:
OK, I'll give that a try.  Thanks!!
trinity2007Author Commented:
Still no good.  We removed the RAID configuration for the 2nd datastore (which was 1.65 TB).  I created another RAID configuration with only 2 disks (about 500GB), and I was able to create the 2nd datastore.  Perhaps some kind of size limitation?
Mr TorturSystem EngineerCommented:
Hi Trinity2007,
On ESXi 5.5 your datastore size limit is already high (64 TB in VMFS5) so this is not the issue here.
I would give it another try with RAID5 on 4 drives. Wipe it if possible at the RAID menu.
Or call Cisco support...
trinity2007Author Commented:
We tried the 4 drives with RAID5, which gave us the 1.63 TB, but when trying to create the datastore is when we get the error. All drives are online and working and no issue with the controller.  I believe we will need to open the ticket with Cisco.
Thank you for your assistance!!
Mr TorturSystem EngineerCommented:
Ok, sorry I can't help you more.
Maybe another expert will, if not good luck on your own or with Cisco.

At last I also suggest you to do a google search on this text "Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "" failed", there is a lot of result, including the 2 links I already gave you.

On this one same error message resolved with GPT label off on vsphere 4.1

This one same message resolved with MTU parameter (jumbo frames), and I saw that multiple times.

Hope this help... Good luck again!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
trinity2007Author Commented:
Interesting enough, I decided to use another cisco custom image v5.5.1.3, and it seems this allowed me to create the second datastore from vSphere.
Perhaps a known issue with v5.5.0? Not sure, but it's working now with v5.5.1.3
Thank you for you assistance!
Mr TorturSystem EngineerCommented:
Good news! you're welcome.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.