I have had the exact same issue with two different hardware configurations. What happens is that after some period of time (usually days to weeks), the GUI will stop responding, and on the physical screen, I will see these errors scrolling by:
[timestamp] Buffer I/O error on dev nvme0n1p3, logical block 2, async page read
[timestamp] erofs: (device nvme0n1p3): erofs_read_inode: failed to get inode (nid: 274) page, err =5
This first happened when I was running HAOS on a Raspberry Pi5 with an MHAT.2 connected SSD drive. Thinking the drive was bad or something, I decide to replace the whole setup with a NUC, which is currently running HAOS v16.2 installed on the internal SSD drive. This was a fresh install of HAOS with a restored backup of the add-ins and configurations.
Since the errors are exactly the same on the old hardware and the new hardware, I’m now wondering if it’s NOT a hardware issue, but perhaps a software bug.
I’ve tried searching for these error messages, and everything seems to indicate a hardware issue. While not impossible, I would be surprised to have the exact same block fail on 2 different SSDs.
I appreciate any pointers or insights as to how I might be able to troubleshoot this further - even some way to confirm whether it’s a hardware or software issue.
Thanks!