HA Broken, Unable to restore from backup

Installation
1

dear, hi!
I got my installation broken (5-years lifespan) after attempting to update to 2025.3.1.
not better specified unknown error, tried to restore the latest full backup via CLI, unsuccessful…it stops with not better specified unknown error.
now:

How can I better follow up better on logs via CLI? it shoots all the lines without allowing me to read the backward ones…this will allow me to post the log and make better troubleshooting

Any hint to tell me on how to lose 5 years of projects and improvemenets even if I have a full backup to start with?

please help me, for me and my family is painful without HA.

2

Start by explaining what’s wrong, “broken” is not saying much. Does it start up and then crash? Does it not boot? Have you tried booting in safe mode? How are you running HA?

3

Since you say you have backup the easiest and fastest way is:

  • download / copy your backup to a safe place
  • format sd card, ssd … wherever your HA is installed
  • install fresh HA instance
  • restore from your backup.
4

Hi there.
Broken means that even if from the CLI all is set and right, I could not access it anymore neither from LAN or NABU or DuckDNS.
tried to boot in safe mode, without success. there is something gone in core but I could not figure it out.
HA is running in a VMware ESXi VM.

5

try from the esxi console:

ha supervisor repair
ha core rebuild

I can also for the future recommend running snapshot based backups if you are running esxi, makes restores a lot easier. Veeam has a free community edition.

6

Please help us! :pray:

Did you try to update your 5 year old HA to the latest 2025.3.1 :question:

You only have a real :registered: backup if you are able to restore it :warning:
Did you ever try/test this on a different/new HA install? :thinking:

7

I’m trying now the fix.
If I will not come out of this s*it I would move to a proxmox on NUC installation.
the things stopping me are the devices management, how to pass a port to a proxmox VM, how to manage the space of proxmox VM, because I’m not that knowledgeable on linux management.
if you have something to advice a bit more “UI” instead than “CLI” it’s really appreciated.

in the meantime, supervisor repaired as per response from CLI
core in progress.

8

you’re definitely right.
the backup is valid only if you test it.
I tried to restore it into another freshly created VM but without success. as I wrote, I san not knowledgeable enought to retrieve all the logs from CLI, so I cannot point what went wrong.
I tried to update to 2025.3.1 when all this happened, yes.

9

unfortunately core was not able to rebuild.

image
image356×206 5.26 KB

image
image864×710 29.6 KB

what can I check further?

10

I don’t think changing the hypervisor would solve this problem (and it’s probably not caused by the hypervisor either), but up to you.

11

you didn’t get me.
I’m assuming to make everything from scratch an try to take out something in yaml from the backup of the old one…any hint on the rebuild?

12

See if you can find anything here

13

From your comments it does not seem like you should be running any VM. Running HAOS on a basic machine, with a new SSD, is simplest.

Good luck.

14

From what version did you start the update? Didn’t you update the last 5 years? :eyes:

15

no no don’t get me wrong…
my whole experience with HA is 5 years old! :slight_smile:
of course I always updated everything everytime!
and @dzmiller why should I discard the possibility of new learnings? think I could learn new skills also in VM management in proxmox, since in ESXi I think I know enough to manage a VM.

16

digging a bit in other’s cases, I found core container not started.
how might I understand if it’s a fail or simply that I must pull up the container?

image
image550×188 1.69 KB