When I try to attach an existing hard disk to a VM guest, I receive error "The system information reported by the host for 'VirtualDisk' is inconsistent. This device cannot currently be edited"
This occurred AFTER the upgrade to Virtual Center 2.5U2 (Build 104215).
I can successfully attach the same disk if I use Virtual Center and log into the host. Also, I can attach the disk if I use web access to directly manage the host.
I was able to reproduce this in my test VM lab. I had VC 2.5 Build 84676 installed and could perform the task. I then applied the VC 2.5 U2 patch and that functionality was lost.
This happens to most of my guests in the production VC but not all guests.
I have opened an SR with Vm tech support.
Has anyone seen this ????
This occurs because vc2.5U2 checks the VMDK file for the line "ddb.adapterType =". Apparently when upgrading from ESX 2.x to ESX3, the apadpter type "legacyESX" was added to the VMDK for the adapter type. This adapter types appears whether Buslogic or LSIlogic is defined.
You can edit the vmdk file and add the correct adapter type. After changing the adapter type, you can add the disk to an existing guest.
You you add a new disk the correc type is added as expected. Again this appears to be guests that were upgraded.
VM tech support implied that a fix would not soon be coming due to this having a low impact. You will have to modify the VMDK file or http:
hostname and add it there.
Many thanks for the input, could you give me the SR number this was raised under please so I can register with this problem as well. That way more awareness will be raised of the issue.
Many Thanks again.
I am doing a manual import of ESX 2.5.4 VM disk files to the latest ESX 3.5 U2/VC 2.5 and was stumped on this issues for a day.
Thanks to your post I was able to fix the issue, but it would be great if VMware would fix this issue.
The error i was getting was a generic "Error: The value exceeded the acceptable range"
Only adding the disk to a new VM config to VIC showed the error " 'VirtualDisk' is inconsistent" whichhelped me towards a solution.
It's hard to believe ho can Vmware say it's a low priority, We have a large environment and whenever we have to do Disk expansion we run into this issue.
We are planning to open a SR with the Vmware as well, will keep everyone posted about how it went.
I have the same issue... i found that if you log into a host directly rather than the VI Server with your VI Client, adding a disk works fine.
well it worked for me anyway.
Message was edited by: Sealordmwt
Sorry, didnt read the first post properly... you already did that
We too started noticing this after upgrading our hosts to ESX 3.5 Update 2 with VC 2.5.
If you go through the Wizard to add a 2nd disk to a VM, you now don't get the option to change the SCSI options for the new disk which you used to be able to (ie choose a diferent SCSI device node id - 0:1, 1:0 etc) and when you get to the confirmation or summary details at the end of the add-disk wizard, you will see that the disk being added is now shown as an IDE disk! ie ide(1:0)
We reported this bug to VMWare a couple of weeks ago.
We also found that using the VI client directly to the host that the VM is on and adding the 2nd disk from there works ok, when the hosts are ESX 3.5 U2 (but apparently not when they are ESX 3.0.2), so it appears to be a bug in VC 2.5 (Build 104215).
We started noticing this after upgrading our hosts to ESX 3.5 Update 3 with VC 2.5.
We also found that using the VI client directly to the host that the VM is on and adding the 2nd disk from there works ok, when the hosts are ESX 3.5 U2 or U3.