How does KDE actually find and discover ata drives?

skyfishgoo · May 6, 2024, 6:19pm

for a while now KDE has been unable to reliably find certain sata ports, but luckily only the slower ones ( i have 6, 2x6gbp ones and 4x3gbs ones)

so my main OS disk and my windows disk are plugged into the two faster ports and everything else goes to the slower ones (back up drives, HDD, cdrom)

is there some package i can reinstall that might help (maybe got corrupted or something)

shooting in the dark here

i tried creating a new user with admin privilages just to see if it’s happening there too, and it is… but in windows everything “appears” to be fine, no issues.

i’ve read about certain kernel parameters, but then it always turns out that it didn’t work for those who tried it, so i’m at a loss what to do about this short of replacing my computer.

meven · May 7, 2024, 8:12am

Check those disks are simply not hidden.
On dolphin placement panel, right click > “Show all entries”.
Those disks might be there.

You can check what disks dolphin (and other KDE apps or plasma) can see using solid-hardware6 list | grep UDisks (you might need to install a package to get the solid-hardware6 utility).

This is very unlikely to have anything to do with the kind of SATA ports those disks are using.

skyfishgoo · May 7, 2024, 11:22am

they are not hidden because the slower port disks (3gbps) will show in dolphin as unmounted (red icons) when/if they are detected (attached)… the faster (6gbs) ports are stable, thankfully because that were the boot drives are attached.

the problem is the system keeps acting as tho they are being removed and attached over and over again.

if i set my system tray Disks & Devices to show all, it will randomly notify me that my other (slower) disks have been attached.

so i end up with configuration panels that look discombobulated like this

or this

all of these should entries be in the attached section as they are all hardwired to SATA ports on the m/b and should be available at boot.

i tried reseating both ends of each cable, but the issue persists.

here’s just a snippit from the end of a long screen of repeating error messages when i execute

sudo journalctl -b -0 -p3

May 07 04:17:01 FXPC kernel: ata4.00: revalidation failed (errno=-5)
May 07 04:17:11 FXPC kernel: ata4.00: revalidation failed (errno=-5)
May 07 04:17:16 FXPC kernel: ata4: COMRESET failed (errno=-32)
May 07 04:17:27 FXPC kernel: ata4: EH pending after 5 tries, giving up
May 07 04:17:27 FXPC kernel: sd 3:0:0:0: rejecting I/O to offline device
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 2508719840 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 2930276152 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 3014279200 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 2080 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 117712960 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 2508719840 op 0x0:(READ) flags 0x0 phys_seg 5 prio class 2
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj5, logical block 1806036920, async page read
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj5, logical block 1806036921, async page read
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj5, logical block 1806036922, async page read
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj5, logical block 1806036923, async page read
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj5, logical block 1806036924, async page read
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 2508719845 op 0x0:(READ) flags 0x0 phys_seg 3 prio class 2
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 3014279200 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj5, logical block 1806036925, async page read
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj4, logical block 4, async page read
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj5, logical block 1806036926, async page read
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 117712960 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj5, logical block 1806036927, async page read
May 07 04:17:27 FXPC kernel: Buffer I/O error on dev sdj2, logical block 8, async page read
May 07 04:17:27 FXPC kernel: I/O error, dev sdj, sector 2930276152 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May 07 04:17:28 FXPC kernel: ata4.00: exception Emask 0x50 SAct 0x4000 SErr 0x280900 action 0x6 frozen
May 07 04:17:28 FXPC kernel: ata4.00: irq_stat 0x08000000, interface fatal error
May 07 04:17:28 FXPC kernel: ata4: SError: { UnrecovData HostInt 10B8B BadCRC }
May 07 04:17:28 FXPC kernel: ata4.00: failed command: READ FPDMA QUEUED
May 07 04:17:28 FXPC kernel: ata4.00: cmd 60/08:70:a0:88:e0/00:00:e8:00:00/40 tag 14 ncq dma 4096 in
                                      res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
May 07 04:17:28 FXPC kernel: ata4.00: status: { DRDY }
May 07 04:17:29 FXPC kernel: ata4.00: revalidation failed (errno=-5)
May 07 04:17:35 FXPC kernel: ata4.00: failed to set xfermode (err_mask=0x100)
May 07 04:17:46 FXPC kernel: ata4.00: failed to enable AA (error_mask=0x100)
May 07 04:17:46 FXPC kernel: ata4.00: revalidation failed (errno=-5)
May 07 04:17:46 FXPC kernel: sd 3:0:0:0: rejecting I/O to offline device
May 07 04:17:54 FXPC kernel: I/O error, dev sdj, sector 3907029152 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
May 07 04:17:54 FXPC kernel: device offline error, dev sdj, sector 3907029152 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May 07 04:17:54 FXPC kernel: Buffer I/O error on dev sdj, logical block 488378644, async page read
May 07 04:17:56 FXPC kernel: ata4: COMRESET failed (errno=-32)
lines 6835-6939/6939 (END)

ata4 is the HDD and sdj one many SD drives that are part of a SD reader array mounted on the front of the case.

perhaps i should disconnect that array of readers and see what happens.

meven · May 7, 2024, 12:34pm

That’s not something dolphin, or plasma has anything to do about it seems.

It looks like either there is a bug in the concerned driver (motherboard) or your hardware is faulty. But your guess is as good as mine.
The issue seems quite severe looking at the journal output.

You could try to report this to your distro, or linux bug tracker.

skyfishgoo · May 7, 2024, 1:23pm

i’m thinking the hardware is just tired… but it still works in windows7 (for now), and does work for a hot second under linux intermittently.

how would i detect what driver is being used (and maybe reinstall) for the SATA controller(s)?

looked at hwinfo but it’s hard to know what i’m looking for.

from sudo lshw -short i get this line

/0/100/1f.2              scsi0      storage        6 Series/C200 Series Chipset Family 6 port Desktop SATA AHCI Controller

but how do i id the driver or module that is providing this? is that strait from the kernel?

schwarzerkater · May 7, 2024, 2:00pm

See e.g. lspci -v or sudo lspci -vv .

But I would suggest to start from a live USB of your distribution and check from there - if there are similar errors then it is very likely a hardware problem.
You can double-check with another live USB containing a different kernel.

skyfishgoo · May 7, 2024, 3:01pm

00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
        Subsystem: Acer Incorporated [ALI] 6 Series/C200 Series Chipset Family MEI Controller
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 29
        Region 0: Memory at fe729000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [50] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
                Address: 00000000fee02004  Data: 0021
        Kernel driver in use: mei_me
        Kernel modules: mei_me

mei_me

is the kernel driver (also the noise i make every time i reboot and it starts happening again

i’ll try the live USB, should be way back on 5.something, or whatever came with 22.04

skyfishgoo · May 7, 2024, 3:25pm

ok, i’m in using the live USB

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.19.0-32-generic (64-bit)

i’m getting the same connect/disconnect behavior in dolphin and the system tray

sudo journalctl -b -0 -p3 report looks much the same

May 07 15:16:05 kubuntu kernel: ata4.00: status: { DRDY }
May 07 15:16:06 kubuntu kernel: ata4.00: revalidation failed (errno=-5)
May 07 15:16:11 kubuntu kernel: ata4.00: revalidation failed (errno=-5)
May 07 15:16:17 kubuntu kernel: ata4.00: revalidation failed (errno=-5)
May 07 15:16:22 kubuntu kernel: I/O error, dev sdd, sector 2719639221 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919029, async page read
May 07 15:16:22 kubuntu kernel: I/O error, dev sdd, sector 2719639222 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919030, async page read
May 07 15:16:22 kubuntu kernel: I/O error, dev sdd, sector 2719639223 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919031, async page read
May 07 15:16:22 kubuntu kernel: I/O error, dev sdd, sector 2719639216 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919024, async page read
May 07 15:16:22 kubuntu kernel: I/O error, dev sdd, sector 2719639217 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919025, async page read
May 07 15:16:22 kubuntu kernel: I/O error, dev sdd, sector 2719639218 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919026, async page read
May 07 15:16:22 kubuntu kernel: I/O error, dev sdd, sector 2719639219 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919027, async page read
May 07 15:16:22 kubuntu kernel: I/O error, dev sdd, sector 2719639220 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919028, async page read
May 07 15:16:22 kubuntu kernel: device offline error, dev sdd, sector 2719639216 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919024, async page read
May 07 15:16:22 kubuntu kernel: Buffer I/O error on dev sdd6, logical block 210919025, async page read
May 07 15:16:22 kubuntu kernel: device offline error, dev sdd, sector 2719639216 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 07 15:16:22 kubuntu kernel: JBD2: Error -5 detected when updating journal superblock for sdd4-8.
May 07 15:16:22 kubuntu kernel: Aborting journal on device sdd4-8.
May 07 15:16:22 kubuntu kernel: JBD2: Error -5 detected when updating journal superblock for sdd4-8.
May 07 15:16:22 kubuntu kernel: EXT4-fs error (device sdd4): ext4_put_super:1223: comm umount: Couldn't clean up the journal
May 07 15:16:22 kubuntu kernel: EXT4-fs (sdd4): I/O error while writing superblock
May 07 15:16:22 kubuntu kernel: EXT4-fs (sdd4): Remounting filesystem read-only
May 07 15:16:22 kubuntu kernel: JBD2: Error -5 detected when updating journal superblock for sdd2-8.
May 07 15:16:22 kubuntu kernel: Aborting journal on device sdd2-8.
May 07 15:16:22 kubuntu kernel: JBD2: Error -5 detected when updating journal superblock for sdd2-8.
May 07 15:16:22 kubuntu kernel: EXT4-fs error (device sdd2): ext4_put_super:1223: comm umount: Couldn't clean up the journal
May 07 15:16:22 kubuntu kernel: EXT4-fs (sdd2): Remounting filesystem read-only
May 07 15:16:57 kubuntu kernel: ata4.00: exception Emask 0x40 SAct 0x1000000 SErr 0x880800 action 0x6 frozen
May 07 15:16:57 kubuntu kernel: ata4: SError: { HostInt 10B8B LinkSeq }
May 07 15:16:57 kubuntu kernel: ata4.00: failed command: READ FPDMA QUEUED
May 07 15:16:57 kubuntu kernel: ata4.00: cmd 60/08:c0:00:40:aa/00:00:b3:00:00/40 tag 24 ncq dma 4096 in
                                         res 40/00:c8:24:66:1a/00:00:a2:00:00/40 Emask 0x44 (timeout)
May 07 15:16:57 kubuntu kernel: ata4.00: status: { DRDY }
May 07 15:16:58 kubuntu kernel: I/O error, dev sdd, sector 3014279168 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
lines 1506-1552/1552 (END)

so that’s pretty conclusively a hw issue it seems…

time for a new PC.

i should probably stop touching this one until i get the new one up and running because i don’t want to totally break it.

i just find it odd that only the slower half of the sata controller is failing and only in linux (tbf, i’ve not tried installing win10 on this tired beast, that might break it too).

meven · May 7, 2024, 4:00pm

Try to test your disks on another machine. It could be the disk.

time for a new PC.

Also maybe you can avoid using the ata4 port and be fine without creating some new e-waste too early.

skyfishgoo · May 7, 2024, 4:10pm

i’ll definitely do that kind of trouble shooting once i get the new machine up and running, but i think it’s time.

this old beast is intel gen 2 tech and i think i got a good run out of her (circa 2011)

maybe she can be my next project to learn about networks and home servers.

cmdrkotori · May 8, 2024, 12:35am

This is just some general advice: if you can isolate the hardware fault, you should be able to relegate the old rig to a home theater pc hooked up to your TV. You don’t need a powerful rig to play videos after all. No need to chuck out an otherwise working system.

schwarzerkater · May 8, 2024, 11:49pm

Are you sure it is the controller?
Did you try another drive at this port?

skyfishgoo · May 9, 2024, 1:08am

pretty sure, yes, i have several drives and when i tried reseating the m/b end of the sATA cables i moved the drives around to different ports (among the 4 slower ports)

i didn’t mess with the two faster ports as they were working and have been consistently working, where as the others have been going on and off like xmas lights.

if i had to put money on it, i would bet the controller “chip” is probably two separate ICs (for the different speeds) and one of them has a bad solder connection/trace.

I might try to reflow the m/b at some point, but as long as the two fast ports are working i’m not gonna touch it until the new rig is operational.

Slater91 · May 13, 2024, 2:44pm

I would check the SMART data as well to exclude that the drives aren’t dying.

skyfishgoo · May 13, 2024, 4:37pm

the drives (when i can see them) seem to be fine and are relatively new.

moved one of the intermittent drives to a new machine and it’s working fine… slotted right into fresh windows install as drive F: WinSetup just as it should.

and now my old PC is no longer throwing ata errors (so far) and all the remaining drives are working as expected.

wondering if if was just a power supply issue at this point