Kernel version | Linux DoBox 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1~bookworm (2026-03-11) aarch64 GNU/Linux
Architecture | arm64
SBC model | RPi 3 Model B+ (aarch64)
Power supply used | POE
SD card used | SSD via USB
Additional Information (if applicable)
Software title | HomeAssistant
Updating
I don’t think a fresh install would install penv first
← If you sent a “dietpi-bugreport”, please paste the ID here →
Bug report ID | echo $G_HW_UUID
\[ INFO \] DietPi-BugReport | Generating informative command outputs, please wait...
\[ OK \] DietPi-BugReport | Packing upload archive
\[FAILED\] DietPi-BugReport | The bug report upload archive appears to be unexpected large. Please inspect and in case clean up the locations to be uploaded, as their size should never be that large:
CMD_OUT.txt
G_EXEC_ERROR_REPORT
/var/log
/boot/firmware/config.txt
/boot/firmware/cmdline.txt
/boot/boot.ini
/boot/boot.scr
/boot/dietpiEnv.txt
/boot/armbianEnv.txt
/boot/dietpi.txt
/boot/dietpi
/var/lib/dietpi
/var/tmp/dietpi
/run/dietpi
/etc/bash.bashrc
/etc/bashrc.d
/root/.bashrc
/etc/profile
/etc/profile.d
/root/.profile
/etc/X11/xorg.conf
/etc/X11/xorg.conf.d
/etc/asound.conf
/etc/network/interfaces
/etc/network/interfaces.d
/etc/wpa_supplicant/wpa_supplicant.conf
/etc/fstab
/etc/sysctl.conf
/etc/sysctl.d
/etc/systemd/system
/etc/apt/sources.list
/etc/apt/sources.list.d
/etc/apt/preferences
/etc/apt/preferences.d
/etc/apt/apt.conf.d
/etc/apt/keyrings
This is where I am no longer able to use the device.
I can not open another ssh at this point but I have another ssh opened with htop running and that seems to be showing as active. The uptime timer is counting up like normal. (Picture attached).
root@DoBox:\~# dietpi-software reinstall 157
\[ OK \] DietPi-Software | Initialised database
\[ OK \] DietPi-Software | Reading database
DietPi-Software
─────────────────────────────────────────────────────
Mode: Automated reinstall
\[ OK \] DietPi-Software | Reinstalling Home Assistant: Open source home automation platform
\[ OK \] DietPi-Software | DietPi-Userdata validation: /mnt/dietpi_userdata
DietPi-Software
─────────────────────────────────────────────────────
Step: Checking for conflicts and missing inputs
DietPi-Software
─────────────────────────────────────────────────────
Step: Checking for prerequisite software
\[ INFO \] DietPi-Software | uv will be installed
\[ OK \] DietPi-Software | mkdir -p /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads /var/www /opt /usr/local/bin
\[ OK \] DietPi-Software | chown dietpi:dietpi /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
\[ OK \] DietPi-Software | chmod 0775 /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
\[ SUB1 \] DietPi-Services > stop
\[ OK \] DietPi-Services | stop : cron
\[ OK \] DietPi-Services | stop : webmin
\[ OK \] DietPi-Services | stop : home-assistant
\[ OK \] DietPi-Services | stop : filebrowser
\[ OK \] DietPi-Services | stop : lazylibrarian
\[ OK \] DietPi-Services | stop : kavita
\[ OK \] DietPi-Services | stop : nginx
\[ OK \] DietPi-Services | stop : php8.2-fpm
\[ OK \] DietPi-Services | stop : mariadb
\[ OK \] DietPi-Services | stop : redis-server
\[ OK \] DietPi-Services | stop : proftpd
\[ INFO \] DietPi-Software | Skipping APT update, as last call was less than an hour ago and neither sources lists nor architectures changed since.
DietPi-Software
─────────────────────────────────────────────────────
Step: Installing uv: Extremely fast Python package and project manager
\[ OK \] DietPi-Software | cd /tmp/DietPi-Software
\[ OK \] DietPi-Software | curl -sSfL https://github.com/astral-sh/uv/releases/download/0.11.7/uv-aarch64-unknown-linux-gnu.tar.gz -o uv-aarch64-unknown-linux-gnu.tar.gz
\[ OK \] DietPi-Software | tar xf uv-aarch64-unknown-linux-gnu.tar.gz
\[ OK \] DietPi-Software | rm uv-aarch64-unknown-linux-gnu.tar.gz
\[ OK \] DietPi-Software | mv uv-aarch64-unknown-linux-gnu/uv /usr/local/bin/uv
\[ OK \] DietPi-Software | rm -R uv-aarch64-unknown-linux-gnu
DietPi-Software
─────────────────────────────────────────────────────
Step: Installing Home Assistant: Open source home automation platform
\[ INFO \] DietPi-Software | Home Assistant user: homeassistant
\[ INFO \] DietPi-Software | Home Assistant home: /opt/homeassistant
\[ INFO \] DietPi-Software | HA Python version: 3.14
\[ OK \] DietPi-Software | usermod -aG dialout,gpio,i2c -d /opt/homeassistant -s /usr/sbin/nologin homeassistant
\[ OK \] DietPi-Software | mkdir -p /opt/homeassistant
\[ OK \] DietPi-Software | chown homeassistant:homeassistant /opt/homeassistant
\[ OK \] DietPi-Software | cd /opt/homeassistant
\[ INFO \] DietPi-Software | APT install libc6-dev gcc g++, please wait…
Reading package lists…
Building dependency tree…
Reading state information…
libc6-dev is already the newest version (2.36-9+rpt2+deb12u13).
gcc is already the newest version (4:12.2.0-3).
g++ is already the newest version (4:12.2.0-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
\[ OK \] DietPi-Software | APT install libc6-dev gcc g++
\[ OK \] DietPi-Software | mkdir -p /opt/homeassistant/.config/uv
\[ OK \] DietPi-Software | eval echo ‘no-cache = true’ > ‘/opt/homeassistant/.config/uv/uv.toml’
\[ INFO \] DietPi-Software | Installing Python, please wait…
Python 3.14 is already on the latest supported patch release
\[ OK \] DietPi-Software | Installing Python
\[ INFO \] DietPi-Software | Setting up venv, please wait…
Using CPython 3.14.4
Creating virtual environment at: .venv
Activate with: source .venv/bin/activate
\[ OK \] DietPi-Software | Setting up venv
\[ INFO \] DietPi-Software | Installing additional dependencies: isal, please wait…
Resolved 1 package in 685ms
Checked 1 package in 0.27ms
\[ OK \] DietPi-Software | Installing additional dependencies: isal
\[ INFO \] DietPi-Software | Installing Home Assistant core module, please wait…
Resolved 101 packages in 10.40s
Downloading grpcio (6.3MiB)
Downloading homeassistant (51.0MiB)
Downloading uv (22.5MiB)
Downloading botocore (14.3MiB)
Downloading zeroconf (2.0MiB)
Downloading sqlalchemy (1.8MiB)
Downloading cryptography (4.1MiB)
Downloading pillow (6.1MiB)
Downloading aiohttp (1.6MiB)
Building pyric==0.1.6.3
Building lru-dict==1.3.0
Building fnv-hash-fast==2.0.0
Built pyric==0.1.6.3
Downloaded aiohttp
Downloaded sqlalchemy
Downloaded zeroconf
Downloaded cryptography
Downloaded pillow
Downloaded grpcio
Downloaded botocore
Downloaded uv
Built fnv-hash-fast==2.0.0
Built lru-dict==1.3.0
I was not able to get a picture in time. I assume the error is part of the update script.
warning: Failed to hardlink files; falling back to full copy. This may lead to degraded performance.
If the cache and target directories are on different filesystems, hardlinking may not be supported.
If this is intentional, set \`export UV_LINK_MODE=copy\` or use \`--link-mode=copy\` to suppress this warning.
Installed 1 package in 16ms
Some module builds can be heavy. Not uncommon that SSH freezes or glitches temporarily. And the builds can take a while to finish. Did it ever really crash, or were you probably just a bit impatient?
I did wait about 2 hours. I have 2 images in a post above showing the uptime with no activity from the updater script. I could have waited longer but that pi is also the DHCP server/ad blocker and the rest of the household was looking at me.
Looking at the kernel log, it appears as though all read and write operations are stalling on the SSD. This can happen due to power supply issues or a very high I/O load when swap is in use. This is probably the case here. During compilation, the RAM runs out and the system starts swapping. With a high SWAP load, this can almost bring the system to a standstill.
How is the SSD powered? Just by the USB port or has it an own PSU? And what exactly you store on the SSD? The entire user data directory? Where is the SWAP file located?
So I assume rootfs, userdata and swapfile are all on the same SSD, also since it is partition 2.
Even if at its limits, of course it should not crash the system. But to run stable, indeed a dedicated PSU is surely needed.
Other than that, some tweaks might enhance its performance. E.g. if its I/O scheduler is bfq by default, mq-deadline might work better on SSDs, as it is simpler, theoretically better suited for fast drives with low latency, like SSDs.
And does it support APM?
hdparm -B /dev/sda
Last but not least, UAS (USB Attached SCSI), has shown to cause some problems with specific drives, e.g. due to outdated firmware. But that usually shows up immediately, preventing booting from the drive. Very unlikely to be the culprit in your case, since it obviously worked well before.
