XU4 - install and run Hass.io from eMMC

[johnjoemorgan]

Hi

Is it possible to run the XU4 image of Hass.io from the eMMC? If so how?

Thanks

[igorpec]

Hi

Is it possible to run the XU4 image of Hass.io from the eMMC? Is so how?

Thanks

I have no idea about the state of Hass.io image ... but as you were already told - probably the best installation of hass.io will be running their Docker instance.

Very simple:

1. Download image and burn directly to eMMC. Boot from eMMC and do first run, create user, ... (if you don't have eMMC card reader, boot from SD card and use nand-sata-install utility ... after transfer is done, power down, switch to eMMC boot and proceed booting from eMMc)
2. Run armbian-config -> software -> 3rd party -> Hass.io

[johnjoemorgan]

The other thread was asking a similar but different question .. but noted.

"Download image and burn directly to eMMC." Would you have a link on hand? Will have another bash at it tomorrow

[igorpec]

The other thread was asking a similar but different question .. but noted.

"Download image and burn directly to eMMC." Would you have a link on hand? Will have another bash at it tomorrow

You don't have this?


https://www.hardkernel.com/shop/emmc-mo ... s-upgrade/

Image(s): https://www.armbian.com/odroid-xu4/

[mad_ady]

When burning images it's best to use etcher.
I'll give the official images a try hopefully tomorrow or on friday...

[johnjoemorgan]

I have the Hardkernel burner and use Etcher but can't for love nor money find the Docker Image for XU4/Docker/Hass.io

Maybe I'm 'search blind' ;-0

[johnjoemorgan]

LOL - OK So I need my eyes tested. I have tried the Stretch and it failed. Can't remember the reason right now but will go for a clean (chip and brain) install again tomorrow

Thanks again guys

[igorpec]

I have tried the Stretch and it failed.

armbian + apt update and upgrade + armbian-config -> software -> softy -> Hass.io (you don't need to install docker separately. everything is done in this process)

Once installed, you need to wait some time before Hass service is up. Several minutes.

[johnjoemorgan]

@iporpec

**Many thanks** - followed your instructions and everything is installed.

Docker (and so Hassio) are on IP 172.17.0.1

I have tried to find info on this but, how do we get that to 192.168.x.x

[igorpec]

@iporpec

**Many thanks** - followed your instructions and everything is installed.

Docker (and so Hassio) are on IP 172.17.0.1

I have tried to find info on this but, how do we get that to 192.168.x.x

Service becomes available after several minutes on http://192.158.x.x:8123 Did you wait long enough?

[johnjoemorgan]

Yep It was running for a few hours last night while I tried to figure things out.

Network info is:

docker0 - 172.17.0.1
enx001e06366682 - 192.168.0.21
hassio - 172.30.32.1

==============

So just this second I had to turn on some lights connected to my current set up, I noticed that the URL was:

192.168.0.5:8123/lovelace/default_view

I had been trying this for the XU4

192.168.0.21:8123

trying

192.168.0.5:8123/lovelace/default_view

which resolved to

http://192.168.0.21:8123/frontend_es5/onboarding.html

And that sound you heard? That was my palm hitting my forehead!

So, forgoing my newbie mistakes, the process is practically effortless and recommended against the other installs I've been trying and reading about

@iporpec ... You're on my Christmas card list mate! Thanks!

I'll start migrating from my old (Cubie Truck) install next week and report back on the performance/stability differences

[igorpec]

Hehe, you are welcome.

the process is practically effortless

Exactly That's why I was surprised you have reported problems at first.

[johnjoemorgan]

OK Found a problem straight off.

No add-ons are available and I see the error:

“[hassio.arch] Can’t detect underlay machine type!”

The solutions is here:

https://community.home-assistant.io/t/s ... on/83636/5

But as we pulled the image from a 'built-in' script how can we apply that? Is there another way?

I'll be needing MQTT, LetsEncrpt etc.

NOTE - I did update to the latest Hass.io version but that should not have created this problem. Should I reinstall?

[johnjoemorgan]

**Update** got some time today to come back to this.

Installed Armbian (clean install from flash)

Image(s): https://www.armbian.com/odroid-xu4/

then ref:

https://github.com/home-assistant/hassi ... all-hassio

Installed/checked:

docker-ce
bash
jq
curl
avahi-daemon
dbus
apparmor-utils
network-manager

Then:

Run as root (sudo su):

curl -sL https://raw.githubusercontent.com/home- ... io_install | bash -s -- -m odroid-xu

****

This now gives us a working Hassio with add-ons

[mad_ady]

I tried to run the hass.io image on an orange emmc and you're right - it fails to boot. Something is broken in their u-boot:

Code: Select all

MMC Device 0 (eMMC): 29.1 GiB
Info eMMC rst_n_func status = enabled
Card did not respond to voltage select!
mmc_init: -95, time 11
*** Warning - bad CRC, using default environment

Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
** Invalid partition 2 **

Any ideas where to report the issue for hass.io?

[mad_ady]

https://github.com/home-assistant/hassio/issues/951

[millerce]

OK, here's the problem as I see it. The Hass.io images are flashed with etcher- doing so kills everything on the eMMC including the hidden boot partition. From what I can see, the XU3/XU4 eMMC Bootloader Recovery also kills everything on the eMMC. Is there a tool out there that can flash an image to a partition?

[mad_ady]

Etcher (and dd) can't normally write to the hidden emmc blocks.

[igorpec]

OK, here's the problem as I see it. The Hass.io images are flashed with etcher- doing so kills everything on the eMMC including the hidden boot partition. From what I can see, the XU3/XU4 eMMC Bootloader Recovery also kills everything on the eMMC. Is there a tool out there that can flash an image to a partition?

You can restore boot loader (if this is the problem???) by booting armbian form SD card. Than you ran nand-sata-install utility and update boot loader. Then install system to it or unplug eMMC and flash OS directly to it.

In case this doesn't work, there could be an hw issue.

[cseyler]

I've the same issue.

If I restore the emmc with the SD Card + emmc procedure, the odroid boot correclty to android. But once i write the hassio image either with etcher or win32image (ordoid version), the odroid does not boot anymore (the led stay blue).
The hassio image seems overwrite the emmc bootloader, adn the recovery procedure overwite the entire image.

[igorpec]

The hassio image seems overwrite the emmc bootloader

That's why its recommended to use a Docker image (armbian-config -> software ...) ... on top of OS that supports hardware well.

[r4nd0m]

this works perfectly fine https://github.com/home-assistant/hasso ... oid-xu4.md