#Fresh install, sticks on "Waiting for the Home Assistant CLI to be ready..."

1 messages · Page 1 of 1 (latest)

trim brook
#

Installing on a Dell Wyze 5070 with 275 GB Crucial MX300

$ curl -OL https://github.com/home-assistant/operating-system/releases/download/16.2/haos_generic-x86-64-16.2.img.xz

$ sha256sum haos_generic-x86-64-16.2.img.xz
00d1b7da66edacb3f6bdde4e39bdbacf8eb1685ba44ddc827771157c83cf4144  haos_generic-x86-64-16.2.img.xz

$ xzcat haos_generic-x86-64-16.2.img.xz | sudo dd of=/dev/sda bs=4M status=progress
6371221504 bytes (6.4 GB, 5.9 GiB) copied, 14 s, 455 MB/s
0+237870 records in
0+237870 records out
6442450944 bytes (6.4 GB, 6.0 GiB) copied, 17.4654 s, 369 MB/s

All looks good so far.

It boots through the familiar job sequence though it seems to time out with
"A start job is running for /dev/disk/by-label/hassos-data ( ... / 1min 30s)"

Probably /mnt/lib/systemd/system/mnt-data.mount:What=/dev/disk/by-label/hassos-data

I see something like "Failed to start the containerd container runtime" just before it cuts over to the "Waiting for the Home Assistant CLI to be ready...." message.

Then the screen stays stuck there. No combination of ctrl, alt, F1-F12 gets me to a login, nor does hopefully typing "login".

The machine has run HAOS off an older SSD and boots Debian Trixie.

Running Debian I'm not seeing a partition label with blkid or lsblk that would satisfy that mount request, though it looks like it should be associated with sda8 from the GPT.

I've tried flashing the release image twice with the same results.

violet vine
#

I would install ProxmoxVE and VM HAOS, making life easier 😉 (if having 8gb ram minimum)

#

haos is a proper OS and should not be installed over debian.\

#

aah debian to check only..

trim brook
#

That's correct, HAOS is intended to be bare metal booting off sda

When I boot Debian off a USB stick to examine what is there I see

jeff@trixie-stick:~$ sudo blkid /dev/sda*
/dev/sda: PTUUID="cad9f60a-360e-42fc-8e8c-9598e597314f" PTTYPE="gpt"
/dev/sda1: SEC_TYPE="msdos" LABEL_FATBOOT="hassos-boot" LABEL="hassos-boot" UUID="1D1D-30A3" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="hassos-boot" PARTUUID="b3dd0952-733c-4c88-8cba-cab9b8b4377f"
/dev/sda2: BLOCK_SIZE="131072" TYPE="squashfs" PARTLABEL="hassos-kernel0" PARTUUID="26700fc6-b0bc-4ccf-9837-ea1a4cba3e65"
/dev/sda3: UUID="05e03256-e9d2-49fd-a330-1c9b370ba0d1" BLOCK_SIZE="4096" TYPE="erofs" PARTLABEL="hassos-system0" PARTUUID="8d3d53e3-6d49-4c38-8349-aff6859e82fd"
/dev/sda4: PARTLABEL="hassos-kernel1" PARTUUID="fc02a4f0-5350-406f-93a2-56cbed636b5f"
/dev/sda5: PARTLABEL="hassos-system1" PARTUUID="a3ec664e-32ce-4665-95ea-7ae90ce9aa20"
/dev/sda6: PARTLABEL="hassos-bootstate" PARTUUID="33236519-7f32-4dff-8002-3390b62c309d"
/dev/sda7: LABEL="hassos-overlay" UUID="3b59c3b5-e001-4642-9f0a-f7065902a66f" BLOCK_SIZE="1024" TYPE="ext4" PARTLABEL="hassos-overlay" PARTUUID="f1326040-5236-40eb-b683-aaa100a9afcf"

Though there is sda8 in the GPT, it apparently was never initialized.

tight quarry
#

Check lsblk -po +FSTYPE,LABEL,MODEL. The commands look good to me. I'd recommend Proxmox VE too 🙂

trim brook
# 
jeff@trixie-stick:~$ lsblk -po +FSTYPE,LABEL,MODEL
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS FSTYPE   LABEL          MODEL
/dev/sda      8:0    0 256.2G  0 disk                                     Crucial_CT275MX300SSD4
├─/dev/sda1   8:1    0    32M  0 part             vfat     hassos-boot
├─/dev/sda2   8:2    0    24M  0 part             squashfs
├─/dev/sda3   8:3    0   256M  0 part /mnt        erofs
├─/dev/sda4   8:4    0    24M  0 part
├─/dev/sda5   8:5    0   256M  0 part
├─/dev/sda6   8:6    0     8M  0 part
├─/dev/sda7   8:7    0    96M  0 part             ext4     hassos-overlay
└─/dev/sda8   8:8    0 255.5G  0 part
/dev/sdb      8:16   1  14.9G  0 disk                                     Extreme
├─/dev/sdb1   8:17   1   512M  0 part /boot/efi   vfat     trixie-efi
└─/dev/sdb2   8:18   1  14.4G  0 part /           ext4     trixie-root
tight quarry
#

It's possible the partition will be properly formatted during the first boot. Can't test right now. I only have this old output which lacks information: #installation-archived message

violet vine
#

yes at first boot it will resize partition, can take a while depending on storage.

violet vine
tight quarry
trim brook
#

I agree that if the partition isn't labeled, the referenced device isn't going to be generated.

I'll try it again from fresh image in case interrupting the boot did something. The first time was about an hour and a half that I had been away from the machine.

The Dell doesn't have any other job in life. It is an aging, low-TDP Pentium 5005 with 8 GB of soldered-in RAM and a couple of antennas stuck on the back for Bluetooth listening. All in all a reasonable deal at $50.

If I do go with Proxmox VE, the warnings at https://www.home-assistant.io/installation/generic-x86-64/#install-home-assistant-container about not being able to run Add-Ons is not a significant limitation?

tight quarry
#

You can also import the qcow2 via qm disk import or use a "helper" script but I don't like them. Above is fairly painless and all GUI based.