Skip to content

RPi4 B Rev 1.1: USB3.0 Highspeed USB-Boot with SSD doesn't work (but USB2.0 boots) #4654

@drose28357

Description

@drose28357

Describe the issue you are experiencing

I attached a NVMe-USB-Adapter to my RPi4 Rev1.1 with a USB3.1 connection. It boots fine with RPiOS.
The i flashed Home assistant 2026.4 with HAOS 17.2 on that SSD drive.
It doesn't boot. The i changed to an USB2.0 connection (by cable) and it boots fine. But i didn't get the full speed of an USB 3.0 connection.

I am aware of "RPi 4B: Complete USB subsystem failure after update to HAOS 17.2 #4627".

I checked and updated eeprom to the latest version (2026-01-09 newest available from RPi foundation shown in eeprom-update)

I switched from HAOS 17.2 to HAOS 17.1

I made screenshots wirh my mobile phone
Successfull boot:

  1. USB-boot_RPi4_USB2-normalspeed_eeprom => RPi Booteeprom finds MSD
  2. USB-boot_RPi4_USB2-normalspeed_u-boot => u-boot initialised xhci_pci and finds a storage device and later on starts booting

No boot:
3) USB-boot_RPi4_USB3-highspeed-eeprom => RPi Booteeprom finds MSD
4) USB-boot_RPi4_USB3-highspeed-u-boot => u-boot could not scan xhci_pci for devices and did not find a storage device and did unsucsessfull retries.

It seems to be an u-boot problem with failed intialisation of the xhci_pci. Maybe this problem is also related to #4627 .

What operating system image do you use?

rpi4-64 (Raspberry Pi 4/400 64-bit OS)

What version of Home Assistant Operating System is installed?

17.2

Did the problem occur after upgrading the Operating System?

No

Hardware details

It doesn't work with HAOS 17.1 as well as HAOS17.2 :

HAOS-Version:
Installationsmethode Home Assistant OS
Core 2026.4.2
Supervisor 2026.04.0
Operating System 17.1
Frontend 20260325.7

Steps to reproduce the issue

  1. Connect monitor to mini-hdmi
  2. Connect an NVMe-SSD-Adapter to USB-Port with Highspeed cable (USB3.0 or USB3.1)
  3. Make pictures of the screen
  4. Change cable to USB2.0 and repeat.

Anything in the Supervisor logs that might be useful for us?

No logs because no boot.

Anything in the Host logs that might be useful for us?

Becaus u-boot didn't find the NVMe-Drive it couldn't boot

System information

System Information

version core-2026.4.2
installation_type Home Assistant OS
dev false
hassio true
docker true
container_arch aarch64
user root
virtualenv false
python_version 3.14.2
os_name Linux
os_version 6.12.47-haos-raspi
arch aarch64
timezone Europe/Berlin
config_dir /config
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 17.1
update_channel stable
supervisor_version supervisor-2026.04.0
agent_version 1.8.1
docker_version 29.1.3
disk_total 219.4 GB
disk_used 7.9 GB
nameservers fda2:ce9f:d5f6:0:464e:6dff:fe43:a12d, 2003:f5:ff3f:2b00:464e:6dff:fe43:a12d, 192.168.101.1
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board rpi4-64
supervisor_api ok
version_api ok
installed_addons Matter Server (8.4.0), Terminal & SSH (10.1.0), Studio Code Server (6.0.1)
Dashboards
dashboards 2
resources 0
views 0
mode storage
Network Configuration
adapters lo (disabled), end0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth4eb590a (disabled), vethbf18c2b (disabled), veth16f3036 (disabled), veth6954551 (disabled), vethd20cc27 (disabled), veth368447f (disabled), veth8aeccd4 (disabled), veth6492473 (disabled)
ipv4_addresses lo (127.0.0.1/8), end0 (192.168.101.104/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth4eb590a (), vethbf18c2b (), veth16f3036 (), veth6954551 (), vethd20cc27 (), veth368447f (), veth8aeccd4 (), veth6492473 ()
ipv6_addresses lo (::1/128), end0 (2003:f5:ff3f:2b00:20c:a8f3:1433:5e35/64, fda2:ce9f:d5f6:0:a6c9:8725:74e3:7bf7/64, fe80::e1fd:3ecc:ca92:806e/64), docker0 (fe80::44a:8dff:fe4f:6e08/64), hassio (fd0c:ac1e:2100::1/48, fe80::a4ef:7ff:fee0:8d5e/64), veth4eb590a (fe80::4c53:71ff:fe92:822a/64), vethbf18c2b (fe80::9ce0:f2ff:fe82:cab8/64), veth16f3036 (fe80::e415:35ff:fe57:507a/64), veth6954551 (fe80::501b:9aff:feae:da57/64), vethd20cc27 (fe80::499:b1ff:fea3:324c/64), veth368447f (fe80::7c6f:cff:fe50:6f4d/64), veth8aeccd4 (fe80::dc76:aff:fe03:4855/64), veth6492473 (fe80::4c5c:6cff:feca:e34f/64)
announce_addresses 192.168.101.104, 2003:f5:ff3f:2b00:20c:a8f3:1433:5e35, fda2:ce9f:d5f6:0:a6c9:8725:74e3:7bf7, fe80::e1fd:3ecc:ca92:806e
Recorder
oldest_recorder_run 16. April 2026 um 20:12
current_recorder_run 18. April 2026 um 18:29
estimated_db_size 0.58 MiB
database_engine sqlite
database_version 3.49.2

Additional information

  1. Image
  2. Image
  3. Image
  4. Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions