The OTA update is trying to connect to https://github.com/home-assistant/operating-system/releases/download/6.0/hassos_ova-6.0.raucb
But the filename on Github is https://github.com/home-assistant/operating-system/releases/download/6.0/haos_ova-6.0.raucb
…hassos… vs …haos…
21-06-11 12:12:33 INFO (MainThread) [supervisor.hassos] Fetch OTA update from https://github.com/home-assistant/operating-system/releases/download/6.0/hassos_ova-6.0.raucb
21-06-11 12:12:34 ERROR (MainThread) [supervisor.hassos] Error raise form OTA Webserver: 404
21-06-11 12:17:28 INFO (MainThread) [supervisor.hassos] Fetch OTA update from https://github.com/home-assistant/operating-system/releases/download/6.0/hassos_ova-6.0.raucb
21-06-11 12:17:28 ERROR (MainThread) [supervisor.hassos] Error raise form OTA Webserver: 404
Edit:
After a “supervisor reload” it seems te work
A full system reboot sorted it for me, so I’d say the Supervisor was the issue. 
Right, ha supervisor reload should solve the issue
I have a notification about updating to OS6 but when i try to update i get a message saying i’m already on OS6, yet when i reboot etc i still get the update pending notification.
Has anyone got any suggestions ?
Thanks in advance
Home assistant didn’t restart after that OS update, (RPI3B) the USB HDD spins a few seconds at start then stops.
I then tried :
21-06-11 15:57:10 INFO (SyncWorker_4) [supervisor.docker.interface] Updating image homeassistant/raspberrypi3-homeassistant:landingpage to homeassistant/raspberrypi3-homeassistant:2021.6.3
21-06-11 15:57:10 INFO (SyncWorker_4) [supervisor.docker.interface] Downloading docker image homeassistant/raspberrypi3-homeassistant with tag 2021.6.3.
21-06-11 15:58:11 ERROR (SyncWorker_4) [supervisor.docker.interface] Can't install homeassistant/raspberrypi3-homeassistant:2021.6.3: 404 Client Error for http+docker://localhost/v1.41/images/homeassistant/raspberrypi3-homeassistant:2021.6.3/json: Not Found ("no such image: homeassistant/raspberrypi3-homeassistant:2021.6.3: No such image: homeassistant/raspberrypi3-homeassistant:2021.6.3")
21-06-11 15:58:11 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
- clean SD card install OS 6 + backup restore then thought maybe the USB HUB was the problem so I then :
- plugged the SSD with OS 6 64bit straight to the USB port of the RPI3B and everything went fantastic, restored backup and all is now fine !
It seems to be a known problem that upgrading a Odroid (like HA Blue) result in the computer not rebooting.
It seems the fix in that case is wait long enough to be sure the installation of the upgrade is done (like 10-15 minutes) and then power cycle the machine.
I think that might also impact some Raspberry Pis. I just did my upgrade and after way longer than I expected it to be back online. I went and turned on the screen. It was just black. No LEDs flashing on the Pi so thought what the hell, I have a backup and power cycled. It started up fine and is now running 6.0 
The annoying thing is, I didn’t have any trouble updating my test install LOL only when I did it on the production box 
Wish I’d read this before updating as it’s the first live OS update I’ve done running on a Pi. Saw black screen with no lights or Ethernet and power cycled. I think I’ve probably borked the update now? At least I made a backup first.
mine doesn’t come back online either. I’m using an SSD. Is it somehow possible to save/recover the data from my SSD so I don’t have to start over again?
Impressed with how robust the update is. Left it turned on for another hour or so and power cycled and it’s up again
Edit
Having said that after checking it’s still on 5.12 so failed bit didn’t kill my install…
If you have an issue with updating continue trying to boot a few times. It should fall back to the previous OS version after the third boot.
Same here, didn’t boot up after pressing Update. Power cycled, waiting now. Rpi4. Glad I have the HA Pi on a cloud-based Tuya plug so I can power cycle remotely.
Edit: the update was successful, it just didn’t boot back up afterwards.
The migration went smoothly for me, i.e. no manual reboots.
Has anyone noticed any performance changes after OS migration from 5.12 to 6.0. I am running Rpi4 4GB 64 bit booting off SSD.
Under 5.12 opening an addon log file like ESPHome was pretty well instantaneous, and swap file does not change ie stays close to 0 mB. Total memory usage does really move much around sitting at about 50%.
Under 6.0 opening an addon log file like ESPhome takes about 12 - 15 seconds, and swap file jumped from 200MB to 400MB. Total memory usage is the same and does really move much and sits around 50%. CPU usage spikes a bit, but is under 40%. Opening a couple more logs, and swap file is now up to 750MB
after update mine wont boot back up and I have tried rebooting my VM more than three times. Any ideas?
Mine is stuck too. I’m running on a Virtual Machine and upgraded from HassOS 5.x to 6.0 - it just sits at a shell command prompt and looking at the VM, it isn’t doing much in terms of CPU time (ie., don’t think it is loading up Home Assistant)
Here’s a video of it booting up as well.
Any thoughts on what to do next? Of course, did the upgrade without having a full VM backup from about 4 weeks ago.
I’ve done a lot of NodeRED and other config since then, so even if it isn’t bootable, is there a way to access the config files from this point?
Upgrade went smooth so far.
But I discovered 2 things:
Supervisor system section tells me it is a “Development” build. Is this just correct?
The protocol log of each add-on needs a long time to load (~10-15 seconds). This also affects the logging entries for supervisor system (~20 seconds).
At least for the add-on section this sounds like the reporting from @brucek1642
1 reply
Thanks, it’s ok, I just went back to the month old snapshot…
This is what I get every time before it reboots. Any way to save my data or repair this?
here’s a video of the full log: Imgur: The magic of the Internet
1 reply
My VM install updated without any issues. Only took a few minutes too.
Same problem for me xu4 with external data partition. First time attempt to upgrade, it shutdown and never rebooted. After power cycle it was still on 6.0rc3. Retried install and second attempt worked.
Fwiw, the upgrade from 5.13 to 6.0rc3 went smoothly.
I have run into that issue with my virtual machine. To fix it, I remove the virtual drive from the VM, delete the VM, then create a new one with the same virtual drive. Takes about 5 mins to do and it is back up and running.
Then its likely just logical corruption
Update went smooth and rather quickly, didn´t expect that, +1 for this experience.
Next to mentioned “Development build” Home Assistant OS Release 6 - #22 by kauthmbt I´m just curious bout that change:
Verify Power Supply Size by Mariusthvdb · Pull Request #1393 · home-assistant/operating-system · GitHub
Is it only a message shown during boot process (which I never see cause it´s headless)?
And is it only shown when a SSD is being detected?
I´m planning to switch from SD to SSD and currently use original 3.0 A power supply. There even almost are no 3.5 A or 4.0 A power supplies for Pi 4 in my area.
1 reply
And where is the journal you were instructed to generate?
Mine is stuck too. it will upgrade everything else, I just upgraded to core-2021.6.4, but the OS just freezes. Using a virtual machine as well.
Supervisor system section tells me it is a “Development” build.
Yes, we noticed that as well. I forgot to label it correctly 
Will be fixed in the next stable build.
This looks like a corrupted file system 
The system will fall back to the previous installation after three unsuccessful boot attempt. But it seems that the corruption is on the writable partition which is shared between the fallback and the main OS installation, so it likely won’t help.
Probably the best way forward is a new installation on a new SD card…
I am running rpi4 using original 3a power supply with SDD powered off the RPI with no power problems. You just need to do the math on all the peripherals you connect to ensure your external devices do not draw more than 1.2 A
Power Supply - Raspberry Pi Documentation.
After you do the math, you may be ok, if not you can always go with a powered USB hub.
In my case, sata ssd 700mA + USB2sata adapter 100 mA + Insteon PLM 0mA + Argon One Fan 100 mA
Total = 900 mA
I was able to update (rpi4) without any issues. However, before the upgrade, my CPU was pretty steady at around 20-25% pretty much all the time. All this installation does is manage the Z-Wave and Zigbee devices via a HUSBZB-1 dongle. Since the upgrade, every 5-10 minutes the CPU use briefly spikes to 50-70%.
Which version 5.x have you been running before?
What you are seeing is the EFI shell provided by your virtualization system. It seems that the boot partition got corrupted, and your BIOS isn’t able to load the boot loader.
If you have a recent snapshot, a new installation and restore from a snapshot is probably the best way forward.
What Virtualization System are you using? There are instructions how to recover the boot partitions for some installations, e.g.
If KVM/qcow2, this guide might help: Upgrade to OS 5.9 on OVA caused corrupted EFI folder · Issue #1125 · home-assistant/operating-system · GitHub
Same issue here, hassos on VM (synology) on SSD. I checked disk and it’s fine.
Working again after downgrade:
os update --version 5.13
Does someone knows what this means:
[16:06:24] ERROR: The configuration check did not pass!
[16:06:24] ERROR: See the output below for more details.
Testing configuration at /tmp/config
Fatal error while loading config: [Errno 2] No such file or directory: '/usr/local/lib/python3.8/site-packages/idna-3.2.dist-info/METADATA'
Failed config
General Errors:
- [Errno 2] No such file or directory: '/usr/local/lib/python3.8/site-packages/idna-3.2.dist-info/METADATA'
What do I have to do?
3 replies
I have the same error as well. Though I did a full backup and upgraded to os 6 successfully. Before updating from core core-2021.6.3 to core-2021.6.4 I see this error from the Check Home Assistant configuration (v3.7.1).
[20:00:33] INFO: Checking your configuration against this version...
[20:01:50] ERROR: The configuration check did not pass!
[20:01:50] ERROR: See the output below for more details.
Testing configuration at /tmp/config
Fatal error while loading config: [Errno 2] No such file or directory: '/usr/local/lib/python3.8/site-packages/idna-3.2.dist-info/METADATA'
Failed config
General Errors:
- [Errno 2] No such file or directory: '/usr/local/lib/python3.8/site-packages/idna-3.2.dist-info/METADATA'
Successful config (partial)
[20:01:50] INFO: The full output has been written to /share/check_config.txt
I then checked the /share/check_config.txt and this is what it says:
INFO:homeassistant.util.package:Attempting install of colorlog==5.0.1
[01mTesting configuration at /tmp/config[0m
INFO:homeassistant.util.package:Attempting install of mutagen==1.45.1
INFO:homeassistant.util.package:Attempting install of aiohttp_cors==0.7.0
INFO:homeassistant.util.package:Attempting install of gTTS==2.2.2
INFO:homeassistant.util.package:Attempting install of async-upnp-client==0.18.0
INFO:homeassistant.util.package:Attempting install of netdisco==2.8.3
[31mFatal error while loading config: [0m [Errno 2] No such file or directory: '/usr/local/lib/python3.8/site-packages/idna-3.2.dist-info/METADATA'
[01;37mFailed config [0m
[01;31mGeneral Errors: [0m [31m [31m
- [Errno 2] No such file or directory: '/usr/local/lib/python3.8/site-packages/idna-3.2.dist-info/METADATA'
[0m
[01;37mSuccessful config (partial) [0m
Figured I’d wait to see what others say, or another version comes out, before upgrading core.
2 replies
You’d lose the autofill entities of home assistant showing up in Node Red, wouldn’t you?
1 reply
Not that i have noticed.
There is a homeassistant contrib
I dont know if this is the correct one. Just the first google hit. I can check later today
Update: Yep, this is the one I loaded into NR. And it just autofills.
Just updated my Rpi4 4GB running off a Sabrent external enclosure and Crucial 120GB SSD. No issues at all so far. Dropped 5 pings as it rebooted then HA started up shortly afterwards. Whole process took less than 10 minutes 
My VM is running on a QNAP NAS in the Virtualisation Station is actually QEMU.
I started to figure out that it was a problem with the VM image and not Home Assistant, so snapshots wouldn’t have saved me that much, so @agners you are spot on there.
I then switched to trying to recover configuration files (including snapshots) from the disk image itself. After trying a few recover apps, I found that DMDE was able to open the disk image and pull out files from the image - complete the full file names and the directory structure in tact, so worth the purchase price.
I was able to pull out snapshots of individual add-ons, HACs components, my NodeRED config and other stuff, installing from a new VM image of Home Assistant OS Release 6.
Everything is now pretty much back to normal.
I’m going to do more scheduled backups from now on, complete with more image backups of the VM 
Thanks @quadhammer @basesnow @nontijt and @agners for your tips
No problem.
Last night I did exactly the same thing.
I had a slightly older backup of the HA VM. Put that one back. Created a full snapshot and copy it.
Then I downloaded a new .qcow2 image from the download page you mentioned. Installed the new image using the same MAC adres etc. start it, install samba addon, past the full snapshot in the folder back again, restore and 1+ hours later it was back up running again.
I am using proxmox (type 1 hypervisor). HA OS in a VM. I have a separate container for mqtt, node red, zwaveJS2mqtt. So basically the HA is only the frontend, which works perfectly for the past couple of months. fast as hell.
The only question I still have, why/what is the cause of the problem in the first place. ?
2 replies
Ghehehe… agreed… Home Assistant is my hobby. a SERIOUS hobby ofc. 
I’m using Oracle VM virtual box, which uses a different image, and I’m having the same problem, so it can’t be just a problem with the KVM virtual machine.
I was using a ‘headless start’, so I couldn’t see this error in the background. Using the virtual boxmanager, right clicking on the OS and picking ‘show’, brought out the window above, and then when I pressed control D to continue, it updated to OS release 6.
Not sure what those other two errors are, or if they are related, but I hope that helps someone, even if it just lets you get into the snapshots.
Edit: I ended up installing the haos_ova-6.0.vdi from scratch. It was pretty painless, the only caveat was that you had to make a fake/temporary account when first loading home assistant, before you could restore the snapshot. It was good that you didn’t need to install Samba, (there’s an option to upload your snapshot), but you still need to make an account first which is a bit stupid.
Nice to have it auto loading again on start-up.
been getting Error 404 on 120gb ssd with Raspberry PI 4 since update. Tried a fresh install and now getting it on startup, tried downgrading same thing. 
Hi, did you ever figure this out?
I’m trying to get my USB Coral accelerator to work on HaOS to support Frigate but without any success…
Hello! I’m one of the people who had stability problems running releases after 5.3 on a Raspberry Pi. I set up a spare Pi with a mirror installation, updated to 6.0, and it ran without issues for a day!
Seems promising to me, since it crashed every night before. I will keep it running for a week or so, and post any new findings.
After updating OS to 6.0, network (WiFi) became extremely slow. Many timeouts in logs - for all services using network connections (even local ones). HA became simply unusable. After downgrading to 5.13, everything started working again. Then I joined beta channel and upgraded to 6.1. No luck - still many timeouts; SSH login, opening Supervisor / HACS tabs etc. takes ages (but finally succeeds). Downgraded again to 5.13, and again everything is working flawlessly… Have no idea how to diagnose, what’s going on with 6.0 in my case…
Raspberry Pi 4 Model B Rev 1.4, 4GB RAM, Core 2021.6.6
Just a positive update: running HASS OS 6.0 for 10 days without any issues so far. Upgrade went smooth, no hickups afterwards. Pi 4 B 8 GB a lil bit overclocked with ethernet connected network on SD card (I bet all the SSD users suffer on HASS OS updates? Couldn´t manage to migrate from SD to SSD yet unfortunately).
Update: Latest HASS OS 6.1 update went flawlessly too.
1 reply
So far, I’ve gone through all the updates smoothly from HassOS 5.0 to the current HaOS 6.0.
Rpi4 8GB boot SSD.
I am in the same situation, I have a USB Coral accelerator and would like to use it with Frigate within HaOS. I have Frigate working but its using my CPUs and would rather use the USB Coral accelerator for object detection.
What is the kernel option or module name for that option?
I deserved that
After update to Home Assistant OS 6.1 the status of my zwave devices changed to Unavailable
I maked changes:
Set manually usb_path: /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 in configuration.yaml
And now see that status is “Ready”
But after the system started - it’s not changed. I can’t on/off devices from UI. Or if I click light button - in UI it’s not changed. Last status was get when system booted:
It’s bug in 6.1 HA OS? How fix?
When I try light to on in UI in OZW_Log.txt I see these lines:
2021-06-24 11:33:07.620 Detail, Node004, Polling: COMMAND_CLASS_SENSOR_MULTILEVEL index = 1 instance = 1 (poll queue has 0 messages)
2021-06-24 11:33:07.620 Detail, Node004, Queuing (Poll) SensorMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x31, 0x04, 0x25, 0x1f, 0xec
2021-06-24 11:33:07.621 Detail,
2021-06-24 11:33:07.621 Info, Node004, Sending (Poll) message (Callback ID=0x1f, Expected Reply=0x04) - SensorMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x31, 0x04, 0x25, 0x1f, 0xec
2021-06-24 11:33:08.622 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2021-06-24 11:33:08.623 Detail, Node004, Removing current message
2021-06-24 11:33:08.623 Detail, Node004, Notification: Notification - TimeOut
2021-06-24 11:33:31.150 Info, Node011, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Dimming Duration - 5 - 1 - 255
2021-06-24 11:33:31.152 Detail, Node011, Refreshed Value: old value=255, new value=255, type=byte
2021-06-24 11:33:31.152 Detail, Node011, Changes to this value are not verified
2021-06-24 11:33:31.153 Detail, Node011, Notification: ValueChanged
2021-06-24 11:33:31.155 Info, Node011, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 255
2021-06-24 11:33:31.155 Info, Node011, SwitchMultilevel::Set - Setting to level 255
2021-06-24 11:33:31.155 Info, Node011, Duration: Default
2021-06-24 11:33:31.156 Detail, Node011, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Set (Node=11): 0x01, 0x0f, 0x00, 0x13, 0x0b, 0x08, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x01, 0xff, 0xff, 0x25, 0x20, 0xaf
2021-06-24 11:33:31.156 Detail, Node011, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Get (Node=11): 0x01, 0x0d, 0x00, 0x13, 0x0b, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x02, 0x25, 0x21, 0xa1
2021-06-24 11:33:31.170 Detail,
2021-06-24 11:33:31.170 Info, Node011, Sending (Send) message (Callback ID=0x20, Expected Reply=0x13) - MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Set (Node=11): 0x01, 0x0f, 0x00, 0x13, 0x0b, 0x08, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x01, 0xff, 0xff, 0x25, 0x20, 0xaf
2021-06-24 11:33:32.171 Error, Node011, ERROR: Dropping command, expected response not received after 1 attempt(s)
2021-06-24 11:33:32.171 Detail, Node011, Removing current message
2021-06-24 11:33:32.171 Detail, Node011, Notification: Notification - TimeOut
2021-06-24 11:33:32.175 Detail,
2021-06-24 11:33:32.175 Info, Node011, Sending (Send) message (Callback ID=0x21, Expected Reply=0x04) - MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Get (Node=11): 0x01, 0x0d, 0x00, 0x13, 0x0b, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x02, 0x25, 0x21, 0xa1
2021-06-24 11:33:33.175 Error, Node011, ERROR: Dropping command, expected response not received after 1 attempt(s)
2021-06-24 11:33:33.176 Detail, Node011, Removing current message
2021-06-24 11:33:33.176 Detail, Node011, Notification: Notification - TimeOut
Please, help me fix it!
I’ve been running unraid in a VM on Unraid (hassos_ovm-2.12). Is there ever a reason to update the qcow2 file as newer ones become available or is effectively updated internally?
Hi!
I got the same error, and don´n know why… think it has to be some install/uninstall script that caused it, as i never touched that path manually.
Did you solved it and run the upgrade?
Hi all,
just to share my experience as I had to rollback to 5.13.
[Raspberry pi 4]
After the update to the 6 all the add-ons pages where extremely slow to load (+40s). The supervisor page included. i could not find any specific errors in the logs. Inspecting the page i’ve realized the the entrypoint.<code>.js was taking ~36s to load. As well all the web assesst. For example the favicon.ico was loading in 5s. Basically every web assest was taking much longer loading time than required.
All the other pages ( history, map, logbook ) were loading fine.
I did try both the core rollback and the os rollback from the cli, but both were failing because the download was hitting a timeout and could not finish.
Error: Can't fetch OTA update from https://github.com/home-assistant/operating-system/releases/download/5.13/hassos_rpi4-5.13.raucb: Response payload is not completed. Even additional dns in coreDns did not solve the issue.
The only solution was to download the previous release version of the os in a usb storage key and bootstrap it physically form the device.
The bootstrap failed and i had to use the command systemctl restart hassos-config which finally rolled back the OS and fixed all the problems.
Hopefully someone else will be able to find specific logs for this issue so it can be fixed in the next releases.
David.
Thanks for the info!
Sorry for the late reply as I was on vacation. In my instance I believe it sorted itself after a few days. I think the Check Home Assistant configuration add-on auto updated and I believe that resolved the issue with the check. No manual actions required on my part.
Cheers 
Hi!
No problem at all, i found that it was the configuration checker itself that is (or was) buggy.
It was confirmed by the developers them selves 
After some cleanup of a couple of deprecated things, upgrade to 2021.6.6 went fine.