yes but you want to wait a bit, as apparently it has a bug that needs to be solved first.
there is a log flood, not exactly sure from the top of my head which component…
check the OS GitHub for development
I also had AdGuard running. The migration came to a stand-still. All I had to do was change the DNS settings in my router, did a hard reboot of HA, then it brought up the migration screen, took about 10 minutes and I was good to go.
Thanks for the reply. Reading the discussions about it in the github i read also that after installation of the update i am not forced to do the migration but it’s necessary only for a fresh install of the HAOS. Is it true or am i forced to do that ?
Are you now asking me if you read the release notes ? Because it is the way it says there…
1 Like
you should mark this as answer 
otherwise this thread will keep re-iterating
1 Like
Am I right in thinking the v17 update has been withdrawn? I can’t see it in my settings screen any longer.
I don’t think its withdrawn, it’s live on Github at least. Release Home Assistant OS 17.0 · home-assistant/operating-system · GitHub
Still available, I only just updated an hour ago. The only reason I landed on this thread was because I wanted to check nobody ran into any issues before migrating the storage driver.
I just wanted to say that it went entirely smoothly for me and only seemed to reboot once. It took perhaps 2 minutes, I’m wondering if just because my internet is fast if that’s the main dependency speed wise.
bare metal HAOS on a SFF PC here, two machines (home and office) - both went smoothly, just took some minutes. All fine
1 Like
All done!
My advice: when you restart supervisor after running the command, be patient. Don’t panic.
Running HA OS on a N5105 mini pc, 1 GBit internet (fibre connection). Just done the update and migration, was running like a charm.
Same here, doing management on three ha installations, my own with about 20 add-ons.
All three running on bare metal Intel NUC’s, up and running within 3-4 minutes, no issues at all.
Do any of you notice a significant usage of disk space after this migration? Looking at the size of my backups (entire VM via Proxmox), they have increased from around 15Gb to 19Gb.
Yes I can confirm seeing a relative similar increase in disk usage.
This is probably linked to this.
2 Likes
Interesting. Always nice to see the release notes only mention the positives, but not the negatives of a new feature….20-30% storage increase is not insignificant….
Mine took about 40 minutes before I could run the ha docker info command successfully, and containers began to start again (I rebooted a few minutes after running the migrate command). They kept restarting though, and nothing was actually usable. I then performed another reboot, and it appears to be starting containers and the web UI then shows the “Preparing Home Assistant” screen. This process took maybe 10-15 min, then everything was all good.
It was dog-slow even on a decent server with good storage, but it got there in the end.
On HAOS, you can watch journalctl -xf -n10 on the host (advanced terminal/ssh if you have it, etc) and get a bit of an idea of what is going on - otherwise it’s tough to know. This is similar if not the same output shown in the Preparing Home Assistant screen under show details.
My setup has a few addons and a few years of data, I was clocking in at 34gb storage used and have a 100gb virtual disk allocated to the VM.
1 Like
I can now confirm - my extra usage is NOT being consumed by the new log spam bug introduced in version 2.2.0, as I checked my journals.
Rather it is down to the new image storage system of containerd, see here. Also see this - on the same.
2 Likes
HAOS 17 is running fine but every single update consumes another 500mb or so, started at 10gb system, now 14.6gb. Updating matter server yesterday took system from 13.8 to 14.2gb. Today ssh addon update took it from 14.2gb to 14.6gb.
No I don’t back up the old version, my database is not growing and I have tried all possible docker prunes etc. and the logs are maxed out at 500mb.
The used system space just sits steady until something is updated and then more space is permanently gone.
I will be forced to revert to Haos 16 if this continues unabated.
Me too. Each add-on update now makes the disk used size increase by 200-400MB …
Unistalling an add-on makes it decrease by the last 200-400MB, but not all the previous increasings …
Yes, same.
Updating an add-on 3 times might go up say 400mb each time for a total of 1.2gb but uninstalling the add-on only removes the last 400mb. It’s like all the previous versions are still there there and uninstalling or docker prune etc does not clear the space.
I also tried trim, all the possible docker prune commands but the space won’t come back.
Lastly docker reports a lot of reclaimable space.