VMware Cloud Community
ManivelR
Hot Shot
Hot Shot
Jump to solution

Invalid operation for device '0' vcloud director v10 VM while try to extend the virtual disk

Hi All,

We recently did P2V.It has been successfully converted to VMware and the VM is currently running on top of VCD.

vSphere version is 6.7 U1

vcloud director v10

Windows 2012 version

The Windows 2012 has 2 disks with LSI parallel SCSI controller.

C--> 100 GB space--> Tried to extend the space(from tenant VDC) via online with another 50 GB it got successful.

D--> 760 GB space --->Tried to extend the space(from tenant VDC) with another 450 GB it was not successful.Tried with lower space also 10 GB,50 GB etc..Getting the error as Invalid operation for device '0' also  tried out from vCenter server  as well but no luck on both online/offline.

There is no snapshots running on this VM.

VPXA logs:-

020-04-27T03:59:46.638Z info vpxa[8891692] [Originator@6876 sub=Default opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37] [VpxLRO] -- ERROR task-17930 -- vm-233 -- vim.VirtualMachine.reconfigure: vim.fault.InvalidDeviceOperation:

--> Result:

--> (vim.fault.InvalidDeviceOperation) {

-->    faultCause = (vmodl.MethodFault) null,

-->    faultMessage = <unset>,

-->    property = "virtualDeviceSpec.device",

-->    deviceIndex = 0,

-->    badOp = "edit",

-->    badFileOp = <unset>

-->    msg = "Invalid operation for device '0'."

hostd logs

2020-04-27T03:59:46.484Z error hostd[2101441] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-e-drive.vmx opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37-8018 user=vpxuser:VSPHERE.LOCAL\Administrator] New disk capacity change request is ambiguous: (vim.vm.device.VirtualDisk) {

-->    key = 2001,

-->    deviceInfo = (vim.Description) {

-->       label = "Hard disk 2",

-->       summary = "827,983,920 KB"

-->    },

-->    backing = (vim.vm.device.VirtualDisk.FlatVer2BackingInfo) {

-->       fileName = "[]/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-d-drive.vmdk",

-->       datastore = 'vim.Datastore:datastore-15',

-->       backingObjectId = "ee94735e-a092-3899-4236-d4ae52981f05",

-->       diskMode = "persistent",

-->       split = false,

--> writeThrough = false,

--> thinProvisioned = true,

--> eagerlyScrub = <unset>,

-->       uuid = "6000C292-574e-9ef0-ca27-922b2185a051",

-->       contentId = "109a9a3551fe0a5ad2f14dae1068240a",

-->       changeId = <unset>,

-->       parent = (vim.vm.device.VirtualDisk.FlatVer2BackingInfo) null,

--> deltaDiskFormat = <unset>,

--> digestEnabled = false,

--> deltaGrainSize = <unset>,

--> deltaDiskFormatVariant = <unset>,

-->       sharing = <unset>,

-->       keyId = (vim.encryption.CryptoKeyId) null

-->    },

-->    connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,

-->    slotInfo = (vim.vm.device.VirtualDevice.BusSlotInfo) null,

--> controllerKey = 1000,

-->    unitNumber = 1,

-->    capacityInKB = 827988992,

--> capacityInBytes = 847860727808,

-->    shares = (vim.SharesInfo) {

-->       shares = 1000,

-->       level = "normal"

-->    },

--> storageIOAllocation = (vim.StorageResourceManager.IOAllocationInfo) {

-->       limit = -1,

-->       shares = (vim.SharesInfo) {

-->          shares = 0,

-->          level = "normal"

-->       },

-->       reservation = 0

-->    },

-->    diskObjectId = "242-2001",

--> vFlashCacheConfigInfo = (vim.vm.device.VirtualDisk.VFlashCacheConfigInfo) null,

-->    iofilter = <unset>,

-->    vDiskId = (vim.vslm.ID) null,

--> virtualDiskFormat = <unset>,

-->    nativeUnmanagedLinkedClone = <unset>

2020-04-27T03:59:46.485Z info hostd[2101441] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-d-drive.vmx opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37-8018 user=vpxuser:VSPHERE.LOCAL\Administrator] Reconfigure failed: N3Vim5Fault22InvalidDeviceOperation9ExceptionE(Fault cause: vim.fault.InvalidDeviceOperation

--> )

--> [context]zKq7AVICAgAAAJA0nQAYaG9zdGQAAAy3NWxpYnZtYWNvcmUuc28AAJDIGwDwuBcBg/ViaG9zdGQAAUQhagFcp7EBfKexAYK4sQG8VbABh/6wAZUlsAFhoLEBN6quAdIjrwHNLq8BjTGvgiIkAgFsaWJ2aW0tdHlwZXMuc28AATULwgEtFMIAtU0oAJNRKADLLDYDO30AbGlicHRocmVhZC5zby4wAAQdmw5saWJjLnNvLjYA[/context]

2020-04-27T03:59:46.492Z warning hostd[2101441] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-d-drive.vmx opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37-8018 user=vpxuser:VSPHERE.LOCAL\Administrator] Exception thrown during reconfigure: (vim.vm.ConfigSpec) {

2020-04-27T03:59:46.604Z warning hostd[2101441] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:523a90f10336da7b-df2f275d8f869fd4/e194735e-42a7-9f7d-d89c-d4ae52981f05/rfs-d-drive.vmx opID=vcd-752e124f-af8e-4bf7-9202-9260df3e59b0;activity=urn:uuid:06c92315-73e5-4295-8b75-bc7eed8a7063-29-01-37-8018 user=vpxuser:VSPHERE.LOCAL\Administrator] Reconfigure failed,

I dont know why D drive extension only creating this issue ?

Note:-  For testing purpose,we did restoring the VM from Veeam recent backup. After VM restore to vCenter,we tried to extend the D drive with another 100 GB it got successful.

But the main VM is still having the same issue.

Any ideas ?

Thanks,

Manivel R

0 Kudos
1 Solution

Accepted Solutions
scott28tt
VMware Employee
VMware Employee
Jump to solution

This might help you: Workaround for "invalid operation for device '0'." when resizing disks : vmware

Moderator: I am moving this thread to the vSphere area as your issue is not specific to vCenter Server.


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog

View solution in original post

0 Kudos
2 Replies
scott28tt
VMware Employee
VMware Employee
Jump to solution

This might help you: Workaround for "invalid operation for device '0'." when resizing disks : vmware

Moderator: I am moving this thread to the vSphere area as your issue is not specific to vCenter Server.


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
0 Kudos
ManivelR
Hot Shot
Hot Shot
Jump to solution

Yes Scott. I saw this one and it really helped to solve the isse.

Power CLI 6.5 not worked as exception triggered.

I managed to downgrade to 6.0 power cli and it solved.My virtual drive has been successfully extended.

Thanks,

Manivel R

0 Kudos