Page 2 of 3
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 11:13
by Dirk_Lehmann
If you have kept the default settings, then your VM should be located in "/home/dirk/VirtualBox VMs/Windows 2012 R2". I need the output of:
[list]ls -alR "/home/dirk/VirtualBox VMs/Windows 2012 R2"[/list]
dirk@ubuntu:~$ ls -alR "/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2"
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2:
insgesamt 303867272
drwx------ 4 dirk dirk 4096 Aug 19 16:41 .
drwxr-xr-x 14 dirk plugdev 4096 Aug 19 20:07 ..
drwx------ 2 dirk dirk 4096 Aug 19 13:09 Logs
-rw------- 1 dirk dirk 45056 Aug 19 14:56 .save.swp
drwx------ 2 dirk dirk 4096 Aug 18 22:03 Snapshots
-rw------- 1 dirk dirk 310856581120 Jun 12 01:22 Windows 2012 R2-disk001.vmdk
-rw------- 1 dirk dirk 34064 Aug 19 13:20 Windows 2012 R2.vbox
-rw------- 1 dirk dirk 34747 Aug 19 13:10 Windows 2012 R2.vbox-prev
-rw-rw-r-- 1 dirk dirk 4243 Aug 19 16:41 Windows 2012 R2.vbox.zip
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2/Logs:
insgesamt 604
drwx------ 2 dirk dirk 4096 Aug 19 13:09 .
drwx------ 4 dirk dirk 4096 Aug 19 16:41 ..
-rw------- 1 dirk dirk 155309 Aug 19 13:10 VBox.log
-rw------- 1 dirk dirk 154835 Aug 18 22:04 VBox.log.1
-rw------- 1 dirk dirk 122556 Aug 18 22:02 VBox.log.2
-rw------- 1 dirk dirk 159486 Aug 18 21:35 VBox.log.3
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2/Snapshots:
insgesamt 13354184
drwx------ 2 dirk dirk 4096 Aug 18 22:03 .
drwx------ 4 dirk dirk 4096 Aug 19 16:41 ..
-rw------- 1 dirk dirk 8782059324 Aug 11 15:57 2018-08-11T13-56-22-998016000Z.sav
-rw------- 1 dirk dirk 4879142461 Aug 18 15:31 2018-08-18T13-30-05-010926000Z.sav
-rw------- 1 dirk dirk 39452672 Jun 12 01:22 {6a44b215-bec1-49a3-a18f-d49e7b835e18}.vmd
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 11:22
by Dirk_Lehmann
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.
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 11:22
by socratis
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.
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 11:23
by socratis
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...
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 11:24
by Dirk_Lehmann
Did so
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 11:28
by Dirk_Lehmann
Have no earlier backup, yet without recovering from physical HD maybe, Here are the further files you where asking for.
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 11:51
by Dirk_Lehmann
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.
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 16:12
by klaus
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?
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 17:34
by Dirk_Lehmann
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"
here.
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 19:30
by klaus
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.
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 19:50
by Dirk_Lehmann
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.
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 20:36
by Dirk_Lehmann
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?
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 20:44
by Dirk_Lehmann
Maybe see:
VBoxManage internalcommands dumphdinfo /media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows\ 2012\ R2/Windows\ 2012\ R2-disk001.vmdk
--- Dumping VD Disk, Images=1
Dumping VD image "/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2/Windows 2012 R2-disk001.vmdk" (Backend=VMDK)
Header: Geometry PCHS=16383/16/63 LCHS=1024/255/63 cbSector=629145600
Header: uuidCreation={0f332512-5647-4557-b0d5-a9592111718b}
Header: uuidModification={db14dc29-943c-418a-8c3d-9da5db76ea68}
Header: uuidParent={00000000-0000-0000-0000-000000000000}
Header: uuidParentModification={00000000-0000-0000-0000-000000000000}
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:
dirk@ubuntu:~$ VBoxManage internalcommands dumphdinfo /media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows\ 2012\ R2/Snapshots/\{8dc674c1-4c10-430d-bd3d-ef12a927ceb2\}.vmdk
VBoxManage: error: Format autodetect failed: VERR_NOT_SUPPORTED
dirk@ubuntu:~$ VBoxManage internalcommands dumphdinfo /media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows\ 2012\ R2/Snapshots/\{275c7008-2a15-4d2d-844e-1c0f9517c378\}.vmdk
VBoxManage: error: Format autodetect failed: VERR_NOT_SUPPORTED
dirk@ubuntu:~$ VBoxManage internalcommands dumphdinfo /media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows\ 2012\ R2/Snapshots/\{f04a4a92-3ac3-4197-9dce-0e35dd821615\}.vmdk
VBoxManage: error: Format autodetect failed: VERR_NOT_SUPPORTED
dirk@ubuntu:~$ VBoxManage internalcommands dumphdinfo /media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows\ 2012\ R2/Snapshots/\{6a44b215-bec1-49a3-a18f-d49e7b835e18\}.vmdk
--- Dumping VD Disk, Images=1
Dumping VD image "/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2/Snapshots/{6a44b215-bec1-49a3-a18f-d49e7b835e18}.vmdk" (Backend=VMDK)
Header: Geometry PCHS=16383/16/63 LCHS=1024/255/63 cbSector=629145600
Header: uuidCreation={6a44b215-bec1-49a3-a18f-d49e7b835e18}
Header: uuidModification={00000000-0000-0000-0000-000000000000}
Header: uuidParent={0f332512-5647-4557-b0d5-a9592111718b}
Header: uuidParentModification={507fce05-d33f-4264-9f2d-3a108ebf2bcb}
dirk@ubuntu:~$
Re: For the VM a new session can not be opened
Posted: 20. Aug 2018, 20:49
by Dirk_Lehmann
Maybe this output of different directorys with different files might help to get just one vm with latest snapshot up again:
Code: Select all
dirk@ubuntu:~$ ls -alR "/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2 (Kopie)"/
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2 (Kopie)/:
insgesamt 303867728
drwx------ 4 dirk dirk 4096 Aug 19 20:07 .
drwxr-xr-x 14 dirk plugdev 4096 Aug 19 20:07 ..
drwx------ 2 dirk dirk 4096 Aug 19 13:09 Logs
drwx------ 2 dirk dirk 4096 Aug 18 22:03 Snapshots
-rw------- 1 dirk dirk 310856581120 Aug 19 20:11 Windows 2012 R2-disk001.vmdk
-rw------- 1 dirk dirk 34064 Aug 19 13:20 Windows 2012 R2.vbox
-rw------- 1 dirk dirk 34747 Aug 19 13:10 Windows 2012 R2.vbox-prev
-rw-rw-r-- 1 dirk dirk 4243 Aug 19 20:07 Windows 2012 R2.vbox.zip
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2 (Kopie)/Logs:
insgesamt 604
drwx------ 2 dirk dirk 4096 Aug 19 13:09 .
drwx------ 4 dirk dirk 4096 Aug 19 20:07 ..
-rw------- 1 dirk dirk 155309 Aug 19 13:10 VBox.log
-rw------- 1 dirk dirk 154835 Aug 18 22:04 VBox.log.1
-rw------- 1 dirk dirk 122556 Aug 18 22:02 VBox.log.2
-rw------- 1 dirk dirk 159486 Aug 18 21:35 VBox.log.3
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2 (Kopie)/Snapshots:
insgesamt 13392660
drwx------ 2 dirk dirk 4096 Aug 18 22:03 .
drwx------ 4 dirk dirk 4096 Aug 19 20:07 ..
-rw------- 1 dirk dirk 8782059324 Aug 11 15:57 2018-08-11T13-56-22-998016000Z.sav
-rw------- 1 dirk dirk 4879142461 Aug 18 15:31 2018-08-18T13-30-05-010926000Z.sav
-rw------- 1 dirk dirk 39452672 Jun 12 01:22 {6a44b215-bec1-49a3-a18f-d49e7b835e18}.vmdk
dirk@ubuntu:~$ ls -alR "/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2-Klon"/
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2-Klon/:
insgesamt 88
drwx------ 4 dirk dirk 4096 Aug 19 14:58 .
drwxr-xr-x 14 dirk plugdev 4096 Aug 19 20:07 ..
drwx------ 2 dirk dirk 4096 Aug 19 13:30 Logs
drwx------ 2 dirk dirk 4096 Aug 19 14:59 Snapshots
-rw------- 1 dirk dirk 33520 Aug 19 14:58 Windows 2012 R2-Klon.vbox
-rw------- 1 dirk dirk 34374 Aug 19 13:30 Windows 2012 R2-Klon.vbox-prev
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2-Klon/Logs:
insgesamt 280
drwx------ 2 dirk dirk 4096 Aug 19 13:30 .
drwx------ 4 dirk dirk 4096 Aug 19 14:58 ..
-rw------- 1 dirk dirk 154836 Aug 19 13:30 VBox.log
-rw------- 1 dirk dirk 111785 Aug 19 13:30 VBox.log.1
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2-Klon/Snapshots:
insgesamt 13354088
drwx------ 2 dirk dirk 4096 Aug 19 14:59 .
drwx------ 4 dirk dirk 4096 Aug 19 14:58 ..
-rw------- 1 dirk dirk 8782059324 Aug 19 13:27 2018-08-11T13-56-22-998016000Z.vmdk
-rw------- 1 dirk dirk 4879142461 Aug 19 13:30 2018-08-18T13-30-05-010926000Z.vmdk
dirk@ubuntu:~$ ls -alR "/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2_1"/
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2_1/:
insgesamt 36
drwx------ 3 dirk dirk 4096 Aug 19 20:10 .
drwxr-xr-x 14 dirk plugdev 4096 Aug 19 20:07 ..
drwx------ 2 dirk dirk 4096 Aug 19 20:10 Logs
-rw------- 1 dirk dirk 8248 Aug 19 20:10 Windows 2012 R2_1.vbox
-rw------- 1 dirk dirk 8248 Aug 19 20:07 Windows 2012 R2_1.vbox-prev
/media/dirk/59b80d1c-3259-4cf7-b56e-0b24d55f1111/Windows 2012 R2_1/Logs:
insgesamt 124
drwx------ 2 dirk dirk 4096 Aug 19 20:10 .
drwx------ 3 dirk dirk 4096 Aug 19 20:10 ..
-rw------- 1 dirk dirk 112497 Aug 19 20:10 VBox.log
dirk@ubuntu:~$
Re: For the VM a new session can not be opened
Posted: 22. Aug 2018, 19:09
by klaus
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.