VMware Cloud Community
bmorebullets
Contributor
Contributor

The vSphere Client Add Storage Wizard Error: A specified parameter was not correct Vim.Host.Disk.PartitionInfo.spec

I'm trying to create a LOCAL datastore on a Hitachi 500GB HD wit vSphere 5.5. I keep getting the error:

A specified parameter was not correct Vim.Host.Disk.PartitionInfo.spec

Error Stack

Call "HostStorageSystem.ComputeDiskPartitionInfo" for object "storageSystem" on ESXi "192.168.x.x" failed.

================================================================================

I'm followin the VMware KB: Troubleshooting the Add Storage Wizard error: Unable to read partition information from t...

I have a problem when getting to the partedUtil section:

This is the drive (device) I want to use for the datastore:

sata.vmhba0-sata.0:0-t10.ATA_____Hitachi_HDP725050GLA360_______________________GEA530RE2VN8XA

   UID: sata.vmhba0-sata.0:0-t10.ATA_____Hitachi_HDP725050GLA360_______________________GEA530RE2VN8XA

   Runtime Name: vmhba0:C0:T0:L0

   Device: t10.ATA_____Hitachi_HDP725050GLA360_______________________GEA530RE2VN8XA

   Device Display Name: Local ATA Disk (t10.ATA_____Hitachi_HDP725050GLA360_______________________GEA530RE2VN8XA)

   Adapter: vmhba0

   Channel: 0

   Target: 0

   LUN: 0

   Plugin: NMP

   State: active

   Transport: sata

   Adapter Identifier: sata.vmhba0

   Target Identifier: sata.0:0

   Adapter Transport Details: Unavailable or path is unclaimed

   Target Transport Details: Unavailable or path is unclaimed

   Maximum IO Size: 33553920

This is the partedUtil command I'm trying to run:

partedUtil getptbl "/vmfs/devices/disks/t10.ATA_____Hitachi_HDP725050GLA360_______________________GEA530RE2VN8XA"

Nothing happend when I run the command.

I also tried fdisk

fdisk -l "vmfs/devices/disks/t10.ATA_____Hitachi_HDP725050GLA360_______________________GEA530RE2VN8XA"

Nothing happend when I run the command.

NTOE: This may be useful info from  ls /vmfs/devices/disks command

mpx.vmhba32:C0:T0:L0                                                        vml.0000000000766d68626133323a303a30

mpx.vmhba32:C0:T0:L0:1                                                      vml.0000000000766d68626133323a303a30:1

mpx.vmhba32:C0:T0:L0:5                                                      vml.0000000000766d68626133323a303a30:5

mpx.vmhba32:C0:T0:L0:6                                                      vml.0000000000766d68626133323a303a30:6

mpx.vmhba32:C0:T0:L0:7                                                      vml.0000000000766d68626133323a303a30:7

mpx.vmhba32:C0:T0:L0:8                                                      vml.0000000000766d68626133323a303a30:8

t10.ATA_____Hitachi_HDP725050GLA360_______________________GEA530RE2VN8XA    vml.0100000000202020202020474541353330524532564e385841486974616368

t10.ATA_____Hitachi_HDP725050GLA360_______________________GEA530RE2VN8XA:1  vml.0100000000202020202020474541353330524532564e385841486974616368:1

Please advise

Reply
0 Kudos
5 Replies
Vfreak07
Contributor
Contributor

Hi,

Please see if this Discussion helps you in some way. Error attempting to create a Datastore

PS: Please like if this was helpful.

PS: Like if this was helpful!
Reply
0 Kudos
bmorebullets
Contributor
Contributor

I think the problem has something to do with: VMware KB: Multipathing policies in ESXi 5.x and ESXi/ESX 4.x

and/or

Configuring the Storage adapter...

Reply
0 Kudos
Midus
Contributor
Contributor

Just a shot in the dark....  try wiping the disk with gpart and try again? Had this disk been used for something else like VSAN or other OS? It could be the boot-sector or partition table is locked or inaccessible for some reason.

www.midus-fx.com
Reply
0 Kudos
bmorebullets
Contributor
Contributor

I was able to add the internal hard drive by formatting it as vmfs3 format.  It would not take vmfs5 format. Not sure why tho, I suspect there was a compatibility issue.

Reply
0 Kudos
stevemnardini
Contributor
Contributor

I had the same issue with internal storage on an HP DL 380G6.  I added the storage as VMFS3 and then upgraded to VMFS5 OK.

Reply
0 Kudos