I have a similar problem. My X88 Pro 10 box becomes unavailable on the network at 1-2 days after boot.
I have also Home Assistant (docker) installed.
On the serial console I see these repeating messages:
[549535.724967] EXT4-fs error (device sda1): __ext4_find_entry:1614: inode #297037: comm coredns: reading directory lblock 0
[549540.725016] EXT4-fs error (device sda1): __ext4_find_entry:1614: inode #297037: comm coredns: reading directory lblock 0
[549542.223122] EXT4-fs error (device sda1): __ext4_find_entry:1614: inode #98370: comm cron: reading directory lblock 0
[549545.725179] EXT4-fs error (device sda1): __ext4_find_entry:1614: inode #297037: comm coredns: reading directory lblock 0
[549546.552355] EXT4-fs error (device sda1): __ext4_find_entry:1614: inode #854279: comm dockerd: reading directory lblock 0
[549546.584734] EXT4-fs error (device sda1): __ext4_find_entry:1614: inode #1117992: comm dockerd: reading directory lblock 0
[549547.248250] EXT4-fs error (device sda1): __ext4_find_entry:1614: inode #98305: comm dockerd: reading directory lblock 0
So it means that the kernel is alive. Problem is with the disk access.
I am booting from SSD disk attached to the USB port. Disk has two partitions - system (armbian) and data:
root@hassio:~# mount | grep mmcfdisk -l /dev/sda
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Disk model: M4SSD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xbf43edfd
Device Boot Start End Sectors Size Id Type
/dev/sda1 32768 29982719 29949952 14.3G 83 Linux
/dev/sda2 29982720 500118191 470135472 224.2G 83 Linux
How can I log all the messages to the /dev/sda2 partittion? (mounted as /DATA)
Alternatively I can connect USB flash disk to the USB 3.0 port and store the logs here - if possible.
