Closed BarBaar44 closed 9 months ago
Since the behavior you describe is rather erratic, my guess is that the eMMC card/module is somehow damaged. The other, less likely scenario, is that something wrong is with your ODROID itself. ODROID N2+ has an SD card slot as well, could you try copying the system image to that and try again?
Ok...
Using a 64HB Samsung SD:
Repeated with a different SD-card -> Same result Repeated with a different image (non HA): works
Used a different converter (USB to SD) to copy the image to the SD-card (64Gb one) --> Stuck at "Processing new Disk Device" (same as (5)).
To summarize:
--> I noticed I am missing a boot.ini in the image. See here. Not the expert, but just noticed this.
I have no indications there is a hardware problem:
But I do run out of options to try and get it to work :/
Switched the Odroid to SPI-boot
That is wrong. HAOS on N2 does not use Petitboot but U-Boot in the first partition of the SD card/eMMC, so the boot switch should be set to MMC no matter whether you're booting from an eMMC or SD card. See the diagram in ODROID wiki. That also answers why there's no boot.ini
.
Tnx..
The system seems to be working with the SD-Card. Guess the eMMc is bad. Weird as it is a new one.
Closing this one. Thnx for your support @sairon
@sairon I dont think this is an issue with this guys MMC port, theres 2 more issues raised with a bug to do with N2+ not booting.
see:
@piercy thanks for connecting these issues, I agree this seems all to be related. Let's track it in #3227 as this seems to be the issue with most information at this point.
Describe the issue you are experiencing
Hardware
New hardware:
Old Hardware:
Issue
Fresh installation of haos 11.5 fails with a blank screen and no further system action
What operating system image do you use?
odroid-c2 (Hardkernel ODROID-C2)
What version of Home Assistant Operating System is installed?
n.a.
Did you upgrade the Operating System.
No
Steps to reproduce the issue
Second scenario is upgrading to haos 11.5 from existing install. Leads to same situation. See below for details and steps taken ...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
No response
Additional information
dd if=<image> of=<disk> bs=4M
Same result. So ruled out hardware issues and Etcher issues.Working with dd from now on..
dd if=/dev/zero of=/dev/disc bs=4M
Trying again:
One day later...
Also managed to boot using haos 10.5. But after the initial boot, a reboot fails. Seems I am stuck here as I haven't found an image yet that allows the system to reboot..