URGENT! An entire drive couldn't be written/modified anymore after a failed Steam's Game update. Is it dieing or is Steam or the game having issues?

I don’t know much, so I can’t say much.

Suddenly, yesterday, while Space Marine 2 and other games were updating on Steam, Space Marine 2 gave a “Disk Write Error” and all other games (on the same drive) couldn’t write faster than 10MiB/s on it.
It’s an SSD.




I’ll explain more in a moment, but:

  1. I asked my brother to try using Steam on Fedora (he has it but still uses W10 all the time). BEFORE updating (still on Kernel 7.17) he updated SM2, and it went swiftly. Then he installed all the updates, restarted the machine, and updated Helldivers 2 and Darktide. They both went smootly.
    I want to see if deleting SM2 from the drive and reinstalling from 0 may fix the issue, BUT I WILL NOT DO IT RIGHT NOW IN CASE SOMEONE WHO KNOWS MORE THAN ME HAS SOME DIAGNOSTIC TEST TO MAKE ME DO.

  2. I managed to “temporarily fix” this (at least make it function, because it seems to WANT to break over and over again again), but now it went down to that speed once again, and then it started boing at 210MiB/s again, and literally now it just crashed once more…


I have to edit the whole text in real time as I am trying to figure this out in real time. I have been at this for almost 3 hours…
I really hope my SSD ain’t dieing. IT’S JUST OVER 2 YEARS OLD!!!

It gave the Write Error 3 more times (as I am trying to figure stuff out, right now), and now I installed a software to test the SSD.
Even tho it says “the drive is fine” I’ll say more later tho, I have to describe the whole issue…




So,
“Disk Write Error” on Steam’s download, written in bold, and red letters.

I tried to manually delete or create files on there, but it wouldn’t let me.

I then tried to remove and add back the folder to Steam, and I was greeted with this:

So I was afraid the SSD is dieing, but at least from what SMART is telling me it should be allright… (I can do more tests later):




Now, after the “fix”, Space Marines 2 does the “writing small files consecutively dance”, but after not even 8% of the way it just gives the error…


I tested all the OTHER drives and they seem to function normally.

How did I “fix” this?

Basically, I went to KDE Partition Manager, unmounted the drive, ran this Mounting permanently a Storage unit in Fedora KDE (automount at boot, no password, all users can see and edit files) - #37 by isaac0clarke again and then re-mounted it.
Now, after I did this THE FIRST TIME, I just unmount and remount the 2tb SSD and it works… until it doesn’t once again. I do not re-run the commands every time.


I actually tried to run

sudo setfacl -R -m d:o::rwx /NEW-DRIVE-2tb_SSD_Ext4
sudo setfacl -R -m o::rwx /NEW-DRIVE-2tb_SSD_Ext4

when the drive was still mounted, and A LOT of text was flashing on the screen, until “it was done” (nothing changed) and then I tried doing the same from here


but it says “failed to change stuff”, starting from Blender folders (which could be important, but I don’t know what or why; as you can see, blender is the fourth program inside the /NEW-DRIVE-2tb_SSD_Ext4/Steam_Games/steamapps/common/ folder AND Amid Evil has the first data in “the queue/list” which is not folders, since steamapps and common are the very first folders of every containing folder before).




As I said above, I managed to make the SSD work again, but after Steam tries to update Space Marine 2 it stops working, with Space Marine 2 giving “Disk Write Error” and other games updating at VERY SLOW SPEEDS.

I REALLY hope it’s either Steam having this bug, or Space Marine 2 spasming out for some dumb reason (the files in the “download folder” are basically 77gb, because I guess Steam first creates a dummy version of the game there, updates that one, and only then replaces the old version with the updated one, to avoid a full re-download I guess???).




As said above I asked my brother to try it out himself, and nothing bad seems to be happening…

I hope I get a solution ASAP because this is bad. The SSD can’t be written/modified once Disk Write Error occurs on Steam…

This is only a suggestion. Use at your own risk.
To repair Steam on Linux, you can try running the command LIBGL_ALWAYS_SOFTWARE=1 steam -no-cef-sandbox in the terminal, which may help resolve loading issues. If that doesn’t work, consider deleting Steam’s files while keeping the userdata and steamapps folders, then reinstalling Steam.

If you wish to check the drive for issues, you can use fsck.ext4 -f /dev/sdaX where sdaX is your 2TB ext4 formatted drive (you can determine which device it is from running lsblk

I assume it’s ext4 from the name you’ve given it in some of your screenshots.

You’ll want to do this from a live USB boot, as you don’t want to be running this on a mounted drive. It won’t change anything (the -f forces the check even if the drive looks clean) but it will tell you whether the issue is with the device itself, at which point you’re going to be faffing about with steam any downloading stuff again anyway.

:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0   9.1T  0 disk 
└─sda1        8:1    0   9.1T  0 part /NEW-DRIVE-10tb_Backup
sdb           8:16   0   1.8T  0 disk 
└─sdb1        8:17   0   1.8T  0 part /NEW-DRIVE-2tb_SSD_Ext4
sdc           8:32   0 894.3G  0 disk 
└─sdc1        8:33   0 894.3G  0 part 
sdd           8:48   0 232.9G  0 disk 
sde           8:64   0 476.9G  0 disk 
├─sde1        8:65   0    16M  0 part 
└─sde2        8:66   0 476.9G  0 part 
sdf           8:80   0   1.8T  0 disk 
├─sdf1        8:81   0    16M  0 part 
├─sdf2        8:82   0   1.6T  0 part /NEW-DRIVE-2tb_Video
└─sdf3        8:83   0 195.3G  0 part 
sdg           8:96   0   3.6T  0 disk 
└─sdg1        8:97   0   3.6T  0 part /NEW-DRIVE-4tb_Programs
sdh           8:112  1  14.5G  0 disk 
└─sdh1        8:113  1  14.5G  0 part 
zram0       251:0    0     8G  0 disk [SWAP]
nvme0n1     259:0    0 465.8G  0 disk 
├─nvme0n1p1 259:1    0   191M  0 part /boot/efi
├─nvme0n1p2 259:2    0   4.7G  0 part /boot
├─nvme0n1p3 259:3    0  93.1G  0 part /
├─nvme0n1p4 259:4    0 360.4G  0 part /NEW-DRIVE-NVMe_Data
└─nvme0n1p5 259:5    0   7.4G  0 part [SWAP]
:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0   9.1T  0 disk 
└─sda1        8:1    0   9.1T  0 part /NEW-DRIVE-10tb_Backup
sdb           8:16   0   1.8T  0 disk 
└─sdb1        8:17   0   1.8T  0 part 
sdc           8:32   0 894.3G  0 disk 
└─sdc1        8:33   0 894.3G  0 part 
sdd           8:48   0 232.9G  0 disk 
sde           8:64   0 476.9G  0 disk 
├─sde1        8:65   0    16M  0 part 
└─sde2        8:66   0 476.9G  0 part 
sdf           8:80   0   1.8T  0 disk 
├─sdf1        8:81   0    16M  0 part 
├─sdf2        8:82   0   1.6T  0 part /NEW-DRIVE-2tb_Video
└─sdf3        8:83   0 195.3G  0 part 
sdg           8:96   0   3.6T  0 disk 
└─sdg1        8:97   0   3.6T  0 part /NEW-DRIVE-4tb_Programs
sdh           8:112  1  14.5G  0 disk 
└─sdh1        8:113  1  14.5G  0 part 
zram0       251:0    0     8G  0 disk [SWAP]
nvme0n1     259:0    0 465.8G  0 disk 
├─nvme0n1p1 259:1    0   191M  0 part /boot/efi
├─nvme0n1p2 259:2    0   4.7G  0 part /boot
├─nvme0n1p3 259:3    0  93.1G  0 part /
├─nvme0n1p4 259:4    0 360.4G  0 part /NEW-DRIVE-NVMe_Data
└─nvme0n1p5 259:5    0   7.4G  0 part [SWAP]
:~$ fsck.ext4 -f /dev/sdb1
e2fsck 1.47.3 (8-Jul-2025)
fsck.ext4: Permission denied while trying to open /dev/sdb1
You must have r/w access to the filesystem or be root
:~$ sudo fsck.ext4 -f /dev/sdb1
[sudo] password for : 
e2fsck 1.47.3 (8-Jul-2025)
Pass 1: Checking inodes, blocks, and sizes
Inode 3410145 extent tree (at level 2) could be narrower.  Optimize<y>?

What do you suggest?
Because Inode 3410145 extent tree (at level 2) could be narrower. doesn’t really seem to be a problem, at least to me.
What does this mean?

I found this one https://unix.stackexchange.com/questions/392537/inode-extent-tree-could-be-shorter-message-during-fsck-what-does-it-mean but it’s meaningless to me, I have no knowledge about this as a reference…

Nope - don’t update or optimise anything until you know the drive is OK. You may be making errors found later in the scan worse by changing stuff at this point.

We check everything and change nothing. If it’s all good, THEN we can make updates to optimise the layout.

e2fsck 1.47.3 (8-Jul-2025)
Pass 1: Checking inodes, blocks, and sizes
Inode 3410145 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 3410146 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 3410149 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 3410150 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 3410504 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 3411223 extent tree (at level 2) could be narrower.  Optimize<y>? no
n
Inode 12714069 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 12714076 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 12714077 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 12714078 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 12714079 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 12714080 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 12714081 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 12714082 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 72583685 extent tree (at level 1) could be shorter.  Optimize<y>? no
Inode 73138261 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138263 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 73138267 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138269 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138270 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 73138271 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138272 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 73138273 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 73138299 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138362 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 73138366 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138367 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138368 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138369 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138370 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138371 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138372 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138373 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138374 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138375 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138376 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138377 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138378 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138379 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73138380 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 73139218 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 73663042 extent tree (at level 1) could be shorter.  Optimize<y>? no
Inode 81134020 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 81134021 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 81134022 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 81134355 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 97914400 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 97914610 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 97914788 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 97915232 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 97915378 extent tree (at level 1) could be narrower.  Optimize<y>? no
Inode 98435631 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98435711 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98453370 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98454039 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98454040 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98454041 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98454042 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98454043 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98454044 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98454045 extent tree (at level 2) could be narrower.  Optimize<y>? no
Inode 98454046 extent tree (at level 2) could be narrower.  Optimize<y>? no
nPass 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

2tb_Ext4_SSD: ***** FILE SYSTEM WAS MODIFIED *****
2tb_Ext4_SSD: 654294/122101760 files (1.8% non-contiguous), 388512323/488378368 blocks

That one “yes” was because the Konsole was stopping and starting, and I pressed “Send” by mistake…

If I’d known there would be so many optimisations offered, we could have used the -n flag to switch them all off. Too late now though.

Crack on - hopefully nothing horrific is found.

1 Like

Should I do anything else?

Nope - just let it run all the way though and scan everything. If it comes back clean, and the SMART stats say the drive is good, the we have to assume it’s a perfectly OK device.

It’s actually done. That’s all.

Seems to be ok then - there’s nothing terrible found - I’d mount it and try again.

You could always have a journalctl -f running in a terminal as your updates execute - any horror stories should be spat out in there if they are found.

By this you mean “mount the drive, run journalctl -f, start Steam, update the game, and post errors”, aye?

Aye.

You’ll soon know if it’s soiling itself as it’ll be vomiting all throughout the systemd journal.

Ok, I’ll be doing it right now.

It could take as little as 5 minutes to around 20 to fail, so you don’t need to stay here eagle-eyed.

Thanks for the help, see you in half an hour.

1 Like

Gotta write piece-by-piece because, after enough characters, the console deletes the oldest ones.

:~$ journalctl -f
Feb 27 15:43:46 Host-001 plasmashell[2518]: Failed to find service for Unity Launcher "gldriverquery.desktop"
Feb 27 15:43:46 Host-001 plasmashell[2518]: Failed to find service for Unity Launcher "gldriverquery.desktop"
Feb 27 15:43:47 Host-001 plasmashell[2518]: Failed to find service for Unity Launcher "gldriverquery.desktop"
Feb 27 15:43:47 Host-001 plasmashell[2518]: Failed to find service for Unity Launcher "gldriverquery.desktop"
Feb 27 15:43:47 Host-001 steamwebhelper[21904]: exec ./steamwebhelper -nocrashdialog -lang=en_US -cachedir=/home/iclarke/.lo
cal/share/Steam/config/htmlcache -steampid=21844 -buildid=1769025840 -steamid=0 -logdir=/home/iclarke/.local/share/Steam/log
s -uimode=7 -startcount=0 -steamuniverse=Public -realm=Global -clientui=/home/iclarke/.local/share/Steam/clientui -steampath
=/home/iclarke/.local/share/Steam/ubuntu12_32/steam -launcher=0 --valve-enable-site-isolation --enable-smooth-scrolling --pa
ssword-store=basic --log-file=/home/iclarke/.local/share/Steam/logs/cef_log.txt --disable-quick-menu --disable-component-upd
ate --gaia-url=http://disabled.invalid --enable-features=PlatformHEVCDecoderSupport --disable-features=WinRetrieveSuggestion
sOnlyOnDemand,SpareRendererForSitePerProcess,DcheckIsFatal,BlockPromptsIfIgnoredOften,ValveFFmpegAllowLowDelayHEVC
Feb 27 15:43:47 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:43:47 Host-001 steam[21758]: [2026-02-27 15:43:47.877] [MANGOHUD] [info] [blacklist.cpp:83] process 'vulkandriverq
uery' is blacklisted in MangoHud
Feb 27 15:43:48 Host-001 steam[21758]: [2026-02-27 15:43:48.469] [MANGOHUD] [info] [blacklist.cpp:83] process 'vulkandriverq
uery' is blacklisted in MangoHud
Feb 27 15:43:48 Host-001 steam[21758]: /usr/share/themes/Breeze-Dark/gtk-2.0/widgets/entry:70: error: unexpected identifier
'direction', expected character '}'
Feb 27 15:43:48 Host-001 steam[21758]: /usr/share/themes/Breeze-Dark/gtk-2.0/widgets/styles:36: error: invalid string consta
nt "combobox_entry", expected valid string constant
Feb 27 15:43:54 Host-001 steam[21758]: Desktop state changed: desktop: { pos: 0, 0 size: 2560,1440 } primary: { pos:
0, 0 size: 2560,1440 }
Feb 27 15:43:54 Host-001 steam[21758]: Caching cursor image for , size 32x32, serial 3, cache size = 0
Feb 27 15:43:57 Host-001 kwin_wayland[2232]: Could not delete texture because no context is current
Feb 27 15:43:57 Host-001 steam[21758]: reaping pid: 21845 -- steam
Feb 27 15:43:58 Host-001 steam[21758]: ProtonFixes[23866] WARN: Skipping fix execution. We are probably running a unit test.
Feb 27 15:43:58 Host-001 steam[21758]: wineserver: NTSync up and running!
Feb 27 15:43:59 Host-001 steam[21758]: [2026-02-27 15:43:59.586] [MANGOHUD] [info] [blacklist.cpp:83] process 'explorer.exe'
is blacklisted in MangoHud
Feb 27 15:43:59 Host-001 steam[21758]: [2026-02-27 15:43:59.924] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:43:59 Host-001 steam[21758]: [2026-02-27 15:43:59.925] [MANGOHUD] [info] [gpu.cpp:89] Set renderD128 as active GPU
(driver=amdgpu id=1002:73ef pci_dev=0000:09:00.0)
Feb 27 15:43:59 Host-001 steam[21758]: [2026-02-27 15:43:59.928] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:43:59 Host-001 steam[21758]: [2026-02-27 15:43:59.929] [MANGOHUD] [info] [gpu.cpp:89] Set renderD128 as active GPU
(driver=amdgpu id=1002:73ef pci_dev=0000:09:00.0)
Feb 27 15:43:59 Host-001 steam[21758]: [2026-02-27 15:43:59.958] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:43:59 Host-001 steam[21758]: [2026-02-27 15:43:59.959] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:43:59 Host-001 steam[21758]: Fossilize INFO: Overriding serialization path: "/home/iclarke/.local/share/Steam/shad
er_cache_temp_dir_d3d11_64/fozpipelinesv6/steamapprun_pipeline_cache".
Feb 27 15:44:02 Host-001 steam[21758]: ProtonFixes[24100] WARN: Skipping fix execution. We are probably running a unit test.
Feb 27 15:44:02 Host-001 steam[21758]: wineserver: NTSync up and running!
Feb 27 15:44:03 Host-001 steam[21758]: [2026-02-27 15:44:03.704] [MANGOHUD] [info] [blacklist.cpp:83] process 'explorer.exe'
is blacklisted in MangoHud
Feb 27 15:44:04 Host-001 steam[21758]: [2026-02-27 15:44:04.060] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:44:04 Host-001 steam[21758]: [2026-02-27 15:44:04.062] [MANGOHUD] [info] [gpu.cpp:89] Set renderD128 as active GPU
(driver=amdgpu id=1002:73ef pci_dev=0000:09:00.0)
Feb 27 15:44:04 Host-001 steam[21758]: [2026-02-27 15:44:04.082] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:44:04 Host-001 steam[21758]: [2026-02-27 15:44:04.083] [MANGOHUD] [info] [gpu.cpp:89] Set renderD128 as active GPU
(driver=amdgpu id=1002:73ef pci_dev=0000:09:00.0)
Feb 27 15:44:04 Host-001 steam[21758]: [2026-02-27 15:44:04.097] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:44:04 Host-001 steam[21758]: [2026-02-27 15:44:04.117] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:44:04 Host-001 steam[21758]: [2026-02-27 15:44:04.171] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:44:04 Host-001 steam[21758]: Fossilize INFO: Overriding serialization path: "/home/iclarke/.local/share/Steam/shad
er_cache_temp_dir_d3d12_64/fozpipelinesv6/steamapprun_pipeline_cache".
Feb 27 15:44:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:44:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:44:07 Host-001 systemd[1]: fprintd.service: Deactivated successfully.
Feb 27 15:44:07 Host-001 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 27 15:44:08 Host-001 audit: BPF prog-id=128 op=UNLOAD
Feb 27 15:44:36 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDirectory=/sys/class/bluetooth
Feb 27 15:44:36 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:44:52 Host-001 Discord[8236]: 15:44:52.063 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:44:52 Host-001 Discord[8236]: 15:44:52.064 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:44:52 Host-001 Discord[8236]: 15:44:52.064 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:44:52 Host-001 Discord[8236]: 15:44:52.064 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:44:52 Host-001 Discord[8236]: 15:44:52.064 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:44:52 Host-001 Discord[8236]: 15:44:52.064 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:44:55 Host-001 kernel: ata2.00: exception Emask 0x0 SAct 0xaf80c007 SErr 0x0 action 0x6 frozen
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/08:00:d0:4b:78/00:00:94:00:00/40 tag 0 ncq dma 4096 out
                                          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/30:08:60:14:47/01:00:74:00:00/40 tag 1 ncq dma 155648 out
                                          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/08:10:00:38:e7/00:00:95:00:00/40 tag 2 ncq dma 4096 out
                                          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/58:70:38:7e:45/1b:00:02:00:00/40 tag 14 ncq dma 3584000 ou
                                          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/00:78:f0:b1:45/20:00:02:00:00/40 tag 15 ncq dma 4194304 ou
                                          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/00:b8:38:1e:45/20:00:02:00:00/40 tag 23 ncq dma 4194304 ou
                                          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/00:c0:38:3e:45/20:00:02:00:00/40 tag 24 ncq dma 4194304 ou
                                          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/00:c8:38:5e:45/20:00:02:00:00/40 tag 25 ncq dma 4194304 ou
                                          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: READ FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 60/08:d0:18:fe:58/00:00:54:00:00/40 tag 26 ncq dma 4096 in
                                          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/08:d8:f0:a1:45/08:00:02:00:00/40 tag 27 ncq dma 1052672 ou
                                          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: READ FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 60/08:e8:00:72:f2/00:00:95:00:00/40 tag 29 ncq dma 4096 in
                                          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Feb 27 15:44:55 Host-001 kernel: ata2.00: cmd 61/10:f8:f0:d1:45/16:00:02:00:00/40 tag 31 ncq dma 2891776 ou
                                          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 15:44:55 Host-001 kernel: ata2.00: status: { DRDY }
Feb 27 15:44:55 Host-001 kernel: ata2: hard resetting link
Feb 27 15:44:55 Host-001 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 27 15:44:55 Host-001 kernel: ata2.00: configured for UDMA/133
Feb 27 15:44:55 Host-001 kernel: ahci 0000:02:00.1: port does not support device sleep
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#13 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#13 CDB: Write(10) 2a 00 02 44 34 50 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38024272 op 0x1:(WRITE) flags 0x4000 phys_seg 79 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 02 44 54 50 00 11 20 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38032464 op 0x1:(WRITE) flags 0x0 phys_seg 48 prio class 2
Feb 27 15:44:55 Host-001 kernel: EXT4-fs warning (device sdb1): ext4_end_bio:368: I/O error 10 writing to inode 72770168 starting block 4754058)
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752778
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752779
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752780
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752781
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752782
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752783
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752784
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752785
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752786
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752787
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#17 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#17 CDB: Write(10) 2a 00 02 44 6d 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38038840 op 0x1:(WRITE) flags 0x4000 phys_seg 80 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#18 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#18 CDB: Write(10) 2a 00 02 44 8d 38 00 0a f0 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38047032 op 0x1:(WRITE) flags 0x0 phys_seg 28 prio class 2
Feb 27 15:44:55 Host-001 kernel: EXT4-fs warning (device sdb1): ext4_end_bio:368: I/O error 10 writing to inode 72770168 starting block 4755879)
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#19 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#19 CDB: Write(10) 2a 00 02 44 9e 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38051384 op 0x1:(WRITE) flags 0x4000 phys_seg 80 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#20 CDB: Write(10) 2a 00 02 44 be 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38059576 op 0x1:(WRITE) flags 0x4000 phys_seg 81 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#21 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#21 CDB: Write(10) 2a 00 02 44 de 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38067768 op 0x1:(WRITE) flags 0x4000 phys_seg 80 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#22 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#22 CDB: Write(10) 2a 00 02 44 fe 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38075960 op 0x1:(WRITE) flags 0x4000 phys_seg 80 prio class 2
Feb 27 15:44:55 Host-001 kernel: ata2: EH complete
Feb 27 15:45:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDirectory=/sys/class/bluetooth
Feb 27 15:45:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:45:07 Host-001 kernel: EXT4-fs warning (device sdb1): ext4_end_bio:368: I/O error 10 writing to inode 72770168 starting block 4763591)
Feb 27 15:45:07 Host-001 kernel: buffer_io_error: 2936 callbacks suppressed
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756167
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756168
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756169
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756170
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756171
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756172
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756173
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756174
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756175
Feb 27 15:45:07 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4756176
Feb 27 15:45:13 Host-001 Discord[8236]: 15:45:13.327 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:45:13 Host-001 Discord[8236]: 15:45:13.327 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:45:13 Host-001 Discord[8236]: 15:45:13.327 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:45:13 Host-001 Discord[8236]: 15:45:13.327 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:45:13 Host-001 Discord[8236]: 15:45:13.327 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:45:13 Host-001 Discord[8236]: 15:45:13.327 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Feb 27 15:45:29 Host-001 Discord[8236]: 15:45:29.592 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:45:29 Host-001 Discord[8236]: 15:45:29.593 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:45:29 Host-001 Discord[8236]: 15:45:29.593 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:45:29 Host-001 Discord[8236]: 15:45:29.593 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:45:29 Host-001 Discord[8236]: 15:45:29.593 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:45:29 Host-001 Discord[8236]: 15:45:29.593 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:45:36 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:45:36 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:45:46 Host-001 steam[21758]: [2026-02-27 15:45:46] Background update loop checking for update. . .
Feb 27 15:45:46 Host-001 steam[21758]: [2026-02-27 15:45:46] Checking for available updates...
Feb 27 15:45:46 Host-001 steam[21758]: [2026-02-27 15:45:46] Downloading manifest: https://client-update.fastly.steamstatic.
com/steam_client_ubuntu12
Feb 27 15:45:46 Host-001 steam[21758]: [2026-02-27 15:45:46] Manifest download: send request
Feb 27 15:45:46 Host-001 steam[21758]: [2026-02-27 15:45:46] Manifest download: waiting for download to finish
Feb 27 15:45:47 Host-001 steam[21758]: [2026-02-27 15:45:47] Manifest download: finished
Feb 27 15:45:47 Host-001 steam[21758]: [2026-02-27 15:45:47] Download skipped: /steam_client_ubuntu12 version 1769025840, in
stalled version 1769025840, existing pending version 0
Feb 27 15:45:47 Host-001 steam[21758]: [2026-02-27 15:45:47] Nothing to do
Feb 27 15:46:04 Host-001 Discord[8236]: 15:46:04.742 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:04 Host-001 Discord[8236]: 15:46:04.742 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:04 Host-001 Discord[8236]: 15:46:04.742 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:04 Host-001 Discord[8236]: 15:46:04.742 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:04 Host-001 Discord[8236]: 15:46:04.743 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:04 Host-001 Discord[8236]: 15:46:04.743 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:46:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:46:09 Host-001 Discord[8236]: 15:46:09.342 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:09 Host-001 Discord[8236]: 15:46:09.343 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:09 Host-001 Discord[8236]: 15:46:09.343 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:09 Host-001 Discord[8236]: 15:46:09.343 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:09 Host-001 Discord[8236]: 15:46:09.343 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:46:09 Host-001 Discord[8236]: 15:46:09.343 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.

Feb 27 15:46:31 Host-001 wireplumber[2226]: wp-event-dispatcher: <WpAsyncEventHook:0x561e74262940> failed: failed to activat
e item: Object activation aborted: proxy destroyed
Feb 27 15:46:36 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:46:36 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:46:51 Host-001 systemd[1903]: Starting app-org.kde.spectacle.service - Spectacle screenshot capture utility...
Feb 27 15:46:51 Host-001 systemd[1903]: Started app-org.kde.spectacle.service - Spectacle screenshot capture utility.
Feb 27 15:46:51 Host-001 spectacle[24363]: Attempting to use Tesseract library "libtesseract.so.5.5"
Feb 27 15:46:51 Host-001 spectacle[24363]: Detected Tesseract version "5.5.2"
Feb 27 15:46:51 Host-001 spectacle[24363]: Loaded Tesseract runtime library from "libtesseract.so.5.5"
Feb 27 15:46:59 Host-001 spectacle[24363]: KFileFilterCombo::setCurrentFilter: Could not find file filter KFileFilter(MIME p
atterns: QList("image/png") File patterns: QList() label: "PNG image")
Feb 27 15:46:59 Host-001 spectacle[24363]: KFileFilterCombo::setCurrentFilter: Could not find file filter KFileFilter(MIME p
atterns: QList() File patterns: QList("*.png") label: "PNG image")
Feb 27 15:46:59 Host-001 spectacle[24363]: KFileFilter::fromMimeType() called with unknown MIME type "image/hej2k"
Feb 27 15:46:59 Host-001 spectacle[24363]: No node found for item that was just removed: QUrl("file:///NEW-DRIVE-10tb_Backup
/10tb/when installing steamtinkerlaunch dependencies, 2026 01 22")
Feb 27 15:47:00 Host-001 systemd[1]: Starting sssd-kcm.service - SSSD Kerberos Cache Manager...
Feb 27 15:47:00 Host-001 systemd[1]: Started sssd-kcm.service - SSSD Kerberos Cache Manager.
Feb 27 15:47:00 Host-001 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=sssd-kcm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 27 15:47:00 Host-001 sssd_kcm[24467]: Starting up
Feb 27 15:47:00 Host-001 kioworker[24473]: Not a JPEG file: starts with 0x52 0x49
Feb 27 15:47:00 Host-001 kioworker[24473]: Not a JPEG file: starts with 0x52 0x49
Feb 27 15:47:00 Host-001 kioworker[24473]: Not a JPEG file: starts with 0x52 0x49
Feb 27 15:47:00 Host-001 kioworker[24473]: Not a JPEG file: starts with 0x52 0x49
Feb 27 15:47:03 Host-001 systemd[1903]: app-org.kde.spectacle.service: Consumed 3.098s CPU time, 301.9M memory peak.
Feb 27 15:47:06 Host-001 systemd[1903]: Started app-org.kde.dolphin@0083f1f634de456e8dd3b6953e1f8121.service - Dolphin - Fil
e Manager.
Feb 27 15:47:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:47:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:47:07 Host-001 plasmashell[2518]: error creating screencast "Could not find window id {b8abdf3c-8e7c-4d25-8655-b83
85df3b926}"
Feb 27 15:47:07 Host-001 kioworker[24695]: Not a JPEG file: starts with 0x52 0x49
Feb 27 15:47:07 Host-001 kioworker[24695]: Not a JPEG file: starts with 0x52 0x49
Feb 27 15:47:07 Host-001 kioworker[24695]: Not a JPEG file: starts with 0x52 0x49
Feb 27 15:47:07 Host-001 kioworker[24695]: Not a JPEG file: starts with 0x52 0x49
Feb 27 15:47:10 Host-001 wireplumber[2226]: wp-event-dispatcher: <WpAsyncEventHook:0x561e7423b300> failed: <WpSiStandardLink
:0x561e7453a4e0> link failed: 1 of 1 PipeWire links failed to activate
Feb 27 15:47:36 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:47:36 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:47:52 Host-001 kwin_wayland[2232]: This plugin does not support grabbing the keyboard
Feb 27 15:48:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:48:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:48:07 Host-001 steam[21758]: Proton: Upgrading prefix from GE-Proton10-28 to GE-Proton10-32 (/NEW-DRIVE-2tb_SSD_Ex
t4/Steam Games/steamapps/compatdata/2183900/)
Feb 27 15:48:07 Host-001 steam[21758]: Proton: Prefix has an invalid version?! You may want to back up user files and delete
this prefix.
Feb 27 15:48:09 Host-001 wireplumber[2226]: wp-event-dispatcher: <WpAsyncEventHook:0x561e7423b300> failed: <WpSiStandardLink
:0x561e74569320> link failed: 1 of 1 PipeWire links failed to activate
Feb 27 15:48:13 Host-001 steam[21758]: wineserver: NTSync up and running!
Feb 27 15:48:14 Host-001 steam[21758]: [2026-02-27 15:48:14.266] [MANGOHUD] [info] [blacklist.cpp:83] process 'explorer.exe'
is blacklisted in MangoHud
Feb 27 15:48:14 Host-001 steam[21758]: [2026-02-27 15:48:14.618] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:48:14 Host-001 steam[21758]: [2026-02-27 15:48:14.619] [MANGOHUD] [info] [gpu.cpp:89] Set renderD128 as active GPU
(driver=amdgpu id=1002:73ef pci_dev=0000:09:00.0)
Feb 27 15:48:14 Host-001 steam[21758]: [2026-02-27 15:48:14.651] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:48:15 Host-001 Discord[8236]: 15:48:15.829 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:15 Host-001 Discord[8236]: 15:48:15.829 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:15 Host-001 Discord[8236]: 15:48:15.830 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:15 Host-001 Discord[8236]: 15:48:15.830 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:15 Host-001 Discord[8236]: 15:48:15.830 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:15 Host-001 Discord[8236]: 15:48:15.830 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:16 Host-001 steam[21758]: regsvr32: Successfully unregistered DLL 'C:\windows\\Microsoft.NET\Framework\v4.0.303
19\diasymreader.dll'
Feb 27 15:48:16 Host-001 steam[21758]: regsvr32: Successfully unregistered DLL 'C:\windows\\Microsoft.NET\Framework64\v4.0.3
0319\diasymreader.dll'
Feb 27 15:48:20 Host-001 steam[21758]: [2026-02-27 15:48:20.902] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:48:20 Host-001 steam[21758]: [2026-02-27 15:48:20.903] [MANGOHUD] [info] [gpu.cpp:89] Set renderD128 as active GPU
(driver=amdgpu id=1002:73ef pci_dev=0000:09:00.0)
Feb 27 15:48:20 Host-001 steam[21758]: [2026-02-27 15:48:20.938] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:48:24 Host-001 Discord[8236]: 15:48:24.546 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:24 Host-001 Discord[8236]: 15:48:24.546 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:24 Host-001 Discord[8236]: 15:48:24.546 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:24 Host-001 Discord[8236]: 15:48:24.546 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:24 Host-001 Discord[8236]: 15:48:24.547 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:24 Host-001 Discord[8236]: 15:48:24.547 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:28 Host-001 Discord[8236]: 15:48:28.974 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:28 Host-001 Discord[8236]: 15:48:28.975 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:28 Host-001 Discord[8236]: 15:48:28.975 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:28 Host-001 Discord[8236]: 15:48:28.975 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:28 Host-001 Discord[8236]: 15:48:28.975 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:48:28 Host-001 Discord[8236]: 15:48:28.975 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.

It did it, without problems…
Jokes aside… wow…

I think you might have some badblocks perhaps on /dev/sdb1:

Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#13 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#13 CDB: Write(10) 2a 00 02 44 34 50 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38024272 op 0x1:(WRITE) flags 0x4000 phys_seg 79 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 02 44 54 50 00 11 20 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38032464 op 0x1:(WRITE) flags 0x0 phys_seg 48 prio class 2
Feb 27 15:44:55 Host-001 kernel: EXT4-fs warning (device sdb1): ext4_end_bio:368: I/O error 10 writing to inode 72770168 starting block 4754058)
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752778
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752779
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752780
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752781
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752782
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752783
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752784
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752785
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752786
Feb 27 15:44:55 Host-001 kernel: Buffer I/O error on device sdb1, logical block 4752787
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#17 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#17 CDB: Write(10) 2a 00 02 44 6d 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38038840 op 0x1:(WRITE) flags 0x4000 phys_seg 80 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#18 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#18 CDB: Write(10) 2a 00 02 44 8d 38 00 0a f0 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38047032 op 0x1:(WRITE) flags 0x0 phys_seg 28 prio class 2
Feb 27 15:44:55 Host-001 kernel: EXT4-fs warning (device sdb1): ext4_end_bio:368: I/O error 10 writing to inode 72770168 starting block 4755879)
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#19 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#19 CDB: Write(10) 2a 00 02 44 9e 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38051384 op 0x1:(WRITE) flags 0x4000 phys_seg 80 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#20 CDB: Write(10) 2a 00 02 44 be 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38059576 op 0x1:(WRITE) flags 0x4000 phys_seg 81 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#21 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#21 CDB: Write(10) 2a 00 02 44 de 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38067768 op 0x1:(WRITE) flags 0x4000 phys_seg 80 prio class 2
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#22 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=49s
Feb 27 15:44:55 Host-001 kernel: sd 1:0:0:0: [sdb] tag#22 CDB: Write(10) 2a 00 02 44 fe 38 00 20 00 00
Feb 27 15:44:55 Host-001 kernel: I/O error, dev sdb, sector 38075960 op 0x1:(WRITE) flags 0x4000 phys_seg 80 prio class 2

My theory is that these are bad, but currently unused so the filesystem check finds nothing wrong with them as there’s nothing in them. When they are called inti use by Steam to hold some new data, they whine.

ext4 should take care of relocating them but something to be aware of.

I’m just basing this on searching around a bit, but apparently that error can often be due to a cable problem. Might be worth replugging the SATA cable at both ends, or trying a different one if you have one spare.

So you think, with the few data we have, that some of the SSD’s blocks (data blocks, in cells) are bad/dead?

Anyways, I am “verifying the data” of Helldivers 2 and SM2 right now.

Here’s H2

:~$ journalctl -f
Feb 27 15:57:09 Host-001 Discord[8236]: 15:57:09.267 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:57:09 Host-001 Discord[8236]: 15:57:09.267 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:57:09 Host-001 Discord[8236]: 15:57:09.267 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:57:09 Host-001 Discord[8236]: 15:57:09.267 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 15:57:36 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:57:36 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:57:49 Host-001 Discord[8236]: 15:57:49.999 › [WindowVisibilityVideoManager] Incoming video enabled changed, incomi
ngVideoEnabled = false
Feb 27 15:57:53 Host-001 systemd[1903]: app-org.kde.dolphin@0083f1f634de456e8dd3b6953e1f8121.service: Consumed 4.408s CPU ti
me, 333.8M memory peak.
Feb 27 15:57:59 Host-001 systemd[1903]: Started app-org.kde.konsole@7975561c0f1a4960b6b159d55114d7e1.service - Konsole - Ter
minal.
Feb 27 15:57:59 Host-001 systemd[1903]: Started app-org.kde.konsole-25611.scope.
Feb 27 15:58:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:58:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:58:10 Host-001 steam[21758]: wineserver: NTSync up and running!
Feb 27 15:58:11 Host-001 steam[21758]: [2026-02-27 15:58:11.816] [MANGOHUD] [info] [blacklist.cpp:83] process 'explorer.exe'
is blacklisted in MangoHud
Feb 27 15:58:12 Host-001 steam[21758]: [2026-02-27 15:58:12.363] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:58:12 Host-001 steam[21758]: [2026-02-27 15:58:12.364] [MANGOHUD] [info] [gpu.cpp:89] Set renderD128 as active GPU
(driver=amdgpu id=1002:73ef pci_dev=0000:09:00.0)
Feb 27 15:58:12 Host-001 steam[21758]: [2026-02-27 15:58:12.398] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:58:36 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:58:36 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false

SM2

Feb 27 15:59:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:59:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 15:59:21 Host-001 steam[21758]: wineserver: NTSync up and running!
Feb 27 15:59:22 Host-001 steam[21758]: [2026-02-27 15:59:22.853] [MANGOHUD] [info] [blacklist.cpp:83] process 'explorer.exe'
is blacklisted in MangoHud
Feb 27 15:59:23 Host-001 steam[21758]: [2026-02-27 15:59:23.349] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:59:23 Host-001 steam[21758]: [2026-02-27 15:59:23.351] [MANGOHUD] [info] [gpu.cpp:89] Set renderD128 as active GPU
(driver=amdgpu id=1002:73ef pci_dev=0000:09:00.0)
Feb 27 15:59:23 Host-001 steam[21758]: [2026-02-27 15:59:23.387] [MANGOHUD] [warning] [overlay_params.cpp:1139] You have spe
cified both gpu_list and pci_dev, ignoring pci_dev.
Feb 27 15:59:36 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 15:59:36 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 16:00:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 16:00:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 16:00:36 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 16:00:36 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 16:00:57 Host-001 Discord[8236]: 16:00:57.012 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:00:57 Host-001 Discord[8236]: 16:00:57.013 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:00:57 Host-001 Discord[8236]: 16:00:57.013 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:00:57 Host-001 Discord[8236]: 16:00:57.013 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:00:57 Host-001 Discord[8236]: 16:00:57.013 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:00:57 Host-001 Discord[8236]: 16:00:57.013 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:00 Host-001 CROND[26286]: (root) CMD (run-parts /etc/cron.hourly)
Feb 27 16:01:00 Host-001 run-parts[26289]: (/etc/cron.hourly) starting 0anacron
Feb 27 16:01:00 Host-001 run-parts[26295]: (/etc/cron.hourly) finished 0anacron
Feb 27 16:01:00 Host-001 CROND[26285]: (root) CMDEND (run-parts /etc/cron.hourly)
Feb 27 16:01:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 16:01:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 16:01:07 Host-001 Discord[8236]: 16:01:07.142 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:07 Host-001 Discord[8236]: 16:01:07.142 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:07 Host-001 Discord[8236]: 16:01:07.142 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:07 Host-001 Discord[8236]: 16:01:07.142 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:07 Host-001 Discord[8236]: 16:01:07.142 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:07 Host-001 Discord[8236]: 16:01:07.142 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:12 Host-001 Discord[8236]: 16:01:12.103 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:12 Host-001 Discord[8236]: 16:01:12.103 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:12 Host-001 Discord[8236]: 16:01:12.103 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:12 Host-001 Discord[8236]: 16:01:12.103 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:12 Host-001 Discord[8236]: 16:01:12.104 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:12 Host-001 Discord[8236]: 16:01:12.104 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:17 Host-001 Discord[8236]: 16:01:17.976 › The resource https://discord.com/assets/189422196a4f8b53.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:17 Host-001 Discord[8236]: 16:01:17.977 › The resource https://discord.com/assets/ce3b8055f5114434.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:17 Host-001 Discord[8236]: 16:01:17.977 › The resource https://discord.com/assets/cb2006dbced0e246.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:17 Host-001 Discord[8236]: 16:01:17.977 › The resource https://discord.com/assets/7a6a566c2e88a35d.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:17 Host-001 Discord[8236]: 16:01:17.977 › The resource https://discord.com/assets/e52f0cba712e2fb4.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:17 Host-001 Discord[8236]: 16:01:17.978 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was pr
eloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an approp
riate `as` value and it is preloaded intentionally.
Feb 27 16:01:36 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 16:01:36 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false
Feb 27 16:01:42 Host-001 brave-browser-stable[10597]: [10667:10864:0227/160142.819198:ERROR:components/viz/service/display/d
isplay.cc:275] Frame latency is negative: -0.256 ms
Feb 27 16:02:06 Host-001 systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDir
ectory=/sys/class/bluetooth
Feb 27 16:02:06 Host-001 kdeconnectd[2890]: Cannot find Bluez 5 adapter for device search false

That would be funny.

Yeah, I’ve had a few ‘impenetrable’ issues which I look back on saying “doh! if only I’d tried changing the cable right at the start!”

1 Like