Backup stuck, no way to restart?

Configuration
1

image
image937×130 6.19 KB

This has been stuck like this for 2 days now.
I thought I’d leave it and see what happens but it hasn’t shifted

So went to restart and it won’t let me until the backup finishes (which I’m confident isn’t going to happen!)

image
image787×398 21.9 KB

It also won’t let me reboot

image
image702×698 38.5 KB

So, how the hell do I get out of this backup cycle and kill that process?
I can understand checking that this is what you want to do, but actively preventing a reboot because an upload is stuck is not logical

2

Have you tried refreshing the browser cache? CTRL-F5 should do it.

3

Yeah, that didn’t work. Eventually got it to restart through the terminal, but you really should be able to a) cancel a backup and b) force a restart through the UI

4

I found have the same problem, its been running for days, finally had time to look and found this post
Was going to reboot the devise but started with this

ha supervisor restart

that fixed it for me, ran another backup and it appears fine

strangely it was only causing problems accessing add-ons, and pushing an update to a device

1 Like
5

I’ve been having this EXACT same issue and it’s been driving me nuts. Restarting the supervisor/OS doesn’t help.

6

Any solution? Inhave the Same Problem

Best regards

7

The same symptoms for me. The nightly backup on June 9th apparently got stuck, the next nightly backup on 10th did not happen, and the history from devices was not recorded before reboot:

image
image1194×799 43.9 KB

My backups are saved locally and to GoogleDrive.

I was not able to reboot from the UI, but was able to

$ ssh -l root homeassistant.local
[core-ssh ~]$ reboot

The processes before reboot looked like this:

[core-ssh ~]$ ps -ef f
PID   USER     TIME  COMMAND
    1 root      0:00 /package/admin/s6/command/s6-svscan -d4 -- /run/service
   17 root      0:00 s6-supervise s6-linux-init-shutdownd
   19 root      0:00 /package/admin/s6-linux-init/command/s6-linux-init-shutdownd -d3 -c /run/s6/basedir -g 3000 -C -B
   26 root      0:00 s6-supervise s6rc-oneshot-runner
   27 root      0:00 s6-supervise s6rc-fdholder
   35 root      0:00 /package/admin/s6/command/s6-ipcserverd -1 -- /package/admin/s6/command/s6-ipcserver-access -v0 -E -l0 -i data/rules -- /package/admin/s6/command/s6-sudod -t 30000 -- /package/admin/s6-rc/command/s6-rc-oneshot-run -l ../.. --
  155 root      0:00 s6-supervise sshd
  157 root      0:00 s6-supervise ttyd
  158 root      0:00 sshd: /usr/sbin/sshd -D -e [listener] 0 of 10-100 startups
  159 root      0:07 ttyd --writable -p 8099 tmux -u new -A -s homeassistant bash -l
  198 root      0:00 {tmux: server} tmux -u new -A -s homeassistant bash -l
  199 root      0:00 bash -l
  304 root      0:00 sshd: root@pts/0
  306 root      0:00 -bash
  319 root      0:00 ps -ef f
8

Same hrere.

9

I have also been having this problem since April. I’ve been running in a guest VM (to avoid issues with power etc), but that seems to not be enough. I have had to force destroy the VM to “reboot”, and the back ups NEVER complete. There hasn’t been a successfully completed back up in almost two months. I’m trying to move to a dedicated RPi5 to see if that helps, but now I’m getting an error 500 from the RPi5 trying to upload the TAR.