So, I was taking a shower and did not shut down my computer, as usual. Upon coming back to me KDE greeted me with a nasty popup - I should check my journal, there are errors.
So I did exxactly this, and yes, there are not only errors, but it is still in the sate that more errors occur.
It is basically this in a loop, with other stuff mixed in:
i 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): error writing primary super block to device 1
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 55158490, rd 2174, flush 14501, corrupt 0, gen 0
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 55158491, rd 2174, flush 14501, corrupt 0, gen 0
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 55158492, rd 2174, flush 14501, corrupt 0, gen 0
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 55158493, rd 2174, flush 14501, corrupt 0, gen 0
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 55158494, rd 2174, flush 14501, corrupt 0, gen 0
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 55158494, rd 2174, flush 14502, corrupt 0, gen 0
Mai 18 17:36:00 neuromancer kernel: BTRFS warning (device nvme0n1p2): lost super block write due to IO error on /dev/nvme0n1p2 (-5)
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): error writing primary super block to device 1
Mai 18 17:36:00 neuromancer kernel: BTRFS warning (device nvme0n1p2): lost super block write due to IO error on /dev/nvme0n1p2 (-5)
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): error writing primary super block to device 1
Mai 18 17:36:00 neuromancer kernel: BTRFS warning (device nvme0n1p2): lost super block write due to IO error on /dev/nvme0n1p2 (-5)
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): error writing primary super block to device 1
Mai 18 17:36:00 neuromancer kernel: BTRFS warning (device nvme0n1p2): lost super block write due to IO error on /dev/nvme0n1p2 (-5)
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): error writing primary super block to device 1
Mai 18 17:36:00 neuromancer kernel: BTRFS warning (device nvme0n1p2): lost super block write due to IO error on /dev/nvme0n1p2 (-5)
Mai 18 17:36:00 neuromancer kernel: BTRFS error (device nvme0n1p2): error writing primary super block to device 1
Mai 18 17:36:01 neuromancer kernel: BTRFS warning (device nvme0n1p2): lost super block write due to IO error on /dev/nvme0n1p2 (-5)
Mai 18 17:36:01 neuromancer kernel: BTRFS warning (device nvme0n1p2): lost super block write due to IO error on /dev/nvme0n1p2 (-5)
Mai 18 17:36:01 neuromancer kernel: BTRFS warning (device nvme0n1p2): lost super block write due to IO error on /dev/nvme0n1p2 (-5)
Mai 18 17:36:01 neuromancer kernel: BTRFS error (device nvme0n1p2): error writing primary super block to device 1
Mai 18 17:36:05 neuromancer kernel: BTRFS warning (device nvme0n1p2): lost super block write due to IO error on /dev/nvme0n1p2 (-5)
My “disc” layout looks like this:
sudo lsblk -o +uuid,name,model
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS UUID NAME MODEL
sda 8:0 0 476,9G 0 disk sda Samsung SSD 860 PRO 512GB
└─sda1 8:1 0 476,9G 0 part /Data fc6a43bb-ec9a-4f23-94e9-eff7cf5f250c sda1
sdb 8:16 0 14,6T 0 disk sdb ST16000NM001G-2KK103
├─sdb1 8:17 0 3,8T 0 part /Misc e0e1bff4-1418-4574-b3da-823cfe4fc668 sdb1
├─sdb2 8:18 0 9,3T 0 part /Stuff 545f70e0-5226-4d38-862e-cf159fbf6e7f sdb2
└─sdb3 8:19 0 1,5T 0 part /backup 8c7a3875-418a-49de-8a6e-47a480315c22 sdb3
zram0 252:0 0 16G 0 disk [SWAP] 0bb369f7-c2cd-4af9-814e-e6f21decf2eb zram0
nvme0n1 259:0 0 0B 0 disk nvme0n1 Seagate FireCuda 530 ZP2000GM30013
├─nvme0n1p1 259:2 0 1000M 0 part /boot/efi BDEB-C54C nvme0n1p1
└─nvme0n1p2 259:3 0 1,8T 0 part /var/log 178ba18b-3faa-4b38-b7e5-5b0f5d2f285c nvme0n1p2
/var/cache
/home
/Virtual
/
nvme1n1 259:1 0 1,8T 0 disk nvme1n1 Seagate FireCuda 530 ZP2000GM30013
├─nvme1n1p1 259:4 0 1000M 0 part 5B0B-DC27 nvme1n1p1
└─nvme1n1p2 259:5 0 1,8T 0 part 178ba18b-3faa-4b38-b7e5-5b0f5d2f285c nvme1n1p2
I use a btrfs “Raid1”:
sudo btrfs fi show
Label: 'endeavouros' uuid: 178ba18b-3faa-4b38-b7e5-5b0f5d2f285c
Total devices 2 FS bytes used 1.08TiB
devid 1 size 1.82TiB used 1.24TiB path /dev/nvme0n1p2
devid 2 size 1.82TiB used 1.24TiB path /dev/nvme1n1p2
Soooo what do I do now?