Samsung NVME randomly goes down during activity

Rocherd87 · 16 October 2022 02:35

also check bios power-saving features regarding pcie turned them off, no change
Temps are not an issue, the activity need not be taxing or long.
Solid state drive/NVMe - ArchWiki Requires replacing stuff i dont understand in the first place (when in doubt, dont), of the stuff i could do, powersaving issue does not appear to be the issue ie got all zero’s timings in log.

SSD slow (NVME/PCIe4.0) (does not apply, not having a speed issue)
Just in case heres the output

00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge (prog-if 00 [Normal decode])
		LnkCap:	Port #1, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <64us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge (prog-if 00 [Normal decode])
		LnkCap:	Port #0, Speed 16GT/s, Width x8, ASPM L1, Exit Latency L1 <32us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge (prog-if 00 [Normal decode])
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L1, Exit Latency L1 <64us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] (prog-if 00 [Normal decode])
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] (prog-if 00 [Normal decode])
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCap:	Port #0, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L1 <64us
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream (prog-if 00 [Normal decode])
		LnkCap:	Port #0, Speed 16GT/s, Width x8, ASPM L1, Exit Latency L1 <32us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge (prog-if 00 [Normal decode])
		LnkCap:	Port #1, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <32us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge (prog-if 00 [Normal decode])
		LnkCap:	Port #4, Speed 16GT/s, Width x1, ASPM L1, Exit Latency L1 <32us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge (prog-if 00 [Normal decode])
		LnkCap:	Port #5, Speed 16GT/s, Width x1, ASPM L1, Exit Latency L1 <32us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge (prog-if 00 [Normal decode])
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge (prog-if 00 [Normal decode])
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge (prog-if 00 [Normal decode])
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCap:	Port #0, Speed 8GT/s, Width x2, ASPM L1, Exit Latency L1 <8us
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCap:	Port #4, Speed 5GT/s, Width x1, ASPM L1, Exit Latency L1 <8us
		LnkCap2: Supported Link Speeds: 2.5-5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 <64us
		LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCap:	Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCap:	Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us

Manjaro Linux Samsung SSD 970 Evo Plus not showing up in Boot Menu Not my issue solution also clearly does not apply.

FSTAB optimization check to see if hotswap was on, its not. the rest does not apply

Nvme0: controller is down; will reset - Framework Laptop - Framework Community this could be related but have no clue how to implement to find out at all even with the wiki above.

some other stuff from various sites to check info
sudo cat /etc/fstab

#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=3585-7F42                            /boot/efi      vfat    umask=0077 0 2
UUID=f26229a1-274c-472f-a55f-9c34aa6eec05 /              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
/dev/disk/by-label/other /mnt/other auto nosuid,nodev,nofail,x-gvfs-show 0 0

sudo lsblk -f

sda                                                                                   
└─sda1      vfat   FAT32 USB DISK 3D26-C255                               4.4G    70% /run/media/richard/USB DISK
nvme1n1                                                                               
├─nvme1n1p1 vfat   FAT32 NO_LABEL 3585-7F42                             299.1M     0% /boot/efi
└─nvme1n1p2 ext4   1.0            f26229a1-274c-472f-a55f-9c34aa6eec05  187.4G    15% /
nvme0n1                                                                               
└─nvme0n1p1 ext4   1.0   other    d6a952af-46be-4a58-a448-a8a99b521f5a  506.1G    41% /mnt/other

sudo fsck -vcck /dev/nvme0n1p1

fsck from util-linux 2.38.1
e2fsck 1.46.5 (30-Dec-2021)
Checking for bad blocks (non-destructive read-write test)
Testing with random pattern: done
other: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Inode 1313493 extent tree (at level 2) could be narrower. Optimize<y>? yes
Inode 1313515 extent tree (at level 2) could be narrower. Optimize<y>? yes
Inode 1313521 extent tree (at level 1) could be narrower. Optimize<y>? yes
Inode 1704115 extent tree (at level 1) could be shorter. Optimize<y>? yes
Inode 2359297 extent tree (at level 2) could be narrower. Optimize<y>? yes
Inode 2359432 extent tree (at level 2) could be narrower. Optimize<y>? yes
Inode 2359538 extent tree (at level 1) could be narrower. Optimize<y>? yes
Inode 2359551 extent tree (at level 1) could be narrower. Optimize<y>? yes
Inode 2359552 extent tree (at level 1) could be narrower. Optimize<y>? yes
yyyyyInode 5639092 extent tree (at level 1) could be narrower. Optimize ('a' enables 'yes' to all) <y>? yes
Inode 5639095 extent tree (at level 1) could be narrower. Optimize ('a' enables 'yes' to all) <y>? yes
Inode 10224490 extent tree (at level 1) could be narrower. Optimize ('a' enables 'yes' to all) <y>? yes
Inode 10224499 extent tree (at level 2) could be narrower. Optimize ('a' enables 'yes' to all) <y>? yes
Inode 12323561 extent tree (at level 2) could be narrower. Optimize<y>? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

other: ***** FILE SYSTEM WAS MODIFIED *****

  208609 inodes used (0.33%, out of 62513152)
    3867 non-contiguous files (1.9%)
     178 non-contiguous directories (0.1%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 202087/854/6
104858838 blocks used (41.94%, out of 250050816)
0 bad blocks
18 large files

  156164 regular files
   15685 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
   36751 symbolic links (5654 fast symbolic links)
       0 sockets

  208600 files

Oddly the above check took 4 hours and no issue, then again was unmounted sooo??? ~has no idea what that might mean~

This is the log of what it looks like when its down but could not see what presepitated it, maybe you can??? In order to get it back up, i restart system, then its running again basically untill this happens again.
Sudo journalctl -b -1

Oct 14 17:01:01 Office CROND[86475]: (root) CMD (run-parts /etc/cron.hourly)
Oct 14 17:01:01 Office CROND[86474]: (root) CMDEND (run-parts /etc/cron.hourly)
Oct 14 17:28:04 Office kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 80601032 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 73154992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 17:28:04 Office kernel: nvme 0000:01:00.0: enabling device (0000 -> 0002)
Oct 14 17:28:04 Office kernel: nvme nvme0: Removing after probe failure status: -19
Oct 14 17:28:04 Office kernel: nvme0n1: detected capacity change from 2000409264 to 0
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 998679288 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0
Oct 14 17:28:04 Office kernel: Aborting journal on device nvme0n1p1-8.
Oct 14 17:28:04 Office kernel: EXT4-fs error (device nvme0n1p1): ext4_journal_check_start:83: comm kworker/u64:1: Detected aborted journal
Oct 14 17:28:04 Office kernel: Buffer I/O error on dev nvme0n1p1, logical block 124813312, lost sync page write
Oct 14 17:28:04 Office kernel: JBD2: Error -5 detected when updating journal superblock for nvme0n1p1-8.
Oct 14 17:28:04 Office kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
Oct 14 17:28:04 Office kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
Oct 14 17:28:04 Office kernel: EXT4-fs (nvme0n1p1): Remounting filesystem read-only
Oct 14 17:28:04 Office kernel: EXT4-fs (nvme0n1p1): ext4_writepages: jbd2_start: 1024 pages, ino 4982215; err -30
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 1658092360 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Oct 14 17:28:04 Office kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:344: I/O error 10 writing to inode 4982212 starting block 207261546)
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 207261289
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 1226383344 op 0x1:(WRITE) flags 0x0 phys_seg 12 prio class 0
Oct 14 17:28:04 Office kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:344: I/O error 10 writing to inode 396399 starting block 153297951)
Oct 14 17:28:04 Office kernel: EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 396399, error -30)
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297662
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297663
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297664
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297665
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297666
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297667
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297668
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297669
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297670
Oct 14 17:28:05 Office systemd[1]: Unmounting /mnt/other...
Oct 14 17:28:05 Office umount[87717]: umount: /mnt/other: target is busy.
Oct 14 17:28:05 Office systemd[1]: mnt-other.mount: Mount process exited, code=exited, status=32/n/a
Oct 14 17:28:05 Office systemd[1]: Failed unmounting /mnt/other.
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 16:53:49 Office rtkit-daemon[1542]: Supervising 10 threads of 5 processes of 1 users.
Oct 14 16:53:49 Office rtkit-daemon[1542]: Supervising 10 threads of 5 processes of 1 users.
Oct 14 16:53:49 Office rtkit-daemon[1542]: Successfully made thread 86277 of process 85434 owned by '1000' RT at priority 10.
Oct 14 16:53:49 Office rtkit-daemon[1542]: Supervising 11 threads of 6 processes of 1 users.
Oct 14 17:01:01 Office CROND[86475]: (root) CMD (run-parts /etc/cron.hourly)
Oct 14 17:01:01 Office CROND[86474]: (root) CMDEND (run-parts /etc/cron.hourly)
Oct 14 17:28:04 Office kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 80601032 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 73154992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 17:28:04 Office kernel: nvme 0000:01:00.0: enabling device (0000 -> 0002)
Oct 14 17:28:04 Office kernel: nvme nvme0: Removing after probe failure status: -19
Oct 14 17:28:04 Office kernel: nvme0n1: detected capacity change from 2000409264 to 0
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 998679288 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0
Oct 14 17:28:04 Office kernel: Aborting journal on device nvme0n1p1-8.
Oct 14 17:28:04 Office kernel: EXT4-fs error (device nvme0n1p1): ext4_journal_check_start:83: comm kworker/u64:1: Detected aborted journal
Oct 14 17:28:04 Office kernel: Buffer I/O error on dev nvme0n1p1, logical block 124813312, lost sync page write
Oct 14 17:28:04 Office kernel: JBD2: Error -5 detected when updating journal superblock for nvme0n1p1-8.
Oct 14 17:28:04 Office kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
Oct 14 17:28:04 Office kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
Oct 14 17:28:04 Office kernel: EXT4-fs (nvme0n1p1): Remounting filesystem read-only
Oct 14 17:28:04 Office kernel: EXT4-fs (nvme0n1p1): ext4_writepages: jbd2_start: 1024 pages, ino 4982215; err -30
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 1658092360 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Oct 14 17:28:04 Office kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:344: I/O error 10 writing to inode 4982212 starting block 207261546)
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 207261289
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 1226383344 op 0x1:(WRITE) flags 0x0 phys_seg 12 prio class 0
Oct 14 17:28:04 Office kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:344: I/O error 10 writing to inode 396399 starting block 153297951)
Oct 14 17:28:04 Office kernel: EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 396399, error -30)
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297662
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297663
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297664
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297665
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297666
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297667
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297668
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297669
Oct 14 17:28:04 Office kernel: Buffer I/O error on device nvme0n1p1, logical block 153297670
Oct 14 17:28:05 Office systemd[1]: Unmounting /mnt/other...
Oct 14 17:28:05 Office umount[87717]: umount: /mnt/other: target is busy.
Oct 14 17:28:05 Office systemd[1]: mnt-other.mount: Mount process exited, code=exited, status=32/n/a
Oct 14 17:28:05 Office systemd[1]: Failed unmounting /mnt/other.
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393217: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #2: comm pool: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #2: comm pool: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #2: comm pool: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
Oct 14 17:28:17 Office NetworkManager[924]: <info>  [1665793697.4957] dhcp4 (wlp5s0): state changed new lease, address=192.168.0.245
Oct 14 17:28:18 Office kernel: EXT4-fs error: 7 callbacks suppressed
Oct 14 17:28:18 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:28:18 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:28:48 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:28:48 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:29:18 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:29:18 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:29:48 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:29:48 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:30:10 Office kernel: EXT4-fs error (device nvme0n1p1): ext4_wait_block_bitmap:531: comm wineserver: Cannot read block bitmap - block_group = 1185, block_bitmap = 38797313
Oct 14 17:30:10 Office kernel: EXT4-fs error (device nvme0n1p1): ext4_discard_preallocations:5042: comm wineserver: Error -5 reading block bitmap for 1185
Oct 14 17:30:11 Office kernel: EXT4-fs warning: 24 callbacks suppressed
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #394756: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #394756: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #394756: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #393501: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #395860: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #395860: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #395860: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #393501: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error: 66 callbacks suppressed
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs warning: 44 callbacks suppressed
Oct 14 17:30:21 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:28:05 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
Oct 14 17:28:17 Office NetworkManager[924]: <info>  [1665793697.4957] dhcp4 (wlp5s0): state changed new lease, address=192.168.0.245
Oct 14 17:28:18 Office kernel: EXT4-fs error: 7 callbacks suppressed
Oct 14 17:28:18 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:28:18 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:28:48 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:28:48 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:29:18 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:29:18 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:29:48 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:29:48 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393409: comm wineserver: reading directory lblock 0
Oct 14 17:30:10 Office kernel: EXT4-fs error (device nvme0n1p1): ext4_wait_block_bitmap:531: comm wineserver: Cannot read block bitmap - block_group = 1185, block_bitmap = 38797313
Oct 14 17:30:10 Office kernel: EXT4-fs error (device nvme0n1p1): ext4_discard_preallocations:5042: comm wineserver: Error -5 reading block bitmap for 1185
Oct 14 17:30:11 Office kernel: EXT4-fs warning: 24 callbacks suppressed
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #394756: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #394756: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #394756: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #393501: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #395860: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #395860: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #395860: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #393501: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error: 66 callbacks suppressed
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs warning: 44 callbacks suppressed
Oct 14 17:30:21 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:33 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:33 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:33 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:33 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:33 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:33 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:33 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:33 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:33 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:33 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:33 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:33 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:39 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:39 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:39 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:39 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:39 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:39 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:39 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:39 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:39 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:39 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:39 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:39 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:45 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:45 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:45 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:45 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:45 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:45 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:45 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:45 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:45 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:45 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:45 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:45 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:51 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:51 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:51 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:51 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:51 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:51 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:51 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:51 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:51 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:51 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:51 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:51 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:57 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:57 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:57 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:57 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:57 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:57 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:57 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:57 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:57 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:57 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:57 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:57 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:03 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:03 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:31:03 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:03 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:03 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:31:03 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:03 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:03 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:31:03 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:03 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:03 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:31:03 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:09 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:09 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:31:09 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:09 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:09 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:31:09 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:09 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:09 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:31:09 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:09 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:31:09 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:31:09 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): dx_probe:813: inode #394765: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #394756: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #394756: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #394756: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #393501: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #395860: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #395860: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #395860: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393501: comm services.exe: reading directory lblock 0
Oct 14 17:30:11 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #393501: lblock 0: comm services.exe: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error: 66 callbacks suppressed
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs warning: 44 callbacks suppressed
Oct 14 17:30:21 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:21 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:21 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1067: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0
Oct 14 17:30:27 Office kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1658: inode #393218: comm CIPCServer::Thr: reading directory lblock 0

i think you get the point by now this goes on and on and on…

Erim · 16 October 2022 05:18

Please use preformatting for your logs. This way it is very difficult to read.

See

Keruskerfuerst · 16 October 2022 05:26

Can you post inxi -Fza ?

Rocherd87 · 16 October 2022 05:33

 Kernel: 5.15.65-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=f26229a1-274c-472f-a55f-9c34aa6eec05 rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: Xfce v: 4.16.1 tk: Gtk v: 3.24.34 info: xfce4-panel wm: xfwm
    v: 4.16.1 vt: 7 dm: LightDM v: 1.32.0 Distro: Manjaro Linux
    base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X570-P v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 4002
    date: 06/15/2021
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K360
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M510
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 4042 high: 4043 min/max: N/A cores: 1: 4042 2: 4042
    3: 4043 4: 4042 5: 4042 6: 4042 7: 4042 8: 4042 9: 4042 10: 4042 11: 4042
    12: 4042 13: 4042 14: 4042 15: 4042 16: 4042 bogomips: 129421
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl and seccomp
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: ZOTAC driver: nvidia
    v: 515.65.01 alternate: nouveau,nvidia_drm non-free: 515.xx+ status: current
    (as of 2022-08) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0a:00.0
    chip-ID: 10de:1b80 class-ID: 0300
  Device-2: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 5-2:3 chip-ID: 046d:082d
    class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 21.1.4 compositor: xfwm v: 4.16.1 driver:
    X: loaded: nvidia gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x572mm (40.00x22.52")
    s-diag: 1166mm (45.9")
  Monitor-1: DP-0 pos: primary res: 3840x2160 hz: 60 dpi: 157
    size: 621x341mm (24.45x13.43") diag: 708mm (27.89") modes: N/A
  Monitor-2: HDMI-0 pos: primary size-res: N/A modes: N/A
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: ZOTAC
    driver: snd_hda_intel v: kernel bus-ID: 5-2:3 pcie: chip-ID: 046d:082d
    class-ID: 0102 gen: 3 speed: 8 GT/s serial: <filter> lanes: 16
    bus-ID: 0a:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo
  Sound Server-1: ALSA v: k5.15.65-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.57 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp6s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-6:4 chip-ID: 8087:0029 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
  Local Storage: total: 1.18 TiB used: 428.39 GiB (35.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung
    model: MZVLQ1T0HALB-000H1 size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: HPS4NFXV temp: 30.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: PC SN520
    SDAPNUW-256G-1006 size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter>
    rev: 20120006 temp: 35.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB model: USB DISK 3.0 size: 14.76 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
    rev: PMAP scheme: MBR
Partition:
  ID-1: / raw-size: 238.17 GiB size: 233.38 GiB (97.99%) used: 34.05 GiB
    (14.6%) fs: ext4 dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 288 KiB
    (0.1%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 37.5 C mobo: N/A gpu: nvidia temp: 44 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 39%
Info:
  Processes: 427 Uptime: 1d 1h 32m wakeups: 344 Memory: 31.26 GiB used: 6.13
  GiB (19.6%) Init: systemd v: 251 default: graphical tool: systemctl
  Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 1134 pm: pacman pkgs: 1115
  libs: 322 tools: pamac pm: flatpak pkgs: 19 Shell: Bash v: 5.1.16
  running-in: xfce4-terminal inxi: 3.3.21

Rocherd87 · 16 October 2022 05:41

most of it i couldnt understand in the first place sooo the difficulty is higher than 1 star.

brahma · 16 October 2022 06:43

your hard disk is damaged, just look at the logs, all related to errors and input/output, to superblocks, to sectors … back up your data asap!!!
check the smart status on your drive…

maycne.sonahoz · 16 October 2022 07:47

If you have difficulty understanding some tutorials, you can ask for details/clarification there.

Rocherd87 · 16 October 2022 09:45

Rocherd87:

Oct 14 17:28:04 Office kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 80601032 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 73154992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Oct 14 17:28:04 Office kernel: nvme 0000:01:00.0: enabling device (0000 -> 0002)
Oct 14 17:28:04 Office kernel: nvme nvme0: Removing after probe failure status: -19
Oct 14 17:28:04 Office kernel: nvme0n1: detected capacity change from 2000409264 to 0
Oct 14 17:28:04 Office kernel: blk_update_request: I/O error, dev nvme0n1, sector 998679288 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0
Oct 14 17:28:04 Office kernel: Aborting journal on device nvme0n1p1-8.
Oct 14 17:28:04 Office kernel: EXT4-fs error (device nvme0n1p1): ext4_journal_check_start:83: comm kworker/u64:1: Detected aborted journal
Oct 14 17:28:04 Office kernel: Buffer I/O error on dev nvme0n1p1, logical block 124813312, lost sync page write
Oct 14 17:28:04 Office kernel: JBD2: Error -5 detected when updating journal superblock for nvme0n1p1-8.
Oct 14 17:28:04 Office kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write

while I dont understand your guys tutorials over all,
maybe I’m id10t, but the controller is going down and refusing to reengage, and its only being discovered during audits. Remains down unless a system restart happens (turn it off then back on again.) That wouldnt be a superblock issue would it? The superblock cant be found because the controller is down (cant send mail across the country if the postal office is closed).

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.65-1-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZVLQ1T0HALB-000H1
Serial Number:                      S4U7NF0R546964
Firmware Version:                   HPS4NFXV
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,024,209,543,168 [1.02 TB]
Unallocated NVM Capacity:           0
Controller ID:                      5
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,024,209,543,168 [1.02 TB]
Namespace 1 Utilization:            1,024,208,953,344 [1.02 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 a511d1d5ca
Local Time is:                      Sun Oct 16 02:33:08 2022 PDT
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     4.86W       -        -    0  0  0  0        0       0
 1 +     4.49W       -        -    1  1  1  1        0       0
 2 +     2.37W       -        -    2  2  2  2        0     500
 3 -   0.0500W       -        -    3  3  3  3      210    1200
 4 -   0.0050W       -        -    4  4  4  4     1000    9000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0
 1 -    4096       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        31 Celsius
Available Spare:                    100%
Available Spare Threshold:          5%
Percentage Used:                    0%
Data Units Read:                    7,481,317 [3.83 TB]
Data Units Written:                 8,630,080 [4.41 TB]
Host Read Commands:                 38,094,528
Host Write Commands:                58,965,752
Controller Busy Time:               421
Power Cycles:                       214
Power On Hours:                     1,359
Unsafe Shutdowns:                   63
Media and Data Integrity Errors:    0
Error Information Log Entries:      172
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               31 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0        172     0  0x900c  0x4004      -            0     0     -

There is logs only, that shows errors, but it passed its i can account for everyone of those, does anyone know how to do the long test maybe i wont PASS that one, i have been dealing with this problem for over 2 months… soo yeah, that pretty much is going to be the same exact error over and over.

and its -h is about as helpfull as not giving actual examples… because according to the -h
sudo smartctl --test=long /dev/nvme0n1p1 should run long test it doesnt, so i try with one less tac (-), nope, then -t as then asks me to use, so i use it both ways, -t=long, and -t long, nope… Edit: had to put that in because it politely reminds me that sudo is required.

Nachlese · 16 October 2022 11:03

Test the device - not a partition on it.
this:
sudo smartctl --test=long /dev/nvme0n1
or this:
sudo smartctl -t long /dev/nvme0n1
both are the same

man smartctl

In some editions there is even a GUI tool to more easily use smartctl preinstalled, I believe.

Rocherd87 · 16 October 2022 11:21

i had to get rid of a conflict at-spi2-atk in order to get the smartctl (god only knows how thats going to bite me in the ass later)

edit add in:

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.74-3-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

NVMe device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information

i dont think thats suppose to happen like that, from what i saw on some webpages, even running short has some time to it.

Nachlese · 16 October 2022 11:29

I think it is.
The long test can take a … long time, very long even.
I don’t know whether you can access the data while the test is still running.
It looks like it. It even tells you how to.
I have only ever run the short offline test - I can’t tell you how to use the tool.

man smartctl

Zesko · 16 October 2022 11:38

Check nvme --help instead smartctl

Example:

$ sudo nvme smart-log /dev/nvme0

$ sudo nvme error-log /dev/nvme0

Rocherd87 · 16 October 2022 11:49

OKAY, the Samsung debugs are needed and i have no idea how to implement them

power_on_hours				: 107671072856885234789626228506624

Now… Im pretty sure i havent even been alive for that long, divied that by 24, coomes out tooooo 4.4862947e+30 atleast according to google calculator. right nor not… Im pretty sure i havent been alive that long.

.................
 Entry[ 0]   
.................
error_count	: 173
sqid		: 0
cmdid		: 0x701d
status_field	: 0x2002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag	: 0
parm_err_loc	: 0xffff
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................

The rest are as boring as can be

Zesko · 16 October 2022 11:59

smartctl

nvme

Maybe nvme has the bug. But I have no problem with that. What nvme device are you using?

I think you can ignore this error_count. I have more error_count than you, but I have no issue with my nvme device.

.................
 Entry[ 0]   
.................
error_count     : 3896
sqid            : 0
cmdid           : 0xc
status_field    : 0x2002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag       : 0
parm_err_loc    : 0xffff
lba             : 0
nsid            : 0
vs              : 0
trtype          : The transport type is not indicated or the error is not transport related.
cs              : 0
trtype_spec_info: 0
.................

megavolt · 16 October 2022 12:01

I guess this error is the problem and refer to the power saving feature.

I found this here:

Linux-Kernel Archive: Re: [BUG][5.18rc5] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10

1. Turn off APST (nvme_core.default_ps_max_latency_us=0)
2. Turn off APSM (pcie_aspm=off)
3. Turn off both

So add

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off

to the kernel parameter.

One of them or both should solve the issue.

Rocherd87 · 16 October 2022 12:03

im assuming sudo will do or is that su root?

Am i going to use sudo,
but because its kernel related will i need to switch user (su) root

mithrial · 16 October 2022 12:04

That’s the same thing.

Rocherd87 · 16 October 2022 12:06

okay, always thought sudo stood for switch user domain
not user account.

Zesko · 16 October 2022 12:08

No, @megavolt means you try to add these the kernel parameters:

If you use GRUB

Edit /etc/default/grub to add these kernel parameters in GRUB_CMDLINE_LINUX_DEFAULT=

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off

Run sudo update-grub
Reboot

Rocherd87 · 16 October 2022 12:13

i see a grub.d and something is telling to wait for a reply, because this seems like something that needs VERY clear instructions.

i litterally went to /ect/ and i see a grub.d folder, now… This looks like something that can screw up my system badly, unless i follow and understand correctly what you are asking me to do.

if i havent been clear, please be VERY clear with your instructions. Step by step.