batmangrubbs wrote:I made no unsupported assertion.
Eh? Of course you did. You made an assertion - you verbally stated that the file is present - but provided no supporting evidence. That is the very definition of the term.
And now the evidence appears to show a newly created VM with an empty VDI and a missing .vbox file.
What I now suspect will be part of this is that you were running from a live CD of this Linux distro, and you reset the VM. But that still doesn't explain what you are doing to get the "file not found" error.
This is what the normal folder structure would have been. Try to get it looking like this. Note however that if the best VDI you can recover is only 2MB then it is empty (2MB is just the header), in which case you may as well delete the VM and start again. You would only continue if there is a large .SAV file inside the Snapshots subfolder AND you can restore the lost .vbox file.
Code: Select all
"VirtualBox VMs" (or other container folder)
"HackOne" (I assume this is a group folder)
"SecurityOnion-HackOne" (VM name)
"Snapshots" (subfolder for snapshots and saved state files)
"SecurityOnion-HackOne.vbox" (control file)
"SecurityOnion-HackOne.vdi" (primary hard disk)