operating-system VS borgmatic

https://github.com/home-assistant/operating-system/pull/3248

BTW found exact same issue with homeassistant browsing the internet; Add support for Intel GMAC Ethernet controller (#2589) (#2593) · home-assistant/operating-system@9ca836f (github.com)

HAOS (https://github.com/home-assistant/operating-system) is not "vanilla" linux, and I have somewhat little experience of linux, although using raspberry-based systems (Domoticz, Pihole, etc) and basic usage of unix mainframes since early 90s. But the question I could not find answer for by googling is, could I use HAOS to farm chia as well, or is it too much optimized towards HA usage to reasonably serve as a chia farming computer too?

The main issue with the 3A+ is the 512MB of RAM. Combined with only having one USB port and no Ethernet, I would not advise using a pi3A+ as a sustainable foundation for HA.

Home assistant was the last thing I had running as a VM, but recently switched over to running it in a LXC container with their ContainerOS (i think that's what they call it). I would say don't do it (at least not yet), and go with their full OS in a VM (dl link to correct KVM/qcow2 version). I say don't start with HomeAssistantContainer b/c you lose Supervisor and the add-on store, and it's a bit less straighforward to get installed.

One thing to notice, I have been able to successfully boot Home Assistant OS Generic x86-64 https://github.com/home-assistant/operating-system which is using kernel 5.15+ and I don't know why I am able to boot HAOS (maybe they are using uncompressed kernel?), but not other general or special Linux distributions.

Raspberry Pi 4 64-bit

hass.io builds the whole gamut of images. There's a list at the bottom of the github page https://github.com/home-assistant/operating-system/releases/tag/8.0.rc2

- for important files, a separate box where I have borgmatic [1] in deduplication mode installed; this is updated once in a while

Just curious: Do you have any reason to believe that such a data corruption bug is likely in ZFS? It seems like saying that ext4 could have a bug and you should also store stuff on NTFS, just in case (which I think does not make sense..).

[1]: https://github.com/borgmatic-collective/borgmatic

Not really dumb. I do use them too but with Borgbackup on the top (since they support it natively).

I found Borgmatic ( https://torsion.org/borgmatic/ ) to be the best way to run my backups. It takes care of everything from pruning to verifying the checksum etc... and it integrates with some monitoring (like cronitor).

So Borgmatic + rsync.net is the best combo

For backups I use Borg myself. If you need a GUI, you can use Vorta or Pika. With borgmatic, there is also a wrapper that extends the range of functions of Borg.

Furthermore, Borgmatic is a wrapper for Borg that extends or improves the range of functions.

For those of you not familiar, borgmatic is a very convenient tool which runs as a wrapper around borg.

I recommend Borg and Borgmatic. Automated, easy to setup, capable of notifying you if anything happens, deduplication and compression makes backups smaller, etc.

To add to this, Borg backup can be a little daunting to configure. There is a wrapper script called Borgmatic that distills it down to a single yaml config file. There are also some cloud hosts like BorgBase and rsync.net with native Borg support.