Hot-add of Digest Enabled Disk Not Supported
Article ID: CTX227397
Updated On:
Description
The CachePoint Appliance could not create the boot image of Windows 10. Error is: Failed to reattach disks to the desktop that were temporarily attached to the CachePoint Appliance. In vSphere a vm reconfigure task displays, "Hot-add of digest enabled disk not supported".
Resolution
First, select your Unidesk Pools in the View Administrator page and Edit them. In the Advanced Storage tab, look for Host Caching and/or View Storage Accelerator, and disable it. That should stop VSA from making your desktops any worse, though you might need to stop and start them again to allow View to properly reconfigure them.
Specifically how to do this depends on the version of View (or Horizon View) you're using.
For instance, this URL describes turning it off for View 5.1. http://blogs.vmware.com/euc/2012/05/view-storage-accelerator-in-practice.html In View 5.2 and beyond, the feature is no longer called Host Caching, but is explicitly called View Storage Accelerator.
After you have disabled VSA on your pools, go to vSphere and find the CachePoint that the bad desktop is on. (You may need to do this on multiple CPs.) Use the vSphere "Browse Datastore" function and go into the CachePoint/UnideskLayers folder. Look through all of the layers (OS, App and User) and look for files named something-digest.vmdk and something-digest-flat.vmdk. Simply delete those.
The presence of a digest file is how VMware knows that a VMDK is digest-enabled, so removing an leftover files is necessary.
Once you have all the digest and digest-flat files deleted from the UnideskLayers tree, attempt your rebuild again. It should be sufficient to do a Restart from Unidesk.
If disabling VSA at the pool level and scrubbing out the leftover files isn't sufficient, you will need to turn VSA off at the vCenter level. In View Administrator, go to View Configuration, Servers, and edit your vCenter. Turn off Host Caching/VSA there, and then go back and search for the digest files again.
Specifically how to do this depends on the version of View (or Horizon View) you're using.
For instance, this URL describes turning it off for View 5.1. http://blogs.vmware.com/euc/2012/05/view-storage-accelerator-in-practice.html In View 5.2 and beyond, the feature is no longer called Host Caching, but is explicitly called View Storage Accelerator.
After you have disabled VSA on your pools, go to vSphere and find the CachePoint that the bad desktop is on. (You may need to do this on multiple CPs.) Use the vSphere "Browse Datastore" function and go into the CachePoint/UnideskLayers folder. Look through all of the layers (OS, App and User) and look for files named something-digest.vmdk and something-digest-flat.vmdk. Simply delete those.
The presence of a digest file is how VMware knows that a VMDK is digest-enabled, so removing an leftover files is necessary.
Once you have all the digest and digest-flat files deleted from the UnideskLayers tree, attempt your rebuild again. It should be sufficient to do a Restart from Unidesk.
If disabling VSA at the pool level and scrubbing out the leftover files isn't sufficient, you will need to turn VSA off at the vCenter level. In View Administrator, go to View Configuration, Servers, and edit your vCenter. Turn off Host Caching/VSA there, and then go back and search for the digest files again.
Problem Cause
View Storage Accelerator (VSA) has been enabled (also called Host Caching). VSA causes a set of additional files to be associated with every VMDK it affects: diskname-digest.vmdk and diskname-digest-flat.vmdk.
Was this article helpful?
Yes
No
Powered by
