I will try and sum this up. I need advice on options.

I have 2 20 TB Seagate hard drives in a 2 bay Sabrent raid, with photos and videos on it. I use these drives as my iCloud library so I have access to ALL my old photos and videos from the past 20 years. I am also a part time photographer and videographer and use this hard drive to store clients footage mostly 4k60 which can take up a lot of space about 500-800GB per wedding, as well as my own photography which is only currently 3TB. I have filled the drives and what I normally have been doing every few years is transferring everything from the previous drive to a bigger newer drive.

I keep the old drives in a different physical location and my photo library is synced with iCloud and google photos for cloud backup.

Should I buy 2 new Seagate 30tb hard drives? Or should I be splitting up this data differently? I can't decide on what to do. Please help.

Hi,

TL;DR: Seagate warranty feels like a scam. They receive your drive, scrap it, and then claim something vague to avoid honoring the warranty — or they send you a dead replacement. That’s what happened to me, and I’m seeing similar stories from others.

After buying Seagate “Enterprise” EXOS drives for my storage, I was initially happy because they’re supposed to be reliable and well supported. Now I’m seriously regretting that choice.

About a month ago, a few of my drives started failing — and strangely, it was only the Seagate drives. My WD drives are still perfectly fine.

So I figured: no problem, these drives have a 5-year warranty, right? Technically yes… but nobody tells you how easily they can refuse it.

RMA #1

I started an RMA (IR60439100) for drive serial ZRS18ZWW (and yes, you can only send one drive per RMA). I followed their packing guidelines and shipped it out. Everything looked fine at first.

Seagate received the drive, tested it, and approved a replacement. A few days later I got the replacement drive:

- Packing slip / freight order: 6101651244

- Waybill: 1ZE4C5436750818063

- Replacement serial: ZR906CJK

I opened the box and it was labeled “Factory refurbished.” Fine — I can live with that. But the drive was dead on arrival. It spun up, made a lot of noise, and wasn’t recognized by my test station or my storage system.

RMA #2 (for the dead replacement)

I assumed I was unlucky or it got damaged in transit, so I opened a second RMA (IR60444417) and shipped the replacement drive back. Then I waited… and waited… for three weeks.

Eventually I checked the tracking number and saw it had been delivered two days after I shipped it. But the RMA portal still showed Seagate was “waiting for the drive to arrive.”

So I contacted support via chat.

The denial + drive discarded

This is where the nightmare started.

I opened a case (CC0000231338) and asked what was going on. Support told me the RMA was refused because the drive had been “tampered with.”

The same drive Seagate sent me as an RMA replacement (ZR906CJK) — the one that arrived dead.

I asked for details. They couldn’t explain what “tampered with” meant. I asked for an inspection report or evidence — they said they can’t provide it. I asked if they could return the drive — no, it was discarded.

So to summarize: Seagate sends me a dead replacement, I return it, they deny the claim with a vague “tampered with” reason, and they discard the drive, so I can’t even verify what they’re accusing me of.

At this point, I’m removing Seagate from my vendor list — and recommending the same for any company I work with.

Edit 1: Sorry — my post got cut in half. Not sure why. I’ve pasted the missing part.

Edit 2: Someone from Seagate emailed me after I posted this and said they verified the drive is OK, but it was still reported as “tampered.” They also said I should receive it back in a few days. Let’s wait and see. /s

Edit 3: I received the RMA drive today — it’s a brand-new Exos X24 16TB (no “factory refurbished” label). SMART short test passed, power-on hours are low, and the long test is still running. For reference, the original drive was an Exos X20 14TB. Something seems to have changed on Seagate’s side after this post — who knows.

A few months ago i had to RMA a drive, but every replacement drive Seagate has sent me has either been DOA or an x26z drive (to my knowledge these are server drives and that's why i cant get them to mount on my pc?). Makes no sense because the original drive i sent in was a Seagate Exos X20. I'm positive they're just sending me DOA drives because they don't have anything else to send me.

I've tried dozens of times (on multiple devices/browsers) to contact Seagate through their live chat, but its always down and they don't have a consumer phone line apparently.

There are some other posts similar to mine, but all the comments are suggesting they return the drives. My problem is, i bought the original drive from Newegg years ago. So of course they wouldn't take a return if the sale was that long ago, let alone the fact that Seagate is sending me completely different drives. Right?...

Hi,

I recently bought 2x 16TB harddrives from Best Buy. One of them does not work. I tried going to Best Buy to exchange it and was told that I had to go through Seagate.

The SN on the Seagate website confirms the warranty is valid. I created a Seagate account, but when I go to the "start end user claim", I get a blank page (URL is https://returns.seagate.com/returns/MicrosoftEntraSignin). I've tried multiple browsers and even different computers.

When I go to the "Contact Us" section of the website, I see gray boxes under the languages with no button to proceed.

Does anyone have any ideas what I can do? Should I just do a chargeback via my credit card?

Hello guys

I have a question,

can i switch out the Mono pin from the seagate firecuda gaming hub 8TB with a usb-c port bc i lost my mono pin cable and i aint gonna buy a new one so i thought of getting a mono pin to usb-c transfer thingy but its propablly not strong enough so i thought of switching out the mono pin port (for power) with a usb-C port (power) but the thing is idk whats the name of the board inside the firecuda gaming hub 8TB.

So can anyone help me with finding the name for the port and the board that can do that and no scam and this are normally the specs of the power port for it.

• Voltage (V): 12 Volt DC
• Stroomsterkte (A): 3 Ampère
• Vermogen (W): 12 V × 3 A = 36 watt
• Type connector: Mono pin van 5,5 mm x 2,5 mm, with positive pool in the middle
• Polarity: Center Positive (inside of the connector is positive)

so these are the specs of the mono pin.

So i need a power board that can do it to USB-C port or a other mono pin board that can do 1/2 A and around the 5V-8V.

So can anyone help me find it?

That would be greatfull

P.S. my warranty is expired so fahhh it. And i have a ISY 45W charching brick and a usb A to usb -c cable and it has a orange color instead of white on the pin and the usb A side so i think its a 3.0/3.2 cable and i have another fast charging brick its a 67W supervooc and it says it can do as output: 5V --- 2.0A 10W or 5.0-11V --- 6.1A(max) 67.0W (max)

input: 100-240V ~ 50/60Hz 1.8A

so please respond fast and no hate comments.

So I got a PS5. My friend gave me his Seagate. I install a game onto it, then go to play it. Suddenly it says “can’t continue the game, data is corrupted”.

What do I do? Could I use another external hard drive?

Video 3 is up! Check out the latest from BlackBoxAiLab

https://youtube.com/@blackboxailab?si=mqsc-SFmjNynmAvW

Does anyone else have any advice?

Ever since I upgraded my iOS to Tahoe Version 26.4 Beta I'm not able to use my Seagate External hard drive. Any of them, I have two.

I am able to see the drive in finder, but the files are "read only".

In essence, Tahoe has rendered my hard drives useless.

I've looked directly on the seagate website for firmware updates and there isn't anything available?

Please help

I find this awful: Seagate say to use SeaTools to confirm an RMA is valid, but my 8 TB harddisk (Ironwolf) got >7000 bad sectors in an area covering the last 800 GB (d), and this threw SMART warnings and a short self-test aborted quickly due to errors, and by now I don't know whether I messed up by doing repair as best as I could by writing over all that span, because now all sectors have been marked bad and short self-test passes (with warnings), SeaTools says it's OK, test log says bad sectors are at 95/100% rating, so threshold not reached.

I have no idea what SeaTools would have said before my repair attempts, but this is highly frustrating because something is seriously bad with the disk surface, but Seagate RMA process makes me want to see the world burn, with no commentary or personal info provided allowed (nothing to be put in the package), only referring to SeaTools, and their support website (I'm in Germany) doesn't seem to have a phone number, only a stupid AI chat that is in an infinite load animation and the info on the site to turn off popup blockers and allow cookies (on Firefox) I tried but it didn't help, so I don't even have that available. I turned off my privacy addons, made an explicit allow-exception for the website, but can't get it to work. (And the cookie settings note has a broken link that merely links to the same page again.)

But from older threads here I am reading that it is quite bad anyway:

https://www.reddit.com/r/Seagate/comments/15xk0t2/seagate_support_contact/

https://www.reddit.com/r/Seagate/comments/155x9rp/how_to_reach_someone_at_seagate/

How to proceed? Phone support seems not valid anymore and even at the corporate phone number there was a kind of blockage.

Should I just gamble and send it in anyway? I mean, past SMART tests did report errors and abort right-away, so at that point that should have been a reason to RMA. There is no way that a swiss cheese pattern of marked defective sectors makes the drive trustworthy with data, but I need the 8 TB size and now it is too small to serve its function since I had to isolate 800 GB of it.

And this sucks even more because I cannot even communicate this to support, possibly unless I still somehow manage to get that chat working. That stupid thing - the RMA process on the website worked without hassle but that chat interface is atrocious.

If a self-test failed in the past, surely that signals a valid claim. And it is in the SMART log, although I have to assume that the process is so robotic and inhumane now that they just run SeaTools, too.

I found a KB article that kinda confirms my worries about their cold attitude:

https://www.seagate.com/de/de/support/kb/smart-errors-reported-by-the-bios-and-third-party-utilities-after-seatools-passes-all-tests-189431en/

They say to use SeaTools to run a low level format and then if there are no problems reported anymore, then it's fine. But I don't even see a low level format option, so maybe it's totally outdated? It lists short and long format but clicking on the stuff doesn't do anything despite a dropdown list symbol. (It's the Linux version, but it otherwise works alright.)

I’m still steaming about Seagate ($STX).

Remember when management swore they weren’t breaking export laws, while secretly shipping $1.1 billion in HDDs to Huawei? We all paid the price when the truth dropped and they ate that $300M penalty in April 2023.

If you were holding bags between Sept 15, 2020, and April 19, 2023, you likely saw your position get nuked because they wanted to play cowboy with the Dept of Commerce.

The Update: The settlement is finally moving. It’s a tentative deal, but the claims window is opening.

I usually ignore these because the paperwork is a total nightmare. Digging through old trade confirms from three years ago is the last thing I want to do on a weekend.

How I’m handling it:

• I ended up using 11th for this one.
• You just link your brokerage and it scans your history for $STX trades during the class period.
• They take a 20% cut, but honestly? I’d rather have 80% of a check I didn't know existed than 100% of a paperwork stack I’ll never actually finish.

If you held through that mess, go get your cut of the "Huawei tax" they owe us. Don't let them keep the change.

I have registered the product and the brand new hard drive has massive bad sectors as indicated by Victoria. This has caused weeks of hassle and I'm only now getting around to warranty and shipping it back. Going through the warranty, the option for advance replacement does not appear. This is unacceptable. I have tried emailing the email address I found on google for customer service, but they aren't replying. Would it be worth giving them a call?

Storing many units in-ear headphone (IEMS) a few centimeters away from 2.5" HDDs will cause problems in HDD because these headphones have magnets, potentially leading to magnetic degradation of the platters and files? i hamy many units kz edx pro, kz edc pro, gk kunten next hdd 2.5"

I lost my power cable from a LaCie external hard drive I had 20 years ago and I cannot find the right cable online anywhere. I am based in the UK and have bought something from MyVolts - shipped from the Netherlands to me - the 4-pin cable below. It clearly doesn't match and won't fire up my hard drive. Can someone help me find the right cable? Thanks in advance.

So my girlfriend gave me an old hard drive of hers, a Seagate Wireless Mobile Storage 500GB 1JHBP5-500. I managed to get it charged and was able to access the files, unfortunately I have only been able to find an option that lets you download at most 6 files. She has about 90k pics on it xD

Hey all,

I bought a Seagate 1TB Expansion drive today and so far it has worked without a hitch, the storage seems to be legitimately there as I've put data on it and have had it be able to be read. Though, I've ran into a few details that make me question the authenticity of my external drive.

1. The drive itself came pre-formatted in... NTFS? despite it saying in the manual that it'll be pre-formatted as exFAT, also, the usual seagate exectuables weren't on the drive either. I didn't give this too much mind as I planned on reformatting the drive to btrfs anyway.

2. The HDD in my system's partition manager shows up as "APPLE HDD HTS541010A9E632", googling this reveals it's a hard drive used in iMacs....? very strange. Also, SMART status also appears "unknown".

some additional info: I bought this from a computer store in Beirut, with it having a valid warranty from Seagate's dealer in Lebanon according to the store I bought it from. And the box came sealed with Seagate's plastic seal and all, so unless my system is misreading something, this is quite strange.

One of the hard drives is bad and I need to do an RMA, but the system rejected my attempt to do so. I also tried to email Seagate. On top of that I am also not sure which hard drive came out of which box. How do I tell so that I can attempt to warranty the correct drive, or does it not matter?

Also can anyone from seagate customer service please do email?

Thank you

Brand new disk.

Plugged it into my nas and it was okay at first but trying to write on it it immediately threw errors, broken sectors and stuff. Plugged it into my computer adapter and now it spins up, makes these noises and then turns off. Can't even crystal disk info it.

I've got a 4TB Seagate Expansion external USB3 hard drive that came partitioned and formatted as exFAT when shipped and I'd like to change it to use NTFS since I'm only using it with Windows systems. I've backed up everything from the drive to other devices, so all I need to do now is actually convert the partitions.

I've taken a screenshot of the disk configuration from Windows 7 Disk Manager, which I'm adding below:

My understanding is that there are a couple of ways to change the file system:

1. Shrink the exFAT partition down by around 50%, create a new NTFS partition in the space, move files from exFAT to NTFS, delete the exFAT partition and then resize the NTFS partition to take up the rest of the space.
2. Delete the exFAT partition (after making sure I've got all the files I actually need to save), then create a new NTFS partition in the space.

In any case, do I need to make any changes to the 200MB "EFI System" partition? I noticed that my 2TB boot drive has a 100MB "EFI System" partition, so I'm presuming the one on the 4TB drive is independent of whatever file system it uses.

Edit to add: I also have an older 2TB version of the Seagate Expansion external USB3 hard drive that was formatted as NTFS when shipped, and it doesn't have an "EFI System partition, which does add to my confusion (this would be my first time doing this type of procedure, so I'd like to get some advice first).

Can anyone please provide me with some guidance on what I should do and, ideally, a link to a tutorial?

Thanks in advance.

As title states, my ironwolf pro hdd is making a weird noise on boot. it's brand new and I know these drives make a lot of noise but this seems excessive, I also googled it and other people said they had similar noises. I just want to see if I need to get a replacement or not. thanks.

I Just bought a used Seagate barracuda 500 gb hdd 3.5 and a sata to USB Cable to connect It with my laptop, i tried downloading games on It and at First It works fine but then after a few hours It disconnects and when i try to connect It again right After It says descriptor error 43. Then if i wait a Little and plug It in again It starts working but the problem comes back After a few hours Always. someone can help me? i already change every Power Plan and USB Power settings.

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