SOLVED Badblocks destructive test and returned errors

[Fire-Dragon-DoL]

I've been running disk-burning tests on my new HDDs using https://forums.freenas.org/index.ph...for-freenas-scripts-including-disk-burnin.28/

Of 4 HDDs, 3 of them are showing a lot of read errors.
Are they really all damaged? 1 of them is a WD blue (meant for backups, not to run inside the NAS, just plug-in and plug-out), the other 2 are WD Red and I'm surprised they all come with damages (they have been bought various years apart from each other)

I must point out that I updated the script to use the -c 262143 flag: badblocks -b 4096 -c 262143 -wsv -o "$BB_File" /dev/"$Drive"
Which should speed up the process (it's been running for 3 days straight and it's still far from being completed. URGH).

Do I have to change all those disks? Could it be a software problem related to the readings and the -c flag?

 

[Johnny Fartpants]

Not sure but this is what I do.

sysctl kern.geom.debugflags=0x10

badblocks -b 4096 -ws /dev/da0

The only time I've had errors similar to this on lots of drives is when I ran badblocks on an already configured pool. The pool had no data on it and was still in the build process but it didn't like it. Therefore now I always run badblocks before I configure the pool.

 

[Fire-Dragon-DoL]

@Johnny Fartpants I did run the same sysctl command (and didn't reboot), and don't have a pool configured. My only difference is that -c flag

Sigh, either I need to rerun the tests or my hdds are broken. Amazing...

 

[Chris Moore]

I must point out that I updated the script to use the -c 262143 flag: badblocks -b 4096 -c 262143 -wsv -o "$BB_File" /dev/"$Drive"
Which should speed up the process (it's been running for 3 days straight and it's still far from being completed. URGH).

I worry that the change to the script may be the root cause here.
I looked back over your posts and I may have missed it because I was scanning visually, but what kind of drives are we talking about?

 

[Fire-Dragon-DoL]

I worry that the change to the script may be the root cause here.
I looked back over your posts and I may have missed it because I was scanning visually, but what kind of drives are we talking about?

No sorry, I forgot to mention the specs:

3 WD Red 3TB and 1 WD Blue 3 TB (it's not meant to run in FreeNAS, I'm just using it to test the drive before usage)

 

[Chris Moore]

3 WD Red 3TB and 1 WD Blue 3 TB

Not trying to be a pain. I was looking for the model number. I have seen quite a few failures out of the WD40EFRX drives. I was just curious if that is what you have. There was a user here earlier this week that had five out of seven drives failing, unfortunately, it was after data was already in the pool.

 

[Fire-Dragon-DoL]

Not trying to be a pain. I was looking for the model number. I have seen quite a few failures out of the WD40EFRX drives. I was just curious if that is what you have. There was a user here earlier this week that had five out of seven drives failing, unfortunately, it was after data was already in the pool.

I got this as model numbers:

Code:

WDC_WD30EFRX-68EUZN0_WD-WCC4N1055000
WDC_WD30EFRX-68EUZN0_WD-WMC4N0H1F8DY
WDC_WD30EFRX-68N32N0_WD-WCC7K4LDR575
WDC_WD30EZRZ-00Z5HB0_WD-WCC4N3TSV5C2      

What drives do you use as an alternatives to wd red?

 

[Spearfoot]

I've been running disk-burning tests on my new HDDs using https://forums.freenas.org/index.ph...for-freenas-scripts-including-disk-burnin.28/

Of 4 HDDs, 3 of them are showing a lot of read errors.
Are they really all damaged? 1 of them is a WD blue (meant for backups, not to run inside the NAS, just plug-in and plug-out), the other 2 are WD Red and I'm surprised they all come with damages (they have been bought various years apart from each other)

I must point out that I updated the script to use the -c 262143 flag: badblocks -b 4096 -c 262143 -wsv -o "$BB_File" /dev/"$Drive"
Which should speed up the process (it's been running for 3 days straight and it's still far from being completed. URGH).

Do I have to change all those disks? Could it be a software problem related to the readings and the -c flag?

Regarding the badblocks program: the -b and -c options work together; -b lets you specify the block size, and -c lets you specify the number of blocks to test at a time. The default for the latter is 64; I often use 128 or 512.

I reviewed the source code for badblocks some time ago, and -- if memory serves -- it allocates a buffer which is basically sized by multiplying the number of blocks (-b option) times the number of blocks tested at a time (-c) option. So you want to keep this number small enough that the resulting buffer will fit in the RAM available to the badblocks program. Otherwise it will end up swapping to disk, which wreaks havoc on performance. In any case, I honestly never saw any noticeable gain in performance from using larger values for the '-c' option.

The upshot is that I recommend you use a much smaller number for the badblocks '-c' option, say in the range of 128-1024.

Having said all that... I really don't know if your badblocks invocation caused the drive errors you're seeing, so I wouldn't give up on the disks just yet. I'd look at the results you get from the short and long smartctl tests, and if those look okay, perhaps run the badblocks test again with a much smaller '-c' value, just to rule out the possibility that it was indeed the large '-c' value that caused the errors.

I don't want to give you any false hopes, but it never hurts to double-check.

Good luck!

 

[Fire-Dragon-DoL]

The other HDDs are still running badblocks. Sigh.

The sad part is that one of the 4 drives ended up perfectly healthy after all those tests, even the extended smart shows all good, so it's a clear indication that I got 3 faulty drives...

I'll find some usage for those (obviously I'll run all the tests we discussed about).
What I'm not convinced though is that the -c flag can impact something. The only reason it could is if the RAM has a problem, but then the other HDD would have the same problem

also, -b 4096 -c 262143 is 1GB of RAM (I have 32), which should be totally fine. Now I don't know how badblocks manages the whole thing, but the docs didn't point out at any such problem.

SIGH again. I really wish I'm wrong.

Code:

+-----------------------------------------------------------------------------
+ Started burn-in of /dev/da1 : Mon Feb 11 17:33:30 PST 2019
+-----------------------------------------------------------------------------
Host: zeus.local
Drive Model: WDC_WD30EFRX-68N32N0
Serial Number: WD-WCC7K4LDR575
Short test duration: 2 minutes
Short test sleep duration: 120 seconds
Extended test duration: 343 minutes
Extended test sleep duration: 20580 seconds
Log file: ./burnin-WDC_WD30EFRX-68N32N0_WD-WCC7K4LDR575.log
Bad blocks file: ./burnin-WDC_WD30EFRX-68N32N0_WD-WCC7K4LDR575.bb
+-----------------------------------------------------------------------------
+ Run SMART short test on drive /dev/da1: Mon Feb 11 17:33:30 PST 2019
+-----------------------------------------------------------------------------
Short test started, sleeping 120 seconds until it finishes
Timeout polling for SMART self-test status
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%        21         -
# 2  Short offline       Completed without error       00%        15         -
# 3  Extended offline    Completed without error       00%         6         -
# 4  Short offline       Completed without error       00%         0         -
# 5  Extended offline    Aborted by host               90%         0         -
# 6  Short offline       Completed without error       00%         0         -

Finished SMART short test on drive /dev/da1: Mon Feb 11 21:40:52 PST 2019
+-----------------------------------------------------------------------------
+ Run SMART extended test on drive /dev/da1: Mon Feb 11 21:40:52 PST 2019
+-----------------------------------------------------------------------------
Extended test started, sleeping 20580 seconds until it finishes
SMART self-test complete
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)

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%        51         -
# 2  Extended offline    Completed without error       00%        21         -
# 3  Short offline       Completed without error       00%        15         -
# 4  Extended offline    Completed without error       00%         6         -
# 5  Short offline       Completed without error       00%         0         -
# 6  Extended offline    Aborted by host               90%         0         -
# 7  Short offline       Completed without error       00%         0         -

Finished SMART extended test on drive /dev/da1: Tue Feb 12 04:57:53 PST 2019
+-----------------------------------------------------------------------------
+ Run badblocks test on drive /dev/da1: Tue Feb 12 04:57:53 PST 2019
+-----------------------------------------------------------------------------
Finished badblocks test on drive /dev/da1: Fri Feb 15 03:13:32 PST 2019
+-----------------------------------------------------------------------------
+ Run SMART short test on drive /dev/da1: Fri Feb 15 03:13:32 PST 2019
+-----------------------------------------------------------------------------
Short test started, sleeping 120 seconds until it finishes
SMART self-test complete
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)

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%       121         -
# 2  Short offline       Completed without error       00%        51         -
# 3  Extended offline    Completed without error       00%        21         -
# 4  Short offline       Completed without error       00%        15         -
# 5  Extended offline    Completed without error       00%         6         -
# 6  Short offline       Completed without error       00%         0         -
# 7  Extended offline    Aborted by host               90%         0         -
# 8  Short offline       Completed without error       00%         0         -

Finished SMART short test on drive /dev/da1: Fri Feb 15 03:15:33 PST 2019
+-----------------------------------------------------------------------------
+ Run SMART extended test on drive /dev/da1: Fri Feb 15 03:15:33 PST 2019
+-----------------------------------------------------------------------------
Extended test started, sleeping 20580 seconds until it finishes
SMART self-test complete
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       127         -
# 2  Short offline       Completed without error       00%       121         -
# 3  Short offline       Completed without error       00%        51         -
# 4  Extended offline    Completed without error       00%        21         -
# 5  Short offline       Completed without error       00%        15         -
# 6  Extended offline    Completed without error       00%         6         -
# 7  Short offline       Completed without error       00%         0         -
# 8  Extended offline    Aborted by host               90%         0         -
# 9  Short offline       Completed without error       00%         0         -

Finished SMART extended test on drive /dev/da1: Fri Feb 15 08:58:33 PST 2019
+-----------------------------------------------------------------------------
+ SMART information for drive /dev/da1: Fri Feb 15 08:58:33 PST 2019
+-----------------------------------------------------------------------------
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68N32N0
Serial Number:    WD-WCC7K4LDR575
LU WWN Device Id: 5 0014ee 20ff0ff9f
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Feb 15 15:54:16 2019 PST
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:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Enabled

SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (32220) 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:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 343) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x303d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   100   253   021    -    0
  4 Start_Stop_Count        -O--CK   100   100   000    -    3
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   100   100   000    -    134
 10 Spin_Retry_Count        -O--CK   100   253   000    -    0
 11 Calibration_Retry_Count -O--CK   100   253   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    3
192 Power-Off_Retract_Count -O--CK   200   200   000    -    1
193 Load_Cycle_Count        -O--CK   200   200   000    -    10
194 Temperature_Celsius     -O---K   120   116   000    -    30
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    0
                            ||||||_ 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  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x04       GPL,SL  R/O      8  Device Statistics log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS       1  Device vendor specific log
0xb7       GPL,SL  VS      56  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       127         -
# 2  Short offline       Completed without error       00%       121         -
# 3  Short offline       Completed without error       00%        51         -
# 4  Extended offline    Completed without error       00%        21         -
# 5  Short offline       Completed without error       00%        15         -
# 6  Extended offline    Completed without error       00%         6         -
# 7  Short offline       Completed without error       00%         0         -
# 8  Extended offline    Aborted by host               90%         0         -
# 9  Short offline       Completed without error       00%         0         -

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):       258 (0x0102)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    30 Celsius
Power Cycle Min/Max Temperature:     27/33 Celsius
Lifetime    Min/Max Temperature:     22/33 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/65 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (419)

Index    Estimated Time   Temperature Celsius
 420    2019-02-15 07:57    32  *************
 ...    ..( 58 skipped).    ..  *************
   1    2019-02-15 08:56    32  *************
   2    2019-02-15 08:57    33  **************
 ...    ..(  3 skipped).    ..  **************
   6    2019-02-15 09:01    33  **************
   7    2019-02-15 09:02    32  *************
 ...    ..(  3 skipped).    ..  *************
  11    2019-02-15 09:06    32  *************
  12    2019-02-15 09:07    31  ************
 ...    ..(  4 skipped).    ..  ************
  17    2019-02-15 09:12    31  ************
  18    2019-02-15 09:13    30  ***********
 ...    ..( 37 skipped).    ..  ***********
  56    2019-02-15 09:51    30  ***********
  57    2019-02-15 09:52    29  **********
 ...    ..(197 skipped).    ..  **********
 255    2019-02-15 13:10    29  **********
 256    2019-02-15 13:11    30  ***********
 ...    ..(162 skipped).    ..  ***********
 419    2019-02-15 15:54    30  ***********

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               3  ---  Lifetime Power-On Resets
0x01  0x010  4             134  ---  Power-on Hours
0x01  0x018  6     48458304560  ---  Logical Sectors Written
0x01  0x020  6       206066760  ---  Number of Write Commands
0x01  0x028  6     44507236764  ---  Logical Sectors Read
0x01  0x030  6       173859073  ---  Number of Read Commands
0x01  0x038  6       482400000  ---  Date and Time TimeStamp
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4             134  ---  Spindle Motor Power-on Hours
0x03  0x010  4             117  ---  Head Flying Hours
0x03  0x018  4              12  ---  Head Load Events
0x03  0x020  4               0  ---  Number of Reallocated Logical Sectors
0x03  0x028  4               0  ---  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               1  ---  Number of High Priority Unload Events
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               0  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               0  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              30  ---  Current Temperature
0x05  0x010  1              31  ---  Average Short Term Temperature
0x05  0x018  1               -  ---  Average Long Term Temperature
0x05  0x020  1              33  ---  Highest Temperature
0x05  0x028  1              26  ---  Lowest Temperature
0x05  0x030  1              32  ---  Highest Average Short Term Temperature
0x05  0x038  1              29  ---  Lowest Average Short Term Temperature
0x05  0x040  1               -  ---  Highest Average Long Term Temperature
0x05  0x048  1               -  ---  Lowest Average Long Term Temperature
0x05  0x050  4               0  ---  Time in Over-Temperature
0x05  0x058  1              65  ---  Specified Maximum Operating Temperature
0x05  0x060  4               0  ---  Time in Under-Temperature
0x05  0x068  1               0  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4               4  ---  Number of Hardware Resets
0x06  0x010  4               0  ---  Number of ASR Events
0x06  0x018  4               0  ---  Number of Interface CRC Errors
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-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
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            0  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            1  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4       429097  Vendor specific

+-----------------------------------------------------------------------------
+ Finished burn-in of /dev/da1 : Fri Feb 15 15:56:33 PST 2019
+-----------------------------------------------------------------------------

 

[Chris Moore]

What drives do you use as an alternatives to wd red?

I have seen a much higher failure rate out of this model line of WD drives. We have a couple servers at work that came with the "plain" WD Red drives and those two servers, between them, have needed seven replacement drives, out of 32, over the last two years. I have several other servers, amounting to 64 drives, using the Red Pro drives and those systems have also suffered seven failures, but the "failure rate" is half because the population is twice as many. See where I am going with that?
The Red Pro drives are a bit more expensive though.
Personally, I like Seagate drives better because I appreciate the additional diagnostic data they provide.

 

[Fire-Dragon-DoL]

I have seen a much higher failure rate out of this model line of WD drives. We have a couple servers at work that came with the "plain" WD Red drives and those two servers, between them, have needed seven replacement drives, out of 32, over the last two years. I have several other servers, amounting to 64 drives, using the Red Pro drives and those systems have also suffered seven failures, but the "failure rate" is half because the population is twice as many. See where I am going with that?
The Red Pro drives are a bit more expensive though.
Personally, I like Seagate drives better because I appreciate the additional diagnostic data they provide.

Which seagate model do you get? IronWolf? The problem with wd red pro is that come with 4tb minimum in size, so the price ends up being almost DOUBLE

Edit:
It start making sense if I buy a 6tb though. that's 320 vs 280 for wd red, so for barely 40 more, I get the pro. I'll watch those for the next time

 

[Chris Moore]

Which seagate model do you get? IronWolf?

I have bought some of the Seagate NAS drives for testing purposes, but the servers at work are using either Seagate Constellation drives or the newer Seagate Exos drives.

 

[Fire-Dragon-DoL]

Attached, the four smart tests. da0 is the healthy disk and da3 the wd blue

 

[Chris Moore]

Attached, the four smart tests. da0 is the healthy disk and da3 the wd blue

Maybe I am overlooking something but I don't see anything in the SMART results that would stop me from using those drives.
I can't explain the errors you were seeing, but the SMART test results look passing.

 

[Fire-Dragon-DoL]

Maybe I am overlooking something but I don't see anything in the SMART results that would stop me from using those drives.
I can't explain the errors you were seeing, but the SMART test results look passing.

well, badblocks wrote 1.5GB of bad-blocks (list) for 3 hdds, but all of them have healthy smart tests...

 

[Chris Moore]

well, badblocks wrote 1.5GB of bad-blocks (list) for 3 hdds, but all of them have healthy smart tests...

That makes no sense to me. How do the SMART results show no faults if there actually are bad blocks. I think there must have been some sort of memory fault between the data written and the data that was read back, like @Spearfoot was suggesting, the data in RAM didn't match the data read back from the disk, so badblocks thought it was a fault, but the fault was software, not mechanical. Strange results.
If you ran the script again, setting the values back the way they originally were, it might pass with no errors.

 

[Fire-Dragon-DoL]

That makes no sense to me. How do the SMART results show no faults if there actually are bad blocks. I think there must have been some sort of memory fault between the data written and the data that was read back, like @Spearfoot was suggesting, the data in RAM didn't match the data read back from the disk, so badblocks thought it was a fault, but the fault was software, not mechanical. Strange results.
If you ran the script again, setting the values back the way they originally were, it might pass with no errors.

That's my thought, but I must point out that one of the drives didn't get any error with the same parameters.
I wonder if the issue might be related to hyperthreading? Who knows.

With those smart tests, I can't even send those HDDs back.