You are not logged in.

Pages: 1

#1 2025-08-26 04:40:52

hevin
Member
Registered: 2021-08-14
Posts: 63

error with file IO

hi
recently i install archlinux on my new desktop
In the process of copying large files, my computer freezes. After hanging in dmesg, errors appear

[Mon Aug 25 05:45:57 2025] ata6.00: exception Emask 0x0 SAct 0x7fe0001f SErr 0x50000 action 0x6 frozen
[Mon Aug 25 05:45:57 2025] ata6: SError: { PHYRdyChg CommWake }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:00:28:a1:de/00:00:4f: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)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:08:48:a3:de/00:00:4f:00:00/40 tag 1 ncq dma 4096 out
                                    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:10:a0:40:47/00:00:50:00:00/40 tag 2 ncq dma 4096 out
                                    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:18:c8:40:47/00:00:50:00:00/40 tag 3 ncq dma 4096 out
                                    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:20:88:7e:6f/00:00:00:00:00/40 tag 4 ncq dma 4096 out
                                    res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: READ FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 60/00:a8:a8:49:2b/01:00:52:00:00/40 tag 21 ncq dma 131072 in
                                    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: READ FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 60/00:b0:a8:4a:2b/01:00:52:00:00/40 tag 22 ncq dma 131072 in
                                    res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:b8:70:4e:c5/00:00:03:00:00/40 tag 23 ncq dma 4096 out
                                    res 40/00:ff:82:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/48:c0:60:cb:ef/00:00:4e:00:00/40 tag 24 ncq dma 36864 out
                                    res 40/00:ff:82:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:c8:10:99:de/00:00:4f:00:00/40 tag 25 ncq dma 4096 out
                                    res 40/00:ff:ff:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:d0:a0:9a:de/00:00:4f:00:00/40 tag 26 ncq dma 4096 out
                                    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:d8:c0:9b:de/00:00:4f:00:00/40 tag 27 ncq dma 4096 out
                                    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:e0:d0:9b:de/00:00:4f:00:00/40 tag 28 ncq dma 4096 out
                                    res 40/00:ff:82:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:e8:38:9d:de/00:00:4f:00:00/40 tag 29 ncq dma 4096 out
                                    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6.00: failed command: WRITE FPDMA QUEUED
[Mon Aug 25 05:45:57 2025] ata6.00: cmd 61/08:f0:c8:9d:de/00:00:4f:00:00/40 tag 30 ncq dma 4096 out
                                    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[Mon Aug 25 05:45:57 2025] ata6.00: status: { DRDY }
[Mon Aug 25 05:45:57 2025] ata6: hard resetting link
[Mon Aug 25 05:45:57 2025] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Mon Aug 25 05:45:57 2025] ata6.00: configured for UDMA/133
[Mon Aug 25 05:45:57 2025] sd 5:0:0:0: [sdb] tag#21 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=39s
[Mon Aug 25 05:45:57 2025] sd 5:0:0:0: [sdb] tag#21 CDB: Read(16) 88 00 00 00 00 00 52 2b 49 a8 00 00 01 00 00 00
[Mon Aug 25 05:45:57 2025] I/O error, dev sdb, sector 1378568616 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 2
[Mon Aug 25 05:45:57 2025] sd 5:0:0:0: [sdb] tag#22 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=39s
[Mon Aug 25 05:45:57 2025] sd 5:0:0:0: [sdb] tag#22 CDB: Read(16) 88 00 00 00 00 00 52 2b 4a a8 00 00 01 00 00 00
[Mon Aug 25 05:45:57 2025] I/O error, dev sdb, sector 1378568872 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 2
[Mon Aug 25 05:45:57 2025] ata6: EH complete
[Mon Aug 25 05:49:56 2025] usb 1-3.3: USB disconnect, device number 7
[Mon Aug 25 05:49:56 2025] Buffer I/O error on dev sdc1, logical block 0, lost sync page write

sda is my system ssd drive
sdb hdd
sdc flash
What does it mean?
I think the hardware is working, because in windows no freezes appear when large file IO processing, and smart status good.

Offline

#2 2025-08-26 07:00:49

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,365

Re: error with file IO

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

smart status good

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
https://wiki.archlinux.org/title/SMART / smart -a

Though

[Mon Aug 25 05:45:57 2025] ata6.00: exception Emask 0x0 SAct 0x7fe0001f SErr 0x50000 action 0x6 frozen
[Mon Aug 25 05:45:57 2025] ata6: SError: { PHYRdyChg CommWake }

looks more like a bus error, the drive doesn't power up.
If it's not a cable and this /is/ the "sdb hdd" probably ASPM
Please post your complete system journal for a boot covering this, eg. 

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

for the previous (-1) one

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2025-08-26 08:13:11

mmy8x
Member
Registered: 2025-03-02
Posts: 91

Re: error with file IO

Looks like a dodgy SATA cable to the disk, either data or power.

Get SMART diagnostics and look at "199 CRC_Error_Count" (data) and "12 Power_Cycle_Count", "192 Unsafe_Shutdown_Count" (power). Except for Power_Cycle_Count, raw values should be low or zero and if any of them increases after each burst of I/O errors, you have your answer.

Could also try other SATA ports if it's data.

Last edited by mmy8x (2025-08-26 18:59:34)

Offline

#4 2025-08-27 18:26:18

hevin
Member
Registered: 2021-08-14
Posts: 63

Re: error with file IO

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

The output of this command is very large and contains confidential information. Perhaps you don't need the whole thing, but something specific?

Offline

#5 2025-08-27 18:29:42

hevin
Member
Registered: 2021-08-14
Posts: 63

Re: error with file IO

mmy8x wrote:

Looks like a dodgy SATA cable to the disk, either data or power.

Get SMART diagnostics and look at "199 CRC_Error_Count" (data) and "12 Power_Cycle_Count", "192 Unsafe_Shutdown_Count" (power). Except for Power_Cycle_Count, raw values should be low or zero and if any of them increases after each burst of I/O errors, you have your answer.

Could also try other SATA ports if it's data.

sda

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0000   005   000   000    Old_age   Offline      -       5
  3 Spin_Up_Time            0x0000   100   100   000    Old_age   Offline      -       0
  4 Start_Stop_Count        0x0000   100   100   000    Old_age   Offline      -       0
  5 Reallocated_Sector_Ct   0x0000   100   100   000    Old_age   Offline      -       0
  9 Power_On_Hours          0x0000   100   100   000    Old_age   Offline      -       57567
 12 Power_Cycle_Count       0x0000   100   100   000    Old_age   Offline      -       4645
232 Lifetime_Writes         0x0000   100   100   000    Old_age   Offline      -       49246470316
233 Media_Wearout_Indicator 0x0000   088   000   000    Old_age   Offline      -       88

sdb

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   068   064   006    Pre-fail  Always       -       5829546
  3 Spin_Up_Time            0x0003   097   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2562
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   082   060   045    Pre-fail  Always       -       4440284207
  9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       14550
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       775
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   082   000    Old_age   Always       -       4 5 31
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   066   052   040    Old_age   Always       -       34 (Min/Max 34/35)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       345
193 Load_Cycle_Count        0x0032   093   093   000    Old_age   Always       -       15077
194 Temperature_Celsius     0x0022   034   048   000    Old_age   Always       -       34
195 Hardware_ECC_Recovered  0x001a   068   064   000    Old_age   Always       -       5829546
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       5
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       8032h+43m+52.448s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       50213512521
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       781522673189

sdc is my USB flash drive. There is no SATA cable. It connects to the USB port. And there are errors with it.

on sdb 199 UDMA_CRC_Error_Count The value 5 appeared a long time ago and has not changed. I tried different cables and connecting via a USB box, but it did not change.

Last edited by hevin (2025-08-27 18:32:32)

Offline

#6 2025-08-27 18:59:34

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,365

Re: error with file IO

x-ref, https://bbs.archlinux.org/viewtopic.php … 9#p2258819

Feel free to pseudonymize stuff you think is "confidential" (which nothing of that nature is supposed to be in the journal, nor actually sensitive data), ie. turn "aaa" into "xxx" and "bbbb" into "yyyy" - do not just steamroll "xxx" over everything.
Then post the journal - if this (likely) is a bus error this can have a plethora of causes, in doubt a broken/loose cable.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2025-08-27 19:31:47

mmy8x
Member
Registered: 2025-03-02
Posts: 91

Re: error with file IO

hevin wrote:

sdc is my USB flash drive. There is no SATA cable. It connects to the USB port. And there are errors with it.

That's I/O errors after USB disconnection. Avoid it by unmounting the filesystem before pulling the flash drive out.

If it disconnects itself spontaneously for no reason then it's another story. It could be some USB problem. Or else, any chance that the 5V rail from your PSU is bad? That could affect both USB and SATA devices, while still possibly allowing the motherboard, CPU and PCIe cards to function.

hevin wrote:

on sdb 199 UDMA_CRC_Error_Count The value 5 appeared a long time ago and has not changed. I tried different cables and connecting via a USB box, but it did not change.

Check if 192 Power-Off_Retract_Count isn't increasing, particularly during time when the computer is turned on and those errors show up.

I once had a broken SATA power cable which caused a disk to randomly reset every few minutes. Replaced it, problem gone.

Last edited by mmy8x (2025-08-27 19:33:58)

Offline

#8 2025-09-18 14:57:22

hevin
Member
Registered: 2021-08-14
Posts: 63

Re: error with file IO

I disconnected the monitor's USB hub from the system and the error disappeared.

Offline

#9 2025-09-18 14:58:54

hevin
Member
Registered: 2021-08-14
Posts: 63

Re: error with file IO

It's been 8 days now. Under various loads and with different settings, no errors have appeared.

Offline

#10 2025-09-18 15:07:33

hevin
Member
Registered: 2021-08-14
Posts: 63

Re: error with file IO

The USB hub built into the monitor is very convenient. You don't have to constantly crawl under the table to plug in a flash drive. Why do you think this problem occurs and how can it be fixed?

Offline

#11 2025-09-18 19:01:49

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,365

Re: error with file IO

For clarification, the errors occur when connecting the flash drive through the usb hub of the monitor?
Not when the monitors usb hub is just randomly also connected but the drive is plugged in directly to the system?

this can have a plethora of causes, in doubt a broken/loose cable

but most likely it's power related (the affected disk is a spinner, right?)
If this happens when the monitor is randomly *also* connected but not part of the drives chain, try to move the monitor and the drive to different hubs

lsusb -tv

Edit: some clarification.

Last edited by seth (2025-09-18 19:02:55)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2025-09-19 03:41:59

hevin
Member
Registered: 2021-08-14
Posts: 63

Re: error with file IO

No! It doesn't matter what is connected to the monitor's USB hub. Even if nothing is connected at all. Still, when connecting an empty USB hub monitor to a PC, such errors occur.

Offline

#13 2025-09-19 05:11:33

mmy8x
Member
Registered: 2025-03-02
Posts: 91

Re: error with file IO

So if you now connect the monitor's hub again you will start seeing errors on internal SATA disks and external USB disks after a week without any error?

That's getting rather odd. Two things come to mind:
1. Possibly some electronic interference coming from the monitor.
2. Possibly some internal malfunction of the chipset or CPU "uncore", if the SATA port and the USB port which the monitor is connected to both come from the chip.

Offline

#14 2025-09-19 08:09:29

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,549
Website

Re: error with file IO

@hevin If you wonder where your post went, you reported the above post of @mmy8x instead of replying to it.

Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#15 2025-09-19 08:09:49

hevin
Member
Registered: 2021-08-14
Posts: 63

Re: error with file IO

It seems like you know something. big_smile mmy8x
Yes, indeed. At first, I removed the overclocking from DDR, set JEDEC 4800, and everything was automatic. That didn't help. Then I updated the BIOS to the latest version. That didn't help. I updated IntelME, and that didn't help either. I turned ASPM on and off in the BIOS—no effect. I replaced the SATA cables and reconnected the power supply. That didn't help either. I turned off Turbo Boost, set the voltage offset to -100 and LLC mode to 1. That didn't help either. at the end  I disconnected the empty hub from the monitor, and suddenly the error disappeared. I've been using the computer for quite a long time, but the error has not reappeared yet. So, I didn't actually check whether the problem would return when I reconnected the hub. Well, I just turned it on. I'm waiting.

Last edited by hevin (2025-09-19 08:18:46)

Offline

#16 2025-09-19 08:12:16

hevin
Member
Registered: 2021-08-14
Posts: 63

Re: error with file IO

schard wrote:

@hevin If you wonder where your post went, you reported the above post of @mmy8x instead of replying to it.

I wanted to quote him. I didn't want to complain about him.

Offline

#17 2025-09-19 08:24:02

hevin
Member
Registered: 2021-08-14
Posts: 63

Re: error with file IO

lsusb -tv
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 002: Dev 014, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:2817 VIA Labs, Inc.
    |__ Port 003: Dev 011, If 0, Class=Mass Storage, Driver=usb-storage, 480M
        ID 13fe:4100 Phison Electronics Corp. Flash drive
    |__ Port 005: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 2ea8:2125
    |__ Port 005: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        ID 2ea8:2125
    |__ Port 006: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 09da:18c3 A4Tech Co., Ltd.
    |__ Port 006: Dev 004, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        ID 09da:18c3 A4Tech Co., Ltd.
    |__ Port 006: Dev 004, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        ID 09da:18c3 A4Tech Co., Ltd.
    |__ Port 009: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 05e3:0608 Genesys Logic, Inc. Hub
    |__ Port 011: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 1462:7d90 Micro Star International
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 20000M/x2
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 002: Dev 005, If 0, Class=Hub, Driver=hub/4p, 5000M
        ID 2109:0817 VIA Labs, Inc.
        |__ Port 003: Dev 006, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Kyson
    |__ Port 004: Dev 004, If 0, Class=Mass Storage, Driver=uas, 5000M
        ID 152d:1576 JMicron Technology Corp. / JMicron USA Technology Corp. External Disk 3.0

Offline

Pages: 1

Board footer

Powered by FluxBB