Hello together!
I’m having troubles with my supervised HA installation with the systemd-journald service which is not able to be killed. This is not the first time I’m having this issue. Hard-reset of the system lead to a normal start of HA. Then a few day HA is working without problems. Afterwards the system hangs.
Pls see shell-output of the CLI interface
➜ / ha info
arch: amd64
channel: stable
docker: 28.0.4
features:
- reboot
- shutdown
- services
- network
- hostname
- timedate
- os_agent
- haos
- resolved
- journal
- disk
- mount
hassos: "15.2"
homeassistant: 2025.5.2
hostname: homeassistant
logging: info
machine: qemux86-64
operating_system: Home Assistant OS 15.2
state: running
supervisor: 2025.05.1
supported: true
supported_arch:
- amd64
- i386
I tried to delete the journal folder with all logs with no success:
➜ / ls -la /var/log/journal/b0731988e1eb4871ad864967fc69effe
total 86740
drwxr-sr-x 2 root 104 4096 May 23 07:17 .
drwxr-sr-x 3 root 104 4096 May 18 10:48 ..
-rw-r----- 1 root 104 8388608 May 23 08:11 system.journal
-rw-r----- 1 root 104 8388608 May 23 05:10 [email protected]~
-rw-r----- 1 root 104 2472560 May 18 11:21 system@55b71b202b6340e9a583bc8cec477242-000000000f19c8f9-0006356588c0a555.journal
-rw-r----- 1 root 104 21290992 May 19 23:22 system@55b71b202b6340e9a583bc8cec477242-000000000f19cd11-0006356588dd5b04.journal
-rw-r----- 1 root 104 20489368 May 21 14:00 system@55b71b202b6340e9a583bc8cec477242-000000000f1a2c18-00063583bac90104.journal
-rw-r----- 1 root 104 20474640 May 23 05:10 system@55b71b202b6340e9a583bc8cec477242-000000000f1a83b8-000635a41ac6f809.journal
-rw-r----- 1 root 104 4745776 May 18 11:21 system@c66eaf69554a41d7b30193333e78d31e-000000000f19bb68-0006356513d99c4a.journal
-rw-r----- 1 root 104 2530336 May 23 07:17 system@e50e215d1b6740418887bb689454c3a8-000000000f1adc57-000635c6b62f21a8.journal
➜ / sudo rm -rf /var/log/journal/*
rm: can't remove '/var/log/journal/b0731988e1eb4871ad864967fc69effe/system@55b71b202b6340e9a583bc8cec477242-000000000f19c8f9-0006356588c0a555.journal': Read-only file system
rm: can't remove '/var/log/journal/b0731988e1eb4871ad864967fc69effe/system@e50e215d1b6740418887bb689454c3a8-000000000f1adc57-000635c6b62f21a8.journal': Read-only file system
rm: can't remove '/var/log/journal/b0731988e1eb4871ad864967fc69effe/system@55b71b202b6340e9a583bc8cec477242-000000000f1a83b8-000635a41ac6f809.journal': Read-only file system
rm: can't remove '/var/log/journal/b0731988e1eb4871ad864967fc69effe/[email protected]~': Read-only file system
rm: can't remove '/var/log/journal/b0731988e1eb4871ad864967fc69effe/system@55b71b202b6340e9a583bc8cec477242-000000000f1a2c18-00063583bac90104.journal': Read-only file system
rm: can't remove '/var/log/journal/b0731988e1eb4871ad864967fc69effe/system.journal': Read-only file system
rm: can't remove '/var/log/journal/b0731988e1eb4871ad864967fc69effe/system@55b71b202b6340e9a583bc8cec477242-000000000f19cd11-0006356588dd5b04.journal': Read-only file system
rm: can't remove '/var/log/journal/b0731988e1eb4871ad864967fc69effe/system@c66eaf69554a41d7b30193333e78d31e-000000000f19bb68-0006356513d99c4a.journal': Read-only file system
Running a df -h shows a usage of 69% which seems ok for me.
Someone a clue what’s going on here?
…