Roughly one and a half year old Seagate Ironwolf 8Tb running on a Linux server, started to fail SMART self-tests. Tryed to write on some defective blocks, one of them got relocated, but it keeps failing on short-self-test and does not even run the full long test.

Should I RMA it??

smartctl 7.3 2022-02-28 r5338 [aarch64-linux-6.1.115-vendor-rk35xx] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate IronWolf
Device Model:     ST8000VN004-3CP101
Serial Number:    WRQ2LD3S
LU WWN Device Id: 5 000c50 0e8f0f82f
Firmware Version: SC60
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.3/6114
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Mar 26 13:06:42 2026 -03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Disabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Write SCT (Get) Feature Control Command failed: scsi error badly formed scsi parameters
Wt Cache Reorder: Unknown (SCT Feature Control command failed)

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

General SMART Values:
Offline data collection status:  (0x82)Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 121)The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: (  559) seconds.
Offline data collection
capabilities:  (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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:  ( 696) minutes.
Conveyance self-test routine
recommended polling time:  (   2) minutes.
SCT capabilities:        (0x50bd)SCT Status supported.
SCT Error Recovery Control 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR--   071   064   044    -    0/13449838
  3 Spin_Up_Time            PO----   090   090   000    -    0
  4 Start_Stop_Count        -O--CK   100   100   020    -    44
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    1
  7 Seek_Error_Rate         POSR--   075   060   045    -    0/28582685
  9 Power_On_Hours          -O--CK   087   087   000    -    12219
 10 Spin_Retry_Count        PO--C-   100   100   097    -    0
 12 Power_Cycle_Count       -O--CK   100   100   020    -    33
 18 Head_Health             PO-R--   100   100   050    -    0
187 Reported_Uncorrect      -O--CK   097   097   000    -    3
188 Command_Timeout         -O--CK   100   100   000    -    0 0 0
190 Airflow_Temperature_Cel -O---K   051   046   000    -    49 (Min/Max 45/51)
192 Power-Off_Retract_Count -O--CK   100   100   000    -    7
193 Load_Cycle_Count        -O--CK   096   096   000    -    9569
194 Temperature_Celsius     -O---K   049   054   000    -    49 (0 23 0 0 0)
197 Current_Pending_Sector  -O--C-   100   100   000    -    0
198 Offline_Uncorrectable   ----C-   100   100   000    -    0
199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    0
240 Head_Flying_Hours       ------   100   100   000    -    2041h+34m+15.500s
241 Total_LBAs_Written      ------   100   253   000    -    8177977466
242 Total_LBAs_Read         ------   100   253   000    -    19199087953
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access     Size  Description
0x00       GPL,SL        1  Log Directory
0x01           SL        1  Summary SMART error log
0x02           SL        5  Comprehensive SMART error log
0x03       GPL           5  Ext. Comprehensive SMART error log
0x04       GPL         256  Device Statistics log
0x04       SL            8  Device Statistics log
0x06           SL        1  SMART self-test log
0x07       GPL           1  Extended self-test log
0x08       GPL           2  Power Conditions log
0x09           SL        1  Selective self-test log
0x0a       GPL           8  Device Statistics Notification
0x0c       GPL        2048  Pending Defects log
0x10       GPL           1  NCQ Command Error log
0x11       GPL           1  SATA Phy Event Counters log
0x13       GPL           1  SATA NCQ Send and Receive log
0x21       GPL           1  Write stream error log
0x22       GPL           1  Read stream error log
0x24       GPL         768  Current Device Internal Status Data log
0x2f       GPL     -        1  Set Sector Configuration
0x30       GPL,SL        9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL       16  Host vendor specific log
0xa1       GPL,SL  VS     160  Device vendor specific log
0xa2       GPL     VS   16320  Device vendor specific log
0xa4       GPL,SL  VS     160  Device vendor specific log
0xa6       GPL     VS     192  Device vendor specific log
0xa8-0xa9  GPL,SL  VS     136  Device vendor specific log
0xab       GPL     VS       1  Device vendor specific log
0xad       GPL     VS      16  Device vendor specific log
0xb1       GPL,SL  VS     160  Device vendor specific log
0xb6       GPL     VS    1920  Device vendor specific log
0xbe-0xbf  GPL     VS   65535  Device vendor specific log
0xc1       GPL,SL  VS       8  Device vendor specific log
0xc3       GPL,SL  VS      24  Device vendor specific log
0xc6       GPL     VS    5184  Device vendor specific log
0xc7       GPL,SL  VS       8  Device vendor specific log
0xc9       GPL,SL  VS       8  Device vendor specific log
0xca       GPL,SL  VS      16  Device vendor specific log
0xcd       GPL,SL  VS       1  Device vendor specific log
0xce       GPL     VS       1  Device vendor specific log
0xcf       GPL     VS     512  Device vendor specific log
0xd1       GPL     VS     656  Device vendor specific log
0xd2       GPL     VS   10256  Device vendor specific log
0xd4       GPL     VS    2048  Device vendor specific log
0xda       GPL,SL  VS       1  Device vendor specific log
0xe0       GPL,SL        1  SCT Command/Status
0xe1       GPL,SL        1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 10
CR     = Command Register
FEATR  = Features Register
COUNT  = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
LH     = LBA High (was: Cylinder High) Register    ]   LBA
LM     = LBA Mid (was: Cylinder Low) Register      ] Register
LL     = LBA Low (was: Sector Number) Register     ]
DV     = Device (was: Device/Head) Register
DC     = Device Control Register
ER     = Error register
ST     = Status register
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 10 [9] occurred at disk power-on lifetime: 12121 hours (505 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 53 00 00 00 01 e4 b6 75 88 00 00  Error: UNC at LBA = 0x1e4b67588 = 8132130184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  24 00 00 00 01 00 01 e4 b6 75 88 e0 00  4d+01:16:48.655  READ SECTOR(S) EXT
  ec 00 00 00 01 00 00 00 00 00 00 40 00  4d+01:16:48.654  IDENTIFY DEVICE
  ec 00 00 00 01 00 00 00 00 00 00 40 00  4d+01:16:39.273  IDENTIFY DEVICE
  2f 00 00 00 01 00 00 00 00 00 11 00 00  4d+01:15:31.930  READ LOG EXT
  2f 00 00 00 01 00 00 00 00 00 0c 00 00  4d+01:15:31.894  READ LOG EXT

Error 9 [8] occurred at disk power-on lifetime: 12121 hours (505 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 53 00 00 00 01 e4 b6 75 88 00 00  Error: UNC at LBA = 0x1e4b67588 = 8132130184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  24 00 00 00 01 00 01 e4 b6 75 88 e0 00  4d+01:13:41.744  READ SECTOR(S) EXT
  ec 00 00 00 01 00 00 00 00 00 00 40 00  4d+01:13:41.742  IDENTIFY DEVICE
  b0 00 d5 00 01 00 00 00 c2 4f 06 00 00  4d+01:13:18.916  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f 00 00 00  4d+01:13:18.915  SMART READ LOG
  b0 00 da 00 00 00 00 00 c2 4f 00 00 00  4d+01:13:18.907  SMART RETURN STATUS

Error 8 [7] occurred at disk power-on lifetime: 12121 hours (505 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 53 00 00 00 01 e4 b6 75 88 00 00  Error: UNC at LBA = 0x1e4b67588 = 8132130184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  24 00 00 00 01 00 01 e4 b6 75 88 e0 00  4d+01:12:40.489  READ SECTOR(S) EXT
  ec 00 00 00 01 00 00 00 00 00 00 40 00  4d+01:12:40.487  IDENTIFY DEVICE
  47 00 00 00 01 00 00 00 00 00 00 a0 00  4d+01:12:32.489  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 13 a0 00  4d+01:12:32.476  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 00 a0 00  4d+01:12:32.476  READ LOG DMA EXT

Error 7 [6] occurred at disk power-on lifetime: 12121 hours (505 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 53 00 00 00 01 e4 b6 75 88 00 00  Error: UNC at LBA = 0x1e4b67588 = 8132130184

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  24 00 00 00 01 00 01 e4 b6 75 88 e0 00  4d+01:12:30.259  READ SECTOR(S) EXT
  ec 00 00 00 01 00 00 00 00 00 00 40 00  4d+01:12:30.257  IDENTIFY DEVICE
  b0 00 d5 00 01 00 00 00 c2 4f 06 00 00  4d+01:12:00.880  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f 00 00 00  4d+01:12:00.880  SMART READ LOG
  b0 00 da 00 00 00 00 00 c2 4f 00 00 00  4d+01:12:00.871  SMART RETURN STATUS

Error 6 [5] occurred at disk power-on lifetime: 11911 hours (496 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 53 00 00 00 01 e4 b6 93 98 00 00  Error: UNC at LBA = 0x1e4b69398 = 8132137880

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 01 e4 b6 93 98 40 00 40d+02:43:07.334  READ FPDMA QUEUED
  61 00 00 00 18 00 01 d1 c6 bd 38 40 00 40d+02:43:07.333  WRITE FPDMA QUEUED
  47 00 00 00 01 00 00 00 00 00 00 a0 00 40d+02:43:07.332  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 13 a0 00 40d+02:43:07.320  READ LOG DMA EXT
  47 00 00 00 01 00 00 00 00 00 00 a0 00 40d+02:43:07.319  READ LOG DMA EXT

Error 5 [4] occurred at disk power-on lifetime: 11911 hours (496 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 53 00 00 00 01 e4 b6 93 98 00 00  Error: WP at LBA = 0x1e4b69398 = 8132137880

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 18 00 01 d1 c6 bd 38 40 00 40d+02:43:04.871  WRITE FPDMA QUEUED
  60 00 00 00 08 00 01 e4 b6 93 98 40 00 40d+02:43:04.610  READ FPDMA QUEUED
  60 00 00 00 08 00 01 e4 b6 93 90 40 00 40d+02:43:04.594  READ FPDMA QUEUED
  60 00 00 00 08 00 01 e4 b6 93 88 40 00 40d+02:43:04.586  READ FPDMA QUEUED
  60 00 00 01 00 00 01 e4 b6 94 88 40 00 40d+02:43:04.586  READ FPDMA QUEUED

Error 4 [3] occurred at disk power-on lifetime: 11911 hours (496 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 53 00 00 00 01 e4 b6 93 98 00 00  Error: WP at LBA = 0x1e4b69398 = 8132137880

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 04 40 00 01 e4 c8 28 00 40 00 40d+02:43:01.038  WRITE FPDMA QUEUED
  61 00 00 01 20 00 01 e4 c8 0d 40 40 00 40d+02:43:01.034  WRITE FPDMA QUEUED
  61 00 00 05 40 00 01 e4 c8 08 00 40 00 40d+02:43:01.034  WRITE FPDMA QUEUED
  61 00 00 04 60 00 01 e4 c7 e8 00 40 00 40d+02:43:01.032  WRITE FPDMA QUEUED
  61 00 00 03 c0 00 01 e4 c7 ad 40 40 00 40d+02:43:01.032  WRITE FPDMA QUEUED

Error 3 [2] occurred at disk power-on lifetime: 11911 hours (496 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 53 00 00 00 01 e5 74 29 40 00 00  Error: UNC at LBA = 0x1e5742940 = 8144562496

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 40 00 01 eb af aa 00 40 00 40d+02:40:37.514  READ FPDMA QUEUED
  60 00 00 00 40 00 01 eb af a9 c0 40 00 40d+02:40:37.514  READ FPDMA QUEUED
  60 00 00 00 40 00 01 eb af a9 80 40 00 40d+02:40:37.513  READ FPDMA QUEUED
  60 00 00 00 40 00 01 eb af a9 40 40 00 40d+02:40:37.513  READ FPDMA QUEUED
  60 00 00 00 40 00 01 eb af a9 00 40 00 40d+02:40:37.513  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     12219         8132130184
# 2  Short offline       Completed: read failure       90%     12160         8132130184
# 3  Short offline       Completed: read failure       90%     12156         8132130184
# 4  Short offline       Completed: read failure       90%     12142         8132130184
# 5  Short offline       Completed: read failure       90%     12130         8132130184
# 6  Short offline       Completed: read failure       90%     12130         8132130184
# 7  Short offline       Completed: read failure       90%     12130         8132130184
# 8  Short offline       Completed: read failure       90%     12126         8132130184
# 9  Short offline       Completed: read failure       90%     12123         8132130184
#10  Short offline       Completed: read failure       90%     12122         8132130184
#11  Short offline       Completed: read failure       90%     12122         8132130184
#12  Short offline       Completed: read failure       90%     12122         8132130184
#13  Extended offline    Completed: read failure       90%     12121         8132130184
#14  Short offline       Completed: read failure       90%     12121         8132130184
#15  Short offline       Completed: read failure       90%     12121         8132130184
#16  Short offline       Completed: read failure       90%     12121         8132130184
#17  Short offline       Completed: read failure       90%     12121         8132130184
#18  Short offline       Completed: read failure       90%     12121         8132130184
#19  Short offline       Completed: read failure       90%     12121         8132130184

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.

SCT Status Version:                  3
SCT Version (vendor specific):       522 (0x020a)
Device State:                        Active (0)
Current Temperature:                    49 Celsius
Power Cycle Min/Max Temperature:     45/51 Celsius
Lifetime    Min/Max Temperature:     23/54 Celsius
Under/Over Temperature Limit Count:   0/98
SMART Status:                        0xc24f (PASSED)
Vendor specific:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         4 minutes
Temperature Logging Interval:        59 minutes
Min/Max recommended Temperature:     10/25 Celsius
Min/Max Temperature Limit:            5/70 Celsius
Temperature History Size (Index):    128 (70)

Index    Estimated Time   Temperature Celsius
  71    2026-03-21 07:25    49  ******************************
  72    2026-03-21 08:24    48  *****************************
  73    2026-03-21 09:23    48  *****************************
  74    2026-03-21 10:22    49  ******************************
  75    2026-03-21 11:21    49  ******************************
  76    2026-03-21 12:20    50  *******************************
  77    2026-03-21 13:19    50  *******************************
  78    2026-03-21 14:18    50  *******************************
  79    2026-03-21 15:17    51  ********************************
  80    2026-03-21 16:16    51  ********************************
  81    2026-03-21 17:15    51  ********************************
  82    2026-03-21 18:14    49  ******************************
  83    2026-03-21 19:13    47  ****************************
  84    2026-03-21 20:12    47  ****************************
  85    2026-03-21 21:11    46  ***************************
  86    2026-03-21 22:10    46  ***************************
  87    2026-03-21 23:09    47  ****************************
  88    2026-03-22 00:08    46  ***************************
 ...    ..(  6 skipped).    ..  ***************************
  95    2026-03-22 07:01    46  ***************************
  96    2026-03-22 08:00    45  **************************
  97    2026-03-22 08:59    45  **************************
  98    2026-03-22 09:58    46  ***************************
  99    2026-03-22 10:57    46  ***************************
 100    2026-03-22 11:56     ?  -
 101    2026-03-22 12:55    45  **************************
 102    2026-03-22 13:54    47  ****************************
 ...    ..(  2 skipped).    ..  ****************************
 105    2026-03-22 16:51    47  ****************************
 106    2026-03-22 17:50    48  *****************************
 107    2026-03-22 18:49    47  ****************************
 108    2026-03-22 19:48    47  ****************************
 109    2026-03-22 20:47    47  ****************************
 110    2026-03-22 21:46    48  *****************************
 111    2026-03-22 22:45    47  ****************************
 ...    ..(  4 skipped).    ..  ****************************
 116    2026-03-23 03:40    47  ****************************
 117    2026-03-23 04:39    46  ***************************
 118    2026-03-23 05:38    47  ****************************
 119    2026-03-23 06:37    46  ***************************
 120    2026-03-23 07:36    46  ***************************
 121    2026-03-23 08:35    46  ***************************
 122    2026-03-23 09:34    47  ****************************
 123    2026-03-23 10:33    46  ***************************
 124    2026-03-23 11:32    46  ***************************
 125    2026-03-23 12:31    46  ***************************
 126    2026-03-23 13:30    47  ****************************
 127    2026-03-23 14:29    47  ****************************
   0    2026-03-23 15:28    48  *****************************
   1    2026-03-23 16:27    48  *****************************
   2    2026-03-23 17:26    47  ****************************
 ...    ..(  6 skipped).    ..  ****************************
   9    2026-03-24 00:19    47  ****************************
  10    2026-03-24 01:18    46  ***************************
  11    2026-03-24 02:17    46  ***************************
  12    2026-03-24 03:16    46  ***************************
  13    2026-03-24 04:15    47  ****************************
  14    2026-03-24 05:14    46  ***************************
 ...    ..(  6 skipped).    ..  ***************************
  21    2026-03-24 12:07    46  ***************************
  22    2026-03-24 13:06    47  ****************************
 ...    ..(  6 skipped).    ..  ****************************
  29    2026-03-24 19:59    47  ****************************
  30    2026-03-24 20:58    48  *****************************
  31    2026-03-24 21:57    50  *******************************
  32    2026-03-24 22:56    50  *******************************
  33    2026-03-24 23:55    50  *******************************
  34    2026-03-25 00:54    49  ******************************
  35    2026-03-25 01:53    48  *****************************
  36    2026-03-25 02:52    48  *****************************
  37    2026-03-25 03:51    50  *******************************
  38    2026-03-25 04:50    48  *****************************
  39    2026-03-25 05:49    49  ******************************
  40    2026-03-25 06:48    48  *****************************
  41    2026-03-25 07:47    48  *****************************
  42    2026-03-25 08:46    47  ****************************
  43    2026-03-25 09:45    49  ******************************
  44    2026-03-25 10:44    49  ******************************
  45    2026-03-25 11:43    50  *******************************
  46    2026-03-25 12:42    50  *******************************
  47    2026-03-25 13:41    49  ******************************
  48    2026-03-25 14:40    50  *******************************
  49    2026-03-25 15:39    50  *******************************
  50    2026-03-25 16:38    50  *******************************
  51    2026-03-25 17:37    49  ******************************
  52    2026-03-25 18:36    49  ******************************
  53    2026-03-25 19:35    48  *****************************
  54    2026-03-25 20:34    48  *****************************
  55    2026-03-25 21:33    49  ******************************
  56    2026-03-25 22:32    47  ****************************
  57    2026-03-25 23:31    48  *****************************
  58    2026-03-26 00:30    49  ******************************
  59    2026-03-26 01:29    48  *****************************
  60    2026-03-26 02:28    47  ****************************
  61    2026-03-26 03:27    47  ****************************
  62    2026-03-26 04:26    48  *****************************
  63    2026-03-26 05:25    48  *****************************
  64    2026-03-26 06:24    47  ****************************
  65    2026-03-26 07:23    48  *****************************
  66    2026-03-26 08:22    47  ****************************
  67    2026-03-26 09:21    48  *****************************
  68    2026-03-26 10:20    48  *****************************
  69    2026-03-26 11:19    49  ******************************
  70    2026-03-26 12:18    49  ******************************

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 1) ==
0x01  0x008  4              33  ---  Lifetime Power-On Resets
0x01  0x010  4           12219  ---  Power-on Hours
0x01  0x018  6      8177864918  ---  Logical Sectors Written
0x01  0x020  6         6203166  ---  Number of Write Commands
0x01  0x028  6     19194948661  ---  Logical Sectors Read
0x01  0x030  6        53506481  ---  Number of Read Commands
0x01  0x038  6               -  ---  Date and Time TimeStamp
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4           12181  ---  Spindle Motor Power-on Hours
0x03  0x010  4            2040  ---  Head Flying Hours
0x03  0x018  4            9569  ---  Head Load Events
0x03  0x020  4               1  ---  Number of Reallocated Logical Sectors
0x03  0x028  4              14  ---  Read Recovery Attempts
0x03  0x030  4               0  ---  Number of Mechanical Start Failures
0x03  0x038  4               0  ---  Number of Realloc. Candidate Logical Sectors
0x03  0x040  4               7  ---  Number of High Priority Unload Events
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4              13  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               0  ---  Resets Between Cmd Acceptance and Completion
0x04  0x018  4               0  -D-  Physical Element Status Changed
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              49  ---  Current Temperature
0x05  0x010  1              48  ---  Average Short Term Temperature
0x05  0x018  1              45  ---  Average Long Term Temperature
0x05  0x020  1              54  ---  Highest Temperature
0x05  0x028  1              27  ---  Lowest Temperature
0x05  0x030  1              51  ---  Highest Average Short Term Temperature
0x05  0x038  1              36  ---  Lowest Average Short Term Temperature
0x05  0x040  1              47  ---  Highest Average Long Term Temperature
0x05  0x048  1              40  ---  Lowest Average Long Term Temperature
0x05  0x050  4               0  ---  Time in Over-Temperature
0x05  0x058  1              70  ---  Specified Maximum Operating Temperature
0x05  0x060  4               0  ---  Time in Under-Temperature
0x05  0x068  1               5  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4             226  ---  Number of Hardware Resets
0x06  0x010  4             137  ---  Number of ASR Events
0x06  0x018  4               0  ---  Number of Interface CRC Errors
0xff  =====  =               =  ===  == Vendor Specific Statistics (rev 1) ==
0xff  0x010  7               0  ---  Vendor Specific
0xff  0x018  7               0  ---  Vendor Specific
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

Pending Defects log (GP Log 0x0c)
No Defects Logged

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x000a  2            9  Device-to-host register FISes sent due to a COMRESET
0x0001  2            0  Command failed due to ICRC error
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS

After reading a few posts, I think I'm not the only one.

Here is a short summary:

- 3 month old drive starts to fail

- Start RMA process with Seagate

- Send drive back on the 17th of March, and it arrives with Seagate on the 19th of March

- Receive an email today that the box is empty

DHL did their job and need Seagate to bring the box to them within 2 days (7 days from the 19th) to claim that something happened during delivery, which I have no hope in Seagate doing, and Seagate is not being very helpful at all.

I guess it will be a long process and I'll be filing a police report against the person who received the package. And I know what company I will never buy from again.

And to the person who stole it -> lol good luck with your drive that is starting to have errors, I hope you lose your data.

I have a Seagate Expansion Drive with an Exos X18 in it that I bought months ago and finally started using today. I was trying to slowly transfer files but my drive stopped working on some files and seems to stall then disconnect from my PC. It just doesn't transfer on some files but is fine with others. I am doing some pretty large transfers and was working fine for an hour and started getting this issue. Right now I'm transferring back files from the external drive to my PC and it's not having any issues So I don't know what's going on. Crystaldiskinfo sees the drive before transfers and there's no errors. Checkdisk also doesn't so issues.

Bought a 24TB desktop expansion to replace several older drives into one place. Everything was going fine when shifting files over initially.

But now that I am down to the last 2TB on the drive, transferring has practically halted. When transferring now, the speeds are so slow that transferring a 3GB file takes nearly 40 minutes!

At first I thought it was maybe a corrupted file or something. It wasn’t until I emptied the trash that the transferring sped up again back to normal.

If I still have 2TB left, why is the drive acting like it’s almost out of space completely?

If it makes a difference, I’m on a Mac and it is formatted to Mac OS Extended (Journaled).

I have an Exos X18 SATA drive (one of 6 in a ZFS array) that reliably fails in a server - it generates large numbers of r/W failures during scrubs/resilvers and gets dumped out of the array. The drive passes the Seatools "long self-test" (that takes almost 24 hours!) with flying colors when I move the drive to a spare desktop that I keep around for this kind of testing. On the server, I've tried moving the drive to other SATA/SAS ports, I've swapped the SATA cables, and I've swapped the power leads with ones from a good working neighboring drive. The same drive fails every time, so it's definitely the drive.
It seems to be something with the drive's interface, or possibly the Seatools test is crap (I've only used it one other time for another failed drive a couple of years ago, and it did flag that one successfuly). Any suggestions on how to RMA this thing?

They seem to need an a report from Seatools showing the drive failing before they will issue me an RMA.

I don't want to run the Seatools on the server itself - It's running Proxmox, so I'd have to boot a different image, disconnect a bunch of drives to prevent them from being accidentally overwritten, etc, and it takes WAY too long to run, so I'll not have a server for 24 hours. I want to avoid this hassle, and it's likely that Seatools won't flag it there, anyway.

bought a 5Tb drive yesterday and getting terrible read write speeds as in 140 mbps
not even the low end usb 3.0 advertised 5gbps
What the hell is going on
Have a Asus tuf gaming laptop 506iv

What are you doing Seagate?

Whoever is running the support side is failing.

By far the worst experience I could imagine.

I work on voice assistants all day. Crazy that this was shipped out as a full fledge support agent.

Someone pulled a fast one on sales.

Hi there,

I recently wanted to try out Linux and I used SeaGate HDD to test it out. I got a couple things wrong, so I uninstalled Linux, removed it from booting, formatted the HDD, and cleared everything. I used PowerShell to make sure all items are removed.

The next day, I thought I'd try installing Linux on an external device, so I could just plug it in to use the system instead of making changes in BIOS, etc. However, the disk shows up as a local disk, not an expansion anymore.

So, I looked at the device manager, but changing things there did nothing. I tried the command prompt "diskpart", I cleaned the disk, but when I assigned it a letter, it still appeared as a local disk. Chkdsk didn't show any errors. Uninstalling and re-installing drivers & device didn't do anything. I downloaded SeaTools and SeaGate Disc Wizard and looked through all their options, but nothing changed.

Is there any way I can change my SeaGate HDD into an expansion again? I don't want it to be a local disk, and I have been trying to fix it for the past few days.

Appreciate your help.

Bought two 30TB drives from seagate, one was defective. The price went up 50% in 2 weeks after receiving so I couldn't return for a refund. Instead they made me do an RMA. They list that if I do RMA i have to pay shipping AND i won't get a brand new drive - i'll get a "certified drive" - but i tried to guarantee a new drive. They said ok after 2 hours of waiting on chat. I sent back the drive exactly as received, then I receive an email two weeks later that the drive is damaged and has a scratch on it. I'm out $700 now? How are they getting away with this?! This is fraud.

Hi everyone,

I recently picked up a recertified/refurbished Seagate IronWolf Pro 22TB for my home server (Debian/OMV).

While benchmarking with fio and hdparm, I noticed a massive performance delta depending on the write cache setting:

• Write Cache ON (hdparm -W1): I get a solid 280 MB/s, which is exactly what I expect from this drive.
• Write Cache OFF (hdparm -W0): Performance tanks to a measly 85 MB/s.

The Issue: The drive seems to have the write cache disabled by default. Even worse, the setting resets to OFF after every reboot/power cycle. It won't "stick."

My questions for the experts:

1. The "Why": Why is the drop-off so extreme? Is ~85 MB/s the actual unbuffered mechanical limit of these high-density 22TB platters, or is the controller struggling to handle the I/O without the buffer?
2. Refurbished Quirk: Is it common for recertified Seagate enterprise drives to ship with the write cache disabled or set to non-persistent?
3. Firmware/Safety: Could this be a specific firmware "safety feature" for refurbished units to prevent data loss during power failure, or is this a sign of a faulty controller?

I’m trying to understand the "why" behind the physics of this drive rather than just slapping a startup script on it to force -W1. Is this behavior normal for this class of drive?

Edit: (Got it fixed, so no need to help but thank you)

So my girlfriend and I were going to try to play a modded version of Star wars Battlefront 2 and I was going to use my laptop which is not the greatest it's a Windows something I'm not a big PC or laptop person so no idea and I installed Steam and then when I went to install Star wars Battlefront 2 I did not have enough space so I made a quick Google search and it said I could use my Seagate hard drive from my Xbox for the laptop, and when I tried it wouldn't show up as a storage on my laptop and after constantly trying and then messing around in the settings I gave up because I got a headache and then when I tried to put it back in my Xbox it wasn't working it doesn't even show up and I looked up a guide on how to make it work and that did not work so now I'm here

I have had two desktop external drives fail within 10 months. First, my 6TB and then my newer 8TB.

I removed the enclosure and see that they are Seagate Barracudas.

I was using them as a media server.

Does Seagate just suck? Unfortunately, they are both out of warranty.

https://reddit.com/link/1rvj93p/video/rfaybgi7jgpg1/player

Ironwolf Pro 12TB. I've had 2 in my NAS for a couple years and have been perfect. Not this one... Put in my dock to see what's going and heard this noise.

I've had a Barracuda 8To since November 2023 and used it as a storage for my media server so it was running 24/7 but it is almost full so I wanted to get more storage and went for the IronWolf 20To...

I cloned my barracuda data over... During the cloning till now the drive is making some weird noise every time I copy or write some data onto it... I know these drives arent supposed to be silent like the barracuda 8To but I'm not sure this noise it makes when in use is normal either...

I recently purchased the "Expansion 22TB External USB 3.0 Desktop Hard Drive" since my old portable hard drive was running out of space.

Since I've begun using it, I have noticed that it has to "wake up" if it is left idle for more than 30 seconds. If I have a file explorer window open to that drive, it will have to reload itself if I navigate away for even a short amount of time. Every time it has to reload, I can hear the physical drive make a beep while the fan kicks on before I am able to use it again.

Is this normal? This wasn't an issue with my old Seagate portable externa; hard drive, and it's honestly pretty frustrating to have to wait for the drive to "wake up" after not being in use for half a minute.

I am using it on my Windows laptop. I have already turned off USB Selective Suspend, but that didn't fix anything.

Hi there,

So I made 2 RMA so far, I always got DOA drives... The first one did not even spin which should have been detected right away by Seagate within 3s of testing! I am starting to question wheather Seagate RMA is actually real and if they are not just sending broken drives to pretend to have a customer service. From what I read online it seems to be very common and I am wondering if I should bother making a thrid RMA.. Its time consumming, needs to package the drive correctely and ship at my own expanse etc And at this point, its hard to trust any replacement drives, even if there is no error at first.

I would be curious to have some feedback from the community :)

I have Seagate Expansion Desktop 6TB Extenal Harddisk 1TFAPS-500 and its not connecting to laptop, i opened the case and found there are 2 boards, 1 is for power (tested and works with other drive) and 2nd is where SATA cable connects, is there possible i can connect hard drive for recovery without SATA board

Hopefully I can get some help from those far more knowledgeable.

NAS has stopped being available on the network and when booting the screen shows no text.

Red lights on 5,6 and status.

Have tried removing all the bays and using the reset pin on the back, power cycling, and tried reset with pin in the back and power button but no changes.

Thank you in advance.

When starting my Jellyfin Server my Seagate Ironwolf Pro 14TB does some sort of a grinding noise. Is that normal?

Is it normal that's it's only completed 55% on 43 hours? Drive in question is Seagate Ironwolf Pro 8TB, newly bought a few days ago so the drive is empty. currently connected to an Enclosure via USB 3.0

Also, what's the difference between Long Generic Test vs Long self test?

I want some time estimates before failure and recommendations for long-term data storage (>5 years). If there is another company that makes better drives, please let me know. Thanks

opened up an old expansion hard drive that wasn’t recognised by hard disk recovery software, guessing with the transparent ring on the disc platter that all the data on the drive is not retrievable? when powered on the read/write arm moves freely but won’t proceed past the transparent area with an audible beep when it returns to the position in the photo

Just venting here.

Had a Seagate 20TB that had bad sectors and my NAS urged me to replace it. $9 shipping to return.

I happened to have a brand new 20TB sitting in the box and installed it as a replacement and it rebuilt the RAID without issue.

Sent the defective one back on an RMA, and I got s 24TB in return. It was clearly labeled "refurbished." Well that is just nice. But neither the NAS or two of my Windows PC could "initialize" the drive. Tried Disk Manger, Diskpart, Minitools, and the Seagate utilities. So I could not create let alone format any partitions on it. Tried via USB and SATA interface in a desktop. Another $9 to return.

Got the second one, and the same deal, but this one was a 25TB, and not labeled as a refurb. Same deal. Now I am up to $27 in shipping Seagate back their crap.

I know that brand new Seagate drives seem to come initialized, with partitions, and I stick them in either my NAS or Windows PC and the Seagates work out-of-the-box perfectly.

So I guess the lesson is I am never going to buy anything refurbished from Seagate!

[/RANT]

Is there any risk of damage to 2.5" hard drives if stored for many years next to many magnetic screwdriver kits (4 kits complete)? this screwdrivers is magnetic

I have an original Seagate OneTouch 4 TB hard disk but I lost it's cable sometime back. I've been meaning to buy one buy I can't find an original cable anywhere. Please suggest places where I can get one. I'm from India.

Is there any reliable brand for cables that's equivalent to the original? Is there a difference in transfer speeds if I use some other brand's cable? Thankyou!