No, there is no need to copy the elf files. As long as the eeprom is updated, flash the 64-bit HassOS 5.0 to the SSD and boot it!
The 32-bit OS will not work with USB boot.
Thanks, will try that, was not clear to me before.
I checked on Installation - Home Assistant and 32bit is the recommended build for PI4.
What if any are the pros and cons between the two?
I have successfully tested the bootloader by copying to SSD and USB SANDISK the PI OS and both those boot without SD card inserted.Will revert again once tested with 64bit OS
hey mark, what steps did you follow? i cant get mine to boot from the SSD
Have you got the latest EEPROM?
use vcgencmdbootloader_version to find out from command line.
this is mine and status is stable.
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Thu 16 Jul 15:15:46 UTC 2020 (1594912546)
LATEST: Thu 16 Jul 15:15:46 UTC 2020 (1594912546)
FW DIR: /lib/firmware/raspberrypi/bootloader/stable
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
I Installed PI OS 32 bit on SD card with Raspberry PI Imager.
booted up with SD to GUI and went to SD CARD copier
copied SD Card To SDD, once complete shutdown and remove SD Card.
Power on and Raspberry PI then booted from SSD.
Shutdown PI and use Balena Etcher to burn the Home Assistant V5.0 64 bit to SSD.
Plug SSD into PI without SD Card and boot, If you have a monitor attached to the PI you should see the Installation begin, otherwise wait until you can access HA on http://192.168.x.x:8123
2 Likes
cheers, will try that now.
interestingly, i did manage to get PiOS running fine.
I then did a diag test, with the following results.
Unless im reading it wrong, the microSD is faster then the SSD over USB3?
MicroSD
Raspberry Pi Diagnostics - version 0.4
Mon Jul 27 07:25:24 2020
Test : SD Card Speed Test
Run 1
prepare-file;0;0;39839;77
seq-write;0;0;37925;74
rand-4k-write;0;0;2763;690
rand-4k-read;9975;2493;0;0
Sequential write speed 37925 KB/sec (target 10000) - PASS
Random write speed 690 IOPS (target 500) - PASS
Random read speed 2493 IOPS (target 1500) - PASS
Test PASS
Kingston SSD
Raspberry Pi Diagnostics - version 0.4
Mon Jul 27 07:18:26 2020
Test : SD Card Speed Test
Run 1
prepare-file;0;0;26705;52
seq-write;0;0;26793;52
rand-4k-write;0;0;14972;3743
rand-4k-read;17044;4261;0;0
Sequential write speed 26793 KB/sec (target 10000) - PASS
Random write speed 3743 IOPS (target 500) - PASS
Random read speed 4261 IOPS (target 1500) - PASS
Test PASS
hey mark, i have the latest EEPROM.
I got this all working fine:
I Installed PI OS 32 bit on SD card with Raspberry PI Imager.
booted up with SD to GUI and went to SD CARD copier
copied SD Card To SDD, once complete shutdown and remove SD Card.
Power on and Raspberry PI then booted from SSD.
i then did this:
Shutdown PI and use Balena Etcher to burn the Home Assistant V5.0 64 bit to SSD.
Plug SSD into PI without SD Card and boot, If you have a monitor attached to the PI you should see the Installation begin
i keep getting the “Timeout waiting for hardware cmd interrupt” error now
Could it be your hardware?
Im using
ELUTENG USB 3.0 to SATA Cable
and Crucial BX500 120 GB CT120BX500SSD1(Z)
turns out i had to wait.
so HA loads up and i can access the UI - all good
i keep seeing the “timeout waiting for hardware cmd interrupt” message however
The error message you see is the linux kernel trying to access your SD-card that is no longer present.
Add the following to config.txt:
dtparam=sd_poll_once
1 Like
will do - where is that file?
It is here: /mnt/boot/config.txt
Are you on HassOS 5.0 or are you on Rasperrypi OS running a Supervised install?
1 Like
I finally got the V5.0 beta stable working. For the beta to work stable i added 2 extra lines to the config.txt
1:
dtparam=sd_poll_once=on
This line makes disable the time-out messages for the SD card
2:
usb-storage.quirks=174c:0825:u
This disable UAS (for my specific device geekworn x285) for USB3.0 devices as explained in this link https://www.raspberrypi.org/forums/viewtopic.php?t=245931
I don’t know if the kernel part from HassOS uses this feature as in PiOS, but in my case i had now reliable preformance and no corruptions after powerdowns (unplugging) or controlled shutdown.
1 Like
HassOS 5.0
nice!
are you running HassOS 5.0? if so, how did you edit config.txt
I have activated Developer access to HassOS 5.0 using the above procedure. That gives ssh access on port 22222 directly to the operating system.
1 Like
There a several ways to do this. The easy way is direct after buring the image, to edit the file on your computer when the drive is still attached to youre computer.
The other way is mentioned also in this thread, by gaining ssh acces to HassOS
thanks, tried a few times but still getting stuck
Thats it!! i used the 32 bit, but Erik is right, now i used the 64 bit rpi4 version.