Upgrade Odroid N2+ to 12.3, now unable to boot. #3351
Comments
|
Booting with a keyboard and monitor attached produces this |
|
Having the same issue on my ODROID N2+ device. |
csimonosian
changed the title
|
Ugh 😢 What eMMC size/type do you have? This is most likely related to #3319 which came in with this release, and helped fix other eMMC sizes/types. But it seems to cause problem in your case 😢 |
It seems that for certain folks the new build causes issues, see: home-assistant/operating-system#3351
|
I have the "standard" 64GB eMCC from Hard Kernel |
|
Mine was the 32GB eMMC from the UK distributor. https://www.odroid.co.uk/odroid-accessories/odroid-os?product_id=1118. I have been preparing myself for a clean install of 12.2! |
|
very same problem here on ODROID N2+ 4GB and eMMC 5.1, 64 GB from ALLNET (https://www.reichelt.at/at/de/entwicklerboards-emmc-5-1-64-gb-erweiterungsspeicher-debo-emmc5-0-64-p248578.html?search=emmc&&r=1) |
|
I'm having the same problem. I don't understand much of this. How do I undo what happened in #3319? All I have is an |
|
Same issue. Wife mad. Awaiting a fix or way back to get out of the dog house. |
|
For those who need a "way back now": If you don't have a recent backup (?!?) .... 1 out of 10 or 20 boot attempts seems to be successfully here on my side. So perhaps you are lucky too. |
|
Having same issue, ODROID N2+ 4GB and eMMC 64GB. As prevoius poster said it seems to boot 12.2 sucessfully occasionally, so if your lucky then make sure you get a backup downloaded when it does. Is there a way to set it to always boot from the "good" 12.2 slot? |
|
Could you please all check for the eMMC manufacturer on the modules you are using? Either send a close-up picture of the module (ideally with the sticker removed) or check for one of the following:
We tried to test all possible eMMC cards with Hardkernel devs but there might still be some nuances we missed 😰 |
|
@sairon Here is a picture of the emmc, it had a large "64" sticker on it, when removed it has taken the detail with it
|
|
@dw01113 Thank you, it's a bit obscured by the glue residue but the QR code and marking placement corresponds with the Samsung eMMC chips. I wonder if we find any pattern with other reports 👀 |
|
@sairon Doh! Yes it was the glue, here's a cleaned up picture
|
|
Same problem here. Re-flashed 12.2 and still refusing to boot from eMMC 😟 |
|
As a quick update to above, I've reflashed 12.1 and now seems to be booting. Not sure if that was my fault with the flashing process for 12.2 or something else. |
|
I have a home assistant blue, and 12.3 flashed and works fine for me. I have a couple more laying around somewhere I can try if it would help. |
|
Mine still with sticker inside the case...but it looks like a Samsung with the QR code in the corner. |
|
Well...I've just been getting it ready to flash 12.2 to it, but I couldn't get it to boot into SPI mode, however it's now booting seemingly correctly into HA! I'm not getting the error messages I first posted above, there are other messages about "invalid checksum on backup superblock" but then moves switflty on to booting into HA command line. And I can now access it. I just don't know what's going on and whether it's going to be stable. It wouldn't boot at all last night, now it's OK but with those checksum errors. [EDIT : ah, found out the problem, it's not booting with my USB Z-Wave dongle plugged in, with the errors I first posted above. If I remove it, it boots. I had taken it out in order to open the case. So is it not an eMMC problem but a USB problem,, as noted in other reports here about 12.3 not booting?] |
@csimonosian but you are on 12.2 now not on 12.3 .... your original problem occurred after update from 12.2 to 12.3 .... so not think is related to USB, the USB dongle issue posted also is not on a Odroid N2 platform btw |
|
@smarthomefamilyverrips No, I'm still on 12.3. I didn't flash it back to 12.2 because I couldn't get it to boot into SPI mode, the switch acted as though it was still in eMMC mode and booted from eMMC. The fact remains, it boots without the USB dongle, but doesn't boot with it. |
@csimonosian Ha OK now I see I did read to quick and did miss read the "getting ready" as flashed 12.2 ... sorry my mistake 🫣 Let's see then if for more people unplug their USB device(s) solve their issues. |
|
I have USB Sonoff Zigbee coordinator and Edge TPU Coral USB. Still wouldn't boot (wasn't even posting) when I unplugged these to go to a monitor. But then, wouldn't post when I thought I'd flashed 12.2 either... |
I have this too. |
Thank you for this. Back up and running on 12.2! I am out of the dog house! I would say I got lucky between 10 and 20 boots it actually went on 12.3 got back up, reflashed 12.2, restored backup, Bazinga! |
|
I've tested this further, as mentioend I can boot into 12.3 by unplugging the USB Z-Wave dongle. Obviously, all my Z-wave devices are then Unavailable. But if I plug the dongle back in, it works and looks like nothing is wrong. Was there any change related to USB made in 12.3? As also mentioned, USB seems to be a frequent factor in the many reports of boot issues with 12.3. |
|
Just wanted to add that my situation does not seem to be affected by USB devices, after performing 12.3 upgrade and it failed, it will boot into 12.2 occasioanly (I didn't downgrade it must have not upgraded correctly) and work. So have left it running until hopefully a new version is available. |
|
Having the same problem. Won't boot. Says serverip not set and Config file not found. Cannot autoload with TFTPGET |
I have the exact same issue! Any solution please? |
As we don't have proper solution for #3319 and #3351 yet, revert to previous U-Boot which was proven working. This is intended as a workaround but as there's nothing in the latest U-Boot that will be really missed on N2, we can stay on the older version for the time being. This also means reverting the "40 MHz hack" back to the 24 MHz one. Since this patch only applies to N2 (meson gx), it can stay along the common hardkernel uboot patches.
As we don't have proper solution for #3319 and #3351 yet, revert to previous U-Boot which was proven working. This is intended as a workaround but as there's nothing in the latest U-Boot that will be really missed on N2, we can stay on the older version for the time being. This also means reverting the "40 MHz hack" back to the 24 MHz one. Since this patch only applies to N2 (meson gx), it can stay along the common hardkernel uboot patches.
|
Closing this in favor of #3227 which was probably never resolved fully. Currently the 12.4 release will contain a revert that will use a U-Boot version that was proven working until 11.5, however the U-Boot update will inevitably have to be done in the future, so we need to come up with a better fix. If you had issues with the ODROID-N2 booting with any of the 11.5+ releases with |
Describe the issue you are experiencing
Upgraded my Odroid to HAOS 12.3, now HA is not accessible.
What operating system image do you use?
odroid-n2 (Hardkernel ODROID-N2/N2+)
What version of Home Assistant Operating System is installed?
12.3
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
Cannot get to System Information because the system is unreachable.
Additional information
No response
The text was updated successfully, but these errors were encountered: