Page 3 of 3
Re: For the VM a new session can not be opened
Posted: 22. Aug 2018, 20:41
by Dirk_Lehmann
I unmounted the drive.
Re: For the VM a new session can not be opened
Posted: 22. Aug 2018, 20:59
by klaus
Dirk_Lehmann wrote:I unmounted the drive.
And what should I learn from such a statement without any context? Everything just gets more mysterious instead of more clear.
At the moment all I can do is hack up a .vbox file which will resurrect the VM as of June 12, i.e. when you took the first snapshot. I'd like to do better, but you need to have the disk images somewhere or it's simply not possible.
Re: For the VM a new session can not be opened
Posted: 23. Aug 2018, 22:21
by Dirk_Lehmann
I unmounted the drive that no more write access will be done to the drive and to going to undelete somehow the missing vdmk. I did not delete them and since this accident and since cloning the damaged vm there are only those .sav files ans these vdmk any more.
Re: For the VM a new session can not be opened
Posted: 25. Aug 2018, 09:36
by Dirk_Lehmann
Seems I need files back which where changed or deleted by VirtualBox. Do you got a hint or contact? Ext4 file system is not damaged.
Re: For the VM a new session can not be opened
Posted: 27. Aug 2018, 16:12
by klaus
You're the only (or very very few, but never verified) case where VirtualBox seems to have spontaneously deleted important files - but since that's right now something which no one can confirm or reproduce we can't work in this direction anyway.
Which valid VMDK images can you find on your external disk? Anything which "VBoxManage internalcommands dumphdinfo" declares as "VBoxManage: error: Format autodetect failed: VERR_NOT_SUPPORTED" are likely damaged, and this really shouldn't be VirtualBox's fault because it takes great care to never modify disk images related to some snapshot (or even open these for writing).
Should I write up a config file which covers the 2 images which you have accessible? Right now that's the best anyone can do - but if you actually have any further intact VMDKs then it'd be the least effort if you provide the dumphdinfo details. It's much less effort to do this once than to adjust the config several times.