#Rpi3b+ Fresh installation of HAOS, can't access the UI

1 messages · Page 1 of 1 (latest)

fading hedge
#

Hi all!

I've been running my smart home for 8 years now on a Raspberry Pi 3b+ (Supervised installation in a Docker container) and all was fine until my ecosystem grew - the Rpi3b+ became slow, even though I increased the swap to 2 GB, the responsiveness was not what I would expect from a modern smart home system. I upgraded today to Rpi5 and it's been great so far.

I want to repurpose the Rpi3b+ and install it in my caravan to monitor a couple of sensors and my solar system - nothing too fancy - I am sure that 1 GB RAM with 2 GM more swap would handle that just fine, given that I have been running it with 100s of devices in my home for years.

I did a fresh install via Raspberry Pi imager on my USB HDD and booted fine, it downloaded all the packages and updates, however, when I get to the Create user screen it just stops. Has anyone experienced this issue before?

#1284966353798697001

limpid furnace
#

make sure to choose a model with at least 2 GB of RAM)
https://www.home-assistant.io/installation/raspberrypi/
Can you tell me the username you used? I remember there were some strange issues soe time ago related to that.
Can you connect a keyboard and monitor and check the logs?

fading hedge
#

Yeah, I guess I will do that first to check what's in the logs and then come back. I don't see a reason why a barebones HAOS shouldn't run on 1 GB of RAM with 1-2 GB of swap. Yes, it won't be snappy, but it should run just fine.

#

P.S. I don't even get to choose the username. It stops right where the screenshot is

fading hedge
#

Nor the mDNS name

fading hedge
#

There was a hostname conflict. I have two instances and both had "homeassistant" hostname.
I fixed that and restarted both instances on the same network, but that shouldn't have mattered anyways as I am trying to access the instance via IP.
I can issue commands in the CLI, all logs look good, but the UI is still inaccessible.

#

Any ideas?

#

Rpi3b+ Fresh installation of HAOS, can't access the UI

limpid furnace
#

What does ha network info and ha core logs and ha supervisor logs say?

#

You can also enter login and then try ss -lntp.

fading hedge
#

Just started fresh and this is what I see in the supervisor logs while the UI is stuck on Create user page

limpid furnace
#

Oof. Do you have a different/faster storage medium you could test with?

fading hedge
#

Faster than SSD on a USB2 interface? I could try with an SD card, but not sure if that is any faster 🙂

limpid furnace
#

Might also be caused by something else but this is a concerning issue.
You can see if it's RAM related by entering login and then free -h. Check ha host logs -vf for more host/kernel logs.

fading hedge
#

I will try that now, let me check if it is still hung ... if it is, I will reboot and check the logs

#

I rebooted since it was not responding. 117 MB free RAM and 299 MB free swap

limpid furnace
#

You have 625MiB "free", actually, so that looks fine. For now.

fading hedge
#

No errors in the host logs

limpid furnace
#

I'd follow the supervisor logs via ha host supervisor logs -vf and see what it's doing. Maybe it can recover. The initial setup is mostly downloading and extracting all the docker images. It might have been overwhelmed by that. This hung task message should not ever happen though.

fading hedge
#

The issue is that after the hung and the subsequent "hard" restart (e.g. power cycle) it never goes back to the UI. It refuses to connect. I just have access to the CLI via the Raspberry Pi. Is there a way to "restart" the onboarding process and the account creation or to restart the UI part?

#

The initial setup process hangs -> power cycle due to unresponsiveness -> can't re-enter the initial setup process and the UI is not available

limpid furnace
#

What's the supervisor and core logs say?

#

You can try something like ha supervisor repair or ha core rebuild. To restart the whole thing you wan do ha os datadisk wipe but that's destructive.

fading hedge
#

Nothing disturbing in the supervisor logs imho. I am going to rebuild and repair it to see if that makes a difference

limpid furnace
#

A bit hard to read but it says core crashed. Check core logs.

fading hedge
#

When trying to rebuild the core it says that it is still in setup state

limpid furnace
#

What's the core logs say?

fading hedge
#

And the supervisor logs says that Home Assistant has crashed ...

limpid furnace
#

I remember that version compare issue. I have no clue how I solved it though :<

#

If it's not too much work I'd just reflash and let it stay alone for a little bit.

fading hedge
#

I resolved the version compare error by deleting .HA_VERSION file

#

However I now have other errors. I think that some initialization script was interrupted and now some files are either corrupted or missing

#

Do you know of a way to increase the swap from the CLI right after the flashing, but before the initi

limpid furnace
#

Not at the top of my head.