Hi James, how are things for you now, a week later? Can you confirm your install is full HassoOS, not supervised install? I’m about to begin on the SD card to SSD journey.
I can confirm that I have been running Home Assistant OS (5.1 64 bit) on a Rpi 4 using a USB3 drive for a week. NO SD card. So far I am extremely happy. No issues and system seems to be faster and stable.
Check this guide. It’s in German but I use google to translate it.
Since August 1, 2020 so far good.
You can use following: PI4 HASSOS
You can use
Development 5 build 0 or Development 5 build 1
Please elaborate how exactly…
Check this guide. It’s in German but I use google to translate it.
I did same on PI4 4 GB and 8GB. Use following steps:
- Boot from a standard microSD card with the latest Raspberry Pi OS on it.
- Update your OS and firmware by typing:
sudo apt update
sudo apt full-upgrade
sudo rpi-update
- Edited the rpi-eeprom-update file and changed the “critical” value for the FIRMWARE_RELEASE_STATUS option to “stable”, using sudo nano /etc/default/rpi-eeprom-update.
- Install the latest bootloader by typing:
sudo rpi-eeprom-update -d -a
- Reboot the Pi and check the bootloader version by opening Terminal and running:
vcgencmd bootloader_version
Result:
Jul 16 2020 16:15:46
version 45291ce619884192a6622bef8948fb5151c2b456 (release)
timestamp 1594912546
After rebooting PI you’ll see:
- Download HassOS 5.2 (latest) for PI4 64 bit.
- Use balenaEtcher to burn image “HassOS 5.0” to SSD drive.
- Turn off PI, remove SD card connect SSD.
- Turn PI on.
- Navigate to
http://PI4_IP_Address:8123 - Wait for setup to finish.
- After about 5 min it’s done.
11 Likes
Vlad
Thank you for such a clear walkthrough!
Followed this process and it worked perfectly with HassOS 5.2.
Only difference was that after eeprom update the bootloader version was dated 3rd September not 16 July - so maybe there is an updated version?
I restored everything from RasPi3B snapshot (other than 0.114 OS).
It has only been a couple of hours but all add-ins are currently working without any issues:
- Node-red
- UniFi controller
- deconz (with Conbee II on an extension lead - all sensors and lights working)
- Mosquitto broker (all entities showing as available)
- File editor (and also Notepad++ with SSH)
- Samba share
- Home assistant Google Drive Back up
Hardware used:
- RasPi4 4gb
- Crucial BX500
- Simplecom SE221 Enclosure
This SSD and enclosure also previously worked on my RasPi3B.
If it is of any use to someone, the following custom cards also working without issue (all were previously installed manually on RasPi3b, and restored from snapshot - I did try to link but as a new user I couldn’t have more than 2 links):
- auto-entities
- battery-entity
- bom-weather-card
- fan-control-entity-row
- simple-thermostat
And these integrations in addition to those mentioned above:
- Daikin AC
- Google Cast
- Logitech Harmony hub
- TP-Link Kasa Smart
Hope the above is useful for someone.
Once again, thanks to the community for all the help and assistance in making this work.
Rob
Rob, it’s updated version.
Glad it’s helps.
Thank you.
Since I have a nvme drive that I’m not using,I’m thinking about using it for HA install. I have a couple items I’m looking at,but wanted to make sure that they would work. Going to use the instructions.
Boot SSD
SSD Board
Power
Enclosure
Power adapter
You should probably verify that the piggyback board that hosts the NVME drive supports UASP for the storage access. (That’s USB- attached SCSI protocol.) It will give you better performance than the plain vanilla “USB Mass Storage Bulk-Only Transport” storage interface since the host OS can have multiple queued I/O requests pending against the device, improving the throughput. The Raspian kernels on the Raspberry Pi support this; I have no idea what HASS-OS uses as a Linux kernel and if it has this support turned on.
That product page on Amazon seems to not mention UASP support, so that’s a little notable by its absence.
1 Like
Found this on their wiki page…
Q7:Does the X872 interface support UASP?
A7:This is not tested. Here is the chip information for your reference: The JMS583 supports TRIM to the SSD and can transmit and receive data by both of USB Mass Storage Class Bulk-Only Transport (BOT) and USB Attached SCSI Protocol (UASP) to and from the host respectively.
Everything seems to be working at the moment. I had a SSD and adapter from a previous project and they worked fine.
SSD
Adapter
I followed the directions here…Boot from SSD
I stopped at “The second command will show us what boot order we are using. We are looking for 0xf41 as the BOOT_ORDER value.” After this I shutdown removed the sd card and plugged in the SSD and booted up.
Everything booted as if I was still using the sd card. Have to see how things are in a few days.
Hello,
Any ideas what is happening here?
Just started to migrate to the ssd following the steps by vlad…
I’m using kingston a400 120GB and fujtech ssd case (jmicron jms578 chip)
Is your ssd connected to USB3? Try USB2
You might also consider disabling microSD checks to avoid flooding output/logs by those mmc0:sdhci register dumps.
BTW do you guys know, what is causing, that Pi4 boots from SSD for the first time, but after reboot (power toggle) it never boot again reseting itself again and again?
If i use usb2 i’m not able to get signal to monitor :-/
So no idea if it’s booting or not. Probably not
Ok, my bad. The hdmi cable was badly inserted. Now it works (from the USB2 port). Is it how it should be?
It might be due to early development. Might need seting up quirks.
Read this article: https://www.raspberrypi.org/forums/viewtopic.php?t=245931
Thanks, I’ll check that link!
I also tested with the raspberry OS and boot from USB3 was trashy and from USB2 it worked really nice.
I read that also bad power source could have something to do with boot problems from USB3? I have an old Huawei charger which should output 3A though…
You are a god! I followed these steps and got it working on Hass OS 5.2
Here is my equipment:
- SSD Enclosure:
Sabrent USB 3.0 to SATA External Hard Drive Docking Station for 2.5" or 3.5"’ HDD, SSD [Support UASP] (EC-UBLB) - SSD:
Samsung 128GB EVO Series - Raspberry Pi 4 with official power supply
My snapshot from my Raspberry Pi 3 MicroSD was loaded onto the setup and it worked 100% out of the box.
Here are some things I had:
- Z wave network of light switches, Schlage connect lock
- Blue Iris Cameras with motion detection cards
- I have red node but haven’t used it yet… it carried forward into this build
- Nabu Casa integration
The only issue I am trying to solve is the constant SSH dmesg notification that the microSD cannot be found (“mmc0: sdhci: Timeout waiting for hardware cmd interrupt”).
Glad it’s helps.
Check if any configuration from add-ins point to SD card.
The dmesg SD card error on the Pi terminal was occurring after I installed Hass OS 5.2, before I did my restore from snapshot. Unless you know of native configurations pointing to the SD card?