Orphaned Persistent Disks

[ForgeFlakshack]

After deleting a pool, there are some "orphaned" disks remaining in the Persistent Disks section that still show as "attached."  The VMs were removed by View when the pool was deleted and the VMDK files don't exist anymore.

If I try to click on "detach", I see the message:

You cannot remove the primary data disk until all the secondary disks have been detached from the VM.

How can I remove these entries?

[Jubish]

Hi,

A few questions:

1) Are you still seeing the deleted pools/desktops in the pool/desktop inventory?

2) Are you still seeing the deleted VMs in the vCenter console?

3) Did you perform any backup restore or snapshot revert operations on the Connection Server?

If the desktops are deleted and peristent disks archived, the persistent disks will be under 'Detached' tab, not under 'Attached'

Thanks,

- J

[ForgeFlakshack]

Thanks for the reply.

1.  The Pools no longer appear in View Administrator.

2.  The VMs are no longer in vCenter and the VMDK files are no longer in the Datastore.

3.  To my knowledge, we did not do any back-end operations (restoring the Connection Server, manually deleting VMs, etc).

When the pool was deleted, the option was selected to delete all the persistent disks.  We did not want to keep them.

We don't have a lot in our View Administrator yet since we're still doing proof of concept work.  Failing all else, I can just reinstall.  I was just hoping to learn from this experience now in case something similar happens again once we're in production.

[bhamm · Accepted solution]

Was there an error during the deletion of the pool?  You should be able to see it in the event log if there was.

My guess is there's still some data on the pool in adam or view composer.  The link below will tell you how to clear it out:

http://kb.vmware.com/kb/1008658

[ForgeFlakshack]

Thanks for the help, that solved my issue.

To recap if anyone else has this problem:

1. On the view connection server I used ADSI edit to connect to dc=vdi, dc=vmware, dc=int on localhost.
2. In OU=Data Disks, I found the disks that were the problem by checking the pae-DataDiskDatastorePath property.
3. Deleted the node and the disk disappeared from View Administrator.
4. Used SQL Enterprise Manager to check the View Composer database for orphans by cross referencing SVI_SIM_CLONE and SVI_SC_PDISK_INFO.  All the disks there were correct so no changes needed.