Man you are a wizard.
I set up the Udev rule for the scheduler and
Ive been running a game now for 6 hours, and all seems fine. The Dmesg is clean, the drives are all accounted for, seems all is in order. }
Will check in tommorow if it stays the same.
Thank you so so much.
Youâre welcome, glad that helped. 
As said, Iâve corrected I/O errors in the past by changing the scheduler. Itâs not something that is done that often, but occaisionally it helps.
I hope that is a permanent fix, and that the new scheduler keeps things working properly for the forseable future.
Hi seems I sang too soon, turned on the pc and the two drives just went MIA.
FSCK states the same thing for both the working and the bad drives.
At this point im thinking the drives are really dying.
But then again, changing the scheduler did Let me use the PC
The only thing I did after is install Sunshine. I turned off the pc, and went to sleep
I wake up go to the p tunr it on start steam and the disks go poof again.
So, i reloaded the checkpoint from snapper to the point where we were yesterday.
It would surprise me if this was related, as I cannot imagine how Sunshine could affect the disks. and why only two outta three. (or 4 if we count the root drive)
ââlance@GarudaKing in ~ as đ§ took 12ms
[đ´] Ă sudo fsck /dev/sdc
[sudo] password for lance:
fsck from util-linux 2.40.2
e2fsck 1.47.1 (20-May-2024)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
/dev/sdc contains `DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 "Invalid partition table" at o
ffset 0x17b "Error loading operating system" at offset 0x19a "Missing operating system"; partition 1 : ID=0xee
, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors' data
ââlance@GarudaKing in ~ as đ§ took 2s
[đ´] Ă sudo fsck /dev/sdc1
fsck from util-linux 2.40.2
e2fsck 1.47.1 (20-May-2024)
SteamLib: clean, 12/250052608 files, 15985043/1000196352 blocks
Sorry to hear that @Lancer669. Sadly, I had a sneaking suspicion the fix wouldnât be permanent.
Can you run smart tests on all your drives and report on their health status?
Do you have any external enclosures that you can transfer one of your drives into?
Do you have another computer that you could swap one or more of the problematic drives into, to see if they work properly in another system?
Can you boot from a live disk and see/access the missing drives?
Unfortunately, this is not sounding good. Did you perhaps have a power failure event just before you started noticing problems?
No power outage, just the issues with the crashing.
I have a suspicion I may have killed the drives recreating the filesystem.
either that or sunshine really hates me. After using snapper to return back before sunshine install The drives are back and havent dissapeared. yet.
so Ill see. granted i wasnt around most day.
Il run the tests, try another pc and a few other things.
Might see if I was just dumb and formatted them wrong.
At this point im giving up on the drives but i want to find out what i Effed up to not repeat it , since i have one storage drive left XD
Hi to report back the findings.
Disks work currently and i observed a peculiar behaviour.
The disks dissapear again shortly after booting from a shut down. After a restart they work seemingly normally.
I ordered a external sata neclosure and will run them over usb for a while to see if that changes anything.
For now. They are functional.
Thank you for your help. Much appreciated
Do you have fast boot/fast startup disabled in Windows?
Be sure you double check, as Windows update sometimes re-enables it.
Hi, No I disabled it both before reinstalling the entire system. as you said it was
reenabled. I wiped windows from the pc completely. had enough of its shenanigans. not worth it.
also updated the BIOS, turned off C-states and set the sata controller to ahci.
Unbelievably Windowâs shenanigans can still linger even after itâs uninstalled.
Just to be sure no strange side effects remain I would reset your bios to the factory default, then power down. After power down remove all power sources from your computer for 5 minutes, then restart.
You will need to change some bios settings again for Linux compatibility as before when you installed Garuda.
Nothing suprises me anymore with it 
is what drove me to Linux in the first place.
Will try the cold reset later in the day when im done with work. Thank you again 
garuda-inxi detected your system as a dual boot with Windows. Thatâs why I was wondering if Windows was interfering with proper hardware initialization as it is want to do.
yeah, the inxi is from before I nuked the pc.
here the fresh one.
System:
Kernel: 6.10.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=bd9ed32b-a33e-45ba-beb7-17eb178049d4 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASRock product: B650E Taichi Lite v: N/A
serial: <superuser required>
Mobo: ASRock model: B650E Taichi Lite serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends LLC. v: 3.06
date: 07/26/2024
Battery:
ID-1: hidpp_battery_2 charge: 43% condition: N/A volts: 3.8 min: N/A
model: Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A
serial: <filter> status: discharging
CPU:
Info: model: AMD Ryzen 9 7950X3D bits: 64 type: MT MCP MCM arch: Zen 4
gen: 5 level: v4 note: check built: 2022+ process: TSMC n5 (5nm)
family: 0x19 (25) model-id: 0x61 (97) stepping: 2 microcode: 0xA601206
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 dies: 2 smt: enabled
cache: L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 16 MiB
desc: 16x1024 KiB L3: 128 MiB desc: 1x32 MiB, 1x96 MiB
Speed (MHz): avg: 1310 high: 4740 min/max: 545/5759 scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 545 2: 545 3: 3774
4: 545 5: 545 6: 3993 7: 545 8: 545 9: 3630 10: 545 11: 545 12: 4740
13: 545 14: 545 15: 545 16: 3319 17: 545 18: 545 19: 545 20: 545 21: 545
22: 545 23: 545 24: 545 25: 545 26: 545 27: 545 28: 4733 29: 545 30: 4114
31: 545 32: 545 bogomips: 268800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
vendor: ASUSTeK TUF Gaming driver: amdgpu v: kernel arch: RDNA-3
code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3,
Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:744c class-ID: 0300
Device-2: AMD Raphael vendor: ASRock driver: amdgpu v: kernel arch: RDNA-2
code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: none empty: DP-4, DP-5, DP-6,
HDMI-A-2, Writeback-2 bus-ID: 4e:00.0 chip-ID: 1002:164e class-ID: 0300
temp: 48.0 C
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu,amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 3840x2160 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: radeonsi device: 2 drv: swrast gbm: drv: kms_swrast
surfaceless: drv: radeonsi wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.2-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
navi31 LLVM 18.1.8 DRM 3.57 6.10.10-zen1-1-zen) device-ID: 1002:744c
memory: 23.44 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.295 layers: 7 device: 0 type: discrete-gpu name: AMD
Radeon RX 7900 XTX (RADV NAVI31) driver: mesa radv v: 24.2.2-arch1.1
device-ID: 1002:744c surfaces: xcb,xlib,wayland device: 1
type: integrated-gpu name: AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)
driver: mesa radv v: 24.2.2-arch1.1 device-ID: 1002:164e
surfaces: xcb,xlib,wayland device: 2 type: cpu name: llvmpipe (LLVM
18.1.8 256 bits) driver: mesa llvmpipe v: 24.2.2-arch1.1 (LLVM 18.1.8)
device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab30
class-ID: 0403
Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 4e:00.1
chip-ID: 1002:1640 class-ID: 0403
Device-3: AMD Family 17h/19h HD Audio driver: N/A alternate: snd_hda_intel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 4e:00.6 chip-ID: 1022:15e3
class-ID: 0403
Device-4: Generic USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-8:4
chip-ID: 26ce:0a06 class-ID: 0300
Device-5: Logitech PRO X Wireless Gaming Headset
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 5-1.4.2:79 chip-ID: 046d:0aba class-ID: 0300
API: ALSA v: k6.10.10-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek Killer E3000 2.5GbE vendor: ASRock driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: a000 bus-ID: 49:00.0
chip-ID: 10ec:3000 class-ID: 0200
IF: enp73s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-7:3 chip-ID: 8087:0032
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 10.68 TiB used: 1.92 TiB (18.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: HP model: SSD EX900 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: S0614B0 temp: 46.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Samsung model: SSD 980 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 3B4QFXO7 temp: 42.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: TeamGroup model: T-FORCE T253TY004T
size: 3.73 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 6364 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: TeamGroup model: T2532TB
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 18D8 scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: TeamGroup model: T2534TB
size: 3.73 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 60.0 scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 31.94 GiB (3.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:2
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 31.94 GiB (3.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 31.94 GiB (3.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 31.94 GiB (3.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 61.88 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 32 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 58.9 C mobo: N/A
Fan Speeds (rpm): N/A
GPU: device: amdgpu temp: 63.0 C mem: 64.0 C fan: 369 watts: 69.00
device: amdgpu temp: 47.0 C
Info:
Memory: total: 64 GiB note: est. available: 61.88 GiB
used: 11.91 GiB (19.3%)
Processes: 579 Power: uptime: 22h 33m states: freeze,mem,disk
suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 24.73 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1453 libs: 423 tools: octopi,paru Compilers:
gcc: 14.2.1 Shell: garuda-inxi default: Bash v: 5.2.32 running-in: konsole
inxi: 3.3.35
Garuda (2.6.26-1):
System install date: 2024-09-19
Last full system update: 2024-09-22 âť
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units:
An old garuda-inxi is as valuable as yesterdayâs weather report.
I did as you said and Seems to be working now.
Didnt see the same beheviour.
Not sure if its the cold reset, or the fact i tried changing scheduler on all drives to none just to see.
But.
It works.
Ill check the drives never the less when the enclosure arrives but for now, id say
its good.
Ty vm
Well maybe itâs still to soon to say, but at least thatâs encouraging.
Many people balk when they are suggested to do a factory reset of the bios, just as when suggested to do a factory reset of their network router. Many people seem very hesitant to do that when it is suggested. Which makes little sense, because you can always create a backup of your current configuration before doing a factory reset.
Fortunately, you werenât one of those types of people and you were very proactive when any suggestions were made.
Unfortunately, in the back of my mind I still think this may be a hardware issue and in the long term these workarounds may not last. Hopefully though, they will.
Good luck.
Thank you,
I agree with you though. If it is a hardware issue. its gonna suck, but I saved most of the data and I never keep it al in one place.
Worst case scenario ill order a small bulk of disks.
Have in plan to build a homeserver solution for backups among other things.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.