Yes, you (@Jpsy) are right. For a test, or a system without addons, it is ok.
I bought a Raspi4 4gb, and the difference is recognizable.
E.g. with my system (Zigbee2mqtt, Esphome and some other addons) the 4gb version shows a much better reaction time and i can get the logs on the superviisor page, which was not possible with the 1gb version.
But only Hass.io without addons, the 1gb version could be enough to test stuff, but not much more.
I am really happy now with 4gb version, but more power could be better in the future (raspi5?)
@Jpsy
Just to let people know that have been following this guide that a new beta HAOS (7.1) has been released that fixes the freeze issues that many of us have experienced with certain RPI 4 models. It is currently in test by many of us that have been commenting in the GitHub 1119 issue and so far no one has reported any issues with the beta or the pre beta. There were some great users (a special thanks to (Oliver), RPI developers (several) and HAOS developers (@agners & others) that finally figured out the issue and a solution. By the way it was not an issue with the controllers, power supplies or SSD. If interested the fix is list here:
I would not expect you to. The fix was for a clock timing issue that effected some of us. If you read the discussion the original change was based on a theory from Broadcom. The new change is in the RPI firmware. Some users are in the weeks of testing with no issues.
Anyone using this Anker power bank to power their rpi4 with SSD? Would this work in replace with the raspberry pi official PS? The Power Delivery (PD) is rated as follows from this Anker model:
Valuegist USB 3.0 to SATA 3.0 Adapter Cable for 2.5" SSD/HDD Drives, SATA III to USB 3.0 External Converter Cable does not work properly, ordered the startech one now
@bschatzow,
Yes, followed that thread closely since I had the freeze issue. Actually got my installation working after reverting to OS 4.2, was rock solid for weeks (got some flak here for mentioning that suggestionâŠ)
After reading about the release of 7.1 I uppgraded and my system continued being stable (Seems 7.1 is actually using some older files/settings that were present in for instance 4.2)
Anyway, would like to say something about my perception of the troubleshooting in this thread; seems itâs sometimes a bit one sided, focusing sometimes a bit too much on power supply. In my case I tried to get focus away from that since I had recommended amps and still had issues, wanting to investigate other venues, but focus steered back to power supply.
Just my humble opinion.
I believe the people were of good intentions. They did not understand how since most had no issues and some of us did it had to be something wrong in our setup (Power supply, controller, SSD, etc.) They were guessing on what it could be. It took one of the developers (Stefan) to finally see what many of us saw for over a year to finally ask the correct questions of the Raspberry developer team as well as a couple of people in the HA community that truly understood how the firmware was being loaded to try many different version to figure out what got changed and how to fix it. If you read the GitHub #1646 that I referenced above you can read through all the troubleshooting steps and what the fix was.
Can you please a bit more elaborate option with PI Imager. Which recovery should I use? If I understand correctly it will automatically change settings to boot from SSD? Is this permanenet fix?
I followed this guide just over 1 year ago and currently my system is still on OS version 5.10.17-v7l+ everything have been very stable. Should I update the OS to the latest 7.1 or is there no advantages in doing this? Also if there are benefits to upgrading the OS, can this be done completely remotely via SSH? Iâm away from home so cannot mechanically interface with the RPi.
System Health:
version: core-2021.12.10
installation_type: Home Assistant Supervised
dev: false
hassio: true
docker: true
user: root
virtualenv: false
python_version: 3.9.7
os_name: Linux
os_version: 5.10.17-v7l+
arch: armv7l
timezone: Europe/London
GitHub API: ok
Github API Calls Remaining: 4816
Installed Version: 1.19.3
Stage: running
Available Repositories: 947
Downloaded Repositories: 31
logged_in: true
subscription_expiration: 23 February 2022, 00:00
relayer_connected: true
remote_enabled: true
remote_connected: true
alexa_enabled: true
google_enabled: true
remote_server: eu-west-2-0.ui.nabu.casa
can_reach_cert_server: ok
can_reach_cloud_auth: ok
can_reach_cloud: failed to load: timeout
But if your system is stable I see no advantage in updating it. Especially if you are not on site I recommend the conservative strategy to ânever change a running systemâ.
Your location can be configured through configuration.yaml as well as through the web frontend. configuration.yaml has precedence. Look for latitude:, longitude: and time_zone:.
Hi and thanks for the guide.
I have raspberry pi 4 4GB and using and trying to use an SSD.
I have followed your guide exactly but with one SSD (kingston) I get:
Trying to partition: 0
Unable to read partiton as FATâŠ
and trying another SSD it some times boots (very rarely) and others throws thousands of errors like this:
SQUASHFS error: Failed to read block 0x715cf5: - 5
SQUASHFS error: Unable to read fragment cache entryâŠ
system[1]: Failed to start Journal Service
Buffer I/O error on dev sd8, logical block 0, lost syncâŠ
EXT4-fs (sda8): I/O while writing superblock
and many many other errors.
If unplug and plug again after many many trials may some time boot again.
I have original raspberry power adaptor, tried both usb 3 and usb 2 ports and have this USB to sata
Decided to completely forget about getting my HA to run on SSD, not worth the hassle after over a year of pointless troubleshooting.
SanDisk Extreme Pro SD-card, basic recorder optimization and moved the whole database inside the rpi4 4gb RAM-memory. Now that there is no more continuous writes to the SD-card HA should run all peachy.
EDIT: As a reminder about my issue, old 5.3 version of HAOS was working fine on the SSD but anything newer than that froze the system within 24 hours. No error logs available to see etc. Plenty of people lurking here with this exact same issue and devs havenât been able to locate&fix the issue in all this time.
EDIT2: Oh, they actually located and fixed the issue on the 7.1 beta version? Oh well, Iâll still roll with the SD card as I have Raspbee II plugged to my rpi4.