Missing Data

[jay0071]

I have VMware Workstation 15 on Windows 10  running Ubuntu VM with Odoo installed.  I had an issue with my pc not booting so I've moved the whole VM folder to a new PC. When I load Odoo it is from June of this year. Last time VM was working fine was 27th September 19.  Even the files in the VM folder are dated 10-06-19. My VMX file is dated 30-09-19. The VM runs and all but it is from JUNE. Any idea how to get this back. I also copied to a demo esxi server but this was also Junes data. I seem to have lost a few months of work. No errors, VM runs fine. Even on the Odoo server, I changed the password about 2 weeks ago but I have to use a password form before that. This is my first time using VMware workstation. How can this happen? My Pc has 2 hard drives. An SDD with the OS on it and a 1 TB 3.5 HDD. The VM is saved on the 1TB drive. The SSD became corrupt so I just copied the VM folder from the 1TB drive and installed a demo of Workstation on my laptop but I am missing data and cannot figure out how?

[jay0071]

Its loading data only from that date.

[continuum]

Please attach the 4 vmware.log files to your next reply.

That should provide the missing details.

Either you operated the VM with nonpersistrent flag or a snapshot was used.

[jay0071]

Log files attached..

[jay0071]

Have you any idea from the logs?

[continuum]

The data that you are missing is stored in this files:

Ubuntu 64-bit-000002.vmdk

Ubuntu 64-bit-000002-s001.vmdk

Ubuntu 64-bit-000002-s002.vmdk

Ubuntu 64-bit-000002-s003.vmdk

Ubuntu 64-bit-000002-s004.vmdk

Ubuntu 64-bit-000002-s005.vmdk

Ubuntu 64-bit-000002-s006.vmdk

Ubuntu 64-bit-000002-s007.vmdk

Ubuntu 64-bit-000002-s008.vmdk

Ubuntu 64-bit-000002-s009.vmdk

Ubuntu 64-bit-000002-s010.vmdk

Ubuntu 64-bit-000002-s011.vmdk

Ubuntu 64-bit-000002-s012.vmdk

Ubuntu 64-bit-000002-s013.vmdk

Ubuntu 64-bit-000002-s014.vmdk

Ubuntu 64-bit-000002-s015.vmdk

Ubuntu 64-bit-000002-s016.vmdk

Ubuntu 64-bit-000002-s017.vmdk

Ubuntu 64-bit-000002-s018.vmdk

Ubuntu 64-bit-000002-s019.vmdk

Ubuntu 64-bit-000002-s020.vmdk

Ubuntu 64-bit-000002-s021.vmdk

Ubuntu 64-bit-000002-s022.vmdk

Ubuntu 64-bit-000002-s023.vmdk

Ubuntu 64-bit-000002-s024.vmdk

Ubuntu 64-bit-000002-s025.vmdk

Ubuntu 64-bit-000002-s026.vmdk    

Ubuntu 64-bit-000001-s001.vmdk

Ubuntu 64-bit-000001-s002.vmdk

Ubuntu 64-bit-000001-s003.vmdk

Ubuntu 64-bit-000001-s004.vmdk

Ubuntu 64-bit-000001-s005.vmdk

Ubuntu 64-bit-000001-s006.vmdk

Ubuntu 64-bit-000001-s007.vmdk

Ubuntu 64-bit-000001-s008.vmdk

Ubuntu 64-bit-000001-s009.vmdk

Ubuntu 64-bit-000001-s010.vmdk

Ubuntu 64-bit-000001-s011.vmdk

Ubuntu 64-bit-000001-s012.vmdk

Ubuntu 64-bit-000001-s013.vmdk

Ubuntu 64-bit-000001-s014.vmdk

Ubuntu 64-bit-000001-s015.vmdk

Ubuntu 64-bit-000001-s016.vmdk

Ubuntu 64-bit-000001-s017.vmdk

Ubuntu 64-bit-000001-s018.vmdk

Ubuntu 64-bit-000001-s019.vmdk

Ubuntu 64-bit-000001-s020.vmdk

Ubuntu 64-bit-000001-s021.vmdk

Ubuntu 64-bit-000001-s022.vmdk

Ubuntu 64-bit-000001-s023.vmdk

Ubuntu 64-bit-000001-s024.vmdk

Ubuntu 64-bit-000001-s025.vmdk

Ubuntu 64-bit-000001-s026.vmdk

Ubuntu 64-bit-000001.vmdk

So your next task is to find those files ....

[jay0071]

Yes I have those files

[jay0071]

I have those files what can I do with them?

[continuum]

I need the current vmx-file

[jay0071]

Last file seemed corrupt and wouldnt open. Please try this one

[continuum]

That vmx-file should load the complete snapshot chain ...

Does the VM try to start from suspended mode maybe ?

Do you have a vmss-file ?

A complete file listing that includes the complete names, date and size would really help ...

[jay0071]

I dont see a vmss file. Below is all files in that folder.

[jay0071]

Here are the files before I ran the VM on my laptop. So these are the files on the original PC. I just copied those files and ran the VM

[jay0071]

Any Ideas I am really stuck here?

[jay0071]

continuum​ Can you help?

[continuum]

sorry it has been a very busy day

and do not see any conclusive hint in the data you provided that would explain the behavior.

maybe its just lack of time ...

the timestamps of the vmdk slices are a bit obscure ....

maybe you have forgotten to mention some details that would help ....

right now I have promising suggestion and need to catch up on sleep

good night

send from phone

[jay0071]

I've given you all the information I have. The SSD drive wouldn't boot but the VM image was stored on another drive. I just copied the folder from that drive to another PC. Ran the VM and it is only booting data from June of this year. The last date the VM was running was 27th September. We think the PC went down Friday 27th at around 11:00 PM.