m.2 compatibility issue "Waiting for the Home Assistant CLI to be ready"

[metal-99]

Describe the issue you are experiencing

This is an update to the previous issue I posted:
#3866

I have since isolated the "Waiting for the Home Assistant CLI to be ready" issue to installing Home Assistant on an internal m.2 drive.

When I flash the Home Assistant image to the internal m.2 drive, then it just gets stuck on "Waiting for the Home Assistant CLI to be ready". and I cannot move past it regardless of what I try.

However, when I flash the Home Assistant image to a USB stick and boot up into that, Home Assistant gets past the "Waiting for the Home Assistant CLI to be ready", and allows it to start.

I can confirm that the internal m.2 SSD in the mini PC is working fine. I was able to install Ubuntu on it, and that is working with 0 issues. So this leads me to believe there is some sort of compatibility issue with installing Home Assistant on an m.2 drive, or at least an issue trying to install it on the m.2 drive I have?

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) and install on an m.2 drive 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

No response

[sairon]

There is timeout for the CLI, it should jump into the emergency console after 60 seconds since "Waiting for the Home Assistant CLI to be ready..." is shown. From there you should be able to check the logs using journalctl (or you can do it from another TTY like you did in the past). In your previous report you mentioned some systemd errors about the data partition and Docker daemon - those almost surely the reason for the behavior you're seeing - without Docker the HA CLI (and anything else) won't work. You should check the journalctl logs for the cause of the first failure, the other ones are just snowballing on that. If there's some HW compatibility issue, dmesg could contain something interesting too.