Fehler beim Speicherplat erweitern einer 'HardDisk' (PowerCLI Set-HardDisk)

[stefMa]

Hallo,

Code:

$vm=get-vm -Name  'testmas-v304'

$vm.PowerState
$size=60
Get-HardDisk -VM testmas-v304 -Name "Hard disk 1"
get-vm -Name  'testmas-v304' | Get-HardDisk  -Name "Hard disk 1" | Set-HardDisk  -CapacityGB 65.2  -Confirm:$false -Verbose

Get-HardDisk -VM testmas-v304 -Name "Hard disk 1"

-->Outputput:

Connected to..
vc-v003
KT\Smarty
PoweredOff

CapacityGB      Persistence                                                    Filename
----------      -----------                                                    --------
60.100          Persistent           ...od_nfs_win2_28d] testmas-v304/testmas-v304.vmdk
AUSFÜHRLICH: 14.03.2018 15:29:39 Set-HardDisk Started execution
AUSFÜHRLICH: Ausführen des Vorgangs "Setting CapacityGB: 65.19999980926513671875." für das Ziel "Hard disk 1".
AUSFÜHRLICH: 14.03.2018 15:29:39 Set-HardDisk Finished execution
Set-HardDisk : 14.03.2018 15:29:40 Set-HardDisk  Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
In \\kt.lunet.ch\shares\Powershell-Include\Server\Maintenance\vm-osLWresize.ps1:28 Zeichen:69
+ ... rd disk 1" | Set-HardDisk  -CapacityGB 65.2  -Confirm:$false -Verbose
+                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-HardDisk], ViError
    + FullyQualifiedErrorId : Client20_ClientSideTaskImpl_ThreadProc_UnhandledException,VMware.VimAutomation.ViCore.Cmdlets.Commands.VirtualDevice.SetHardDisk

60.100          Persistent           ...od_nfs_win2_28d] testmas-v304/testmas-v304.vmdk

Kennt jemand diesen Fehler?

[pwilk]

Please take a look at the following KB article:

VMware Knowledge Base

This should be able to help you resolve your issue.

If not please supply more logs (in english this time please )

Cheers,

Paul Wilk

[a_p_]

Discussion moved from VMware vSphere™ to VMware PowerCLI

[LucD]

Which PowerCLI version are you using?

Do a Get-PowerCLIVersion

[stefMa]

Get-PowerCLIVersion

PowerCLI Version
----------------
   VMware PowerCLI 6.5 Release 1 build 4624819
---------------
Component Versions
---------------
   VMware Cis Core PowerCLI Component 6.5 build 4624453
   VMware VimAutomation Core PowerCLI Component 6.5 build 4624450

[LucD]

You should consider upgarding to PowerCLI 10.

This error is a bit of catch all.

Did you stop/start your PowerShell session in the mean time?

Is the error still there in that case?

Do you get this only with this specific VM, or also with other VMs?

[stefMa]

Did you stop/start your PowerShell session in the mean time?

Yes

Is the error still there in that case?

Yes

Do you get this only with this specific VM, or also with other VMs?

Yes

[LucD]

Can you upgrade your version of PowerCLI?

[stefMa]

No, i can't install the new Version of PowerCLI. My environment does not meet the requirements yet.

[LucD]

From the error message I deduce that this VM is sitting on a NFS datastore. Correct?

Do you have a local disk on which you could create a VMFS datastore for a test, just to verify that a VM on that datastore would also have the issue?
Just trying to find what could be causing this.

It could also be helpful to have a look in the vpxd log at the time when you have the error.

There might be additional info in there.

And finally, is there anything in the vmware.log of that VM?

That log sits in the VM's folder on the datastore.