search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
5.04k stars 987 forks source link

Raspberry Pi3B+ + USB SSD Drive - Update to HassOS 5.8 fail #1095

Closed noide35 closed 1 year ago

noide35 commented 3 years ago

Hello,

just to Notify that I tried this night to upgrade my HA (Hass OS 4.17) installed on my PI3B+ to last Hass OS 5.8. I'm using my PI3B+ with a SSD drive connected on USB. This installation totally broke my setup : my raspberry became totally unresponsive 20 minutes waiting after the beginning of the upgrade. After that, I tried a fresh install of Hass OS 5.8 but also without success. Unfortunately I don't have any logs as I lost access to my PI and I have no screen connected to it.

I was able to get back a HA setup only by doing a fresh install of Hass OS 4.16 (the only one I had) and installing a snapshot on it.

So for now and from what I see, it seems there is some issues with this new Hass OS version and PI with USB boot setup.

Again sorry for not having any logs...

noide35 commented 3 years ago

@stanislav-brabec Freeze issues are managed in another topic and seems to be related to another issue. This topic is only about the "no boot" issue from 5.x on Pi3B+ with SSD

stanislav-brabec commented 3 years ago

@noide35 OK. Thanks.

In my case, the boot failure of 5.9 and at least one freeze of 5.10 had the same reason: massive file system corruption. So I can confirm that freeze of 5.11 has probably a different source.

eketjall commented 3 years ago

Anybody tried the 5.12 release yet? Changelog doesn't bring the hopes up thou.

GuruLarsson commented 3 years ago

Yes I have tried version 5.12 and it has the problem, BUT it works with the workaround.

GuruLarsson commented 3 years ago

I have now also tries with 5.13, same issue, same fix. My raspberry 4 updates ok, my rpi3 doesn't.

naveedmughal commented 3 years ago

Running rpi 3b with 5.11 (fresh install) and 4.2 boot files. Looks like its time to upgrade to rpi4 or nuc to be able to run HassOS via SSD without any workaround.

rgreuel commented 3 years ago

Anyone try updating to 6.0 yet?

maovidal commented 3 years ago

Anyone try updating to 6.0 yet?

I just successfully upgraded my Pi3B. I asked for the upgrades from the Supervisor web page in this order: First HassOS and then the Home Assistant Core.

I have to say that I still keep the same microSD with the 4.20 boot files on it.

It is common procedure for me to restart the power source after this kind of upgrades as the Pi won't show up on the network. As I don't have a monitor attached to it, I haven't been able to check what is the cause of this.

But consistently after the upgrades and very rare power source interruptions, the system starts and works flawless since last January 2021.

GuruLarsson commented 3 years ago

Yes, My PI4 worked as usual, the Pi3B not so good as always, replaced the boot files and it works again! Have a nice reboot :-)

On Sun, 13 Jun 2021 at 00:20, Mauricio Vidal @.***> wrote:

Anyone try updating to 6.0 yet?

I just successfully upgraded my Pi3B. I asked for the upgrades from the Supervisor web page in this order: First HassOS and then the Home Assistant Core.

I have to say that I still keep the same microSD with the 4.20 boot files on it.

It is common procedure for me to restart the power source after this kind of upgrades as the Pi won't show up on the network. As I don't have a monitor attached to it, I haven't been able to check what is the cause of this.

But consistently after the upgrades and very rare power source interruptions, the system starts and works flawless since last January 2021.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/operating-system/issues/1095#issuecomment-860120525, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHUINROP3QKAYAZ2EKJHFMDTSPMR3ANCNFSM4U5FWPHQ .

upwindanderl commented 3 years ago

Had all the

Anyone try updating to 6.0 yet?

tried 6.1 and its freezing in less than 16hours :(

atm i'm even not able to downgrade grafik

agners commented 3 years ago

atm i'm even not able to downgrade

5.20 is not a valid release. Try 5.13.

fabiosci commented 3 years ago

just updated from 4.20 to 6.1 with no success. I needed to use the files from 4.20 boot partition (no need to replace the overlay folder) and then eveything worked fine, so far...

pxFIN commented 3 years ago

Updated to 6.1.. same challenge no boot but after copy of 5.3 boot files all is good again (so far)

xaralis commented 3 years ago

I'm on 4.17 (RPi 4). Is it safe to update to 6.2? If there are some rough edges, can someone tell me what needs to be done besides clicking on the update action?

Also, I would like to update Home Assistant Core to latest as well... Same questions here :)

image

Thanks!

GuruLarsson commented 3 years ago

Hi, I'm running Core 2021.8.1 without any issues and no problem to update. The OS version upgrade is simple as well, BUT if you boot from USB and SSD you might run into the problem this whole thread is about, IF you get the boot proble just replace the boot files to no higher than 4.7 and it will work again, the aother suggest option in this thread is to boot from SD card and configure it to run from SSD, see above

github-actions[bot] commented 3 years ago

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

maovidal commented 3 years ago

The boot problem describen in this thread persist on my Pi3B after I upgrade to the last:

Home Assistant OS 6.6 supervisor-2021.10.8 core-2021.11.0

My workaround it to keep the same microSD with the 4.20 boot files on it. After every upgrade the systems reboots after I re-apply the power source.

agners commented 3 years ago

@MrMauro are you using a SD card to boot from? If you use Supervisor -> System -> Reboot Host, it will not reboot? Anything connected to your system via USB? Can you check if having nothing else connected makes reboot work?

My workaround it to keep the same microSD with the 4.20 boot files on it.

I don't quite understand, what are you doing with it?

I do have a Raspberry Pi 3B with HAOS 6.6 64-bit booting off a SD-card. It seems to reboot when using the Reboot Host command as well as after updates.

maovidal commented 3 years ago

Hi @agners. Thank you for your interest!

I just re-tested my setup with the following findings:

  1. If there is no microSD present, the HDMI monitor attached will not provide any info starting. Just a black screen. It does not matter if the systems is started from a cold state (after disconnected the power source) or if it is already running, removed the microSD and asked to reboot via Supervisor -> System -> Reboot Host.
  2. With a microSD with 4.2 boot files on it, the system will boot from a cold start (). Every time.
  3. With a microSD with 4.2 boot files on it, the system will not successfully boot when asking the interface at Supervisor -> System -> Reboot Host. The same black screen on the HDMI monitor is presented after a while.

I just did that with the SSD hard disk being the only USB device connected . Normally I have an UPS attached to it and the systems behaves the same.

Maybe what I'm missing here is that I should use a microUSB with HAOS 6.6 boot files on it instead the 4.2 version to be able to restart it via the Supervisor?

Thank again.

maovidal commented 3 years ago

Follow up, I didn't succeed booting with an microSD using boot files version 6.6

I tried various combinations from just the bootcode.bin to the full content including the overlays folder.

I noticed that sometimes the splash screen (the colourful gradient graphic) appeared on the HDMI monitor, but there was no progress after that.

While this issue is not that a big deal for me (I'm just careful to have someone around that is able to re-apply power in case of a restart is required), I would be happy to perform any further tests if that helps somehow.

agners commented 2 years ago

I noticed that sometimes the splash screen (the colourful gradient graphic) appeared on the HDMI monitor, but there was no progress after that.

I think that is when the HAOS boot loader is not successfully started.

Can you retest using 7.1? It uses latest firmwares which might help. Also, since we are using U-Boot 2021.10 the framebuffer (screen) support is enabled by default (enabled by #1556). This means if it is U-Boot which hangs on your system, you should see something on the screen (which hopefully helps us to further debug the problem).

pxFIN commented 2 years ago

Hardware RPI3b and SSD Samsung EVO 860 (JMS 580)

I tried to update 6.6 -> 7.0 using working method (up there in this thread) previously using 5.3 boot files.. doesnt work.. boots back to 6.6.. doesnt matter if update is made from GUI or command line

maovidal commented 2 years ago

I'm also stuck at Home Assistant OS 6.6. Neither 7.0, nor 7.1 successfully update.

Unfortunately the Supervisor logs are lost. However, I was able to catch this part that seems okay after I pressed the Update button:

22-01-12 17:38:12 INFO (MainThread) [supervisor.os.manager] Fetch OTA update from https://github.com/home-assistant/operating-system/releases/download/7.1/haos_rpi3-64-7.1.raucb
22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
22-01-12 17:38:49 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token

My RPi3 is running headless, so I'll try to get a monitor to see if I can catch something else.

Again, thank you for the interest.

GuruLarsson commented 2 years ago

I tried to upgrade my raspberry 3B with external USB disk, but it failed as before since version 5.4. Now a started to think about to give up the tiresome replacement of boot files on the usb disk and created a new SD card with the latest 7.4 version. I started the new version and was prepared to fiddle with setting to be able to move data over to USB disk and restore from backup, BUT I was really surprised when my "old" home automation was how it was before my tru to upgrade, somehow the SD-card recognized the USB disk and automatically USED the data-partion on the USB disk, ALL my settings was as before. I am awaiting the next update.... Hope for the best. I have to keep the SD-card of course. Gunnar

On Thu, 13 Jan 2022 at 00:28, Mauricio Vidal @.***> wrote:

I'm also stuck at Home Assistant OS 6.6. Neither 7.0, nor 7.1 successfully update.

Unfortunately the Supervisor logs are lost. However, I was able to catch this part that seems okay after I pressed the Update button:

22-01-12 17:38:12 INFO (MainThread) [supervisor.os.manager] Fetch OTA update from https://github.com/home-assistant/operating-system/releases/download/7.1/haos_rpi3-64-7.1.raucb 22-01-12 https://github.com/home-assistant/operating-system/releases/download/7.1/haos_rpi3-64-7.1.raucb22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING 22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM 22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE 22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR 22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON 22-01-12 17:38:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN 22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE 22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.check] System checks complete 22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING 22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete 22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING 22-01-12 17:38:39 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete 22-01-12 17:38:49 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token

My RPi3 is running headless, so I'll try to get a monitor to see if I can catch something else.

Again, thank you for the interest.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/operating-system/issues/1095#issuecomment-1011545822, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHUINRLUOPRACJUIPRWEDVTUVYFCFANCNFSM4U5FWPHQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Xplouder commented 2 years ago

Did anyone tried the latest releases? Is this still happening?

GuruLarsson commented 2 years ago

I have tried and it didn't :-( Anyway, I have now change my USB to msata converter and now everything seems ok. So my final conclusion is that some HW just have stopped working with never versions of HA. Gunnar

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

joostlitjens commented 2 years ago

Working great with latest update, raspberry 3b ssd boot (no sd inside) thanks for supporting older devices in times of expensive electrical bills

joostlitjens commented 2 years ago

I was running, Core, 2022.10.4, I manually did a shutdown host. (because the power company was closing the power down today in the street) But now when i put power on the PI is isn't booting anymore, the loading led stops blinking at a time and continious burns. I think i have to reinstall...

update: i replaced boot files from 4.2: start.elf, fixup.dat and bootcode.bin + (overlays maybe not nessescary now everything is working!)

Could you look into shutdown host?

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

magin1 commented 1 year ago

Still and issue. Just updated to the latest version and it's not getting past u-boot screen #2876 Will try to replace the boot files like some people did before.