Installation problem on X-86, can't get commnication using homeassistant.local:8123 or IP address:8123

That’s because it is formatted as EXT4, most common in Linux systems which Home Assistant is. As I said before, if you run Partition Manager you should be able to erase existing partitions and repartition it as NTFS and start over.

1 Like

Thanks. I totally missed that.

BTW, there are 256mg M.2 SATA SSD’s on Amazon for about $20 US, but they aren’t the best brands.

I don’t think it is that. Checked my running instance

CONTAINER ID   IMAGE                                                        COMMAND               CREATED        STATUS                PORTS                                                 NAMES
d6eae069cc6b   ghcr.io/home-assistant/raspberrypi2-homeassistant:2023.8.1   "/init"               17 hours ago   Up 14 hours                                                                 homeassistant
d0a43378d789   3983e8d8/armv7-addon-letsdnsocloud:1.1                       "/init /run.sh"       3 days ago     Up 3 days                                                                   addon_3983e8d8_letsdnsocloud
4497b31ab884   ghcr.io/hassio-addons/motioneye/armv7:0.19.1                 "/init"               5 days ago     Up 5 days                                                                   addon_a0d7b954_motioneye
abcd15fc8631   sabeechen/hassio-google-drive-backup-armv7:0.111.1           "python3 -m backup"   5 days ago     Up 5 days             0.0.0.0:1627->1627/tcp, :::1627->1627/tcp, 8099/tcp   addon_cebe7a76_hassio_google_drive_backup
eeeecae9ce83   homeassistant/armv7-addon-configurator:5.6.0                 "/init"               5 days ago     Up 5 days (healthy)                                                         addon_core_configurator
3db68678fbca   ghcr.io/home-assistant/armv7-hassio-multicast:2023.06.2      "/init"               5 days ago     Up 5 days                                                                   hassio_multicast
706c651b78cb   ghcr.io/home-assistant/armv7-hassio-audio:2023.06.0          "/init"               5 days ago     Up 5 days                                                                   hassio_audio
41c9f34bcefb   ghcr.io/home-assistant/armv7-hassio-dns:2023.06.2            "/init"               5 days ago     Up 5 days                                                                   hassio_dns
4df6bca1433d   ghcr.io/home-assistant/armv7-hassio-cli:2023.06.0            "/init"               5 days ago     Up 5 days                                                                   hassio_cli
4cf4ffba3380   ghcr.io/home-assistant/armv7-hassio-observer:2023.06.0       "/usr/bin/observer"   4 weeks ago    Up 5 days             0.0.0.0:4357->80/tcp, :::4357->80/tcp                 hassio_observer
dd18e39f852c   ghcr.io/home-assistant/armv7-hassio-supervisor:latest        "/init"               4 weeks ago    Up 5 days                                                                   hassio_supervisor
:~#

Thank you. If you have an idea what the problem is, please let me know. As it stands, with the help I got from stevemann, I plan to re-etch the SDD, probably tomorrow. Hopefully that will work.

Thanks again. After your telling me it is EXT4, the lack of disk access makes a lot more sense. I’ll probably install the free version of Partition Manager or AOMEI and use that to reformat the disk tomorrow, then re-etch.

Not mentioned yet in this topic, but since you seem to have access to the console, try

ha core repair

and

ha core check

This might help:

https://www.howtogeek.com/235824/how-to-clean-a-flash-drive-sd-card-or-internal-drive-to-fix-partition-and-capacity-problems/

Pay attention to the warnings. You can easily erase a Windows drive if you’re not careful.

Thank you. I will check it out tomorrow when I work on the SSD.

ha core repair (used “core rebuild”):

“Processing… Done.
Error: unknown error, see supervisor”

In the “supervisor logs” error listed as:
ERROR (main thread) [supervisor.utils] Can’t execute rebuild while task is in progress

ha core check

“Processing… Done.
Command completed successfully.”

In the “supervisor logs” the apparent result listed as:
INFO (MainThread) [supervisor.homeassistant.core] Home Assistant config is valid

Does this mean I could somehow turn off all tasks and rebuild and possibly repair without the re-etch?

ha supervisor repair

?

ha supervisor repair
“Processing… Done.
Command completed successfully.”

Supervisor logs: [supervisor.core] Finished repair of supervisor environment

Connecting still doesn’t work for 8123 (but does for 4357) both before and after restart.

It should not do that, it seems supervisor can’t pull the complete home assistant docker.

ha dns options --servers dns://1.1.1.1
ha dns restart

and then wait a little bit.

Try

docker restart hassio_supervisor

I really think it’s time to reflash the SSD. A simple X86-64 installation should just simply work.

Thanks, I welcome all suggestions.

ha dns options --servers dns://1.1.1.1
ha dns restart

This said it completed the request, but it didn’t help.

I agree. I am working on it now.

SUCCESS!! I got the disk reformatted and re-etched a new download of HA and it appears to work! The first time, I could not see the disk on the “Safe Removal Tool” after the etching, so I just unplugged it. This time I shut down my computer before unplugging. I don’t know if that mattered, but it appears to work. I really all the help you folks provided and I learned a lot from you all.

Don’t worry, I’m sure I’ll have more questions as I go along.

2 Likes

Fwiew, good this god solved!

@DocE: please take the time to mark the answer as solution, you do that by selecting the three dots under the post:

image

Then select the check box:

image

By doing so this can be useful to other users as well and prevents that someone else steps in to try to help you.

Done. Thanks for letting me know to do it.

1 Like

You won’t because it is now a Linux formatted drive and Windows is too stupid to know this.