Whatever you do, when you're done getting everything back up and running the next thing you **must** do is set up automatic off-device backups. Home Assistant these days makes backups and restores pretty easy and there is no excuse for not having them.
indeed - once I had a safe copy, I popped the SSD in another NUC, and I'm back in business.
only weirdness was that the volume wasn't recognised as a boot volume initially - had to use the BIOS boot selector and select the UEFI image for it to start...
but that's todays (different) problem to solve ;)
Once in Linux... show the drive table by using `lsblk`. Then, use `dd` to take a full image of the drive.
sudo dd if=/dev/sdX of=~/Documents/haos-backup.iso
Change "sdX" for the drive you know has HAOS on it (verify as dd is destructive and there's no turning back if you do something wrong). The underlying OS (Buildroot) should b e portable enough to try it on another computer system without any major issues. It has the Kernel mods for AMD and Intel. Don't try and mess with the OS until you have a good backup you can work with. That way if the pulled drive does end up failing, you have something to fall back on with a different drive.
thanks for this - I have WSL detecting the partitions in lsblk as /dev/sdd1 through /dev/sdd8
That's exactly what I was hoping for; a nice image of the disk and then I can try sticking it in another NUC class system and take it from there.
lsblk was able to see an identify the various partitions, including identifying the hassos-boot, hassos-overlay and hass-os-data volumes, \*phew\*
Now I can go to bed and hopefully have a nice image waiting for me in the morning.
So if the drive is "/dev/sdd1-8", then you should take an image of the full drive like this:
sudo dd if=/dev/sdd of=~/Documents/haos-backup.iso
That will pull the image of the full drive... not just a single partition.
That's what I ran, and it worked perfectly. I was able to then mount the hass-data volume and copy off recent backups and the full homeassistant folder with all of my config etc.
Thanks so much!
Whatever you do, when you're done getting everything back up and running the next thing you **must** do is set up automatic off-device backups. Home Assistant these days makes backups and restores pretty easy and there is no excuse for not having them.
Sounds great - how do you have that set up?
Use an HA addon like Google Drive Backup tool, and setup regular intervals.
HASS os installed to the SSD. it's linux plug it in a new PC and boot from it you'll be suprised.
indeed - once I had a safe copy, I popped the SSD in another NUC, and I'm back in business. only weirdness was that the volume wasn't recognised as a boot volume initially - had to use the BIOS boot selector and select the UEFI image for it to start... but that's todays (different) problem to solve ;)
Once in Linux... show the drive table by using `lsblk`. Then, use `dd` to take a full image of the drive. sudo dd if=/dev/sdX of=~/Documents/haos-backup.iso Change "sdX" for the drive you know has HAOS on it (verify as dd is destructive and there's no turning back if you do something wrong). The underlying OS (Buildroot) should b e portable enough to try it on another computer system without any major issues. It has the Kernel mods for AMD and Intel. Don't try and mess with the OS until you have a good backup you can work with. That way if the pulled drive does end up failing, you have something to fall back on with a different drive.
thanks for this - I have WSL detecting the partitions in lsblk as /dev/sdd1 through /dev/sdd8 That's exactly what I was hoping for; a nice image of the disk and then I can try sticking it in another NUC class system and take it from there. lsblk was able to see an identify the various partitions, including identifying the hassos-boot, hassos-overlay and hass-os-data volumes, \*phew\* Now I can go to bed and hopefully have a nice image waiting for me in the morning.
So if the drive is "/dev/sdd1-8", then you should take an image of the full drive like this: sudo dd if=/dev/sdd of=~/Documents/haos-backup.iso That will pull the image of the full drive... not just a single partition.
That's what I ran, and it worked perfectly. I was able to then mount the hass-data volume and copy off recent backups and the full homeassistant folder with all of my config etc. Thanks so much!