Maybe I did something wrong, but my USB boot times are really really slow. I am using a USB 3.0 stick in my USB 3.0 port and no usb ssd or hdd etc
What I Did:
Install latest raspberry pi os on MicroSd and boot it
Update firmware and bootloader to latest September firmware and reboot
Set USB Boot in Raspi-config to the primary boot option and reboot
Flash a USB stick with the latest Homeassistant OS 5.2 64bit
Plug it in, remove the MicroSd and boot
Usb drive boots, but as said before the initial setup took hours and a reboot takes forever after the initial setup.
Do I have to apply any more settings?
I followed the same procedure on a RPi 4 8Gb with SSD drive. And I have the same (minor) problem:
The boot time is extremely long (about 30 minutes).
Beside that the system works flawlessly and is extremely fast! HA restarts are very fast too (they are by no means reboots as one might think.)
So after all I found that I hardly ever reboot and I can ignore the problem for now and hope that the long boot times will disappear with the stable version of HA OS 5.
I had the same problem, took hours to boot on usb3 a liite bit better on usb2. Got a new sata to usb adapter and now my SSD boots faster than a SDcard (homeassistant os 5.2 32-bit)
I was talking about an RPi4 with 8 GB of RAM. AFIAK the 32 bit version of HA OS is not compatible with the 8GB version of the Pi. You have to use the 64 bit version. And I think the long boot time currently is a given with that version.
I have just published a step by step guide to get the 8 GB Pi up and running with HA:
@Jpsy did you try boot using usb2? it boots lightning fast for me. First boot obviously takes a few minutes (depending on internet connection speed) because of downloading docker images.
@Recte what’s wrong with bootrom from 3.9? is it something widely kniwn or it’s just issues with your config?
I don’t know exactly what is wrong with it, but my SSD dit got power at boot time but had no activity with the latest eeprom. In other words, it was not accessible.
@maxym: This is astonishing! I can fully confirm your observation: Booting with the SSD connected through USB 2.0 takes about 2 minutes. Booting connected through USB 3 takes forever!
I am not happy though to run the SSD over USB 2 as the transfer rate of USB 3 is about 15 times highter. But I did some tests and HA seems to be very responsive. So I will stay with USB 2 until the problem is fixed. Thanks for that information!
@Recte: I cannot confirm this. My SSD has no power problems with EEPROM firmware 2020-09-03 (Crucial BX500 + Sabrent USB 3 adaptor).
I got my raspberry pi 4 boot from usb stick with HassOS 5.2 beta and everything worked fine less thr Bluetooth sensors, i can get readings from the sensors, but only if i move them really really close to the Pi… And then i went back to the sd card with hassos 4.3 and Bluetooth is working again has it should. Is this a know problem? Or there’s something i can do about it?
@JorgeMaTeixeira yes, this is a known interference!
Unfortunately USB 3.0 signals can interfere with radio transmissions in the 2.4 GHz band. This may affect Bluetooth, Wifi and Zigbee communication.
What you can try to do is using better cables for USB 3.0 and/or try to move any communicating adaptors (like Zigbee sticks) as far away as possible from the Pi and its USB 3 ports using a USB male/female cable. I would also connect such sticks to the USB 2 ports to limit interference of the stick with the signal on its own cable (although the 3.0 ports should switch back to USB 2 protocol on such sticks).
I finally found that the long boot times in my setup were a result of the JMicron JMS583 bridge chip in my SATA adapter. After updating the adapter firmware booting times on USB 3.0 are down to 3 minutes. Read the full story here:
Pi can boot from USB, I have flashed Rapsbian on USB Pendrive 16GB and it boots from it. It does not on with my SSD… So It seems that it’s SSD issue, or HassOS. I need to try with bigger USB Pendrive, maybe HassOS will boot from 64GB Pendrive
For what it’s worth, @Jpsy his SSD boots with EEPROM firmware 2020-09-03, mine doesn’t.
Mine boots with v2020.07.16-138a1. For me it was worth the try.