virtualbox.org

Help, not sure exactly how this happened. Last night I needed to upgrade Nextcloud running on a Ubuntu 18.04 Server VM (Ubuntu 16.04 Host machine). I took a snapshot in case the upgrade went sideways but the upgrade was fine, no issues. Normally I then delete my snapshot but I didn't think to do that this time. Then I needed to do some maintenance work on the raid 1 array that all my VMs are running on, basically just fstab and mount point tweaks. Somehow, and I have literally no clue how, the snapshot went missing and now I'm unable to start the vdi. All data is backed up hourly, including right before this issue, so if I can just get the vdi to run, I can restore any missing data. Is there ANY way to headfake the vdi so I can get it to start?

Virtual Media Manager is expecting:

Share.vdi {50f60500-d627-4ef9-b876-725fab93dfa4} Virtual Size 50.29 GB Actual Size 50.29 GB
> {8a1846f0-45cc-4284-a636-0491bd8a198c}.vdi Virtual Size 50.29 GB Actual Size 2.00 MB

This is probably a stupid question but is it possible to take a snapshot from another VM and change the UUID so it matches the missing snapshot?

I could rebuild the entire VM and restore the databases and data but I'm really hoping to avoid that if at all possible.

Thanks!

***Update - I located this link that suggests to simply remove the offending snapshot from Virtual Media Manager: https://www.evagabond.me/2015/03/solved ... ot-in.html

I tried this and my VM is again running, although with missing data which I fortunately am able to restore. My question now is, do I need to worry about anything by deleting the snapshot such as a stability issue, etc? Or is restoring the missing data the only thing I need to consider?

Glad you kept up the hunt and found a solution! And kudos for having backups!

If neither the VM itself nor the disk file in Virtual Media Manager shows evidence of a snapshot, then you should be OK. Taking backups of the whole VM's files is a good idea.