I have well and truly screwed my stable instance of HA that I have had for years and any help would be greatly appreciated.
I have HomeAssistantOS running in VirtualBox. The day I noticed I had stupidly left a snapshot in place following the last upgrade I did around mid-Feb to go to 2025.2. Luckily I spotted it when I still had ~15GB free on the drive. The snapshot was AFAIK around 80GB so it had a lot of changes to write back into the 100GB VDI disk which of course there wasn’t enough space to do. I did some quick googling and read a post about move the VM to another disk using the Move function in VB. I dug out an old 500GB SSD, plugged it in, moved it over and I was then able to remove the snapshot. Happy days…or so I thought.
Annoyingly I didn’t test the instance at this point. I then did another move to shift it back to the original disk and mid transfer my Server 2019 box screws up. It hadn’t crashed completely but my RDP had gone and I couldn’t log in via the console but the time was still ticking away on the login screen so I knew it hadn’t completely frozen. I decided to leave it be which I went out for an hour. I got back and had to bounce the box. When it came back I could see that the last modified date of the VDI files which was whilst I was out so that seemed to indicate that the move finished all OK. I went to boot up my HA instance and I kept getting an error in VB related to the disk. I removed the VM from VB with keeping all the files and then created a new VM with the disk attached but it’s screwed. This is how the VM disk looked:
But in the snapshot folder it had a vdi file as well:
If I attached both of these disks in Virtual Box Media Manager they show up like this:
Which looks to me like the bd230127 disk is a snapshot (the 3d6a disk has been created since in I have booted up the VM so that is new). If I create a new VM and attach the HomeAssistantOS.vdi disk to it I get a version of HA running 2023.4 which is even more confusing. I would have last been on this version back in May 2023. My config is all old and from around that time as well. This kind of matches up with all these .sav files I found in the folder from a similar timeframe:
I don’t understand why everything has reverted to April 2023 when I have been up to date until before all this happened. How could the HomeAssistantOS.vdi file be from back then? Were changes getting written to another vdi file and if so is that the bd230127 disk I still have?
This is the .vbox file for the VM which references both disks:
The next thing I tried was combined the HomeAssistantOS.vdi and the bd230127 vdi files using the CloneVDI tool. When I attached this disk to a new VM it does not boot:
Whilst I have a config back stored with Nabu Casa I stupidly didn’t realised that was only a config backup and did not include statistics. The thing I am most concerned about losing is all my energy data for the past 5 odd years.
If anyone has any miraculous suggestions that would be amazing although I expect I will be SOL 
or even if you can shed any light on my strange 2023.4 / snapshot behaviour as above.
If anyone has made it this far TIA!
dwarfer16