Is this with the storage driver change or without ?
If memory serves me correctly, I remember seeing a comment (either here, Reddit, or on GitHub) regarding the use of this version of snapshotter having a big bug regarding this. Someone else commented afterward confirming it, but stating it’s already fixed in later versions. We’ll just have to wait for the next OS update.
v17.1 has a release candidate now if anyone wanted to have a look…
2 Likes
Thanks for sharing, had the same issue, saved me!
This is after the storage driver update, and is not the log spamming bug as the logs are limited to 500mb.
thanks, so i will wait with the convert till 17.1 release and recheck the release notes 
Just updated to 17.0 and the storage update afterwards (backup of my Proxmox VM both times). Ran through fine, above picture with “Host information reload completed” also took a bit, but continued without a problem. Took maybe 10min at that point? Saw lots of write access on the Proxmox stats during that time.
I think I have a similar problem. I also performed the migration, and my storage space keeps decreasing. I tried using AI to solve the problem, but I haven’t made any progress.
All I could find out is that the Docker folder is taking up 22.1 GB and the Supervisor folder 11.5 GB; those are the largest amounts.
And that the Snapshot folder within the Docker folder is very large.
Sharing my experience if it helps anyone else.
on a RPi4 it took almost one hour, during which I had the obvious fear the upgrade the whole operation failed.
Instread it was just painfully slow.
2 noticeable issues:
homeassistant container came back relatively quickly but it was set in a “first installation” phase. When checking the logs there were TONS or failure to access sentry.io, something I do block at DNS level. Followed by the communication with supervisor that was keep reporting being in the setup phase.
I have unlcled sentry.io on ADGuard for Homeassistant but that didn’t solve it.
I’ve decided then to restart Supervisor container (hoping not to break anything)
Supervisor came back, and resumed its work but it was still extremely slow, showing entries like:
2026-02-02 13:31:24.044 INFO (MainThread) [supervisor.addons.manager] Found 13 installed add-ons
2026-02-02 13:31:24.310 INFO (MainThread) [supervisor.addons.addon] No 5c53de3b_esphome addon Docker image ghcr.io/esphome/esphome-hassio found
2026-02-02 13:31:24.312 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/esphome/esphome-hassio with tag 2026.1.3.
2026-02-02 13:31:24.320 INFO (MainThread) [supervisor.addons.addon] No cebe7a76_hassio_google_drive_backup addon Docker image ghcr.io/sabeechen/hassio-google-drive-backup-aarch64 found
2026-02-02 13:31:24.322 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/sabeechen/hassio-google-drive-backup-aarch64 with tag 0.112.1.
2026-02-02 13:31:24.328 INFO (MainThread) [supervisor.addons.addon] No core_mosquitto addon Docker image homeassistant/aarch64-addon-mosquitto found
2026-02-02 13:31:24.329 INFO (MainThread) [supervisor.docker.interface] Downloading docker image homeassistant/aarch64-addon-mosquitto with tag 6.5.2.
2026-02-02 13:31:24.333 INFO (MainThread) [supervisor.addons.addon] No 45df7312_zigbee2mqtt addon Docker image ghcr.io/zigbee2mqtt/zigbee2mqtt-aarch64 found
2026-02-02 13:31:24.335 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/zigbee2mqtt/zigbee2mqtt-aarch64 with tag 2.7.2-1.
2026-02-02 13:31:24.342 INFO (MainThread) [supervisor.addons.addon] No core_matter_server addon Docker image homeassistant/aarch64-addon-matter-server found
2026-02-02 13:31:24.344 INFO (MainThread) [supervisor.docker.interface] Downloading docker image homeassistant/aarch64-addon-matter-server with tag 8.2.2.
2026-02-02 13:31:24.347 INFO (MainThread) [supervisor.addons.addon] No a0d7b954_ssh addon Docker image ghcr.io/hassio-addons/ssh found
2026-02-02 13:31:24.348 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/hassio-addons/ssh with tag 23.0.0.
2026-02-02 13:31:24.351 INFO (MainThread) [supervisor.addons.addon] No 491eb00d_hamh addon Docker image ghcr.io/t0bst4r/home-assistant-matter-hub-addon found
2026-02-02 13:31:24.352 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/t0bst4r/home-assistant-matter-hub-addon with tag 3.0.3.
2026-02-02 13:31:24.358 INFO (MainThread) [supervisor.addons.addon] No cc56ba6a_hamh addon Docker image ghcr.io/t0bst4r/home-assistant-matter-hub-addon found
2026-02-02 13:31:24.360 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/t0bst4r/home-assistant-matter-hub-addon with tag 3.0.0-alpha.76.
2026-02-02 13:31:24.364 INFO (MainThread) [supervisor.addons.addon] No a0d7b954_uptime-kuma addon Docker image ghcr.io/hassio-addons/uptime-kuma/aarch64 found
2026-02-02 13:31:24.365 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/hassio-addons/uptime-kuma/aarch64 with tag 0.15.0.
2026-02-02 13:31:24.371 INFO (MainThread) [supervisor.addons.addon] No db21ed7f_qbittorrent addon Docker image ghcr.io/alexbelgium/qbittorrent-aarch64 found
2026-02-02 13:31:24.372 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/alexbelgium/qbittorrent-aarch64 with tag 5.1.2-22.
2026-02-02 13:31:24.382 INFO (MainThread) [supervisor.addons.addon] No a0d7b954_influxdb addon Docker image ghcr.io/hassio-addons/influxdb/aarch64 found
2026-02-02 13:31:24.385 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/hassio-addons/influxdb/aarch64 with tag 5.0.2.
2026-02-02 13:31:24.394 INFO (MainThread) [supervisor.addons.addon] No 246dd49f_matterbridge addon Docker image 246dd49f/aarch64-addon-matterbridge found
2026-02-02 13:31:24.398 INFO (MainThread) [supervisor.addons.addon] No b9845f46_govee2mqtt addon Docker image ghcr.io/wez/govee2mqtt-aarch64 found
2026-02-02 13:31:24.401 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/wez/govee2mqtt-aarch64 with tag 2025.11.25-60a39bcc.
2026-02-02 13:31:24.436 INFO (MainThread) [supervisor.docker.addon] Starting build for 246dd49f/aarch64-addon-matterbridge:2.0.7
2026-02-02 13:31:24.450 INFO (SyncWorker_3) [supervisor.docker.manager] Running command '['docker', 'buildx', 'build', '.', '--tag', '246dd49f/aarch64-addon-matterbridge:2.0.7', '--file', 'Dockerfile', '--platform', 'linux/arm64', '--pull', '--label', 'io.hass.version=2.0.7', '--label', 'io.hass.arch=aarch64', '--label', 'io.hass.type=addon', '--label', 'io.hass.name=Matterbridge Home Assistant Add-on', '--label', 'io.hass.description=Official Matterbridge Home Assistant Add-on', '--label', 'io.hass.url=https://github.com/Luligu/matterbridge-home-assistant-addon', '--build-arg', 'BUILD_FROM=ghcr.io/home-assistant/aarch64-base:latest', '--build-arg', 'BUILD_VERSION=2.0.7', '--build-arg', 'BUILD_ARCH=aarch64']' on docker.io/library/docker:29.1.3-cli
and a lot of warnings regarding threads giving up trying to download some of those images.
It eventually did work, after 40m or so. And apparently the blocker was that docker build command, in the last line, that prevented any other operation from happening. When that did complete (and it took forever), the rest of the upgrade went on the system became operational again.
Good luck and don’t lose hope.
1 Like
so I have an rpi4 4b 64 - updated and well, I am not sure what happened but it never connected to wifi.
After hoping it would find itself and start on its own waiting like an hour… I restarted manually 2x, waiting longer each time(after finding this thread). I then now got out a lan cable… and was relieved that it connected and I was able to setup what was a now mysteriously missing wifi login info - after saving it, it connected and all seems ok again(tbc)
strangely it lost wifi again in the middle of the night!? I again had to plug in a lan cable and once in I found the wifi I setup was gone and had to go in and save once again the wlan connection - nothing like this has ever happened before this update, but I am surprised by this behaviour being impacted by this update.
any ideas?
edit … now into the 2nd 24hr period and it kept the wifi settings … no idea what could have caused it to lose it in the first place, or the 2nd time as I had restarted in between setting it the first time and the 2nd in hopes to avoid any issues.
now a 3rd time … UGH.
opened a seperate post, here:
Do I need to rerun ha docker migrate-storage-driver after recovering Supervisor?
I updated my system to 17.0 and the update itself completed without errors. However, after that my Raspberry Pi 4B started rebooting roughly once every hour for no obvious reason.
While trying to troubleshoot, I ran:
ha docker migrate-storage-driver
Unfortunately, that made things worse. After the command finished, Home Assistant would no longer start.
With help from @trevorstarick, I recovered the system by running:
docker system prune -a
docker pull Package aarch64-hassio-supervisor · GitHub
After a reboot, everything came back up and appears to be working again.
My questions
- Do I need to run
ha docker migrate-storage-driveragain? - How can I verify whether the storage driver migration has already completed successfully?
- Is there a way to confirm I’m on the correct/expected driver now?
I’d like to avoid breaking the installation again, but I also want to be sure the system is in the proper state.
Any guidance would be appreciated.
ps: the output of the below command.
ha docker info
enable_ipv6: null
logging: journald
mtu: null
registries: {}
storage: overlayfs
version: 29.1.3
per posts near top of thread, overlay2 is the old driver, overlayfs is the new one.
so I would expect that the migration is done
1 Like