Score:1

Internal Seagate HDD extremely slow under Linux

sd flag

This computer has a 1 TB Seagate HDD as a second drive at /dev/sdb, formatted as ext4.

Recently the HDD started performing really, really slow. For example, it took almost 20h to copy ~89 GB of data from an external USB drive to the HDD:

sent 89,704,992,410 bytes  received 47,132 bytes  1,281,363.28 bytes/sec
total size is 425,224,910,218  speedup is 4.74

real    1166m47,065s
user    4m3,929s
sys     10m54,856s

It doesn't seem the problem is the USB drive, as normal operations sometimes are very slow too, like deleting files or even using tab completion in a terminal.

Running smartctl -t long /dev/sdb, I got this output:

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.10-arch1-1] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Mobile HDD
Device Model:     ST1000LM035-1RK172
Serial Number:    (removed)
LU WWN Device Id: (removed)
Firmware Version: LVM2
User Capacity:    1.000.204.886.016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Dec 28 19:23:54 2021 -03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                    without error or no self-test has ever 
                    been run.
Total time to complete Offline 
data collection:        (    0) seconds.
Offline data collection
capabilities:            (0x71) SMART execute Offline immediate.
                    No Auto Offline data collection support.
                    Suspend Offline collection upon new
                    command.
                    No Offline surface scan supported.
                    Self-test supported.
                    Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                    General Purpose Logging supported.
Short self-test routine 
recommended polling time:    (   1) minutes.
Extended self-test routine
recommended polling time:    ( 165) minutes.
Conveyance self-test routine
recommended polling time:    (   2) minutes.
SCT capabilities:          (0x3035) SCT Status supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   083   064   034    Pre-fail  Always       -       196192348
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       994
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   082   060   045    Pre-fail  Always       -       155079043
  9 Power_On_Hours          0x0032   080   080   000    Old_age   Always       -       17728 (70 194 0)
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       706
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   098   000    Old_age   Always       -       8590065670
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   063   050   040    Old_age   Always       -       37 (Min/Max 28/45)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       9
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       19
193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       697945
194 Temperature_Celsius     0x0022   037   050   000    Old_age   Always       -       37 (0 22 0 0 0)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
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       -       0
240 Head_Flying_Hours       0x000f   096   096   030    Pre-fail  Always       -       4235 (41 1 0)
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 2
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2 occurred at disk power-on lifetime: 17662 hours (735 days + 22 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      06:23:01.410  NOP [Abort queued commands]
  b0 d4 00 82 4f c2 00 00      06:22:01.104  SMART EXECUTE OFF-LINE IMMEDIATE
  61 00 50 ff ff ff 4f 00      06:21:58.086  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00      06:21:58.086  WRITE FPDMA QUEUED
  b0 d0 01 00 4f c2 00 00      06:21:57.812  SMART READ DATA

Error 1 occurred at disk power-on lifetime: 17662 hours (735 days + 22 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      06:17:33.736  NOP [Abort queued commands]
  b0 d4 00 83 4f c2 00 00      06:16:33.565  SMART EXECUTE OFF-LINE IMMEDIATE
  ea 00 00 00 00 00 a0 00      06:16:33.546  FLUSH CACHE EXT
  61 00 20 ff ff ff 4f 00      06:16:30.631  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00      06:16:30.631  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     17728         -
# 2  Extended offline    Interrupted (host reset)      00%     17702         -
# 3  Extended captive    Interrupted (host reset)      90%     17662         -
# 4  Conveyance captive  Interrupted (host reset)      50%     17662         -
# 5  Short captive       Completed without error       00%     17662         -
# 6  Short offline       Completed without error       00%     12481         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

From what I've researched:

  • those 2 errors (Interrupted (host reset)) are not critical and mean the test was interrupted by a system reboot at some point;
  • the disk is supposedly fine if VALUE and WORST are above THRESH;
  • the huge read/seek error rates aren't really meaningful. I got a value of zero doing that math;

From these results, is the disk ok? If it is, how can I find out why it is so slow?

user10489 avatar
nc flag
The long test had not finished yet when you took this data.
sd flag
@user10489 hmmm, but I did wait until the end. And I've just reissued the `smartctl -a` and the output is the same. Should I run the test commad again?
user10489 avatar
nc flag
A long test could take many hours. Run smartctl -a again and check for test completion. In your output above it says `# 1 Extended offline Self-test routine in progress 90% 17676 -` which should be different by now.
sd flag
I had started a new test before sleeping and it quickly went to 90%. Woke up today and it's still at 90%.
sd flag
@user10489, finally the tests are over! I've updated the question with the new log. It seems to be the same as before. The `Raw_Read_Error_Rate` even improved a little bit (81 -> 83).
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.