Storage P2000 G3 FC

[AndyFila]

Hi, we have Storage P2000 G3 FC Firmware version TS252P005 and SAS HD MM1000FBFVR Firmware version HPD9, Blade-C7000 with ProLiant BL460c Gen8 (host OS ESC 5.5 or 6.5).

We have problem to add storage to ESX OS, i see my volume on ESX Storage devices with LUN, but if i try add storage to ESX have error Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi  failed.

Please help, any idea?

[SUBHAJIT KHANBARMAN_1]

Your issue specific to VMWare and this is nothing to do with MSA

From support perspective, P2000 G3 not compatible with ESX6.5 so no point in trying anything if you have presented MSA volume to ESX6.5 host.

In case you have presented MSA volume to ESX5.5 then you can try below link to fix your issue,

https://communities.vmware.com/thread/482645

http://www.virtualizationteam.com/server-virtualization/call-hostdatastoresystem-createvmfsdatastore-for-object-ha-datastoresystem-on-esxi-xxx-xxx-xxx-xxx-failed.html

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

**********************************************************************

[Shawn_K]

Hello,

I have seen that error before when the array's LUN was previously presented to a different ESXi host. The problem is the new host can detect there is some LUN storage device file header infromation and doesn't know what to do with it.

As long as there is no data on the P2000 array - try wiping the Vdisk clean. You could delele and recreate a new Vdisk but this would delete all data currently on the Vdisk so be careful.

As mentioned previously, the P2000 was never qualified with ESXi 6.5. That would be an unsupported confirguration if further issues on the P2000 were encountered and you needed support help.

Cheers,
Shawn

I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.

[AndyFila]

I tried to solve the problem this way, but getting an error when i run command from ssh 5.5 esx:

# partedUtil mklabel /dev/disks/naa.600c0ff000138d4a0728eb5e01000000 msdos
Error: Connection timed out during write on /dev/disks/naa.600c0ff000138d4a0728eb5e01000000
WriteNewPtable: Unable to commit to device /dev/disks/naa.600c0ff000138d4a0728eb5e01000000

it looks like esx host have just read permission to Storage volume, and dont have writting permision.

On Storage volume settings my volume have full read-writte access.

[AndyFila]

I tried it, recreated it again different TYPE RAID VDIKS , volums- it didn't solve anything.

I try full wipe HDD  with HP sMART Storage Administrator utility and created again VDIKS and volume - nothing helps.

the same situation is observed without Blade and fiber swithc, i try install esx 5.5 to stand allone HP or Dell server and connect direct with fiber cable stand allone server to Storage. The same error. I see all new created volume and lun but cant add storage or created VMFS-5 OR VMFS-3 volume to ESX

[AndyFila]

that's what says ESX on ssh comand line about this disk:

# fdisk -l

***
*** The fdisk command is deprecated: fdisk does not handle GPT partitions. Please use partedUtil
***

Disk /dev/disks/naa.600c0ff000138d4a0728eb5e01000000: 1998.3 GB, 1998375747584 bytes
255 heads, 63 sectors/track, 242955 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/disks/naa.600c0ff000138d4a0728eb5e01000000 doesn't contain a valid partition table
Found valid GPT with protective MBR; using GPT

[WEugene00]

Hi,

try this by SSH on P2000:

# show unwritable-cache (probably displayes about 98 %)

# clear cache (should be 0)