Link to home
Start Free TrialLog in
Avatar of vianceadmin
vianceadmin

asked on

VMDK's showing up on VM even when removed

I have a virtual server where I have removed 2 vmdk's but after a few minutes they show up again?  The vmdk's actually belong to another VM that is online...

I have removed them from the VM twice but they show up again...This is on ESX 5.5.  It's almost like they are mapped some other way?
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

do they belong to another VM, have you crossed checked with RV tools ?

https://www.robware.net/rvtools/
Avatar of vianceadmin
vianceadmin

ASKER

They do belong to another VM that is currently running (let's call that one VM1).  VM2 is another server and has vmdk1 and vmdk2 from VM1 added to it's settings.  I have gone in and removed them from VM2 but they show back up a few minutes later...
When you removed them, did you select remove from the VM inventory ?

what is appearing the listing in the VM
Correct.  I obviously don't want to delete them since they are in use on the other virtual server.  I will see the VMDK's for the server 2 but then the VMDK's that I just removed from inventory (that belong to server 1) show back up on server 2.
No, both VM's are in use and I want to keep both.  I just don't understand why VMDK's from another server continue to show up on this one even after I remove them from inventory...
It's not something I've seen, because you should be able just to use the function remove (not delete from disk), although as they would be locked an on, they would not be deleted.

What you could do, is remove the VM from the inventory, edit the VMX file, and remove the VMDK references.

then add to Inventory again.
I was in the process of moving from an old virtual environment to a new one so I just migrated this one (and the VMDK's) so now the VMDK's that were showing up on that one VM aren't available in that old virtual environment so I guess it's a moot point.  But strange that it was happening in the first place - I had never seen that before...
ASKER CERTIFIED SOLUTION
Avatar of vianceadmin
vianceadmin

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial