HASS.IO -> transfer from SD card to SSD or USB

I bought RPi4 8GB 3 weeks ago. it had bootrom from Feb2020.

Strange,
On another Pi 4 the 32 bit version boots just fine

Just tried all the latest procedures and for the HassOs 5.2 64 bit this works fine - but then the Zwave network does not workā€¦so back to square one here.

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?

You need to put the usb stick on an extension lead away from the Pi to stop this. Itā€™s a known issue with USB3.

This is a well known problem since USB 3 exists. USB3 works with 2,4GHz (or nearby) and that is destroying WLAN or Bluetooth which are also working at 2,4GHz.
The only possibility is to use better USB 3 cables that are better shielded or an enclosure that is better shielded or an USB Hub that is better shielded. Sometimes it is enough to use a longer USB 3 cable to put the device away from the WLAN/Bluetooth antennas.

You can ask nearly every Mac user because this problem exists there also. :frowning:

working absolutely fine with hassio 5.2 supervisor 245 in a rpi4-64 2gb + m2 ssd wd green 120gb + cheap usb cable and case from ali orico brand.

iā€™m trying to check my ssd temperature (iā€™m not sure if its even possible)

~ $ hddtemp -dF
-bash: hddtemp: command not found

and also

~ $ ha hardware info
(...)
disk: []
(...)

tks a lot in advance.

I use this addon

installed protection mode disabled. it did some quick perfomance test

[Mon Sep 28 16:12:53 WEST 2020][Info] HDD Tools start
[Mon Sep 28 16:12:53 WEST 2020][Info] Configuration - disk path: /dev/sda
[Mon Sep 28 16:12:53 WEST 2020][Info] Configuration - check period: 1
[Mon Sep 28 16:12:53 WEST 2020][Info] Configuration - output file: temp.log
[Mon Sep 28 16:12:53 WEST 2020][Info] Init run
/share/hdd_tools/scripts/main.sh: line 11: -1: substring expression < 0
[Mon Sep 28 16:12:53 WEST 2020][Info] Sensor value: Ā°
[Mon Sep 28 16:12:53 WEST 2020][Info] Sensor update response code: 400
[Mon Sep 28 16:12:53 WEST 2020][Info] Run performance test
     Category                  Test                      Result              
HDParm                    Disk Read                 277.88 MB/s              
HDParm                    Cached Disk Read          222.91 MB/s              
DD                        Disk Write                146 MB/s                 
FIO                       4k random read            22188 IOPS (88754 KB/s)  
FIO                       4k random write           3131 IOPS (12527 KB/s)   
IOZone                    4k read                   15599 KB/s               
IOZone                    4k write                  15221 KB/s               
IOZone                    4k random read            15250 KB/s               
IOZone                    4k random write           19122 KB/s               
                          Score: 5526                                        
Compare with previous benchmark results at:
https://storage.jamesachambers.com/ 
[Mon Sep 28 16:14:00 WEST 2020][Info] Performance test end
[Mon Sep 28 16:14:00 WEST 2020][Info] Cron tab update
[Mon Sep 28 16:14:00 WEST 2020][Info] Apply cron tab
[Mon Sep 28 16:14:00 WEST 2020][Info] Device /dev/sda found - staring CRON

but temperature is showing an error i guess
no quirks whatsoever previously added

have you tried reading the sensor from Developer Tools

This is the same here:

[Tue Sep 29 09:51:00 CEST 2020][Info] Init run
[Tue Sep 29 09:51:01 CEST 2020][Info] Sensor value: 0)Ā°
[Tue Sep 29 09:51:01 CEST 2020][Info] Sensor update response code: 201

Hi again, somebody using Crucial 120GB SSD model CT120BX500SSD1?

What should be the problem in using it? The problem is not the SSD itā€™s the USB-SATA controller from the enclosure!

Hi there, Iā€™m experiencing system unreliability as described in this issue: https://github.com/home-assistant/core/issues/40471

My gut feeling is that there is something wrong with my SSD, but it could very well be the controller of course. When the problem arises, I will see errors in home-assistant.log that may suggest that a certain component is acting up, but I doubt that the Tado component is the culprit as it is widely usedā€¦

Do you use that drive? What controller do you use it with?

Thanks!!

No, I have a Crucial BX500 and on another Pi4 I am using a Crucial MX500.

I am using this one: https://www.amazon.de/gp/product/B07D2BHVBD

No issues with that controller? Iā€™m so fed up with my unreliability that Iā€™m going to buy a new controller just in case.

Edit: just ordered mine!

Iā€™m experiencing random lockups too. Iā€™m using a 128GB Crucial drive. Do you have any further insights into what is going on?

Hi there! Are you keeping this list updated somewhere? Thanks a million for putting that together Annā€™s making community

I put a high cfm fan over the rpi and the drive and put some small heatsinks on the drive and I havenā€™t noticed a lockup since.

If someone is searching for the guide. It can now be found here: https://homeassistantforum.de/thema/pi4b-nur-mit-einer-usb-ssd-betreiben-ohne-sd-karte/#post-1069

I updated the guide for the new Pi4B bootloader!

2 Likes