-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not update from 14.1 to 14.2 Yellow with cm5 upgrade with ssd and mmc #3844
Comments
Can you please post the output of |
2025-01-29 15:32:13.730 homeassistant rauc[639]: input bundle: /mnt/data/supervisor/tmp/hassos-14.2.raucb line = await resp.content.readuntil(b"\n") The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Hold on the second command was a few min after a boot so reran it right after and had different reslutls 2025-01-29 15:32:13.730 homeassistant rauc[639]: input bundle: /mnt/data/supervisor/tmp/hassos-14.2.raucb |
Is the eMMC content empty? For example |
I don't think the emmc is empty. It gave me an error right after the migration saying both were in use and did i want to mark the emmc as inactive. This is out of memory so not exactly what it said. How do I enable developer ssh? Right now it says connection refused. |
If that means that HAOS was installed both to the internal eMMC and on the NVMe, then it's almost surely the cause of the problem.
Here's how: https://developers.home-assistant.io/docs/operating-system/debugging/ |
I think I have the same problem. |
And I think I have the same problem too. |
it is very easy to solve. Just use the rpiboot tool and then the Raspberry Pi Imager to erase the eMMC. |
If you are really sure the eMMC can be wiped, either do what @pdonn suggests, or, after connecting to SSH or to the serial console (see my previous posts about that), run |
I can confirm that wiping the emmc worked. Steps I took,
|
@edhahn4444 What did you use to validate that you are using the nvme and not emmc (step 2) ? |
There is probably a better way but I, |
Gotcha! I did the same thing initially when I did the setup for the Yellow + NVME. |
The problem is that we use the cm5 module. It's just not a long-term solution |
Oups...sorry, I've misread the title it seems. I have CM4 actually. So it shouldn't be a problem on CM4 I believe? It's strictly related to CM5 combined with Yellow? 🤔 |
No I have had the Problem on one cm5 and on one cm4 powered HA yellow. |
Oh god...I just did the update from OS 14.1 to 14.2...now the HA page is not loading anymore. |
@pdonn |
I have also used the option to move the data to the NVME SSD, so I guess the emmc is still running the HA OS and not the SSD. Not sure what to do now thought...from your input it seems like I might have to wipe the emmc, but that means that the SSD would only have the data and not the OS...so not sure again what to do next. |
I would start by making sure you are accessing it by ip and port to make
sure it is not a dns thing.
I am by no means an expert but my next move would be to wipe everything and
reset up as if I had just installed the cm5 and restore from the backup.
It is weird that you can ssh in and see the docker instance running so
there is probably a better option.
…On Thu, Jan 30, 2025 at 3:23 PM mihaicristianpetrescu < ***@***.***> wrote:
I can confirm that wiping the emmc worked.
Steps I took,
1. Full backup and off of local storage
2. confirmed I am using the nvme not emmc
3. rpi boot following these instructions
https://yellow.home-assistant.io/guides/reinstall-os/#:~:text=Option%202%3A%20Reinstall%20Home%20Assistant%20OS%20using%20rpiboot
4. rpi imager but instead of selecting an image I used the erase
option for only the emmc.
5. reset jumpers to original position
6. booted yellow back up
7. installed update
8. on the reboot it updated successfully!
I have also used the option to move the data to the NVME SSD, so I guess
the emmc is still running the HA OS and not the SSD.
I've done the update of OS from 14.1 to 14.2 and HA web interface is not
booting up even though the docker container is running as I'm able to
access it via SSH root.
Not sure what to do now thought...from your input it seems like I might
have to wipe the emmc, but that means that the SSD would only have the data
and not the OS...so not sure again what to do next.
—
Reply to this email directly, view it on GitHub
<#3844 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3TAA2R4NFQHSRRWYF6QNST2NKC2LAVCNFSM6AAAAABWDH7FY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRVGQ4TSNBXGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@edhahn4444 I actually did the wipe on the CM4 eMMC and now it doesn't boot anything up...so it seems that just DATA was migrated to the SSD, OS was left on eMMC, however after update to OS 14.2 it didn't boot up anymore but SSH root was working. |
I only started having the issues after upgrading to cm5. I am not sure if
our issues were the same. The advantage is you have a cm4 which is easier
to recover. You can follow the set up instructions here to start over
https://yellow.home-assistant.io/
…On Thu, Jan 30, 2025 at 4:16 PM mihaicristianpetrescu < ***@***.***> wrote:
@edhahn4444 <https://github.com/edhahn4444> I actually did the wipe on
the CM4 eMMC and now it doesn't boot anything up...so it seems that just
DATA was migrated to the SSD, OS was left on eMMC, however after update to
OS 14.2 it didn't boot up anymore but SSH root was working.
Now SSH root is not working anymore after wiping the eMMC so I assume I
just have to start from scratch and reinstall HA on SSD directly somehow
—
Reply to this email directly, view it on GitHub
<#3844 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3TAA2XGGURRMXO3BJUATWT2NKJCTAVCNFSM6AAAAABWDH7FY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRVGYYTCNJXHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Both yes and no... |
In the end the resolution was to wipe the eMMC, download HA OS 14.1, use balena etcher to flash it directly to the NVMe drive (via SSD enclosure), install it back and then boot it up + restore from backup. |
These steps worked for me. Thanks @edhahn4444 ! |
Describe the issue you are experiencing
Many reboots and trying to install the update via the web and ssh. Never updates and says inactive and bad is os info.
ha os info
board: yellow
boot: A
boot_slots:
A:
state: booted
status: good
version: "14.1"
B:
state: inactive
status: bad
version: "14.2"
data_disk: TEAM-TM8FP6512G-TPBF2207070060200211
update_available: true
version: "14.1"
version_latest: "14.2"
What operating system image do you use?
yellow (Home Assistant Yellow)
What version of Home Assistant Operating System is installed?
6.6.62-haos-raspi
Did the problem occur after upgrading the Operating System?
No
Hardware details
Yellow with CM5 that has both an ssd installed and emmc on the rpi. Currently booting off the ssd.
Steps to reproduce the issue
1.try to install update
2.HAOS reboots like nothing happens
3.
...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
Nothing that I saw
Additional information
None
The text was updated successfully, but these errors were encountered: