Solved Problem with the HDD disk Hitachi HDS724040ALE640.

I bought a used drive Hitachi HDS724040ALE640 MJAOA3B0.
Code:
ada1 at ahcich3 bus 0 scbus3 target 0 lun 0
ada1: <Hitachi HDS724040ALE640 MJAOA3B0> ATA8-ACS SATA 3.x device
ada1: Serial Number PK1331PAH34G9S
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 3815447MB (7814037168 512 byte sectors)

It has a capacity of 4TB. I hooked it up to the system, and it worked for ~one months. This morning I was ripping files from it, using Linux Mint, With Mint, he warned of possible damage of HDD. Also, when trying to rip from FreeBSD with samba, FreeBSD would shut down. Therefore, I used mint.I cleaned him up,using MHDD the speed on Linux reached 100MB/s. I hooked it up again. And there were problems. The installer did not want to create a partition there. So I created it manually. I added it to /etc/fstab and it throws consoles at startup, with the information that he cannot mount. Under windows, it appears to work normally. It is connected to Biostar A68MD PRO Micro ATX as Legacy IDE. It has a power supply Chieftec Smart Series, About which there are opinions that it is not the worst. I decided, to do the cleanup again on FreeBSD, and then mount it manually. The speed is 30kb/s:
Code:
root@Router:~ # dd if=/dev/zero of=/dev/ada1 status=progress
  644608 bytes (645 kB, 630 KiB) transferred 21.007s, 31 kB/s

It shows no problems on windows. Is there a chance to abuse it with some software or should I just accept defeat?

Code:
root@Router:~ # smartctl -a /dev/ada1
smartctl 7.3 2022-02-28 r5338 [FreeBSD 13.1-RELEASE amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi/HGST Deskstar 7K4000
Device Model:     Hitachi HDS724040ALE640
Serial Number:    PK1331PAH34G9S
LU WWN Device Id: 5 000cca 22bcf855d
Firmware Version: MJAOA3B0
User Capacity:    4,000,787,030,016 bytes [4.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/5319
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun May 29 22:10:02 2022 CEST
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

General SMART Values:
Offline data collection status:  (0x80) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Enabled.
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:                (   24) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        ( 569) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   136   136   054    Pre-fail  Offline      -       81
  3 Spin_Up_Time            0x0007   183   183   024    Pre-fail  Always       -       519 (Average 324)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       81
  5 Reallocated_Sector_Ct   0x0033   001   001   005    Pre-fail  Always   FAILING_NOW 213
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   112   112   020    Pre-fail  Offline      -       38
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       808
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       80
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       106
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       106
194 Temperature_Celsius     0x0002   122   122   000    Old_age   Always       -       49 (Min/Max 21/52)
196 Reallocated_Event_Count 0x0032   097   097   000    Old_age   Always       -       213
197 Current_Pending_Sector  0x0022   001   001   000    Old_age   Always       -       21080
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 233 (device log contains only the most recent five errors)
        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 233 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 38 70 4d 21 0e  Error: WP at LBA = 0x0e214d70 = 237063536

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 0b 08 40 89 01 40 00      21:23:22.076  WRITE FPDMA QUEUED
  60 40 00 68 4d 21 40 00      21:23:22.076  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      21:23:22.075  READ LOG EXT
  60 40 e8 68 4d 21 40 00      21:23:18.906  READ FPDMA QUEUED
  60 40 e0 68 48 21 40 00      21:23:18.899  READ FPDMA QUEUED

Error 232 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 38 70 4d 21 0e  Error: UNC at LBA = 0x0e214d70 = 237063536

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 40 e8 68 4d 21 40 00      21:23:18.906  READ FPDMA QUEUED
  60 40 e0 68 48 21 40 00      21:23:18.899  READ FPDMA QUEUED
  60 40 d8 68 41 21 40 00      21:23:18.891  READ FPDMA QUEUED
  61 40 d0 a8 4d 5b 40 00      21:23:18.868  WRITE FPDMA QUEUED
  60 40 c8 68 39 21 40 00      21:23:18.860  READ FPDMA QUEUED

Error 231 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 18 10 56 21 0e  Error: UNC at LBA = 0x0e215610 = 237065744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 40 d8 e8 55 21 40 00      21:10:00.013  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      21:10:00.013  READ LOG EXT
  60 40 c8 e8 55 21 40 00      21:09:56.843  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      21:09:56.842  READ LOG EXT
  60 40 b8 e8 55 21 40 00      21:09:53.672  READ FPDMA QUEUED

Error 230 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 18 10 56 21 0e  Error: UNC at LBA = 0x0e215610 = 237065744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 40 c8 e8 55 21 40 00      21:09:56.843  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      21:09:56.842  READ LOG EXT
  60 40 b8 e8 55 21 40 00      21:09:53.672  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      21:09:53.672  READ LOG EXT
  61 40 a8 e8 8d ac 40 00      21:09:50.502  WRITE FPDMA QUEUED

Error 229 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 18 10 56 21 0e  Error: UNC at LBA = 0x0e215610 = 237065744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 40 b8 e8 55 21 40 00      21:09:53.672  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      21:09:53.672  READ LOG EXT
  61 40 a8 e8 8d ac 40 00      21:09:50.502  WRITE FPDMA QUEUED
  61 40 a0 28 04 99 40 00      21:09:50.502  WRITE FPDMA QUEUED
  61 40 98 68 05 9b 40 00      21:09:50.502  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     47539         -
# 2  Short offline       Completed without error       00%        57         -
# 3  Extended offline    Interrupted (host reset)      90%        10         -
# 4  Short offline       Completed without error       00%         9         -

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.

root@Router:~ #

 
I'm not an expert at interpreting all the error messages, but "Current_Pending_Sector" at 21080 is quite alarming.

I'd remove the disk from service, re-seat the power and data cables, and test it with smartctl one more time before giving up.

If you have a test platform available, use it to get the disk away from anything you care about.
 
The most common failure rate on new hardware is within 30 days. But it's a used hard drive. And I don't know if you bought it off some sketchy website/seller. This is why I never buy used hard drives. I have a 320GB WD that has lasted 10+ years, and is still in great condition. It's a good investment to buy new hard drives. I'd suggest not putting any important data on that drive, and in the future buying only new hard drives from reputable sources. And if you can't afford a new 4TB right now, buy a smaller size.
 
Someone must have thrown it. Because drives don't break by themselves. But the operating culture of this drive also leaves a lot to be desired. Moreover, the temperature is 47*C. I once bought a 2TB SATA WD Black RE4 drive, I still have it now. I wrote to the seller maybe he will replace it.

I'm afraid to plug in a WD drive if it's a board/main power supply issue.

IMG_20220530_082921_689-min.jpg
 
They actually do.. break by themselves. That's why I said the most common failure rate on new hardware is within 30 days. You can buy a brand new hard drive, and it can just be defective. But then you'd have a warranty and be able to get your money back by returning it. And no telling what was done to your hard drive. It could have been thrown, dropped, had soda spilled on it, or the seller could have realized the drive was junk and just resold it to not take a loss on it. Again, you bought a used hard drive. It's worth the extra money to invest in a new hard drive, and get a warranty if something goes wrong. And if you are thinking of replacing it with another used hard drive well.. I'd just try to get a refund instead and shop somewhere else.
 
When I bought it the seller had 227 units of this drive. Now he has 73 units. 0.0118$ per GB. In transportation, it is unlikely that anything happened. Because the head is natively placed in a safe position. I checked. The voltages are respectively12.3V and 5.02V.
 
One thing to add: power supplies have regulators in them so they won't provide more voltage to the motherboard that what's acceptable. It would not just fry that one SATA port, and leave the rest of your motherboard intact. At this point your entire motherboard would be junk. But a failing component on a motherboard with a good power supply is a different story. A seller bought used hard drives in bulk, and probably didn't test every one of them extensively. But even if he did, they are still used. I don't know why you are so convinced you were sold a 100% good drive, when you bought used. They could have been packed and transported well, with no damage in transit. It's a used hard drive. You don't know the history of it, and there's no guarantee that it will last or work. With no warranty. As you know now. Put it this way, would you rather save $30 and buy a used hard drive on a gamble that might not last a week? That you can't trust with any important data. Or would you rather spend $30 more and buy a smaller new hard drive under warranty that will last a long time? Thereby actually saving you more money in the long term?
 
A seller bought used hard drives in bulk, and probably didn't test every one of them extensively.
He wrote that he did. I didn't. He wrote that they were operational and tested. I plugged it into FreeBSD, found it was picky, turned on torrents, and I kill him. :(
 
SATA drives should not be set up in the BIOS as legacy IDE. SATA write/read speeds are much, much faster than IDE. It should be set to SATA/ACHI if its a SATA drive. In fact that might be why your hard drive is underperforming. Try changing that in the BIOS and testing again. Please read everything I posted again fully and I think you will understand that buying used hard drives from unknown people to save a few bucks in the short term is not a good idea.
 
He wrote that he did.

The "test" could have been him, or one of his employees plugging the drive in, booting it, going in BIOS and seeing if the drive registers. Then.. "oh the drive is good, ready to ship". Unfortunately I've seen a lot of people being dishonest when selling used hardware, about the condition of it. And if there's something in the listing like "as is.. no refunds" well... you are stuck.
 
Expand the capacity of your hard drives with the Hitachi HUS726040ALA610. With a capacity of up to 4TB, this hard drive can be a game changer. With 7200 RPM and a 128MB cache, this is one of the best hard drives available on the market.

Nominal uptime is a very important part of the technical specification. The most demanding customers should pay attention to this aspect. A data carrier that will allow for failure-free operation for 2 million hours is a solution for years. This high-end drive is widely used not only on board computers, but also servers, ensuring the comfort of work at a capital level. Choose high functionality and modern technology.

Drives offered in our auctions are thoroughly checked and sold only properly efficient and safe models. In our assortment we have equipment of only reputable manufacturers.
It happens.

By the way. MHDD finished. There are no errors Between LBA 1540000000 and 1550000000. Maybe have been relocated. What does SATA3-L and SATA3-U mean?
IMG_20220530_110014_610-min.jpgIMG_20220530_110626_649.jpg
 
SMART values of your disk are completely bad.
Code:
  5 Reallocated_Sector_Ct   0x0033   001   001   005    Pre-fail  Always   FAILING_NOW 213
194 Temperature_Celsius     0x0002   122   122   000    Old_age   Always       -       49 (Min/Max 21/52)
196 Reallocated_Event_Count 0x0032   097   097   000    Old_age   Always       -       213
197 Current_Pending_Sector  0x0022   001   001   000    Old_age   Always       -       21080
Worst attribute is "197 Current_Pending_Sector = 21080".
Usually if the value in thousands then it usually means that the disk is broken and cannot be repaired at home.

As far as I know, MHDD can't scan the whole 4TB disk. You should use another tool if you want to scan all sectors of the disk.
Try to do SCAN sectors from 237000000 to 240000000. Smart report writes about errors in that zone.
 
You should use another tool if you want to scan all sectors of the disk.

Even if he did, he'd just be investing more time into investigating a failing hard drive. Like.. what's the point? There's already evidence as you said the disk is no good. To install FreeBSD on it and then have it work for a little while and ultimately fail while losing all data? I'd just see if I can get a refund and shop elsewhere. Lesson learned. DON'T BUY USED HARD DRIVES!
 
I plugged it in AHCI, so far it works but I do not know how long. Below is the current smart.

Code:
root@Router:~ # smartctl -a /dev/ada1
smartctl 7.3 2022-02-28 r5338 [FreeBSD 13.1-RELEASE amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi/HGST Deskstar 7K4000
Device Model:     Hitachi HDS724040ALE640
Serial Number:    PK1331PAH34G9S
LU WWN Device Id: 5 000cca 22bcf855d
Firmware Version: MJAOA3B0
User Capacity:    4,000,787,030,016 bytes [4.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/5319
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon May 30 11:30:00 2022 CEST
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:  (0x80) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Enabled.
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:                (   24) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        ( 569) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   136   136   054    Pre-fail  Offline      -       81
  3 Spin_Up_Time            0x0007   134   134   024    Pre-fail  Always       -       630 (Average                                                                                           519)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       86
  5 Reallocated_Sector_Ct   0x0033   089   089   005    Pre-fail  Always       -       322
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   112   112   020    Pre-fail  Offline      -       38
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       821
 10 Spin_Retry_Count        0x0013   095   095   060    Pre-fail  Always       -       1
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       85
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       111
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       111
194 Temperature_Celsius     0x0002   111   111   000    Old_age   Always       -       54 (Min/Max 2                                                                                          1/55)
196 Reallocated_Event_Count 0x0032   001   001   000    Old_age   Always       -       2685
197 Current_Pending_Sector  0x0022   097   097   000    Old_age   Always       -       224
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 315 (device log contains only the most recent five errors)
        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 315 occurred at disk power-on lifetime: 817 hours (34 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 ff 91 70 a1 0b  Error: UNC at LBA = 0x0ba17091 = 195129489

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 ff 91 70 a1 e0 00      08:35:22.895  READ VERIFY SECTOR(S) EXT
  34 00 ff 92 6f a1 e0 00      08:35:22.559  WRITE SECTORS(S) EXT
  34 00 00 90 70 a1 eb 04      08:35:22.526  WRITE SECTORS(S) EXT
  34 00 ff 92 6f a1 e0 00      08:35:19.123  WRITE SECTORS(S) EXT
  42 00 00 90 70 a1 eb 04      08:35:19.094  READ VERIFY SECTOR(S) EXT

Error 314 occurred at disk power-on lifetime: 817 hours (34 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 ff 0f f4 9f 0b  Error: UNC at LBA = 0x0b9ff40f = 195032079

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 ff 0f f4 9f e0 00      08:32:31.891  READ VERIFY SECTOR(S) EXT
  34 00 ff 10 f3 9f e0 00      08:32:31.580  WRITE SECTORS(S) EXT
  34 00 00 0e f4 9f eb 04      08:32:31.547  WRITE SECTORS(S) EXT
  34 00 ff 10 f3 9f e0 00      08:32:28.161  WRITE SECTORS(S) EXT
  42 00 00 0e f4 9f eb 04      08:32:28.132  READ VERIFY SECTOR(S) EXT

Error 313 occurred at disk power-on lifetime: 817 hours (34 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 ff 1e e5 9f 0b  Error: UNC at LBA = 0x0b9fe51e = 195028254

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 ff 1e e5 9f e0 00      08:32:23.458  READ VERIFY SECTOR(S) EXT
  34 00 ff 1f e4 9f e0 00      08:32:23.131  WRITE SECTORS(S) EXT
  34 00 00 1d e5 9f eb 04      08:32:23.098  WRITE SECTORS(S) EXT
  34 00 ff 1f e4 9f e0 00      08:32:19.695  WRITE SECTORS(S) EXT
  42 00 00 1d e5 9f eb 04      08:32:19.666  READ VERIFY SECTOR(S) EXT

Error 312 occurred at disk power-on lifetime: 817 hours (34 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 ff 07 24 78 0b  Error: UNC at LBA = 0x0b782407 = 192422919

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 ff 07 24 78 e0 00      08:27:46.623  READ VERIFY SECTOR(S) EXT
  34 00 ff 08 23 78 e0 00      08:27:46.312  WRITE SECTORS(S) EXT
  34 00 00 06 24 78 eb 04      08:27:46.279  WRITE SECTORS(S) EXT
  34 00 ff 08 23 78 e0 00      08:27:42.893  WRITE SECTORS(S) EXT
  42 00 00 06 24 78 eb 04      08:27:42.864  READ VERIFY SECTOR(S) EXT

Error 311 occurred at disk power-on lifetime: 817 hours (34 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 ff 16 15 78 0b  Error: UNC at LBA = 0x0b781516 = 192419094

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 ff 16 15 78 e0 00      08:27:38.190  READ VERIFY SECTOR(S) EXT
  34 00 ff 17 14 78 e0 00      08:27:37.863  WRITE SECTORS(S) EXT
  34 00 00 15 15 78 eb 04      08:27:37.830  WRITE SECTORS(S) EXT
  34 00 ff 17 14 78 e0 00      08:27:34.436  WRITE SECTORS(S) EXT
  42 00 00 15 15 78 eb 04      08:27:34.406  READ VERIFY SECTOR(S) EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     47539         -
# 2  Short offline       Completed without error       00%        57         -
# 3  Extended offline    Interrupted (host reset)      90%        10         -
# 4  Short offline       Completed without error       00%         9         -

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.
 
Just more port unlocking and I can clean up.

It's almost like you are ignoring everything that's been told to you. You know that this hard drive has issues right? Like it can't be relied on to store data reliably or run an OS in the long term. Unless you are just using this to test if you can install FreeBSD for the very first time, and then later using another good hard drive to run FreeBSD I don't really see the point in going any further. You are just going to run into problems down the road. I'd just see if you can get a refund and call it a day. Then invest in a new hard drive. Don't accept another used hard drive as a replacement. But hey, if gambling on running operating systems on used hard drives with known issues in the chance that they *might* work for X amount of time before they die completely is your thing... you do you.
 
I'm beginning to think that for torrents some SAS drives would be most suitable. I anticipated this, and wanted to buy a board with more PCI-e for the SAS controller. But there was no suitable one in the budget. I once had a server on a Suitsu Futro S450 and killed the disk controller with torrents. Maybe this one will hold up. Yes both are on AHCI and are detected yesterday they were not. The SSD is also used.

This is auction.
https://allegro-pl.translate.goog/oferta/dysk-twardy-4tb-3-5-hgst-7k6000-128mb-7200rpm-sata-11897099858?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=pl&_x_tr_pto=wapp
 
I'm beginning to think that for torrents some SAS drives would be most suitable.

For what? speed? Torrenting at the volume where you are killing disk controllers is going to put heavy strain on any type of hard drive, SATA, SAS, SSD .. whatever it is, expect to replace your hard drives way before their expected lifespan on drives you torrent on. Not sure this is a smart thing to do if you want to save money.
 
That's how it sends masses of data, could say flood. To make matters worse they are scattered, I sent about 13,000 GB. The drive which was used is in the laptop now.

As if anyone asked, I used Erase Delays *DESTRUCTIVE* overnight and then checked the LBA range with badsectors. Using, Scan/Repair.
 
The seller wrote me back and told me to send the drive back and fill out a claim form. Should we replace it?
I didn't lose much.
 
Back
Top