Thanks for this.
One of my RPs (bought from the Australian distributor) works fine with a KingSpec SSD. However the other supposedly identical RP bought off Amazon will not communicate with it.
Interestingly I am having a lot of trouble with WiFi with the Sonoff RF Bridge (flashed with Tasmota). When my desktop starts up, the Bridge become very flakey. It might be related with the mesh, but I do have a fried USB3 port on my desktop and I wonder if that is causing problems.
Wow, this is interesting. So youāre saying that two identical RPi 4Bs behave differently re your SSD? Did you check whether the board revisions are identical? There are many web sources that may help you. Below is an example link.
It would be very interesting to find a correlation between RPi board revisions and SSD boot problems.
I ran the command:
cat /proc/cpuinfo
Both show up as Pi 4 Model B Rev 1.2
The only difference is the one that works with the SSD shows:
BogoMIPS : 126.00
The one that doesnāt is showing
BogoMIPS : 252
The first was taken from the terminal file running Pi-OS on the SSD
The second with the larger number is from a HomeAssistant instance on an A2 SD card.
I guess the different BogoMIPS are the result of the different Linux versions used in RPi OS and in HA OS.
This parameter is in fact relevant for the boot process as it is used to calculate timings. But I guess when you start your first Pi with the SD card of the second it will show the same BogoMIPS as the second.
Are you sure your boot EEPROM code is the same version on both RPis?
Maybe you hit on why the pi with identical hardware works for some with USB boot and not for others. I still have issues on any OS above 5.4.
Interestingā¦ just to add a data point
My RPi 4/4GB shows
Model: Raspberry Pi 4 Model B Rev 1.1
with BogoMIPS of 108 while running the latest HassOS. I have it booting off of a 120GB Samsung 840 EVO SATA SSD, connected via a Startech USB312SAT3CB. Its EEPROM was fully up to date as of about a month ago.
I use m.2 nvme drive to boot up. It was painful to set it up but it works flawlessly.
Mine is 1.2 and same driver and controller. Locks in less than a day on anything above 5.4.
I believe so - I ran the update a couple of times and got the green screen, so it should be okay.
Same process for both machines.
That is the solution!
Turns out the the JMS583 Boards that enable NVMe drives to talk to the Pi (or other USB 3 devices) have a different firmwares. Also turns out that HASSio is rather picky about this firmware. Pi OS is less so (or at leas Pi OS has been patched to not have this issue)
As you recommended, once I updated the firmware of both the powered and non-power JMS583 NVMe -> USB adapters I was able to successfully boot HASSio to a Wester Digital Blue 1T NVMe drive. I have not tried the faster EVO and PRO drives that I have but the āBlueā drive was the one that I was planning to run HA on.
If you want to flash the firmware on your JMS583 based adapterā¦ Use the 2.0.9 version here:
Down Load 2.0.9 firmware patch
USE THAT LINK AT YOUR OWN RISK. I do not confirm that is a virus safe linkā¦ But it did work for me. YMMV.
Thanks for all of your help!
Congratulations for your success.
But I urge everybody here NOT to download and install firmware from any unofficial resources. AFAIS both links for NVMe firmware updates that have been posted here are hosted on dubious URLs.
Please look for an official source and DO NOT USE THE LINKS. Such code could infect your PC/Mac in the update process or could even try to execute on your RPi later.
Sorry for being the fun killer but itās a war raging out there.
Could you provide better/safe links pleaseā¦
Thanks
I think that is your job. I have no NVMe.
You are also free to take any risk you want.
Well, for the benefit of others.
I agree, you are right, as with any link, use at your own risk. I will edit my post with a use warning. But if you have an extra NVMe drive kicking around and you want to use HASSio on it you will need to get your adapterās firmware to 2.00.09 (or newer).
I was not able to find any other links to firmware patch tools that work. I can confirm that the link I provided and the link that Laxarus provided work. I emailed the manufacture to see if they will provide a āmanufactures linkā. I will update if/once they reply. There is a link to a flash tool on GitHub, but that one looks sketchy too and I have not tested it.
In my case all three of my adapters had different firmware. The unpowered one was the oldest had the oldest firmware, it was 1.0.12 (or something like that). The powered ones had 2.0.6 and 2.0.8 firmware versions. So maybe newer adapters will have the firmware that works with HASSio. At least it explains why some were having no problem and others were giving up.
Just note for the initial article.
My RPi did not update the eeprom automatically. I needed to force it to install the update following the RPi docs here: https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md
sudo rpi-eeprom-update -a
Thank you @Jpsy for the tips!
Unfortunately I wouldnāt expect this to happen to me too, so this information comes a bit late 
So, since my backup freezes HA installation, I tried to remove the possibly broken database when reinstalling. Since thereās no way to specifically remove the database, I decided to open my configurations with tar, find the location of the database and remove the file alltogether. Then I re-targz (such a bad word!) and re-tar and tried to upload the file as a snapshot.
Unfortunately this didnāt work. I got a 400 file error when I try to upload the snapshot. If I try the original file instead, everything works. Any insights what I am doing wrong or how to fix this?
Thank you!
I tried to follow a different path. Make a proper installation, install only the plugins and then copy & paste all configuration files, except the database. Unfortunately this didnāt work. After I restarted HA, the interface is not shown again, although āobserverā says that itās āConnectedā with green letters.
Please help?
man, i could kiss you right now.
Just wasted 4 hours trying to recover my MariaDB database after switching to SSD and restoring a full snapshot.
Stopping the addon before creating the snapshot worked!
Greetingsā¦ I have been following this thread for over 6 months as I was keen to upgrade from RPi 3 with SD (64GB) card to the RPi 4 , 4 GB or 8 GB with SSD drive. I am not from a Technology background , but enjoy gadgets and automations . I have a reasonably decent HA in operation with Conbee II and ZHA . Is there a possibility that HA will integrate the Pi 4 and SSD in a simple plug and play option with no boot procedures required ?
