How to diagnose “slow” drive problem

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I have recently installed a new SATA 1TB Seagate Barracuda drive for storage. Recently, I have problems where "reading" from the drive lags for a full minute or two, a few tens of seconds if I'm lucky. Watching media hangs the program, running ls in its directories just lags, playing games hang too.



How would I go about diagnosing the problem (faulty SATA connection/kernel issue)? Recently, I have ran e2fsck on the drive after a dirty shutdown corrupting some directories. I have seen some users recommending starting from SMART to check drive health. I use Debian Stretch.



uname -a



Linux vera 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux


So I looked through /var/log/messages and found this. Looks like a faulty SATA connection and the kernel is trying to jumpstart the connection. Am I correct?



Apr 3 22:55:19 vera kernel: [40047.961486] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:19 vera kernel: [40047.961524] ata4: hard resetting link
Apr 3 22:55:20 vera kernel: [40048.841537] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:20 vera kernel: [40048.870611] ata4.00: configured for UDMA/33
Apr 3 22:55:20 vera kernel: [40048.870632] ata4: EH complete
Apr 3 22:55:54 vera kernel: [40082.779512] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:54 vera kernel: [40082.779551] ata4: hard resetting link
Apr 3 22:55:55 vera kernel: [40083.655597] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:55 vera kernel: [40083.679941] ata4.00: configured for UDMA/33
Apr 3 22:55:55 vera kernel: [40083.679954] ata4: EH complete
Apr 3 22:56:27 vera kernel: [40115.557306] ata4: lost interrupt (Status 0x50)
Apr 3 22:56:27 vera kernel: [40115.557343] ata4: hard resetting link
Apr 3 22:56:28 vera kernel: [40116.433391] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:56:28 vera kernel: [40116.461843] ata4.00: configured for UDMA/33
Apr 3 22:56:28 vera kernel: [40116.461861] ata4: EH complete


similarly in /var/log/syslog,



Apr 3 22:55:19 vera kernel: [40047.961486] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:19 vera kernel: [40047.961502] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
Apr 3 22:55:19 vera kernel: [40047.961507] ata4: SError: RecovComm PHYRdyChg CommWake 10B8B DevExch 
Apr 3 22:55:19 vera kernel: [40047.961510] ata4.00: failed command: READ DMA EXT
Apr 3 22:55:19 vera kernel: [40047.961515] ata4.00: cmd 25/00:18:70:05:16/00:00:2b:00:00/e0 tag 0 dma 12288 in
Apr 3 22:55:19 vera kernel: [40047.961515] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x14 (ATA bus error)
Apr 3 22:55:19 vera kernel: [40047.961518] ata4.00: status: DRDY 
Apr 3 22:55:19 vera kernel: [40047.961524] ata4: hard resetting link
Apr 3 22:55:20 vera kernel: [40048.841537] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:20 vera kernel: [40048.870611] ata4.00: configured for UDMA/33
Apr 3 22:55:20 vera kernel: [40048.870632] ata4: EH complete
Apr 3 22:55:54 vera kernel: [40082.779512] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:54 vera kernel: [40082.779529] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
Apr 3 22:55:54 vera kernel: [40082.779534] ata4: SError: RecovComm PHYRdyChg CommWake 10B8B DevExch 
Apr 3 22:55:54 vera kernel: [40082.779537] ata4.00: failed command: READ DMA EXT
Apr 3 22:55:54 vera kernel: [40082.779542] ata4.00: cmd 25/00:10:e0:cf:16/00:00:2b:00:00/e0 tag 0 dma 8192 in
Apr 3 22:55:54 vera kernel: [40082.779542] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x14 (ATA bus error)
Apr 3 22:55:54 vera kernel: [40082.779545] ata4.00: status: DRDY 
Apr 3 22:55:54 vera kernel: [40082.779551] ata4: hard resetting link
Apr 3 22:55:55 vera kernel: [40083.655597] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:55 vera kernel: [40083.679941] ata4.00: configured for UDMA/33


cat /proc/interrupts



 CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 
 0: 48 0 0 1166123 0 0 0 0 IO-APIC 2-edge timer
 1: 1 0 0 2 0 0 0 0 IO-APIC 1-edge i8042
 8: 0 0 0 0 0 0 0 0 IO-APIC 8-edge rtc0
 9: 0 0 0 0 0 0 0 0 IO-APIC 9-fasteoi acpi
 12: 0 0 0 4 0 0 0 0 IO-APIC 12-edge i8042
 14: 0 0 0 19994 0 0 0 0 IO-APIC 14-edge ata_piix
 15: 0 0 0 0 0 0 0 0 IO-APIC 15-edge ata_piix
 16: 0 0 0 0 0 4 0 0 IO-APIC 16-fasteoi ehci_hcd:usb1, uhci_hcd:usb7
 18: 0 0 0 0 0 0 0 0 IO-APIC 18-fasteoi uhci_hcd:usb4, uhci_hcd:usb8, i801_smbus
 19: 0 0 160 0 0 24990 0 0 IO-APIC 19-fasteoi uhci_hcd:usb5, uhci_hcd:usb6, ata_piix
 21: 94 81 3922 25446 66573 0 0 0 IO-APIC 21-fasteoi uhci_hcd:usb3
 23: 0 0 0 0 0 0 0 0 IO-APIC 23-fasteoi ehci_hcd:usb2, uhci_hcd:usb9
 24: 0 0 0 0 0 0 0 0 PCI-MSI 49152-edge aerdrv, PCIe PME
 25: 0 0 0 0 0 0 0 0 PCI-MSI 458752-edge PCIe PME, pciehp
 26: 0 0 0 0 0 0 0 0 PCI-MSI 468992-edge PCIe PME, pciehp
 27: 0 0 0 0 70083 0 18 0 PCI-MSI 1572864-edge ens133
 28: 0 0 0 0 544 0 0 0 PCI-MSI 442368-edge snd_hda_intel:card0
 29: 0 0 0 0 0 185 0 0 PCI-MSI 526336-edge snd_hda_intel:card1
 30: 0 0 0 0 0 0 531 129765 PCI-MSI 524288-edge radeon
NMI: 742 758 770 770 762 722 761 616 Non-maskable interrupts
LOC: 478730 477562 476552 397908 493850 486872 491882 734216 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 742 758 770 770 762 722 761 616 Performance monitoring interrupts
IWI: 0 0 0 2 0 0 1 1 IRQ work interrupts
RTR: 1 0 0 0 0 0 0 0 APIC ICR read retries
RES: 240104 166326 137077 158336 121230 117014 116487 241295 Rescheduling interrupts
CAL: 39159 40225 43556 34693 52710 37347 44372 37116 Function call interrupts
TLB: 28743 29063 31826 25607 41560 26281 32662 25775 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 9 9 9 9 9 9 9 9 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event
PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event



debian hard-disk hardware




share|improve this question






















  • Sounds like a bad drive. But if you have smartmontools installed run this as root. smartctl -H /dev/sdX where sdX is your device. That will give you the SMART health if smart has been enabled for that drive.
    – datUser
    Apr 3 at 15:16










  • @datUser Hi, I ran it as you said and it passed.
    – user121392
    Apr 3 at 15:17










  • Try running a fsck on the filesystem, honestly I find smartctl unhelpful for most disk issues.
    – datUser
    Apr 3 at 15:23










  • @datUser I looked through /var/log/messages and found some logs that might be relevant
    – user121392
    Apr 3 at 15:23










  • I would guess that it is a faulty drive, but I defer to folks who may have seen these errors before.
    – datUser
    Apr 3 at 15:25














up vote
1
down vote

favorite












I have recently installed a new SATA 1TB Seagate Barracuda drive for storage. Recently, I have problems where "reading" from the drive lags for a full minute or two, a few tens of seconds if I'm lucky. Watching media hangs the program, running ls in its directories just lags, playing games hang too.



How would I go about diagnosing the problem (faulty SATA connection/kernel issue)? Recently, I have ran e2fsck on the drive after a dirty shutdown corrupting some directories. I have seen some users recommending starting from SMART to check drive health. I use Debian Stretch.



uname -a



Linux vera 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux


So I looked through /var/log/messages and found this. Looks like a faulty SATA connection and the kernel is trying to jumpstart the connection. Am I correct?



Apr 3 22:55:19 vera kernel: [40047.961486] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:19 vera kernel: [40047.961524] ata4: hard resetting link
Apr 3 22:55:20 vera kernel: [40048.841537] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:20 vera kernel: [40048.870611] ata4.00: configured for UDMA/33
Apr 3 22:55:20 vera kernel: [40048.870632] ata4: EH complete
Apr 3 22:55:54 vera kernel: [40082.779512] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:54 vera kernel: [40082.779551] ata4: hard resetting link
Apr 3 22:55:55 vera kernel: [40083.655597] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:55 vera kernel: [40083.679941] ata4.00: configured for UDMA/33
Apr 3 22:55:55 vera kernel: [40083.679954] ata4: EH complete
Apr 3 22:56:27 vera kernel: [40115.557306] ata4: lost interrupt (Status 0x50)
Apr 3 22:56:27 vera kernel: [40115.557343] ata4: hard resetting link
Apr 3 22:56:28 vera kernel: [40116.433391] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:56:28 vera kernel: [40116.461843] ata4.00: configured for UDMA/33
Apr 3 22:56:28 vera kernel: [40116.461861] ata4: EH complete


similarly in /var/log/syslog,



Apr 3 22:55:19 vera kernel: [40047.961486] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:19 vera kernel: [40047.961502] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
Apr 3 22:55:19 vera kernel: [40047.961507] ata4: SError: RecovComm PHYRdyChg CommWake 10B8B DevExch 
Apr 3 22:55:19 vera kernel: [40047.961510] ata4.00: failed command: READ DMA EXT
Apr 3 22:55:19 vera kernel: [40047.961515] ata4.00: cmd 25/00:18:70:05:16/00:00:2b:00:00/e0 tag 0 dma 12288 in
Apr 3 22:55:19 vera kernel: [40047.961515] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x14 (ATA bus error)
Apr 3 22:55:19 vera kernel: [40047.961518] ata4.00: status: DRDY 
Apr 3 22:55:19 vera kernel: [40047.961524] ata4: hard resetting link
Apr 3 22:55:20 vera kernel: [40048.841537] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:20 vera kernel: [40048.870611] ata4.00: configured for UDMA/33
Apr 3 22:55:20 vera kernel: [40048.870632] ata4: EH complete
Apr 3 22:55:54 vera kernel: [40082.779512] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:54 vera kernel: [40082.779529] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
Apr 3 22:55:54 vera kernel: [40082.779534] ata4: SError: RecovComm PHYRdyChg CommWake 10B8B DevExch 
Apr 3 22:55:54 vera kernel: [40082.779537] ata4.00: failed command: READ DMA EXT
Apr 3 22:55:54 vera kernel: [40082.779542] ata4.00: cmd 25/00:10:e0:cf:16/00:00:2b:00:00/e0 tag 0 dma 8192 in
Apr 3 22:55:54 vera kernel: [40082.779542] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x14 (ATA bus error)
Apr 3 22:55:54 vera kernel: [40082.779545] ata4.00: status: DRDY 
Apr 3 22:55:54 vera kernel: [40082.779551] ata4: hard resetting link
Apr 3 22:55:55 vera kernel: [40083.655597] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:55 vera kernel: [40083.679941] ata4.00: configured for UDMA/33


cat /proc/interrupts



 CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 
 0: 48 0 0 1166123 0 0 0 0 IO-APIC 2-edge timer
 1: 1 0 0 2 0 0 0 0 IO-APIC 1-edge i8042
 8: 0 0 0 0 0 0 0 0 IO-APIC 8-edge rtc0
 9: 0 0 0 0 0 0 0 0 IO-APIC 9-fasteoi acpi
 12: 0 0 0 4 0 0 0 0 IO-APIC 12-edge i8042
 14: 0 0 0 19994 0 0 0 0 IO-APIC 14-edge ata_piix
 15: 0 0 0 0 0 0 0 0 IO-APIC 15-edge ata_piix
 16: 0 0 0 0 0 4 0 0 IO-APIC 16-fasteoi ehci_hcd:usb1, uhci_hcd:usb7
 18: 0 0 0 0 0 0 0 0 IO-APIC 18-fasteoi uhci_hcd:usb4, uhci_hcd:usb8, i801_smbus
 19: 0 0 160 0 0 24990 0 0 IO-APIC 19-fasteoi uhci_hcd:usb5, uhci_hcd:usb6, ata_piix
 21: 94 81 3922 25446 66573 0 0 0 IO-APIC 21-fasteoi uhci_hcd:usb3
 23: 0 0 0 0 0 0 0 0 IO-APIC 23-fasteoi ehci_hcd:usb2, uhci_hcd:usb9
 24: 0 0 0 0 0 0 0 0 PCI-MSI 49152-edge aerdrv, PCIe PME
 25: 0 0 0 0 0 0 0 0 PCI-MSI 458752-edge PCIe PME, pciehp
 26: 0 0 0 0 0 0 0 0 PCI-MSI 468992-edge PCIe PME, pciehp
 27: 0 0 0 0 70083 0 18 0 PCI-MSI 1572864-edge ens133
 28: 0 0 0 0 544 0 0 0 PCI-MSI 442368-edge snd_hda_intel:card0
 29: 0 0 0 0 0 185 0 0 PCI-MSI 526336-edge snd_hda_intel:card1
 30: 0 0 0 0 0 0 531 129765 PCI-MSI 524288-edge radeon
NMI: 742 758 770 770 762 722 761 616 Non-maskable interrupts
LOC: 478730 477562 476552 397908 493850 486872 491882 734216 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 742 758 770 770 762 722 761 616 Performance monitoring interrupts
IWI: 0 0 0 2 0 0 1 1 IRQ work interrupts
RTR: 1 0 0 0 0 0 0 0 APIC ICR read retries
RES: 240104 166326 137077 158336 121230 117014 116487 241295 Rescheduling interrupts
CAL: 39159 40225 43556 34693 52710 37347 44372 37116 Function call interrupts
TLB: 28743 29063 31826 25607 41560 26281 32662 25775 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 9 9 9 9 9 9 9 9 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event
PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event



debian hard-disk hardware




share|improve this question






















  • Sounds like a bad drive. But if you have smartmontools installed run this as root. smartctl -H /dev/sdX where sdX is your device. That will give you the SMART health if smart has been enabled for that drive.
    – datUser
    Apr 3 at 15:16










  • @datUser Hi, I ran it as you said and it passed.
    – user121392
    Apr 3 at 15:17










  • Try running a fsck on the filesystem, honestly I find smartctl unhelpful for most disk issues.
    – datUser
    Apr 3 at 15:23










  • @datUser I looked through /var/log/messages and found some logs that might be relevant
    – user121392
    Apr 3 at 15:23










  • I would guess that it is a faulty drive, but I defer to folks who may have seen these errors before.
    – datUser
    Apr 3 at 15:25












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have recently installed a new SATA 1TB Seagate Barracuda drive for storage. Recently, I have problems where "reading" from the drive lags for a full minute or two, a few tens of seconds if I'm lucky. Watching media hangs the program, running ls in its directories just lags, playing games hang too.



How would I go about diagnosing the problem (faulty SATA connection/kernel issue)? Recently, I have ran e2fsck on the drive after a dirty shutdown corrupting some directories. I have seen some users recommending starting from SMART to check drive health. I use Debian Stretch.



uname -a



Linux vera 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux


So I looked through /var/log/messages and found this. Looks like a faulty SATA connection and the kernel is trying to jumpstart the connection. Am I correct?



Apr 3 22:55:19 vera kernel: [40047.961486] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:19 vera kernel: [40047.961524] ata4: hard resetting link
Apr 3 22:55:20 vera kernel: [40048.841537] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:20 vera kernel: [40048.870611] ata4.00: configured for UDMA/33
Apr 3 22:55:20 vera kernel: [40048.870632] ata4: EH complete
Apr 3 22:55:54 vera kernel: [40082.779512] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:54 vera kernel: [40082.779551] ata4: hard resetting link
Apr 3 22:55:55 vera kernel: [40083.655597] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:55 vera kernel: [40083.679941] ata4.00: configured for UDMA/33
Apr 3 22:55:55 vera kernel: [40083.679954] ata4: EH complete
Apr 3 22:56:27 vera kernel: [40115.557306] ata4: lost interrupt (Status 0x50)
Apr 3 22:56:27 vera kernel: [40115.557343] ata4: hard resetting link
Apr 3 22:56:28 vera kernel: [40116.433391] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:56:28 vera kernel: [40116.461843] ata4.00: configured for UDMA/33
Apr 3 22:56:28 vera kernel: [40116.461861] ata4: EH complete


similarly in /var/log/syslog,



Apr 3 22:55:19 vera kernel: [40047.961486] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:19 vera kernel: [40047.961502] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
Apr 3 22:55:19 vera kernel: [40047.961507] ata4: SError: RecovComm PHYRdyChg CommWake 10B8B DevExch 
Apr 3 22:55:19 vera kernel: [40047.961510] ata4.00: failed command: READ DMA EXT
Apr 3 22:55:19 vera kernel: [40047.961515] ata4.00: cmd 25/00:18:70:05:16/00:00:2b:00:00/e0 tag 0 dma 12288 in
Apr 3 22:55:19 vera kernel: [40047.961515] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x14 (ATA bus error)
Apr 3 22:55:19 vera kernel: [40047.961518] ata4.00: status: DRDY 
Apr 3 22:55:19 vera kernel: [40047.961524] ata4: hard resetting link
Apr 3 22:55:20 vera kernel: [40048.841537] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:20 vera kernel: [40048.870611] ata4.00: configured for UDMA/33
Apr 3 22:55:20 vera kernel: [40048.870632] ata4: EH complete
Apr 3 22:55:54 vera kernel: [40082.779512] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:54 vera kernel: [40082.779529] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
Apr 3 22:55:54 vera kernel: [40082.779534] ata4: SError: RecovComm PHYRdyChg CommWake 10B8B DevExch 
Apr 3 22:55:54 vera kernel: [40082.779537] ata4.00: failed command: READ DMA EXT
Apr 3 22:55:54 vera kernel: [40082.779542] ata4.00: cmd 25/00:10:e0:cf:16/00:00:2b:00:00/e0 tag 0 dma 8192 in
Apr 3 22:55:54 vera kernel: [40082.779542] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x14 (ATA bus error)
Apr 3 22:55:54 vera kernel: [40082.779545] ata4.00: status: DRDY 
Apr 3 22:55:54 vera kernel: [40082.779551] ata4: hard resetting link
Apr 3 22:55:55 vera kernel: [40083.655597] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:55 vera kernel: [40083.679941] ata4.00: configured for UDMA/33


cat /proc/interrupts



 CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 
 0: 48 0 0 1166123 0 0 0 0 IO-APIC 2-edge timer
 1: 1 0 0 2 0 0 0 0 IO-APIC 1-edge i8042
 8: 0 0 0 0 0 0 0 0 IO-APIC 8-edge rtc0
 9: 0 0 0 0 0 0 0 0 IO-APIC 9-fasteoi acpi
 12: 0 0 0 4 0 0 0 0 IO-APIC 12-edge i8042
 14: 0 0 0 19994 0 0 0 0 IO-APIC 14-edge ata_piix
 15: 0 0 0 0 0 0 0 0 IO-APIC 15-edge ata_piix
 16: 0 0 0 0 0 4 0 0 IO-APIC 16-fasteoi ehci_hcd:usb1, uhci_hcd:usb7
 18: 0 0 0 0 0 0 0 0 IO-APIC 18-fasteoi uhci_hcd:usb4, uhci_hcd:usb8, i801_smbus
 19: 0 0 160 0 0 24990 0 0 IO-APIC 19-fasteoi uhci_hcd:usb5, uhci_hcd:usb6, ata_piix
 21: 94 81 3922 25446 66573 0 0 0 IO-APIC 21-fasteoi uhci_hcd:usb3
 23: 0 0 0 0 0 0 0 0 IO-APIC 23-fasteoi ehci_hcd:usb2, uhci_hcd:usb9
 24: 0 0 0 0 0 0 0 0 PCI-MSI 49152-edge aerdrv, PCIe PME
 25: 0 0 0 0 0 0 0 0 PCI-MSI 458752-edge PCIe PME, pciehp
 26: 0 0 0 0 0 0 0 0 PCI-MSI 468992-edge PCIe PME, pciehp
 27: 0 0 0 0 70083 0 18 0 PCI-MSI 1572864-edge ens133
 28: 0 0 0 0 544 0 0 0 PCI-MSI 442368-edge snd_hda_intel:card0
 29: 0 0 0 0 0 185 0 0 PCI-MSI 526336-edge snd_hda_intel:card1
 30: 0 0 0 0 0 0 531 129765 PCI-MSI 524288-edge radeon
NMI: 742 758 770 770 762 722 761 616 Non-maskable interrupts
LOC: 478730 477562 476552 397908 493850 486872 491882 734216 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 742 758 770 770 762 722 761 616 Performance monitoring interrupts
IWI: 0 0 0 2 0 0 1 1 IRQ work interrupts
RTR: 1 0 0 0 0 0 0 0 APIC ICR read retries
RES: 240104 166326 137077 158336 121230 117014 116487 241295 Rescheduling interrupts
CAL: 39159 40225 43556 34693 52710 37347 44372 37116 Function call interrupts
TLB: 28743 29063 31826 25607 41560 26281 32662 25775 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 9 9 9 9 9 9 9 9 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event
PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event



debian hard-disk hardware




share|improve this question














I have recently installed a new SATA 1TB Seagate Barracuda drive for storage. Recently, I have problems where "reading" from the drive lags for a full minute or two, a few tens of seconds if I'm lucky. Watching media hangs the program, running ls in its directories just lags, playing games hang too.



How would I go about diagnosing the problem (faulty SATA connection/kernel issue)? Recently, I have ran e2fsck on the drive after a dirty shutdown corrupting some directories. I have seen some users recommending starting from SMART to check drive health. I use Debian Stretch.



uname -a



Linux vera 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux


So I looked through /var/log/messages and found this. Looks like a faulty SATA connection and the kernel is trying to jumpstart the connection. Am I correct?



Apr 3 22:55:19 vera kernel: [40047.961486] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:19 vera kernel: [40047.961524] ata4: hard resetting link
Apr 3 22:55:20 vera kernel: [40048.841537] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:20 vera kernel: [40048.870611] ata4.00: configured for UDMA/33
Apr 3 22:55:20 vera kernel: [40048.870632] ata4: EH complete
Apr 3 22:55:54 vera kernel: [40082.779512] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:54 vera kernel: [40082.779551] ata4: hard resetting link
Apr 3 22:55:55 vera kernel: [40083.655597] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:55 vera kernel: [40083.679941] ata4.00: configured for UDMA/33
Apr 3 22:55:55 vera kernel: [40083.679954] ata4: EH complete
Apr 3 22:56:27 vera kernel: [40115.557306] ata4: lost interrupt (Status 0x50)
Apr 3 22:56:27 vera kernel: [40115.557343] ata4: hard resetting link
Apr 3 22:56:28 vera kernel: [40116.433391] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:56:28 vera kernel: [40116.461843] ata4.00: configured for UDMA/33
Apr 3 22:56:28 vera kernel: [40116.461861] ata4: EH complete


similarly in /var/log/syslog,



Apr 3 22:55:19 vera kernel: [40047.961486] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:19 vera kernel: [40047.961502] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
Apr 3 22:55:19 vera kernel: [40047.961507] ata4: SError: RecovComm PHYRdyChg CommWake 10B8B DevExch 
Apr 3 22:55:19 vera kernel: [40047.961510] ata4.00: failed command: READ DMA EXT
Apr 3 22:55:19 vera kernel: [40047.961515] ata4.00: cmd 25/00:18:70:05:16/00:00:2b:00:00/e0 tag 0 dma 12288 in
Apr 3 22:55:19 vera kernel: [40047.961515] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x14 (ATA bus error)
Apr 3 22:55:19 vera kernel: [40047.961518] ata4.00: status: DRDY 
Apr 3 22:55:19 vera kernel: [40047.961524] ata4: hard resetting link
Apr 3 22:55:20 vera kernel: [40048.841537] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:20 vera kernel: [40048.870611] ata4.00: configured for UDMA/33
Apr 3 22:55:20 vera kernel: [40048.870632] ata4: EH complete
Apr 3 22:55:54 vera kernel: [40082.779512] ata4: lost interrupt (Status 0x50)
Apr 3 22:55:54 vera kernel: [40082.779529] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
Apr 3 22:55:54 vera kernel: [40082.779534] ata4: SError: RecovComm PHYRdyChg CommWake 10B8B DevExch 
Apr 3 22:55:54 vera kernel: [40082.779537] ata4.00: failed command: READ DMA EXT
Apr 3 22:55:54 vera kernel: [40082.779542] ata4.00: cmd 25/00:10:e0:cf:16/00:00:2b:00:00/e0 tag 0 dma 8192 in
Apr 3 22:55:54 vera kernel: [40082.779542] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x14 (ATA bus error)
Apr 3 22:55:54 vera kernel: [40082.779545] ata4.00: status: DRDY 
Apr 3 22:55:54 vera kernel: [40082.779551] ata4: hard resetting link
Apr 3 22:55:55 vera kernel: [40083.655597] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 3 22:55:55 vera kernel: [40083.679941] ata4.00: configured for UDMA/33


cat /proc/interrupts



 CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 
 0: 48 0 0 1166123 0 0 0 0 IO-APIC 2-edge timer
 1: 1 0 0 2 0 0 0 0 IO-APIC 1-edge i8042
 8: 0 0 0 0 0 0 0 0 IO-APIC 8-edge rtc0
 9: 0 0 0 0 0 0 0 0 IO-APIC 9-fasteoi acpi
 12: 0 0 0 4 0 0 0 0 IO-APIC 12-edge i8042
 14: 0 0 0 19994 0 0 0 0 IO-APIC 14-edge ata_piix
 15: 0 0 0 0 0 0 0 0 IO-APIC 15-edge ata_piix
 16: 0 0 0 0 0 4 0 0 IO-APIC 16-fasteoi ehci_hcd:usb1, uhci_hcd:usb7
 18: 0 0 0 0 0 0 0 0 IO-APIC 18-fasteoi uhci_hcd:usb4, uhci_hcd:usb8, i801_smbus
 19: 0 0 160 0 0 24990 0 0 IO-APIC 19-fasteoi uhci_hcd:usb5, uhci_hcd:usb6, ata_piix
 21: 94 81 3922 25446 66573 0 0 0 IO-APIC 21-fasteoi uhci_hcd:usb3
 23: 0 0 0 0 0 0 0 0 IO-APIC 23-fasteoi ehci_hcd:usb2, uhci_hcd:usb9
 24: 0 0 0 0 0 0 0 0 PCI-MSI 49152-edge aerdrv, PCIe PME
 25: 0 0 0 0 0 0 0 0 PCI-MSI 458752-edge PCIe PME, pciehp
 26: 0 0 0 0 0 0 0 0 PCI-MSI 468992-edge PCIe PME, pciehp
 27: 0 0 0 0 70083 0 18 0 PCI-MSI 1572864-edge ens133
 28: 0 0 0 0 544 0 0 0 PCI-MSI 442368-edge snd_hda_intel:card0
 29: 0 0 0 0 0 185 0 0 PCI-MSI 526336-edge snd_hda_intel:card1
 30: 0 0 0 0 0 0 531 129765 PCI-MSI 524288-edge radeon
NMI: 742 758 770 770 762 722 761 616 Non-maskable interrupts
LOC: 478730 477562 476552 397908 493850 486872 491882 734216 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 742 758 770 770 762 722 761 616 Performance monitoring interrupts
IWI: 0 0 0 2 0 0 1 1 IRQ work interrupts
RTR: 1 0 0 0 0 0 0 0 APIC ICR read retries
RES: 240104 166326 137077 158336 121230 117014 116487 241295 Rescheduling interrupts
CAL: 39159 40225 43556 34693 52710 37347 44372 37116 Function call interrupts
TLB: 28743 29063 31826 25607 41560 26281 32662 25775 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 9 9 9 9 9 9 9 9 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event
PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event




debian hard-disk hardware





share|improve this question













share|improve this question




share|improve this question








edited Apr 3 at 16:19

























asked Apr 3 at 15:10









user121392

85




85











  • Sounds like a bad drive. But if you have smartmontools installed run this as root. smartctl -H /dev/sdX where sdX is your device. That will give you the SMART health if smart has been enabled for that drive.
    – datUser
    Apr 3 at 15:16










  • @datUser Hi, I ran it as you said and it passed.
    – user121392
    Apr 3 at 15:17










  • Try running a fsck on the filesystem, honestly I find smartctl unhelpful for most disk issues.
    – datUser
    Apr 3 at 15:23










  • @datUser I looked through /var/log/messages and found some logs that might be relevant
    – user121392
    Apr 3 at 15:23










  • I would guess that it is a faulty drive, but I defer to folks who may have seen these errors before.
    – datUser
    Apr 3 at 15:25
















  • Sounds like a bad drive. But if you have smartmontools installed run this as root. smartctl -H /dev/sdX where sdX is your device. That will give you the SMART health if smart has been enabled for that drive.
    – datUser
    Apr 3 at 15:16










  • @datUser Hi, I ran it as you said and it passed.
    – user121392
    Apr 3 at 15:17










  • Try running a fsck on the filesystem, honestly I find smartctl unhelpful for most disk issues.
    – datUser
    Apr 3 at 15:23










  • @datUser I looked through /var/log/messages and found some logs that might be relevant
    – user121392
    Apr 3 at 15:23










  • I would guess that it is a faulty drive, but I defer to folks who may have seen these errors before.
    – datUser
    Apr 3 at 15:25















Sounds like a bad drive. But if you have smartmontools installed run this as root. smartctl -H /dev/sdX where sdX is your device. That will give you the SMART health if smart has been enabled for that drive.
– datUser
Apr 3 at 15:16




Sounds like a bad drive. But if you have smartmontools installed run this as root. smartctl -H /dev/sdX where sdX is your device. That will give you the SMART health if smart has been enabled for that drive.
– datUser
Apr 3 at 15:16












@datUser Hi, I ran it as you said and it passed.
– user121392
Apr 3 at 15:17




@datUser Hi, I ran it as you said and it passed.
– user121392
Apr 3 at 15:17












Try running a fsck on the filesystem, honestly I find smartctl unhelpful for most disk issues.
– datUser
Apr 3 at 15:23




Try running a fsck on the filesystem, honestly I find smartctl unhelpful for most disk issues.
– datUser
Apr 3 at 15:23












@datUser I looked through /var/log/messages and found some logs that might be relevant
– user121392
Apr 3 at 15:23




@datUser I looked through /var/log/messages and found some logs that might be relevant
– user121392
Apr 3 at 15:23












I would guess that it is a faulty drive, but I defer to folks who may have seen these errors before.
– datUser
Apr 3 at 15:25




I would guess that it is a faulty drive, but I defer to folks who may have seen these errors before.
– datUser
Apr 3 at 15:25















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f435303%2fhow-to-diagnose-slow-drive-problem%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f435303%2fhow-to-diagnose-slow-drive-problem%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

Peggy Mitchell

Image
EastEnders character This article is about the soap opera character. For the British tennis player, see Peggy Michell. For the author, see Margaret Mitchell. Peggy Mitchell Barbara Windsor as Peggy Mitchell (2008) EastEnders character Portrayed by Jo Warne (1991) Barbara Windsor (1994–2016) Duration 1991, 1994–2010, 2013–2016 First appearance Episode 650 30 April 1991  ( 1991-04-30 ) Last appearance Episode 5286 17 May 2016  ( 2016-05-17 ) (appearance) Episode 5287 19 May 2016 (voiceover) Introduced by Michael Ferguson (1991) Barbara Emile (1994) Louise Berridge (2004) Kate Harwood (2005) Lorraine Newman (2013) Dominic Treadwell-Collins (2014) Spin-off appearances The Mitchells - Naked Truths (1998) Classification Former; regular Profile Other names Peggy Butcher Occupation Barmaid Businesswoman Pub landlady Jo Warne as Peggy Mitchell (1991) Family Family Mitchell Father Jack Martin Mother Lily Martin Sisters Aunt ...
Read more

Palaiologos

Image
Palaiologos Παλαιολόγος Palaeologus, Palaeologue Imperial Family Double-headed eagle with the family cypher Country Byzantine Empire, Duchy of Montferrat (remaining lineage after Empire annexed by Ottomans) Founded 11th century  ( 11th century ) Founder Nikephoros Palaiologos (first known) Final ruler Constantine XI Palaiologos (Byzantine Empire) Margaret Paleologa (Montferrat) Titles Byzantine Emperor Marquess of Montferrat Style(s) "Augustus" "Basileus" "Autokrator" Traditions Greek Orthodoxy (predominantly) Roman Catholicism (remaining lineage in Montferrat) Dissolution 1533  ( 1533 ) Cadet branches Claimants: House of Kastrioti (defunct) House of Rurik (defunct) Palaiologan dynasty Chronology Michael VIII 1259–1282 with Andronikos II as co-emperor, 1261–1282 Andronikos II 1282–1328 with Michael IX (1294–1320) and Andronikos III (1321–1328) as co-emperors Andronikos III 1328–1341 John...
Read more

The Forum (Inglewood, California)

Image
The Forum "LA Forum" Prairie Ave. façade of The Forum in 2014 Full name The Forum, presented by Chase Former names The Forum (1967–1988) Great Western Forum (1988–2003) Address 3900 W. Manchester Blvd Location Inglewood, California Coordinates Coordinates: 33°57′29″N 118°20′31″W  /  33.95806°N 118.34194°W  / 33.95806; -118.34194 Public transit     Downtown Inglewood station Owner The Madison Square Garden Company Operator MSG Entertainment Seating type Reserved Capacity 17,500 Half-bowl: 8,000 Construction Broke ground July 1, 1966  ( 1966-07-01 ) Opened December 30, 1967  ( 1967-12-30 ) Renovated 1988, 2012–2014 Construction cost $16 million Renovation: 2014: $76.5 million Architect Charles Luckman Associates (original) Brisbin Brook Beynon (renovation) Structural engineer Johnson & Nielsen Associates (original) Severud Associates (renovation) Genera...
Read more