VMware Cloud Community
AnonAdmin
Enthusiast
Enthusiast

Setting Advanced parameters

I'm trying to set a path for ScratchSpace for a single ESXi 5.0 host and receive the following error from my command below;

# vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/[datastore GUID]/.scratch

(vmodl.fault.InvalidArgument) {

   dynamicType = <unset>,

   faultCause = (vmodl.MethodFault) null,

   invalidProperty = <unset>,

   msg = "A specified parameter was not correct.

",

}

I've read some other posts in the forum that this may be a bug? If that's true is there any workaround or fix? Thanks in advance.

0 Kudos
4 Replies
APJ_vm
Enthusiast
Enthusiast

have you tried using the datastore name instead of the GUID ?

This KB article VMware KB: Creating a persistent scratch location for ESXi 4.x and 5.x seems to suggest you can substitute GUID with the datastore name, this in turn will get translated to the GUID.

0 Kudos
bykreddy
Enthusiast
Enthusiast

Hi,

Using Tech Support Mode, This can be done either via the local console or SSH.

1. Create a uniquely-named directory for this ESXi host using the command:

mkdir /vmfs/volumes/DatastoreName/DirectoryName

For example:

mkdir /vmfs/volumes/Datastore1/.locker-ESXHostname

2. Check the current value of the ScratchConfig.ConfiguredScratchLocation configuration option using the command:

vim-cmd hostsvc/advopt/view ScratchConfig.ConfiguredScratchLocation

Example output:

(vim.option.OptionValue) [

(vim.option.OptionValue) {

dynamicType = <unset>,

key = "ScratchConfig.ConfiguredScratchLocation",

value = "/path/to/location",

}

}

3. Change the ScratchConfig.ConfiguredScratchLocation configuration option, specifying the full path to the directory created in step 1, using the command:

vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/DatastoreName/DirectoryName

For example:

/bin/vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/Datastore1/.locker-ESXHostname

4. Put the ESXi host into maintenance mode and reboot for the configuration change to take effect.

Regards, Yash - If you found this or any other answer helpful, please consider the use of the Helpful or Correct buttons to award points.
0 Kudos
netadminIM
Contributor
Contributor

I have the same problem, but this is with ESXi 6.0

vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string /vmfs/volumes/Scratch/.locker-vsphere01

Results in

(vmodl.fault.InvalidArgument) {

   faultCause = (vmodl.MethodFault) null,

   invalidProperty = <unset>,

   msg = "Received SOAP response fault from [<cs p:1f2af560, TCP:localhost:80>]: updateValues

A specified parameter was not correct: "

}

Same error in web client.

Tried using GUID and name, same error.

Can't figure out what parameter that was incorrect..

Tried everything this article suggests, but still the same error.

VMware KB: Creating a persistent scratch location for ESXi 4.x/5.x/6.0

0 Kudos
joboyle
Contributor
Contributor

The directory on the datastore must exist first. So the steps are:

1)Create the folder on the datastore.

2) Modify the Scratch.CofiguredScratchLocation parameter. You can use either the GUID or the datastore name. If you use the name, it will automatically replace it with the GUID.

0 Kudos