#Hello, looking for some help debugging
bright tide
Jul 25 07:16:21 homeassistant systemd[1]: containerd.service: Main process exited, code=exited, status=1/FAILURE
Jul 25 07:16:21 homeassistant systemd[1]: containerd.service: Failed with result 'exit-code'.
Jul 25 07:16:21 homeassistant systemd[1]: Failed to start containerd container runtime.
Jul 25 07:16:26 homeassistant systemd[1]: containerd.service: Scheduled restart job, restart counter is at 99.```
lavish maple
Check the OS logs, looks like the SD card is dead (read only)
bright tide
How do i check OS logs? yeah i was afraid of that, does it mean completely dead or i can just reformat?
lavish maple
SD cards have a short life, it's likely dead dead, and not just mostly dead
maiden kiln
journalctl -r is one way.
bright tide
I just get the containerd error logs repeatedly
Jul 25 07:22:05 homeassistant systemd[1]: dev-disk-by\x2dlabel-hassos\x2ddata.device: Job dev-disk-by\x2dlabel-hassos\x2ddata.device/start failed with result 'timeout'.
Jul 25 07:22:05 homeassistant systemd[1]: systemd-fsck@dev-disk-by\x2dlabel-hassos\x2ddata.service: Job systemd-fsck@dev-disk-by\x2dlabel-hassos\x2ddata.service/start failed
Jul 25 07:22:05 homeassistant systemd[1]: Dependency failed for File System Check on /dev/disk/by-label/hassos-data.
Jul 25 07:22:05 homeassistant systemd[1]: mnt-data.mount: Job mnt-data.mount/start failed with result 'dependency'.
Jul 25 07:22:05 homeassistant systemd[1]: var-lib-docker.mount: Job var-lib-docker.mount/start failed with result 'dependency'.
Jul 25 07:22:05 homeassistant systemd[1]: Dependency failed for Docker persistent data.
Jul 25 07:22:05 homeassistant systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
Jul 25 07:22:05 homeassistant systemd[1]: Dependency failed for Docker Application Container Engine.
If you skip the r you'll probably get a pager that starts with, well, the start of the logs.
Can you check lsblk -o +FSTYPE,LABEL?
lavish maple
fsck ... failed 
bright tide
mmcblk0 179:0 0 29.1G 0 disk
|-mmcblk0p1 179:1 0 32M 0 part /mnt/boot vfat hassos-boot
|-mmcblk0p2 179:2 0 24M 0 part squashfs
|-mmcblk0p3 179:3 0 256M 0 part / squashfs
|-mmcblk0p4 179:4 0 24M 0 part squashfs
|-mmcblk0p5 179:5 0 256M 0 part squashfs
|-mmcblk0p6 179:6 0 8M 0 part
|-mmcblk0p7 179:7 0 96M 0 part /var/lib/systemd ext4 hassos-overlay
| /var/lib/bluetooth
| /var/lib/NetworkManager
| /etc/systemd/timesyncd.conf
| /etc/hosts
| /etc/hostname
| /etc/NetworkManager/system-connections
| /root/.ssh
| /root/.docker
| /etc/udev/rules.d
| /etc/modules-load.d
| /etc/modprobe.d
| /etc/dropbear
| /mnt/overlay
`-mmcblk0p8 179:8 0 28.4G 0 part
zram0 254:0 0 0B 0 disk
zram1 254:1 0 32M 0 disk
zram2 254:2 0 16M 0 disk /tmp
You can try fsck /dev/mmcblk0p8 and check journalctl -fu systemd-fsck... and systemctl status ... but the information is likely the same and the file system likely corrupted. Re-flash and restore. Perhaps on a different SD Card or exchange it with a SSD.
bright tide
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
hassos-data: recovering journal
fsck.ext2: unable to set superblock flags on hassos-data
hassos-data: ***** FILE SYSTEM WAS MODIFIED *****
hassos-data: ********** WARNING: Filesystem still has errors **********
Thanks for the help, gotta go get a new SD card then
lavish maple
SD cards will fail on you, plan to move to better hardware
If you just add an SSD, make sure to use an externally powered USB hub or you'll have power problems and corrupt file systems