I posted also the ls -alR "/home/dirk/VirtualBox VMs/Windows 2012 R2", now it´s gone. Should I post again? This was my last export maybe from the allready not comming up vm from So, 19. Aug 2018 20:02:53. Have to restore anyhow any older.
Do NOT run the VM.
ZIP the following files: 1) Windows 2012 R2.vbox-prev and 2) All the VBox.log.* from the /Logs/ subdirectory.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Maybe I was too fast while editing your message, to include the output in the "quote" and "pre" tags. Could you please post it again in a new post? Sorry about that...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Going to recover a earlier Windows R2 Server.ova with R-Studio from the physical HD that I can send earlier Windows 2012 R2.vbox.zip. The scan therefore takes about one day. Do not yet know, if this will be recoverable.
No other .vmdk files? Because from the timestamps I would expect at least one more file, if not 2.
It seems that you took the first snapshot on June 12, 01:22 (actually a double snapshot or creating a linked clone, since the diff image has the same timestamp and is almost certainly empty, its size would match a ~300G image size).
Everything after this is probably lost unless you can get back some additional files (and no, VirtualBox isn't known to delete files randomly, it's extremely careful with such destructive operations). There are saved state files from August 11 and 18, but they're not worth much (except for some super emergency data scraping of stuff which might be in the VM's filesystem cache, but that's very unreliable) without the associated diff images.
How likely is it that you can get more data from backups etc? How useful would it be for you to reconstruct the VM's disk state as of June 12?
I can recover some more vdmk files with the last two snapshots. Going to do this when the backup of current files and directorys is finished and will post then the new output of
ls -alR "/home/dirk/VirtualBox VMs/Windows 2012 R2"
To be 100% sure how the images belong together (needed to reconstruct the .vbox file as accurately as possible) it'd be extremely useful to get the output of "VBoxManage internalcommands dumphdinfo /path/to/every.vdi" (for every VDI you found).
This gets me the medium UUID and parent UUID information (plus also the modification UUIDs to make sure that everything is intact) to double check. Going purely by the timestamps isn't perfect.
First of all: Thank you for your late reply. Going to do the internal commands as soon as possible and will post it. Hopefully you can get back to me tomorrow, not needed today. Thank you.
Unfortunatly I do not find any .vdi, only .vdmk, maybe see:
dirk@ubuntu:/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111$ cd Windows\ 2012\ R2
dirk@ubuntu:/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2$ lsLogs Windows 2012 R2-disk001.vmdk Windows 2012 R2.vbox-prev.zip
Logs.zip Windows 2012 R2.vbox Windows 2012 R2.vbox.zip
Snapshots Windows 2012 R2.vbox-prev
dirk@ubuntu:/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2$ cd Snapshot
bash: cd: Snapshot: Datei oder Verzeichnis nicht gefunden
dirk@ubuntu:/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2$ cd Snapshots/
dirk@ubuntu:/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2/Snapshots$ ls
2018-08-11T13-56-22-998016000Z.sav {6a44b215-bec1-49a3-a18f-d49e7b835e18}.vmdk
2018-08-18T13-30-05-010926000Z.sav
dirk@ubuntu:/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2/Snapshots$
I can recover some more (3 files) .vdmk and one more .sav in /media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2/Snapshots with the help of R-Studio for Linux Demo. Should I do this? What else can I hand out to you instead of VBoxManage internalcommands dumphdinfo /path/to/every.vdi?
and I recovered three more .vdmk ({f04a4a92-3ac3-4197-9dce-0e35dd821615\}.vmdk and {8dc674c1-4c10-430d-bd3d-ef12a927ceb2\}.vmdk and {275c7008-2a15-4d2d-844e-1c0f9517c378\}.vmdk meanwhile:
Yes, I meant running the dumphdinfo for all *.vmdk files you can find. The ones showing "VBoxManage: error: Format autodetect failed: VERR_NOT_SUPPORTED" are likely damaged. It might be possible to repair them, but that's a lot of extra effort for each of them.
BTW, throwing a lot of unclear information (especially lacking information about their correct timestamps and the like) is just making the job of helping you harder. So far I can't see that you have any intact files besides the 2 files you had originally (and for those I'm already somewhat worried about their integrity since the modification uuids don't match the way they should). Any chance of getting more dumphdinfo details for the files you recovered? Or are they all damaged?
From the latest file list it seems you also renamed the [timestamp].sav files to .vmdk, which doesn't turn them into a disk image magically.