I just followed all the instructions. SSD and USB boot seems to work. I installed 5.6 64bits version of HA. When I started the rpi from the USB boot, it worked as spected. I uploaded my full snapshot during HA set up. After some restoration done I got the EXT4_fs (sda8) error in loop. It never ended so i turn the rpi off and then on. HA is set up however It doesnt work as spected. My config is restored but i cant get some addons like mqtt to work (due to a docker error aparently).
I guess the snapshot wasnt restored correctly, how can I do it?
Do not use the snapshot upload function on the first login screen. Instead do a fresh login (i.e. define a new admin user). When the system is completely up and running, go to Supervisor ā Snapshots and use the dot-menu in the upper right corner to upload and restore your snapshot.
Unfortunately Iām stuck on āUse raspi-config to set boot config to SSD bootā
Iāve flashed an SD card with āRaspberry PI OS (32bit)ā and gone through the steps of updating and rebooting.
Running āsudo rpi-eeprom-updateā gives the information
When running āsudo raspi-configā the menu options differ a bit but Iāve done 6. Advanced options -> A6 Bootloader Version -> E1 Latest -> Reset boot ROM to defaults? No
Then the problem occurs 6. Advanced options -> A6 Boot Order -> B1 USB Boot No EEPROM bin file found for version 2020-10-28 - aborting There was an error running option A6 Boot Order
Iāve also tried with a reboot after āReset boot ROM to defaults? Noā but no change.
Any suggestions on how to solve this?
Should I choose a different Raspberry OS when flashing the SD card?
okā¦ did you update the eeprom? did you flash the USB Drive to HASSio that support SSD? I believe you need to flash special Hassio that can boot from USB. Else it wont boot since it didnt find the right files to boot
The EEPROM should be updated when I have done the steps I describe (as I understand it).
But it fails when doing 6. Advanced options -> A6 Boot Order -> B1 USB Boot with the error message No EEPROM bin file found for version 2020-10-28 - aborting There was an error running option A6 Boot Order
I have flashed my SSD with latest Hassio dev version 5 but havenāt tried booting since the EEPROM is not updated to support USB boot.
And I could run sudo rapsi-config and select the USB boot option.
Next āproblemāā¦
Iāve attached my Samsung T5 SSD, with the cable that was in the box, to one of the USB3 ports. When starting the Pi there is boot information shown on the screen and the green light is flashing.
After a short period the screen goes black and the green light stops flashing.
Is Hassio booting or has things stopped? I guess I should see some Hassio info on screen?
I know that there is a suggestion to try USB2 if the boot time is slow.
Are you talking about screen connected directly to RPi HDMI ?
If so, that I would try with USB2. I believe I have similar symptoms when using āwrongā cable with USB3 (it workded with USB2 though)
Yes, sorry for not being clear. I have a screen connected to RPi HDMI that shows boot messages and then goes black. The green light on the RPi stops flashing.
I tried USB2 as well but same behaviour, i.e. black screen, green light stops flashing and nothing shown from Hassio.
Will try and flash image again to SSD to see if that can solve it.
Otherwise I guess I need to try with a different cable from SSD to USB2 or USB3.
Flashing again didnāt solve anything.
Iāve tested with the USB-A to USB-C cables I have and none is working.
I noticed that for most of the times the blue led on the Samsung T5 SSD starts to flash blue and then turns to red, no flashing, and then blue, again no flashing. I take that as a sign that something is not working.
Any recommendation on a USB-A to USB-C cable that works?
I saw the same behavior as rock3r and I was using the ELUTENG adapter and the Sept 3 2020 bootloader. I ended up just loading Raspian on the SSD, booting from that, and using Docker for HA so I could get something working. If a solution comes up, I would love to switch to a pure HassOS install.
I suspect the issue is the Samsung T5 itself. Itās probably designed as a portable storage medium, not as a boot device. You may need to go for a simple M.2 SSD + enclosure on this list.
I had a short progress yesterday evening. I flashed hassos_rpi4-64-5.6.img.xz and when attached to the upper USB3 it booted and showed a lot of info messages, e.g. Bluetooth being enabled. Then it stopped and showed a āpower save enabledā message. I kept it running during the night but it only shows the same message.
Switching power on/off this morning didnāt help and Iām back to seeing the boot message from RPi4 and the Samsung T5 led blinking blue and then turns to solid blue.
To bad if the Samsung T5 canāt be used as a boot device
I saw that there is a new release (5.7). Will try and see if that might work or if Rasbian and Docker will be the way to go.
After that I could access http://homeassistant:8123 and continue the installation.
Next step is to import a snapshot from RPi3b and also see what happens when I restartā¦
Iām a little bit unsure if there are any drawbacks using hassos_rpi4-64-5.7.img.xz when it comes to Deconz Conbee II stick, IKEA TrĆ„dfri and TP-link smart outlets?
I have a Conbee II running on 5.7 64 bit and it works just fine. Just make sure that you plug it in and restart HA once before you install any integration that accesses the stick.
I also recommend that you use a male to female USB cable to get some distance between the stick and the Pi. Otherwise you might experience bad connection quality.
