I have two ESXi 4.1 servers running on two HP BL460C G1 blade servers. I have a MSA2000 SAN that I am using for fiber channel based shared storage.
When I try to add a new datastore to my ESXi hosts via vCenter server, I receive the following error:
Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" for object "datastoreSystem-32" on vCenter Server "VCNTR.domain.com" failed.
When I try to add the new datastore to an individual ESXi host directly, I receive this error:
Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" for object "ha-datastoresystem" on ESXi "192.168.248.112" failed.
I have two 100GB datastores hosted on this same SAN that I was going to replace with a 500GB datastore. The two 100GB datastores were added without any problems. I have since deleted those datastores, but they are still presented to my ESXi hosts by the SAN, so I can re-add them without any errors.
I have searched for other solutions or explanations to these errors, but hopefully someone here will be able to give me some insight.
I have resolved my issue by going into the RAID configuration on the the VM Host Server and performing a "fast initialize" on the disk. After rebooting the server I successfully added my new datastore.
Hope this helps.
I am seeing the same error at the moment, and I can't seem to find a way to fix it.
Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" for object "datastoreSystem-67" on vCenter Server "***SVR-VC01" failed.
We have a MSA2012i SAN connected via iSCSI.
We just recently deleted an existing vdisk that held a couple of VMDK volumes, then created a new vdisk exactly as before, with the same sized volumes.
(This was done to change the RAID level)
Nothing changed on the ESXi 4 & 4.1 Hosts between deleting and recreating the vdisks and volumes.
I have rebooted the VC Server and 1 of the two ESXi hosts but still no go. Haven't rebooted the SAN or the other host. Planning on rebooting the other host out of hours.
Have disabled and re-enabled software iSCSI on the ESXi 4.1 host.
One thing to note is that this issue only happens on the first volume (LUN1). When I go to create a datastore on the second or third volumes, ESXi has no issues?
My error was actually due to the drive controller on the SAN. The management interface of the SAN became unavailable and all the LUNs that were being newly provisioned were not accessible. All other LUNs that were already provisioned continued to work fine, just new disks were not able to be used. Finally after some scheduled downtime, we were able to reboot the SAN's drive controller, and the error was resolved.
Just in case anyone else has the same issue, and couldn't be resolved using the other posts above, this is what I did:
Disabled the SW iSCSI Adapter then rebooted the host
Removed the vDisk on the SAN
Updated the SAN to the latest firmware (J210P23–02)
Created a new vDisk in Offline rather than Online mode
Created two new volumes
Enabled the SW iSCSI Adapter on the host, and then added the devices again.
After that everything came good.
Obviously some of these steps may not be required (updating the firmware for example), but it may help someone in the future to know.
actually i faced this problem when i tried to add any iscsi storage with size more than 2TB. please advise if there is any limitation for iscsi storage size with esx 4.1.
For posterity, I will add my solution as well.
I also have an MSA 2012fc and was encountering this error on a newly created vdisk/volume. Restarting the host & SAN, or recreating the vdisk/volume did not resolve it.
What did work was fixing the partition table with fdisk.
ssh into the host
fdisk /dev/disks/<drive id>
At this point I received a message that there was a problem with the partition, so I had to press 'w' so it would correct it.