I just recovered from a very odd event. The system attempted to enter hybrid sleep (which I have previously disabled) and was unresponsive until power was cycled on the PSU.
Checking the logs it shows what I suspected (that it tried to hibernate) but now the kernel is giving the following warnings.
Aug 15 21:32:52 nothing-box kernel: EXT4-fs error (device dm-0): ext4_validate_block_bitmap:390: comm rsync: bg 411: bad block bitmap checksum
Aug 15 21:33:21 nothing-box kernel: Uhhuh. NMI received for unknown reason 2c on CPU 0.
Aug 15 21:33:21 nothing-box kernel: Dazed and confused, but trying to continue
Aug 15 21:35:12 nothing-box kernel: EXT4-fs error (device dm-0) in ext4_free_inode:362: Corrupt filesystem
Aug 15 21:35:42 nothing-box kernel: EXT4-fs error (device dm-0): ext4_validate_inode_bitmap:105: comm ThreadPoolForeg: Corrupt inode bitmap - block_group = 12128, inode_bitmap = 397410320
Aug 15 21:35:42 nothing-box kernel: EXT4-fs error (device dm-0) in ext4_free_inode:362: Corrupt filesystem
Kind of at a loss here with dm-0 being the problem, if it was a storage device I would run fsck
but dm-0 is a mystery to me as it’s used for device mapping?
Can’t tell if I should just reboot and test on a proper boot, but I feel I’m just as likely to lose the filesystem.
edit:
ok so this thread on the arch forums lays out the problem
https://bbs.archlinux.org/viewtopic.php?id=249962
So this is related to the encrypted swapfile partition(System drive) if I am following correctly. That’s good to know but I am still at a loss on how to correct it.
Better ideas welcome.