hey thanks for replying. That all seems related to an Ubuntu install which mine is not. It is 100% to do with the SSD because moving back to the same snapshot on my SD card and HA is fully responsive and reliable.
Its strange because I have the same crucial SSD and Startech adapter that you do.
I am going through the guide again and will try this but I doubt it - I cant ssh into the pi either which makes me think its not related to browser cache
I bought it in the Czech Republic, but be careful, if you use an X825 board that has a 5.5 / 2.5 power connector, use a reducer, because the power supply has a 5.5 / 2.1 connector.
Here is a link to what it looks like
I donât know if anyone else has commented on this, my searching skills arenât the best. I wanted to finally get my RPi4 4Gb running and booting HA from SSD, Iâve used the EEPROM boot recovery - just to test it and see - and its worked perfectly. Following @tmm1âs directions and my RPi has booted directly from the SSD, no SD card in it, and itâs currently sat at the onboarding screen.
if you start with a fresh Hassio install on a SSD, you can check your router to see what IP it got
initially you can connect to HA using http://192.168.x.y (whatever your IP is)
you should configure your router so HA always gets the same IP (using DHCP tables / MAC address)
after you restore a snapshot in HA, if you have SSL enabled (eg, DuckDNS), now you can only connect to HA using https://192.168.x.y â note the âsâ after http
I lost some time on this oneâŠ
Second, an issue?
as my snapshot excluded the media/ folder, restoring the snapshot apparently did not mount the media/ folder
so I have no idea where my âhome-assistant_v2.dbâ file is (though HA is maintaining history somehow)
Third, another issue?
I used a second RPi4 to get the SSD working
I created a snapshot on the first RPi, and restored the snapshot on the second RPi
I unplugged the first RPi and moved over the CC2531 USB Zigbee supervisor
I updated my router config so the second RPi used the original IP
it looks like everything worked except⊠I have 3 CC2531 routers that failed to join
I reflashed the routers and tried to get them to rejoin â nothing, not even a Zigbee2mqtt log???
the CC2531 red LEDs continue to flash once a second (trying to join)
I searched but canât find anything recent reporting router join issues
Core Version is 2021.2.3
Supervisor Version is 2021.02.11
Operating System is HA OS 5.12
Is your Zigbee USB Coordinator connected to the RPi via a USB extension cable, or plugged directly into the RPi? Using a USB SSD causes interference with other USB devices, and thus a USB a extension cable is necessary to move the Zigbee Radio far enough away to prevent issues. I noticed the exact same issue with my Conbee2 USB radio.
The explanation could be quite simple: Your primary Zigbee stick could send but not receive. Zigbee routers probably require a bidirectional communication to work.
No, I gave up.
The only way to use the above mentioned combo, is leaving the operating system (HassOS) and the boot on the MicroSD card in the read only partition (or almost), and moving the data partition containing Home Assistant itself, the yaml files, the database, the logs and the add -on, the NVMe external SSD, i.e. where all frequent writes take place, using the # datactl move /dev/sda command.
As a bonus, I was able to enable TRIM.
After a couple of months is rock stable.
Take a look here.
I read your linked thread, you are/were about 6 months ahead of me. Spent a whole day, image, boot, patch, repeat. I know in the Windows world you canât image a SATA boot drive to an NVMe drive. And there are extra steps and processes need to âportâ from a SATA to NVMe. I wonder if that is what is going on here? Super frustrating!