VMware Cloud Community
MikeMedcalf
Contributor
Contributor
Jump to solution

ESXi/vCenter 6.7u2 storage vMotion completed but old datastore still shows VM (verified no ISO or snapshots)

I recently migrated a VM from one datastore to another.  vMotion completed successfully and without error and the settings on the VM only reference the new datastore.  Looking at the file structure of the old datastore, there is only the .sdd.sf and .vSphere-HA folders and no files on root.  However, when I look at attached VMs on that datastore it still shows the migrated Virtual Machine.

I've been digging through forums for the last couple of hours but everything similar suggests a connected ISO, old snapshots, or a failed/corrupt migration.  Neither exist or existed prior to the migration, the migration was successful, and no errors were generated (at least as per the GUI).  For good measure I've also tried vMotion'ing the server to yet another datastore along with another host but to no avail.  As a final desperation I tried connecting/removing an ISO to see if an old link reference existed but this also had no impact.  All this said, if I missed a good reference please let me know!

This is all part of a grander project.  We are migrating from a 5.5 environment to a new 6.7u2 environment (new hosts and vCenter deploy, offline moves) then migrating to new storage.  There are actually two servers that did this out of 10 that were migrated during the same approx. time frame and are the only ones out of ~50 servers migrated so far.  If I can provide more specific information, logs, and/or screenshots, I'm happy to attach it.

Thanks!

Reply
0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

The log file contains a reference to a another datastore for the floppy disk drive

floppy0.fileName = "/vmfs/volumes/56996862-fc72c4f7-2442-0017a4770000/MVSD-UCM-PUB"

Please see whether setting the floppy to e.g. "Client Device" solves the issue.

André

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

View solution in original post

Reply
0 Kudos
5 Replies
a_p_
Leadership
Leadership
Jump to solution

Would you mind to attach the VMs current vmware.log file to a reply post?

André

MikeMedcalf
Contributor
Contributor
Jump to solution

Attached

Thank you for taking a look!

~mike

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

The log file contains a reference to a another datastore for the floppy disk drive

floppy0.fileName = "/vmfs/volumes/56996862-fc72c4f7-2442-0017a4770000/MVSD-UCM-PUB"

Please see whether setting the floppy to e.g. "Client Device" solves the issue.

André

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

Reply
0 Kudos
MikeMedcalf
Contributor
Contributor
Jump to solution

Hi André,

Nice catch!  Apparently floppy drives don't show up in the HTML5 web console when editing a VM.  The floppy showed up both under editing directly from the host and via the Remote console.

I'm good to go!  Thank you!!!

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

That's very interesting. I never noticed this, but the HTML5 client indeed lacks the ability to edit Floppy disk settings. It shows Floppy Disk devices in the Hardware Pane, but they do not show up in Edit Settings!

The Flash Client, the Embedded Host Client, and VMRC provide this functionality.

Definitely a bug, or something that has been overlooked in the product development.

André

Update: I just updated my lab vCSA 6.7 to Build 14070457 to see whether this issue has already been fixed. Unfortunately it's not, i.e. same issue.

Reply
0 Kudos