Compatibility issue (4 Intel 2.5 Gigabit Ethernet NIC)

[metal-99]

Describe the issue you are experiencing

I have been unable to to successfully install Home Assistant OS on a Protectli Vault VP2420 unit with 4 Intel 2.5 Gigabit Ethernet NIC ports and Intel Celeron J6412.

There appears to be some sort of conflict and compatibility issue, which I suspect is network related from the Intel 2.5 NIC ports.

I followed the Home Assistant OS using the official guide here (method 1): https://www.home-assistant.io/installation/generic-x86-64

I am able to boot into Ubuntu from a USB, open Firefox to navigate to the Home Assistant guide to download the image, and write it to the internal disk.

Upon successfully flashing the image to the disk, I then shut off the system, remove the USB when instructed, then boot the system up. When Home Assistant boots for the first time, it gets stuck at "Waiting for the Home Assistant CLI to be ready". I have let it sit for over an hour and it still persists.

Troubleshooting I have tried so far:
• Rebooting the system
• Re-installing Home Assistant: Booting into live Ubuntu off a USB again, downloading the Home Assistant image and flashing it to the internal disk
• Flashed Ubuntu to a different USB stick, booted into it, and downloaded/flashed Home Assistant image to the internal disk again
• Opening a new terminal area (Alt+F2) and running some commands to check network. Successfully shows enp1s0 Wired connection 1 is connected and shows the other 3 ethernet ports as not being connected.
• Tried changing the DNS servers to Cloudflare's
• Disabled IPv6
• Tried 2 separate networks in different locations with different network hardware
• Tried disabling IPv6 in the command line
• Tried ping google.com and it returns nothing, but nslookup google.com and curl https://www.google.com/ both return back just fine
• Tried this guide but there was no hassos-data-old, just hassos-data: https://community.home-assistant.io/t/waiting-for-home-assistant-cli-to-be-ready/635234/2
• Confirmed the connection, Home Assistant sees that an ethernet connection is active on port 1, and that the other 3 are inactive. I also tried other ethernet ports
• Tried accessing the Home Assistant web panel on another device on the network which does not load of course since the install has not completed

Waited, rebooted, kept waiting, after each change and I have had zero success with any of this. It still hangs on to "Waiting for the Home Assistant CLI to be ready". On both networks I have tried to boot into Home Assistant, my network is picking up the device as being part of the network, and also has assigned it a local IP. However when I check my home network administration, I notice there is 0 network activity coming from the Home Assistant/Protectli Vault, so this indicates that Home Assistant/Protectli Vault is not communicating with the internet, even though the Home Assistant guide does specify that upon the first boot, it must download additional components to setup Home Assistant.

Another odd thing to note is when I open another terminal area in Home Assistant while the "Waiting for the Home Assistant CLI to be ready" is showing (Alt+F2), and I try to ping any domain (e.g. ping google.com) it does not bring anything back, but nslookup and curl both return data, indicating that Home Assistant on the Protectli Vault is not actually communicating with the internet in all cases, only some. When I install then boot into Home Assistant after a fresh install, I check my router administration and there is 0 network activity coming from Home Assistant.

Something else to note is that I am using ethernet port 1 on the Protectli Vault and Home Assistant is seeing this as enp1s0 Wired connection 1.

I can confirm that the ethernet port(s) DO work on my unit as when I am booted into a live Ubuntu USB, it perfectly recognizes my network connection connected via port 1 ethernet. The internet works perfectly and I can successfully ping a domain in terminal. So this has to be some sort of setting and/or compatibility issue with Home Assistant with this Protectli Vault that I cannot figure out.

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

14.2

Did the problem occur after upgrading the Operating System?

No

Hardware details

VP2420 – 4x 2.5G Port Intel ® Celeron J6412

Intel Celeron® J6412 Quad Core at 2 GHz (Burst up to 2.6 GHz)
4 Intel® 2.5 Gigabit Ethernet NIC ports
M.2 SATA SSD Slot (Note: This device does not support NVMe drives)
16 GB eMMC module on board
Intel® AES-NI support
Fanless and Silent

Full specs:
https://ca.protectli.com/product/vp2420/

Steps to reproduce the issue

1. Follow official install guide for generic x86 systems (method 1) https://www.home-assistant.io/installation/generic-x86-64

Anything in the Supervisor logs that might be useful for us?

Cannot access them. When I try running the command, it endlessly loads and loads nothing

Anything in the Host logs that might be useful for us?

Cannot access them. When I try running the command, it endlessly loads and loads nothing

System information

No response

Additional information

Another thing I noticed is while pinging a domain does not work e.g. ping google.com brings back "google.com is alive?", nslookup successfully works, curl successfully works.

Thought I would also mention when booting I saw some brief errors being displayed about dependencies, not sure if it is relevant or not but thought I would show them here just in case. Apologies for any typos in the logs (used AI to convert the image I took of my screen to text!)

journalctl -f I grep -1 "dependency"
Feb 09 19:17:37 homeassistant systemd[1]: Dependency failed for File System Check on /dev/disk/by-label/hassos-data.
Feb 09 19:17:37 homeassistant systemd[1]: [email protected]: Job systemd-fsck@dev-disk-byx2dlabel-hassos\x2ddata.service/start failed with result 'dependency'. Feb 09 19:17:37 homeassistant systemd[1]: Dependency failed for HassOS data resizing. Feb 09 19:17:37 homeassistant systemd[1]: hassos-expand.service: Job hassos-expand.service/start failed with result 'dependency'.
Feb 09 19:17:37 homeassistant systemd[1]: Dependency failed for HassOS data partition.
Feb 09 19:17:37 homeassistant systemd[1]: Dependency failed for Grow File Systen on /mnt/data.
Feb 09 19:17:37 homeassistant systemd[1]: [email protected]: Job [email protected]/start failed with result 'dependency'.
Feb 09 19:17:37 homeassistant systemd[1]: Dependency failed for Docker persistent data.
Feb 09 19:17:37 homeassistant systemd[1]: Dependency failed for Docker Application Container Engine.
Feb 09 19:17:37 homeassistant systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'
Feb 09 19:17:37 homeassistant systemd[1]: var-11b-docker.nount: Job var-11b-docker.nount/start failed with result 'dependency'.
Feb 09 19:17:37 homeassistant systemd[1]: mnt-data.mount: Job mnt-data.mount/start failed with result 'dependency'.