Describe the issue you are experiencing
I am experiencing a reproducible issue restoring Home Assistant backups stored on an SMB network share.
The same backup restores successfully when copied to the local Home Assistant backup storage, but fails when restored directly from the SMB backup location.
The restore process starts normally, extracts several folders, stops the Home Assistant container as expected, and then eventually fails with:
Restore <backup_id> error, see supervisor logs
During failed restores the frontend reports:
await_home_assistant_restart
The exact same backup succeeds if I first copy it locally and restore it from there.
This suggests the backup archive itself is valid and the issue appears to be related to restoring directly from the SMB storage.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue
Configure an SMB backup location.
Create a full backup (~16.7 GB).
Leave the backup on the SMB share.
Start a partial restore directly from the SMB backup.
Wait until Home Assistant stops and the restore reaches the restart stage.
Restore fails with "await_home_assistant_restart".
Copy the exact same backup to the local backup storage.
Restore again.
Restore completes successfully.
Anything in the Supervisor logs that might be useful for us?
Partial-Restore <backup-id> start
Restore folder ssl
Restore folder share
Restore <backup-id> starting stage home_assistant
Stopping homeassistant application
Cleaning homeassistant application
...
Restore <backup-id> error, see supervisor logs
System information
System Information
| version |
core-2026.7.4 |
| installation_type |
Home Assistant OS |
| dev |
false |
| hassio |
true |
| docker |
true |
| container_arch |
amd64 |
| user |
root |
| virtualenv |
false |
| python_version |
3.14.6 |
| os_name |
Linux |
| os_version |
6.18.39-haos |
| arch |
x86_64 |
| timezone |
Europe/Prague |
| config_dir |
/config |
Home Assistant Cloud
| logged_in |
false |
| can_reach_cert_server |
ok |
| can_reach_cloud_auth |
ok |
| can_reach_cloud |
ok |
HACS
| GitHub API |
ok |
| GitHub Content |
ok |
| GitHub Web |
ok |
| HACS Data |
ok |
| GitHub API Calls Remaining |
5000 |
| Installed Version |
2.0.5 |
| Stage |
running |
| Available Repositories |
3993 |
| Downloaded Repositories |
81 |
Home Assistant Supervisor
| host_os |
Home Assistant OS 18.2 |
| update_channel |
stable |
| supervisor_version |
supervisor-2026.07.5 |
| agent_version |
1.10.0 |
| docker_version |
29.6.2 |
| disk_total |
428.4 GB |
| disk_used |
58.1 GB |
| nameservers |
192.168.1.1 |
| healthy |
true |
| supported |
true |
| host_connectivity |
true |
| supervisor_connectivity |
true |
| ntp_synchronized |
true |
| virtualization |
kvm |
| board |
ova |
| supervisor_api |
ok |
| version_api |
ok |
| installed_addons |
[Deprecated] DHCP server (1.5.0), Dnsmasq (2.1.0), Duck DNS (2.0.0), Frigate (Full Access) (0.17.2), Git pull (9.0.1), Let's Encrypt (6.4.0), MariaDB (3.0.1), Mosquitto broker (7.1.0), NGINX Home Assistant SSL proxy (4.5.1), Samba share (12.10.0), Studio Code Server (6.0.1), chrony (6.0.1), go2rtc (1.9.14), Zigbee2MQTT (2.13.0-1), SQLite Web (6.0.1), Terminal & SSH (10.3.0), Node-RED (22.0.1) |
Dashboards
| dashboards |
6 |
| resources |
64 |
| views |
42 |
| mode |
storage |
Network Configuration
| adapters |
lo (disabled), enp6s18 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth79c8b0d (disabled), veth53b8870 (disabled), veth7a35400 (disabled), veth5948491 (disabled), veth4780e9e (disabled), veth4989ffd (disabled), veth1497aa7 (disabled), vethee06534 (disabled), veth5906577 (disabled), vethaae3c16 (disabled), vethed18f1e (disabled), veth64b0aff (disabled), veth4f9ebac (disabled), veth096c64a (disabled), veth4e7c392 (disabled), veth4329d22 (disabled) |
| ipv4_addresses |
lo (127.0.0.1/8), enp6s18 (192.168.1.42/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth79c8b0d (), veth53b8870 (), veth7a35400 (), veth5948491 (), veth4780e9e (), veth4989ffd (), veth1497aa7 (), vethee06534 (), veth5906577 (), vethaae3c16 (), vethed18f1e (), veth64b0aff (), veth4f9ebac (), veth096c64a (), veth4e7c392 (), veth4329d22 () |
| ipv6_addresses |
lo (::1/128), enp6s18 (fe80::9fde:c372:11a5:345e/64), hassio (fd0c:ac1e:2100::1/48, fe80::8f8:fff:fe20:1d36/64), docker0 (fdc8:8c6e:d2d9::1/64, fe80::24c0:d7ff:fe37:c397/64), veth79c8b0d (fe80::9850:92ff:fec5:11bc/64), veth53b8870 (fe80::84f1:f8ff:fe92:a2e0/64), veth7a35400 (fe80::bb:11ff:fe50:ec1f/64), veth5948491 (fe80::44e1:17ff:fe98:d553/64), veth4780e9e (fe80::9c53:e7ff:feca:c8b6/64), veth4989ffd (fe80::946d:f7ff:feda:cef4/64), veth1497aa7 (fe80::bc3e:24ff:fe4c:cfdd/64), vethee06534 (fe80::108d:6eff:fe47:928/64), veth5906577 (fe80::90ad:67ff:fe2a:e142/64), vethaae3c16 (fe80::a461:a7ff:feea:c7e0/64), vethed18f1e (fe80::879:2bff:feaa:3ac5/64), veth64b0aff (fe80::f83c:4cff:feb0:d288/64), veth4f9ebac (fe80::a413:bff:fe2e:1ad7/64), veth096c64a (fe80::60fd:65ff:fe92:e23b/64), veth4e7c392 (fe80::98e0:7aff:fe31:561c/64), veth4329d22 (fe80::c842:90ff:fe51:c887/64) |
| announce_addresses |
192.168.1.42, fe80::9fde:c372:11a5:345e |
Recorder
| oldest_recorder_run |
28. marec 2026 ob 12:30 |
| current_recorder_run |
4. avgust 2026 ob 17:16 |
| estimated_db_size |
39548.09 MiB |
| database_engine |
sqlite |
| database_version |
3.53.2 |
Supervisor diagnostics
config_entry-hassio-0ba3b9bfd56446ad3994fe787c5cef9b.json
Additional information
Additional observations:
The same backup archive restores correctly from local storage.
Backup size is approximately 16.7 GB.
Recorder uses SQLite.
SMB share remains reachable during the failed restore.
Samba Share add-on is installed.
Home Assistant OS is running as a VM on Proxmox.
The issue has been reproduced multiple times.
The issue is reproducible with different backups, not only with a single backup archive.
Describe the issue you are experiencing
I am experiencing a reproducible issue restoring Home Assistant backups stored on an SMB network share.
The same backup restores successfully when copied to the local Home Assistant backup storage, but fails when restored directly from the SMB backup location.
The restore process starts normally, extracts several folders, stops the Home Assistant container as expected, and then eventually fails with:
Restore <backup_id> error, see supervisor logs
During failed restores the frontend reports:
await_home_assistant_restart
The exact same backup succeeds if I first copy it locally and restore it from there.
This suggests the backup archive itself is valid and the issue appears to be related to restoring directly from the SMB storage.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue
Configure an SMB backup location.
Create a full backup (~16.7 GB).
Leave the backup on the SMB share.
Start a partial restore directly from the SMB backup.
Wait until Home Assistant stops and the restore reaches the restart stage.
Restore fails with "await_home_assistant_restart".
Copy the exact same backup to the local backup storage.
Restore again.
Restore completes successfully.
Anything in the Supervisor logs that might be useful for us?
System information
System Information
Home Assistant Cloud
HACS
Home Assistant Supervisor
Dashboards
Network Configuration
Recorder
Supervisor diagnostics
config_entry-hassio-0ba3b9bfd56446ad3994fe787c5cef9b.json
Additional information
Additional observations:
The same backup archive restores correctly from local storage.
Backup size is approximately 16.7 GB.
Recorder uses SQLite.
SMB share remains reachable during the failed restore.
Samba Share add-on is installed.
Home Assistant OS is running as a VM on Proxmox.
The issue has been reproduced multiple times.
The issue is reproducible with different backups, not only with a single backup archive.