operating-system: Fail to boot after Upgrade to 10.0 - rpi4 SSD
ℹ️ ℹ️ ℹ️ If you are affected, please state which exact USB to S-ATA/M.2 adapter you are using (make/brand and PID/VID if possible). If you useRaspberry Pi CM4 with a directly attached NVMe, please do not write here but in https://github.com/home-assistant/operating-system/issues/2479 instead. Thank you!
Describe the issue you are experiencing
I have the argon40 case so I’m running my rpi4 from the external SSD (USB-connected).
Failed to boot after upgrading OS to 10.0. Problem was temporarily solved by downgrading back to OS 9.5
Currently running core 4.0.
Similar to #
What operating system image do you use?
rpi4 (Raspberry Pi 4/400 32-bit OS)
What version of Home Assistant Operating System is installed?
10.0
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
- Upgrade to 10.0
…
Anything in the Supervisor logs that might be useful for us?
No
Anything in the Host logs that might be useful for us?
No
System information
System Information
| version | core-2023.4.0 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.10.10 |
| os_name | Linux |
| os_version | 5.15.84-v7l |
| arch | armv7l |
| timezone | Europe/Copenhagen |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 4854 |
| Installed Version | 1.31.0 |
| Stage | running |
| Available Repositories | 1266 |
| Downloaded Repositories | 19 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | August 10, 2023 at 2:00 AM |
| relayer_connected | true |
| relayer_region | eu-central-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | false |
| google_enabled | true |
| remote_server | eu-central-1-12.ui.nabu.casa |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 9.5 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.04.0 |
| agent_version | 1.4.1 |
| docker_version | 20.10.22 |
| disk_total | 234.0 GB |
| disk_used | 9.4 GB |
| healthy | true |
| supported | true |
| board | rpi4 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Home Assistant Google Drive Backup (0.110.3), Terminal & SSH (9.6.1), File editor (5.5.0), Mosquitto broker (6.2.0), Check Home Assistant configuration (3.11.0), Grafana (8.2.1), InfluxDB (4.6.0), Node-RED (13.5.2), Spotify Connect (0.12.3), Samba share (10.0.0), Zigbee2MQTT (1.30.3-1), ESPHome (2023.3.0), VLC (0.1.3), ArgonOne Active Cooling (29c), Shortumation (v0.7.6) |
Dashboards
| dashboards | 1 |
|---|---|
| resources | 17 |
| views | 9 |
| mode | storage |
Recorder
| oldest_recorder_run | April 5, 2023 at 9:47 PM |
|---|---|
| current_recorder_run | April 19, 2023 at 12:06 AM |
| estimated_db_size | 432.94 MiB |
| database_engine | sqlite |
| database_version | 3.38.5 |
Spotify
| api_endpoint_reachable | ok |
|---|
Additional information
No response
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 72 (10 by maintainers)
Hi folks, has anybody attempted to upgrade to 10.1 as yet and did this resolve the boot issue? Trying not to be trigger happy. haha.
The best way to do this is creating a full backup and start with an installation on the SD-card from scratch. Depending on your backup size, you can either upload it at onboarding time (before creating a login) and then enable the data disk feature, or alternatively you can create a user, enable the data disk feature and then upload the backup and restore it.
Succesfull migrated from 9.5 to 10.3… all went smooth… Rpi4 SSD Argon Casing USB … Scandisk SSD
@djalexnl thanks for updating, just for clarity I’m assuming you boot of the SSD (not SD Card)?
FYI, I just updated from 9.5 to 10.1 on my prod. Rpi4 booting from a USB3 Samsung T5 SSD drive and it went without any issue. Prior to that, I tested the same update on my dev. Rpi4 booting from an old Samsung 830 SSD via a Startech USB 3.0 Sata adapter without problem either. Both Rpi4 had their bios updated in late 2021.
If you are booting off SSD, don’t update to 10.x. If you are booting off MicroSD, and using SSD as a data disk, then you can update.
That is my experience of the issue (and I use Argon M.2 case, booting off SSD).
So my vendor ID would be 174c and the model id is 1156, sitting on USB 2-2 (I think).
On Fri, Apr 28, 2023, 12:49 p.m. ESPmonster @.***> wrote:
Well the SSD in the Argon case is in fact coupled to the rpi via a male-to-male USB bridge…
I have basically the same Setup - RPi 4, Booting from SSD with USB 3.0 Adapter (idVendor:174c, idProduct:225c, so Quirk neccesary), updating from 9.5 - and fortunatly didn’t have any Issues.
I remember i updated the RPis Firmware 2-3 Month ago. My Bet for those RPis not booting would be its either because of an incompatibility with an older Firmware, or incompatibility with the USB-Adaptor.
If you wanted to convert to a data disk set up from a boot from USB (SSD, no microSD), how would one go about this?
Do you have a backup? I assume you also boot from the SSD (no microSD present). If so, download the backup to another machine. Use a male to male USB (or a female to male and the argon male to male usb bridge) to connect the SSD to that machine. Write a fresh install with OS 9.5 to the SSD using rpi imager. Put the SSD back and boot. Wait until the rpi appears at <<IP>> :8123 and choose ‘restore from backup’. Upload it, then wait again and that should be it.