Ok, a friend encouraged me to capture the error message so I’ve run dmesg -w
into a file on a USB drive until the error occurred. Here’s the output:
[28922.642400] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
[28922.714515] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[28922.715277] nvme nvme0: Removing after probe failure status: -19
[28922.738512] nvme0n1: detected capacity change from 488397168 to 0
[28922.738531] blk_update_request: I/O error, dev nvme0n1, sector 155211064 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 0
[28922.738543] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 1326875 starting block 19401387)
[28922.738551] Buffer I/O error on device nvme0n1p2, logical block 19270055
[28922.738562] Buffer I/O error on device nvme0n1p2, logical block 19270056
[28922.738564] Buffer I/O error on device nvme0n1p2, logical block 19270057
[28922.738567] Buffer I/O error on device nvme0n1p2, logical block 19270058
[28922.738575] blk_update_request: I/O error, dev nvme0n1, sector 326895840 op 0x1:(WRITE) flags 0x0 phys_seg 46 prio class 0
[28922.738579] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 1326875 starting block 40862038)
[28922.738583] blk_update_request: I/O error, dev nvme0n1, sector 155210992 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
[28922.738587] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 1326871 starting block 19401376)
[28922.738589] Buffer I/O error on device nvme0n1p2, logical block 19270046
[28922.738592] Buffer I/O error on device nvme0n1p2, logical block 19270047
[28922.738588] blk_update_request: I/O error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[28922.738595] blk_update_request: I/O error, dev nvme0n1, sector 155211040 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
[28922.738599] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 1326874 starting block 19401382)
[28922.738602] Buffer I/O error on device nvme0n1p2, logical block 19270052
[28922.738606] Buffer I/O error on device nvme0n1p2, logical block 19270053
[28922.738610] blk_update_request: I/O error, dev nvme0n1, sector 25377560 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
[28922.738609] blk_update_request: I/O error, dev nvme0n1, sector 154671664 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
[28922.738614] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 1326874 starting block 3172196)
[28922.738614] blk_update_request: I/O error, dev nvme0n1, sector 25557080 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
[28922.738615] blk_update_request: I/O error, dev nvme0n1, sector 156009216 op 0x1:(WRITE) flags 0x800 phys_seg 17 prio class 0
[28922.738619] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 4587870 starting block 19333959)
[28922.738621] blk_update_request: I/O error, dev nvme0n1, sector 25361480 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[28922.738625] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 1314679 starting block 19501169)
[28922.738627] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 1326871 starting block 3172197)
[28922.738627] Buffer I/O error on device nvme0n1p2, logical block 19202630
[28922.738624] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 4587872 starting block 47369284)
[28922.738625] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:344: I/O error 10 writing to inode 1319714 starting block 3151507)
[28922.738631] Buffer I/O error on device nvme0n1p2, logical block 3063307
[28922.738637] Buffer I/O error on dev nvme0n1p2, logical block 53478372, lost async page write
[28922.738648] Buffer I/O error on dev nvme0n1p2, logical block 53477393, lost async page write
[28922.738653] Buffer I/O error on dev nvme0n1p2, logical block 53477377, lost async page write
[28922.738657] Buffer I/O error on dev nvme0n1p2, logical block 44564489, lost async page write
[28922.738663] Buffer I/O error on dev nvme0n1p2, logical block 37748741, lost async page write
[28922.738738] EXT4-fs error (device nvme0n1p2): ext4_check_bdev_write_error:217: comm kworker/u32:7: Error while async write back metadata
[28922.738748] Aborting journal on device nvme0n1p2-8.
[28922.738759] JBD2: Error -5 detected when updating journal superblock for nvme0n1p2-8.
[28922.738774] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[28922.738776] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
[28922.738779] EXT4-fs error (device nvme0n1p2) in ext4_reserve_inode_write:5752: Journal has aborted
[28922.738784] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[28922.738786] EXT4-fs error (device nvme0n1p2): __ext4_ext_dirty:183: inode #1326875: comm kworker/u32:7: mark_inode_dirty error
[28922.738792] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[28922.738795] EXT4-fs error (device nvme0n1p2): ext4_check_bdev_write_error:217: comm kworker/u32:7: Error while async write back metadata
[28922.738800] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[28922.738801] EXT4-fs error (device nvme0n1p2) in ext4_reserve_inode_write:5752: Journal has aborted
[28922.738805] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[28922.738807] EXT4-fs error (device nvme0n1p2): ext4_convert_unwritten_extents:4826: inode #1326875: comm kworker/u32:7: mark_inode_dirty error
[28922.738812] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[28922.738815] EXT4-fs (nvme0n1p2): failed to convert unwritten extents to written extents -- potential data loss! (inode 1326875, error -30)
[28922.738869] EXT4-fs (nvme0n1p2): failed to convert unwritten extents to written extents -- potential data loss! (inode 1326874, error -30)
[28922.738875] EXT4-fs (nvme0n1p2): failed to convert unwritten extents to written extents -- potential data loss! (inode 1326871, error -30)
[28922.739083] EXT4-fs error (device nvme0n1p2) in ext4_reserve_inode_write:5752: Journal has aborted
[28922.739119] EXT4-fs error (device nvme0n1p2) in ext4_reserve_inode_write:5752: Journal has aborted
[28922.739140] EXT4-fs error (device nvme0n1p2): ext4_rename:3929: inode #1311214: comm BgIOThr~Pool #6: mark_inode_dirty error
[28922.739162] EXT4-fs error (device nvme0n1p2) in ext4_reserve_inode_write:5752: Journal has aborted
[28922.739787] audit: type=1400 audit(1677268114.756:74): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=746 comm="cupsd" capability=12 capname="net_admin"
[28922.801742] FAT-fs (nvme0n1p1): unable to read boot sector to mark fs as dirty
[28927.899287] EXT4-fs error: 335 callbacks suppressed
[28927.899297] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28927.899378] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28928.202486] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961473: comm gmain: reading directory lblock 0
[28928.202503] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1316123: comm gmain: reading directory lblock 0
[28928.202526] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4587561: comm gmain: reading directory lblock 0
[28928.202541] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4587561: comm gmain: reading directory lblock 0
[28928.202555] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4587522: comm gmain: reading directory lblock 0
[28928.202569] EXT4-fs warning: 208 callbacks suppressed
[28928.202571] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #4588092: lblock 0: comm gmain: error -5 reading directory block
[28928.202591] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961480: comm gmain: reading directory lblock 0
[28928.202608] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961480: comm gmain: reading directory lblock 0
[28928.202620] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961480: comm gmain: reading directory lblock 0
[28928.204002] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gmain: error -5 reading directory block
[28928.262386] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gmain: error -5 reading directory block
[28928.262461] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm gmain: error -5 reading directory block
[28930.708068] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm pool-org.gnome.: error -5 reading directory block
[28930.708089] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm pool-org.gnome.: error -5 reading directory block
[28930.708099] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm pool-org.gnome.: error -5 reading directory block
[28932.933099] EXT4-fs error: 124 callbacks suppressed
[28932.933111] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #232: reading directory lblock 0
[28932.933205] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #232: reading directory lblock 0
[28933.437151] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28933.437257] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28933.939930] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #232: reading directory lblock 0
[28933.939985] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #232: reading directory lblock 0
[28934.443321] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28934.443412] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode
[28936.202528] EXT4-fs warning: 16 callbacks suppressed
[28936.202539] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #4588092: lblock 0: comm gmain: error -5 reading directory block
[28936.203855] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gmain: error -5 reading directory block
[28936.262500] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm gmain: error -5 reading directory block
[28936.262575] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gmain: error -5 reading directory block
[28936.272463] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gnome-shell: error -5 reading directory block
[28936.272489] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gnome-shell: error -5 reading directory block
[28936.272531] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gnome-shell: error -5 reading directory block
[28936.272542] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gnome-shell: error -5 reading directory block
[28936.273540] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gnome-shell: error -5 reading directory block
[28936.273553] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gnome-shell: error -5 reading directory block
[28937.961702] EXT4-fs error: 71 callbacks suppressed
[28937.961708] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #232: reading directory lblock 0
[28937.961751] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #232: reading directory lblock 0
[28938.141788] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm Backgro~ool #44: reading directory lblock 0
[28938.141862] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm Backgro~ool #44: reading directory lblock 0
[28938.149490] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm Backgro~ool #45: reading directory lblock 0
[28938.149540] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm Backgro~ool #45: reading directory lblock 0
[28938.153258] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm Backgro~ool #45: reading directory lblock 0
[28938.153315] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm Backgro~ool #45: reading directory lblock 0
[28938.365190] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311231: comm Cache2 I/O: reading directory lblock 0
[28938.365362] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311231: comm Cache2 I/O: reading directory lblock 0
[28941.874649] EXT4-fs warning: 1893 callbacks suppressed
[28941.874652] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #1311397: lblock 0: comm IndexedDB #272: error -5 reading directory block
[28941.874677] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #1311397: lblock 0: comm IndexedDB #272: error -5 reading directory block
[28941.874684] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #1311397: lblock 0: comm IndexedDB #272: error -5 reading directory block
[28941.874690] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #1311397: lblock 0: comm IndexedDB #272: error -5 reading directory block
[28942.986070] EXT4-fs error: 147 callbacks suppressed
[28942.986082] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28942.986190] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28943.295262] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm mozStorage #6: reading directory lblock 0
[28943.295276] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm mozStorage #6: reading directory lblock 0
[28943.489257] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28943.489332] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28943.570227] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311231: comm Cache2 I/O: reading directory lblock 0
[28943.570346] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311231: comm Cache2 I/O: reading directory lblock 0
[28943.593442] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311231: comm Cache2 I/O: reading directory lblock 0
[28943.709260] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1320643: comm IndexedDB #271: reading directory lblock 0
[28943.713048] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm DNS Res~ver #46: error -5 reading directory block
[28943.713065] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm DNS Res~ver #46: error -5 reading directory block
[28943.719744] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm DNS Res~ver #47: error -5 reading directory block
[28943.719756] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm DNS Res~ver #47: error -5 reading directory block
[28943.741116] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #1311397: lblock 0: comm QuotaManager IO: error -5 reading directory block
[28943.741157] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #1311397: lblock 0: comm QuotaManager IO: error -5 reading directory block
[28943.766977] print_req_error: 151 callbacks suppressed
[28943.766980] blk_update_request: I/O error, dev loop4, sector 311754 op 0x0:(READ) flags 0x800 phys_seg 5 prio class 0
[28943.767076] SQUASHFS error: Failed to read block 0x98395c3: -5
[28943.767082] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767083] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767090] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767091] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767095] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767096] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767099] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767100] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767103] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767104] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767108] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767109] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767112] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767113] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767137] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767140] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767141] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767144] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767145] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767148] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767149] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767152] SQUASHFS error: Unable to read data cache entry [98395c3]
[28943.767153] SQUASHFS error: Unable to read page, block 98395c3, size 4799
[28943.767187] blk_update_request: I/O error, dev loop4, sector 311754 op 0x0:(READ) flags 0x800 phys_seg 5 prio class 0
[28943.767269] SQUASHFS error: Failed to read block 0x98395c3: -5
[28943.767318] blk_update_request: I/O error, dev loop4, sector 311790 op 0x0:(READ) flags 0x800 phys_seg 11 prio class 0
[28943.767379] SQUASHFS error: Failed to read block 0x983dd5c: -5
[28943.767382] SQUASHFS error: Unable to read data cache entry [983dd5c]
[28943.767383] SQUASHFS error: Unable to read page, block 983dd5c, size 9b6e
[28943.767389] SQUASHFS error: Unable to read data cache entry [983dd5c]
[28943.767390] SQUASHFS error: Unable to read page, block 983dd5c, size 9b6e
[28943.767393] SQUASHFS error: Unable to read data cache entry [983dd5c]
[28943.767394] SQUASHFS error: Unable to read page, block 983dd5c, size 9b6e
[28943.767397] SQUASHFS error: Unable to read data cache entry [983dd5c]
[28943.767398] SQUASHFS error: Unable to read page, block 983dd5c, size 9b6e
[28943.767401] SQUASHFS error: Unable to read data cache entry [983dd5c]
[28943.767417] SQUASHFS error: Unable to read page, block 983dd5c, size 9b6e
[28943.767420] SQUASHFS error: Unable to read data cache entry [983dd5c]
[28943.767421] SQUASHFS error: Unable to read page, block 983dd5c, size 9b6e
[28943.767439] blk_update_request: I/O error, dev loop4, sector 311790 op 0x0:(READ) flags 0x800 phys_seg 11 prio class 0
[28943.767490] SQUASHFS error: Failed to read block 0x983dd5c: -5
[28943.767507] blk_update_request: I/O error, dev loop4, sector 311754 op 0x0:(READ) flags 0x800 phys_seg 5 prio class 0
[28943.767513] SQUASHFS error: Failed to read block 0x98395c3: -5
[28943.767526] blk_update_request: I/O error, dev loop4, sector 311754 op 0x0:(READ) flags 0x800 phys_seg 5 prio class 0
[28943.767531] SQUASHFS error: Failed to read block 0x98395c3: -5
[28943.767852] StreamTrans #3[13219]: segfault at 0 ip 0000563901856103 sp 00007ff82f623350 error 6 in firefox[563901825000+99000]
[28943.767863] Code: d8 00 00 00 48 8b b7 c8 00 00 00 4c 8b 87 d0 00 00 00 48 8d 3d cd 84 05 00 31 c0 e8 33 2c 01 00 48 8d 0d 08 c0 06 00 48 89 01 <c7> 04 25 00 00 00 00 7f 00 00 00 e8 cd c7 fd ff 00 00 00 00 00 00
[28943.768069] Core dump to |/usr/share/apport/apport pipe failed
[28946.913853] EXT4-fs warning: 37 callbacks suppressed
[28946.913857] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm DNS Res~ver #46: error -5 reading directory block
[28946.913875] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm DNS Res~ver #46: error -5 reading directory block
[28946.922003] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28946.922165] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28946.929518] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28946.950035] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28946.950044] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28946.950050] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28948.015212] EXT4-fs error: 422 callbacks suppressed
[28948.015221] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28948.015286] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28948.202354] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961473: comm gmain: reading directory lblock 0
[28948.202376] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4587561: comm gmain: reading directory lblock 0
[28948.202382] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4587561: comm gmain: reading directory lblock 0
[28948.202389] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4587522: comm gmain: reading directory lblock 0
[28948.202476] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4588067: comm gmain: reading directory lblock 0
[28948.202495] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1316123: comm gmain: reading directory lblock 0
[28948.202503] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #12060113: comm gmain: reading directory lblock 0
[28948.202526] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1310815: comm gmain: reading directory lblock 0
[28951.969750] EXT4-fs warning: 1959 callbacks suppressed
[28951.969753] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28951.969909] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28951.976806] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28951.995652] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28951.995659] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28951.995665] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28951.995669] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28953.042555] EXT4-fs error: 334 callbacks suppressed
[28953.042565] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28953.042651] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #231: reading directory lblock 0
[28953.546374] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #239: reading directory lblock 0
[28953.546459] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #239: reading directory lblock 0
[28954.004634] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4588067: comm firefox: reading directory lblock 0
[28954.004644] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4588067: comm firefox: reading directory lblock 0
[28954.004647] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4588067: comm firefox: reading directory lblock 0
[28957.352359] EXT4-fs warning: 84 callbacks suppressed
[28957.352361] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28957.352522] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28957.359436] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28957.379337] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28957.381861] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28958.075799] EXT4-fs error: 495 callbacks suppressed
[28958.075810] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #232: reading directory lblock 0
[28958.075902] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #232: reading directory lblock 0
[28963.113248] EXT4-fs error: 68 callbacks suppressed
[28963.113257] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #239: reading directory lblock 0
[28963.113336] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #239: reading directory lblock 0
[28963.617104] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #237: reading directory lblock 0
[28963.617201] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #237: reading directory lblock 0
[28964.121163] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #238: reading directory lblock 0
[28964.121259] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #238: reading directory lblock 0
[28964.202646] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1316123: comm gmain: reading directory lblock 0
[28964.202732] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961480: comm gmain: reading directory lblock 0
[28964.202747] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961480: comm gmain: reading directory lblock 0
[28964.202758] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961480: comm gmain: reading directory lblock 0
[28964.203673] EXT4-fs warning: 15 callbacks suppressed
[28964.203683] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gmain: error -5 reading directory block
#11272204: lblock 0: comm nautilus: error -5 reading directory block
[28966.820544] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm nautilus: error -5 reading directory block
[28966.820569] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm nautilus: error -5 reading directory block
[28968.152926] EXT4-fs error: 95 callbacks suppressed
[28968.152934] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #237: reading directory lblock 0
[28968.153020] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #237: reading directory lblock 0
[28968.202620] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1316123: comm gmain: reading directory lblock 0
[28968.202637] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961473: comm gmain: reading directory lblock 0
[28968.202681] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4587561: comm gmain: reading directory lblock 0
[28968.202695] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4587561: comm gmain: reading directory lblock 0
[28968.202697] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961480: comm gmain: reading directory lblock 0
[28968.202710] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #4587522: comm gmain: reading directory lblock 0
[28968.202712] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961480: comm gmain: reading directory lblock 0
[28968.202725] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #9961480: comm gmain: reading directory lblock 0
[28972.204014] EXT4-fs warning: 16 callbacks suppressed
[28972.204024] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #4588092: lblock 0: comm gmain: error -5 reading directory block
[28972.204199] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gmain: error -5 reading directory block
[28972.262907] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #11272204: lblock 0: comm gmain: error -5 reading directory block
[28972.263138] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm gmain: error -5 reading directory block
[28972.872689] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28972.872845] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28972.879865] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm firefox: error -5 reading directory block
[28972.899649] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28972.899657] EXT4-fs warning (device nvme0n1p2): dx_probe:818: inode #12451841: lblock 0: comm Web Content: error -5 reading directory block
[28973.192589] EXT4-fs error: 179 callbacks suppressed
[28973.192598] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #237: reading directory lblock 0
[28973.192684] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1311230: comm StreamT~ns #237: reading directory lblock 0
[28973.530485] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1310722: comm bash: reading directory lblock 0
[28973.530521] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1310722: comm bash: reading directory lblock 0
[28973.530538] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1310722: comm bash: reading directory lblock 0
[28973.530549] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1310722: comm bash: reading directory lblock 0
[28973.530563] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1310722: comm bash: reading directory lblock 0
[28973.570942] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1310815: comm gnome-terminal-: reading directory lblock 0
[28973.570957] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1663: inode #1310722: comm gnome-terminal-: reading directory lblock 0
# Some duplicate lines removed in order to fit post limits
Hope this helps somebody!