I have a RAID10, which recently caused the following related errors. First thing I realised was that mount points of the raid were 100% full or not accessible. After doing a reboot, the machine didn't get on again.
Dec 14 08:27:10 kernel: [98392532.799306] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:10:45 kernel: [98395147.707884] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #2: block 1185: comm smbd: unable to read itable block
Dec 14 09:10:46 kernel: [98395148.346333] EXT4-fs error (device dm-1) in ext4_reserve_inode_write:5448: IO failure
Dec 14 09:10:46 kernel: [98395148.346543] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:10:46 kernel: [98395148.391103] EXT4-fs error (device dm-1) in ext4_ext_truncate:4665: IO failure
Dec 14 09:10:46 kernel: [98395148.646391] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:10:46 kernel: [98395148.731502] EXT4-fs error (device dm-1) in ext4_ext_truncate:4665: IO failure
Dec 14 09:10:46 kernel: [98395148.813478] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:10:47 kernel: [98395148.902810] EXT4-fs error (device dm-1) in ext4_ext_truncate:4665: IO failure
Dec 14 09:10:47 kernel: [98395149.091617] EXT4-fs error (device dm-1) in ext4_ext_truncate:4665: IO failure
Dec 14 09:10:52 kernel: [98395153.854832] EXT4-fs error (device dm-2): ext4_journal_check_start:56: Detected aborted journal
Dec 14 09:11:01 kernel: [98395162.898190] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487315: block 41943169: comm chown: unable to read itable block
Dec 14 09:11:01 kernel: [98395162.965922] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487323: block 41943169: comm chown: unable to read itable block
Dec 14 09:11:01 kernel: [98395162.965943] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487315: block 41943169: comm chown: unable to read itable block
Dec 14 09:11:01 kernel: [98395162.987948] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487323: block 41943169: comm chown: unable to read itable block
Dec 14 09:11:01 kernel: [98395162.988346] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487327: block 41943169: comm chown: unable to read itable block
Dec 14 09:11:01 kernel: [98395163.022664] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487335: block 41943170: comm chown: unable to read itable block
Dec 14 09:11:01 kernel: [98395163.032301] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487327: block 41943169: comm chown: unable to read itable block
Dec 14 09:11:01 kernel: [98395163.043358] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487382: block 41943173: comm chown: unable to read itable block
Dec 14 09:11:01 kernel: [98395163.065742] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487390: block 41943173: comm chown: unable to read itable block
Dec 14 09:11:01 kernel: [98395163.065758] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487335: block 41943170: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395167.909515] EXT4-fs error: 429 callbacks suppressed
Dec 14 09:11:06 kernel: [98395167.909518] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489148: block 41943283: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395167.931968] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489128: block 41943282: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395167.931981] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489152: block 41943283: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395167.942934] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489156: block 41943284: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395167.953990] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489136: block 41943282: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395167.965180] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489160: block 41943284: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395167.976247] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489144: block 41943283: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395167.987373] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489168: block 41943284: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395168.009761] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489176: block 41943285: comm chown: unable to read itable block
Dec 14 09:11:06 kernel: [98395168.009775] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489148: block 41943283: comm chown: unable to read itable block
Dec 14 09:12:00 kernel: [98395221.995633] EXT4-fs error (device dm-1): ext4_journal_check_start:56: Detected aborted journal
Dec 14 09:17:03 kernel: [98395524.952680] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:17:03 kernel: [98395525.529655] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:32:21 kernel: [98396442.892076] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:32:24 kernel: [98396445.872774] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:47:11 kernel: [98397333.487293] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:47:14 kernel: [98397335.974562] EXT4-fs error (device dm-1): __ext4_get_inode_loc:4363: inode #83627037: block 334495969: comm python3: unable to read itable block
Dec 14 09:55:25 kernel: [98397826.842786] EXT4-fs error (device dm-1): ext4_validate_block_bitmap:384: comm python3: bg 11324: bad block bitmap checksum
Dec 14 09:55:25 kernel: [98397827.443843] EXT4-fs error (device dm-1): ext4_discard_preallocations:4044: comm python3: Error -74 loading buddy information for 11324
Dec 14 09:55:30 kernel: [98397831.903119] EXT4-fs error (device dm-1): ext4_validate_block_bitmap:384: comm python3: bg 9669: bad block bitmap checksum
Dec 14 09:55:30 kernel: [98397831.970501] EXT4-fs error (device dm-1): ext4_discard_preallocations:4044: comm python3: Error -74 loading buddy information for 9669
Dec 14 10:00:22 kernel: [98398124.263809] EXT4-fs error: 47 callbacks suppressed
Dec 14 10:00:22 kernel: [98398124.263813] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487315: block 41943169: comm chown: unable to read itable block
Dec 14 10:00:22 kernel: [98398124.494838] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487323: block 41943169: comm chown: unable to read itable block
Dec 14 10:00:22 kernel: [98398124.538707] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487327: block 41943169: comm chown: unable to read itable block
Dec 14 10:00:22 kernel: [98398124.544773] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487335: block 41943170: comm chown: unable to read itable block
Dec 14 10:00:22 kernel: [98398124.655674] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487382: block 41943173: comm chown: unable to read itable block
Dec 14 10:00:23 kernel: [98398124.760761] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487390: block 41943173: comm chown: unable to read itable block
Dec 14 10:00:23 kernel: [98398124.862457] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487394: block 41943174: comm chown: unable to read itable block
Dec 14 10:00:23 kernel: [98398124.970547] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487418: block 41943175: comm chown: unable to read itable block
Dec 14 10:00:23 kernel: [98398125.032760] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487422: block 41943175: comm chown: unable to read itable block
Dec 14 10:00:23 kernel: [98398125.044861] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10487427: block 41943176: comm chown: unable to read itable block
Dec 14 10:00:27 kernel: [98398129.276676] EXT4-fs error: 131 callbacks suppressed
Dec 14 10:00:27 kernel: [98398129.276680] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488512: block 41943243: comm chown: unable to read itable block
Dec 14 10:00:27 kernel: [98398129.376750] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488516: block 41943244: comm chown: unable to read itable block
Dec 14 10:00:27 kernel: [98398129.460516] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488520: block 41943244: comm chown: unable to read itable block
Dec 14 10:00:27 kernel: [98398129.560703] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488524: block 41943244: comm chown: unable to read itable block
Dec 14 10:00:27 kernel: [98398129.668334] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488528: block 41943244: comm chown: unable to read itable block
Dec 14 10:00:28 kernel: [98398129.771789] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488532: block 41943245: comm chown: unable to read itable block
Dec 14 10:00:28 kernel: [98398129.868509] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488540: block 41943245: comm chown: unable to read itable block
Dec 14 10:00:28 kernel: [98398129.971858] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488548: block 41943246: comm chown: unable to read itable block
Dec 14 10:00:28 kernel: [98398130.164355] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488556: block 41943246: comm chown: unable to read itable block
Dec 14 10:00:28 kernel: [98398130.276552] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10488560: block 41943246: comm chown: unable to read itable block
Dec 14 10:00:32 kernel: [98398134.309920] EXT4-fs error: 81 callbacks suppressed
Dec 14 10:00:32 kernel: [98398134.309923] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489208: block 41943287: comm chown: unable to read itable block
Dec 14 10:00:32 kernel: [98398134.409969] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489212: block 41943287: comm chown: unable to read itable block
Dec 14 10:00:32 kernel: [98398134.510077] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489216: block 41943287: comm chown: unable to read itable block
Dec 14 10:00:32 kernel: [98398134.580315] EXT4-fs error (device dm-2): __ext4_get_inode_loc:4363: inode #10489224: block 41943288: comm chown: unable to read itable block
...
I figured out the affected disk and took it out. It had a bad GPT, which I could restore from a backup. Anyway after that fsck told me that it had a bad superblock. So I tried to reassemble and run the RAID with only 3/4 disks successfully. Unfortunately during the process of making backups of the RAID to external disks, a similar error suddenly occurred again. I turned off the server.
Dec 18 10:26:28 kernel: [ 1728.678148] EXT4-fs error (device dm-1): ext4_lookup:1618: inode #9963357: comm rsync: iget: checksum invalid
Dec 18 10:26:28 kernel: [ 1729.111722] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #10097120: comm rsync: checksumming directory block 0
Dec 18 10:26:29 kernel: [ 1729.237014] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #10097120: comm rsync: checksumming directory block 0
Dec 18 10:26:29 kernel: [ 1729.248067] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #10097120: comm rsync: checksumming directory block 0
Dec 18 10:26:29 kernel: [ 1729.259156] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #10097120: comm rsync: checksumming directory block 0
...
Dec 18 10:27:01 kernel: [ 1761.490727] EXT4-fs error (device dm-1): ext4_lookup:1622: inode #20709934: comm rsync: deleted inode referenced: 20711459
Dec 18 10:27:01 kernel: [ 1761.639790] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #20840944: comm rsync: checksumming directory block 0
Dec 18 10:27:02 kernel: [ 1763.100409] EXT4-fs error (device dm-1): ext4_lookup:1622: inode #10092630: comm rsync: deleted inode referenced: 10098345
Dec 18 10:27:02 kernel: [ 1763.121856] EXT4-fs error (device dm-1): ext4_lookup:1622: inode #10092630: comm rsync: deleted inode referenced: 10098317
Dec 18 10:27:02 kernel: [ 1763.133002] EXT4-fs error (device dm-1): ext4_lookup:1622: inode #10092630: comm rsync: deleted inode referenced: 10098322
Dec 18 10:27:02 kernel: [ 1763.144098] EXT4-fs error (device dm-1): ext4_lookup:1622: inode #10092630: comm rsync: deleted inode referenced: 10098332
Dec 18 10:27:02 kernel: [ 1763.155216] EXT4-fs error (device dm-1): ext4_lookup:1622: inode #10092630: comm rsync: deleted inode referenced: 10098342
Dec 18 10:27:02 kernel: [ 1763.166240] EXT4-fs error (device dm-1): ext4_lookup:1622: inode #10092630: comm rsync: deleted inode referenced: 10098304
Dec 18 10:27:02 kernel: [ 1763.177434] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #10097120: comm rsync: checksumming directory block 0
Dec 18 10:27:03 kernel: [ 1763.188502] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #10097120: comm rsync: checksumming directory block 0
Dec 18 10:27:10 kernel: [ 1770.728345] EXT4-fs error: 40 callbacks suppressed
Dec 18 10:27:10 kernel: [ 1770.728347] EXT4-fs error (device dm-1): mb_free_blocks:1471: group 2225, block 72932936:freeing already freed block (bit 24136); block bitmap corrupt.
Dec 18 10:27:10 kernel: [ 1770.728418] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:759: group 2225, block bitmap and bg descriptor inconsistent: 30869 vs 30874 free clusters
Dec 18 10:27:10 kernel: [ 1770.728468] EXT4-fs error (device dm-1): mb_free_blocks:1471: group 2643, block 86610919:freeing already freed block (bit 5095); block bitmap corrupt.
Dec 18 10:27:10 kernel: [ 1770.728535] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:759: group 2643, block bitmap and bg descriptor inconsistent: 5996 vs 5999 free clusters
Dec 18 10:27:37 kernel: [ 1797.350356] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #21634737: comm rsync: checksumming directory block 0
Dec 18 10:27:37 kernel: [ 1797.373351] EXT4-fs error (device dm-1): ext4_add_entry:2155: inode #21634737: comm rsync: Directory block failed checksum
Dec 18 10:27:37 kernel: [ 1797.473643] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #21634737: comm rsync: checksumming directory block 0
Dec 18 10:27:37 kernel: [ 1797.506858] EXT4-fs error (device dm-1): ext4_add_entry:2155: inode #21634737: comm rsync: Directory block failed checksum
Dec 18 10:27:37 kernel: [ 1797.529176] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #21634737: comm rsync: checksumming directory block 0
Dec 18 10:27:37 kernel: [ 1797.562276] EXT4-fs error (device dm-1): ext4_add_entry:2155: inode #21634737: comm rsync: Directory block failed checksum
Dec 18 10:27:37 kernel: [ 1797.606802] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #21634737: comm rsync: checksumming directory block 0
Dec 18 10:27:37 kernel: [ 1797.617807] EXT4-fs error (device dm-1): ext4_add_entry:2155: inode #21634737: comm rsync: Directory block failed checksum
Dec 18 10:27:37 kernel: [ 1797.629002] EXT4-fs error (device dm-1): ext4_find_entry:1484: inode #21634737: comm rsync: checksumming directory block 0
Dec 18 10:27:37 kernel: [ 1797.640009] EXT4-fs error (device dm-1): ext4_add_entry:2155: inode #21634737: comm rsync: Directory block failed checksum
Dec 18 10:27:42 kernel: [ 1802.361843] EXT4-fs error: 122 callbacks suppressed
Dec 18 10:27:42 kernel: [ 1802.361848] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:42 kernel: [ 1802.372751] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:42 kernel: [ 1802.383862] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:42 kernel: [ 1802.394954] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:42 kernel: [ 1802.406080] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:42 kernel: [ 1802.450497] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:42 kernel: [ 1802.461648] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:42 kernel: [ 1802.472708] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:42 kernel: [ 1802.483810] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:42 kernel: [ 1802.494954] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.372760] EXT4-fs error: 395 callbacks suppressed
Dec 18 10:27:47 kernel: [ 1807.372764] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.383818] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.395070] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.406319] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.417176] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.428555] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.439455] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.450557] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.461725] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:47 kernel: [ 1807.473007] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.383390] EXT4-fs error: 337 callbacks suppressed
Dec 18 10:27:52 kernel: [ 1812.383394] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.405503] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.416736] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.427688] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.438815] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.450067] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.461193] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.472163] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.483392] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:52 kernel: [ 1812.494355] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.393862] EXT4-fs error: 398 callbacks suppressed
Dec 18 10:27:57 kernel: [ 1817.393867] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.474295] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.482838] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.493848] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.504930] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.516094] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.527185] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.538282] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.549474] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:27:57 kernel: [ 1817.560582] EXT4-fs error (device dm-1): ext4_find_extent:929: inode #10880011: comm rsync: pblk 43574935 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
Dec 18 10:32:32 kernel: [ 26.807495] EXT4-fs error (device dm-1): ext4_validate_block_bitmap:394: comm python3: bg 9974: bad block bitmap checksum
Dec 18 10:32:32 kernel: [ 26.862893] EXT4-fs error (device dm-1) in ext4_free_blocks:4950: Filesystem failed CRC
Dec 18 10:32:32 kernel: [ 26.882135] EXT4-fs error (device dm-1): ext4_validate_inode_bitmap:98: comm python3: Corrupt inode bitmap - block_group = 10144, inode_bitmap = 332398608
Dec 18 10:32:32 kernel: [ 26.885074] EXT4-fs error (device dm-1) in ext4_free_inode:363: Filesystem failed CRC
Dec 18 10:32:39 kernel: [ 33.801511] EXT4-fs error (device dm-1): ext4_ext_remove_space:3023: inode #83100238: comm python3: pblk 332447178 bad header/extent: extent tree corrupted - magic f30a, entries 16, max 340(340), depth 0(0)
Dec 18 10:32:39 kernel: [ 33.818812] EXT4-fs error (device dm-1) in ext4_ext_truncate:4691: Filesystem failed CRC
Dec 18 10:32:39 kernel: [ 33.829936] EXT4-fs error (device dm-1) in ext4_free_inode:363: Corrupt filesystem
Dec 18 10:32:55 kernel: [ 49.287126] EXT4-fs error (device dm-1): ext4_validate_block_bitmap:394: comm kworker/u128:3: bg 10145: bad block bitmap checksum
Followed by that I recognised a new boot error, after having taken out all disks again.
[ 846.267647] ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20180531/exfield-393)
[ 846.267654] ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[ 846.267661] ACPI Error: AE_AML_BUFFER_LIMIT, Evaluating _PMM
I think it is kind of a hardware problem with the SATA controller, which caused that mess. I won't put the disks in that server again, which I should have done from the very beginning, so I need to wait for new hardware.
Can anybody give me a hint of what exactly happened to my disks and if there is a chance to fix this and what approach I may take?
Thanks for your help!
