Page 2 of 2

Re: Reconstruct vbox file?

Posted: 6. Oct 2016, 09:43
by mpack
HuntStockwell wrote: As it turns out, I have 2 snapshots that reference the same parent UUID - again I do not know how that could have happened.
Nothing unusual in that. Snapshot chains can have branches. If you have two snapshots linking to the same parent then that's a branch.


By the way, you can stop looking in VirtualBox logs for clues to your problem. This has nothing to do with VirtualBox, you have a corrupted filesystem in the guest OS. The VM itself is running fine.

Re: Reconstruct vbox file?

Posted: 7. Oct 2016, 06:53
by HuntStockwell
I'm pretty sure I didn't have any branches in my snapshot chain, but I'm obviously lacking in the ability to confirm that now.

I thought that the VM terminating might be due to a file problem as you suggest. I got a glimmer of hope when I saw the error in the log. Oh, well. At least I didn't have anything truly important there. I'll play around with it a bit more.

Thanks to you both for all the input.

Re: Reconstruct vbox file?

Posted: 7. Oct 2016, 09:44
by mpack
HuntStockwell wrote:I'm pretty sure I didn't have any branches in my snapshot chain, but I'm obviously lacking in the ability to confirm that now.
Well, you already did pretty much confirm it because of the data you provided: two snapshots with parent links to the same older VDI == a branch. The only other explanation would be that this is a mix of versions of a VM which has been previously backed up, restored, reverted, snapshotted and backed up again etc all without ever wiping obsolete backups.