HASSOS freeze

Installation
1

I have a RPI4 8GB with a 5v 2A power supply, i bought an USB SSD to run HASSOS.

I don’t have an HDMI converter, so i used the UART to read informations since I read there is no fallback config for ethernet with a static ip and I can only directly connect to a pc.

The problem is that the device never starts, what i read in the UART is only the following informations.

U-Boot 2024.01 (Mar 13 2024 - 12:13:26 +0000)

DRAM:  947 MiB (effective 7.9 GiB)
RPI 4 Model B (0xd03115)
Core:  209 devices, 15 uclasses, devicetree: board
MMC:   mmcnr@7e300000: 1, mmc@7e340000: 0
Loading Environment from nowhere... OK
In:    serial,usbkbd
Out:   serial,vidconsole
Err:   serial,vidconsole
Net:   eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_send_command: MMC: 1 busy timeout increasing to: 200 ms.
sdhci_send_command: MMC: 1 busy timeout increasing to: 400 ms.
sdhci_send_command: MMC: 1 busy timeout increasing to: 800 ms.
sdhci_send_command: MMC: 1 busy timeout increasing to: 1600 ms.
sdhci_send_command: MMC: 1 busy timeout increasing to: 3200 ms.
sdhci_send_command: MMC: 1 busy timeout.
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_send_command: MMC: 1 busy timeout.
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_send_command: MMC: 1 busy timeout.
Card did not respond to voltage select! : -110
** Booting bootflow 'usb_mass_storage.lun0.bootdev.part_1' with script

Device 0: Vendor: SSK Port Rev: W081 Prod: able SSD 256
            Type: Hard Disk
            Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
loading env...

usb read: device 0 block # 1214464, count 32 ... 32 blocks read: OK
Working FDT set to 2eff2400
Trying to boot slot A, 2 attempts remaining. Loading kernel ...
25963008 bytes read in 450 ms (55 MiB/s)
storing env...

usb write: device 0 block # 1214464, count 32 ... 32 blocks written: OK
Starting kernel
Moving Image from 0x80000 to 0x200000, end=1be0000
## Flattened Device Tree blob at 2eff2400
   Booting using the fdt blob at 0x2eff2400
Working FDT set to 2eff2400
   Using Device Tree in place at 000000002eff2400, end 000000002f002f1c
Working FDT set to 2eff2400

Starting kernel ...

After more than 10 minutes nothing moves.
How can I proceed?

2

SSD may be exceeding power supply limits of the RPi. Use a powered USB hub.

1 Like
3

I’m with Max. With as little as you’ve given. Ssds are one of the top reasons to overdraw current on a pi.

Also get an hdmi cable and plug tattthing into a monitor. I guarantee the system console is staring at you right now with the error message - my bet is an undervolt and disk read error.

4

Tried with a DUB-H7 with an external power supply of 5V 3A. RPI4 plugged in the other 5V 2A power supply. Same result.

On the other side I tested Raspberry PI OS (always from Raspberry pi imager 1.8.5) with the same hardware (SSD+RPI4) without the hub and it worked, i logged in using console without problems.

Isn’t there a way to enable a verbose output in the console to understand what went wrong?

Thanks

PS: in next days i’ll have the hdmi adapter but now i haven’t got it.

5

It doesn’t matter if you have an external 10a power supply. The Pi is hard limited at usb current unless you inject power behind the USB bus. (dumb choice but I see why they did it) short version of it is if you have power issues move everything you can to an external powered usb bus to offload power.

That said. The Pi os running on the same SSD? It smells (completely unconfirmed) as If it can’t find the bootloader but without seeing it?! (and not really nothing easier than borrowing an hdmi, many of us forget normal humans don’t have six ina drawer…)

6

I’m not understanding, i tried with two Power supply:

2A connected to rpi
3A connected to the dub-h7

An USB cable connected the rpi to the USB hub
The USB SSD was connected to the hub, other ports of the hub was free.

That’s not explaining why with a different os all works well

1 Like
7

What instructions did you follow to build Home Assistant on the SSD?

8

SSD Is an USB SSD as in the First link.

Installed Raspberry Pi imager, selected hassos and the SSD.
Clicked next two or three times

Edited the txt to enable uart

Nothing more

1 Like
9

You’re correct that would seem to eliminate that issue as the culprit. I had an issue once with mine not booting SSD right after I switched and out of a guess rewroethe bootloader.

(instructions were here: Switch from SD card to SSD for Home Assistant on a Raspberry Pi 4)

And that fixed me up.

Maybe?

10

Have you been able to boot the RPi4 from an SD card?

Even though you can boot a Pi OS from the SSD, I would double check that the boot loader eeprom is up-to-date as per these instructions.

I would also echo @NathanCu suggestion to connect a monitor and keyboard to diagnose.

1 Like
11

Sorry, I was busy typing away and didn’t see your reply before I posted.

1 Like
12

Same issue with HASSOS in a SD card.

Update boot-usb from rpi imager, same result

microHDMI adapter will arrive in 2 days, so I have to wait to see if there is some output on the screen

13

It wasn’t freezed, only not showing anything on uart.

With a display I can login and setup up the network but, unfortunatly, I can’t login on web page 8123. The Observer at 4357 is working but I have ERR_CONNECTION_REFUSED when I try 8123 .

What should I check?

Thanks

14

Common tasks - Operating System - Home Assistant.

ha core check 

ha core rebuild 

ha supervisor repair
15

Copying from the screen

ha > core check 
Processing ... Done.

Error: Can't execute command: 500 Server Error for http+docker://localhost/v1.43 ..... : Internal Server Error ("Get "https://ghcr.io/v2/": dial tcp: lookup ghcr.io: Temporary failure in name resolution")

ha > core rebuild 
Processing ... Done.

Error: Another job is running for job group home_assistant_core

ha > supervisor repair 
Processing ... Done.

Command completed successfully
16

and now

ha host reboot

and see if you can get in.

17

Now when it starts it says:

Error returned from Supervisor: System is not ready with state: setup

image

there is a long log, after that but it seems truncated. Does it help?

18

That problem was caused by the absence of internet access. After connecting to a different network with internet access the web page loads, but another problem occurs:

image
image576×797 34.2 KB

I can’t attach logs: s6-rc: info: service s6rc-oneshot-runner: startings6-rc: info: service s6rc-on - Pastebin.com