Installing Home Assistant on a RPi 4b with SSD boot

There are quite some reports of issues similar to yours. Have a look at the response by Frenck to one of the reports:

Otherwise I suggest you do your own search on Google, i.e. for:
home assistant "unable to load the panel source /api/hassio/app/entrypoint.js"

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 wonder if its to do with my Google Coral USB device - maybe its draws too much current?

Doesn’t sounds like hardware related issue. Did you try to clear browser cache?

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

The EXT4FS - error sound like a SSD issue to me?

Trying to find a good power supply, which one are you using?

Which power supply are you using?

As I wrote above
Rpi4 8Gb
board X825
SSD Kingston A400 120 Gb
Power supply 5V 4A (Adapter 230V/5V)

5V / 3A would probably suffice, but this was recommended for the X825 board.

1 Like

I was wondering which brand the power supply is, I have a hard time find one in Europe.

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

https://www.hardkernel.com/shop/5v-4a-power-supply-eu-plug-2/

Here is another one that has the correct 5.5 / 2.5 connector.
I found it in the local e-shop

1 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.

That really couldn’t have been any simpler.

First, a lesson learned (to help others):

  • 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

:frowning:

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.

Directly connected but with an external antenna several inches away.

I don’t think this is the problem because all my other Zigbee devices (within range) have connected successfully.

Might still be worth a try


1 Like

Well, thank you very much! It was worth a try! I attached the CC2531 USB stick to a 3ft extension and now all 3 routers have re-joined.

I honestly can’t believe most of my 2032-powered Zigbee sensors could talk to the supervisor but the AC-powered routers could not.

Now about my phantom database file
 :}

Update: fixed typo

1 Like

The explanation could be quite simple: Your primary Zigbee stick could send but not receive. Zigbee routers probably require a bidirectional communication to work.

2 Likes

Did you ever get this to work, I have the exact same issue
 SATA SSD’s boot to HASSio. on USB3 but NVMe drives do not


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!