asked on

VMWARE - Unable to update disk partition table

I recently added two drives to our VMWare host. The drives are stripped. When I attempt to add the drive set as a data storage group in VMWARE. I get the error message "Unable to update disk partition table"

I researched on line and I found the VMWare KB article that tells me to use fdisk from the console etc. However, the error that I get when I try the fdisk -u <identifier> is "unable to read from <identifier> I know the syntax is correct because I can change the identifier and all is well.

if I look under the dev\disks directory I do see the disk that I need to parition. If I run fdisk -l it does not display.

bgoering

Assuming you are using ESX or ESXi, from within your vSphere client select the server. Click on the configuration tab, then storage adapters. Select the rescan all link.

Now go to Storage and click Add Storage. The new drives should show up at that point and give you an opportunity to create a new datastore.

Good Luck

Tom892

ASKER

I'm running ESXi 4.0. I tried that but that did not work. I can see the storage that I need to add however it tells me it cannot update the partition table.

This is the VMWare KB I am referencing http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001489

However I cannot get past the part that says run fdisk -u <identifier> because it says it cannot read from <identifier>

bgoering

What kind of server and disk controller are you working with?

Tom892

ASKER

HP DL360 G5 Smart Array p400i

bgoering

If you haven't already you will need to run the Array configuration utility you need to do that.

If you have run the array configuration utility, how did you define the new drives? Are they a mirror set? Or just single drives?

Tom892

ASKER

Yea that was done, the array is stripped and is visible to the VMware Hypervisor. It shows as unallocated space. Pretty much I type the command fdisk -u mpx.vmhba1:C0:T1:L0. an it tells me it cant read it.

bgoering

Try

/dev/disks/fdisk -u mpx.vmhba1:C0:T1:L0

Tom892

ASKER

Tried that before. It works fine if I try a different disk identifier. You think its worth it to delete the array and recreate?

ASKER CERTIFIED SOLUTION

bgoering

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

bgoering

Well - added another disks to my (virtual) ESXi and all works as expected. I can see the disk in the client - storage adapters - click on vmhba1 and see disks in bottom pane. Can add as datastore under storage.

Played with fdisk - note that it didn't work without the full path (try one)
worked with full path (try two)
Diidn't work with case error in full path c0:t1:l0 (try three)

How did recreate array go?
fdisk.png

Tom892

ASKER

Sorry for the delay on responding. I have to schedule the server to come down.

bgoering

Thanks for the update

Tom892

ASKER

I was fooling around with it again. I notice that if the syntax is incorrect I get the cannot open error as you did. If the syntax is correct, I get the cannot read from error. These seperate array sets are connected to the same controller so that explains why it would be locked for editing from the vsphere client, however all the documentation says I should be able to do this from the console.

Tom892

ASKER

Something was messed up with the array. Once I took it down, removed and than recreated, I was able to add the other datastore without any problems.