While attempting to upgrade my HA Yellow to CM5 from CM4, I ended up overwriting the SSD and wiping out my installation. Luckily, so I thought, I made an image of the SSD prior to commiting the overwrite. Unluckily Macrium Reflect has a security issue with their driver when trying to open the image as a drive. I have now acquired a new SSD and have successfully reimaged that drive.
Unfortunately it does not boot in the Yellow. Red and green lights are lit and stay lit.
Do I need to somehow make the SSD bootable? I have a Linux computer available if that is required. The newly imaged SSD does not mount on Windows although it does appear in Disk Manager. Under Linux it does mount and the files seem to be intact.
My alternative is to copy the files onto the current SSD. Are there caveats to simply replacing the Home Assistant folder wholesale? This would restore all of the device yaml files and also the integrations, HACS files, and history database. The history database is obviously obsolete but that would simply mean a gap in the data.
The system is currently running on the CM4 and I expect to try the CM5 upgrade as soon as I build up the courage. Is there a reason that the upgrade path necessarily overwrites the SSD? Restoring a backup is the logical way to restore the installation but previous attempts to do that resulted in an error that involved the incorrect version of the OS.
Make sure you get the ENTIRE config folder including any hidden folders. (or you’ll miss the registry dB and a bunch of important stuff.) if you were on haos your addons are in a separate folder. You’ll want them too.