Pending sector count on two WD Red 6TB drives

[Piers]

Hello,

I have two questions I hope you can help with.

1. I performed the repair disk feature after reading the help documentation and it 'repaired' the pending sector count. I then adjusted the offset number in SMART (as I've seen advised on this forum). I have two of these drives which appear to have failed at the same time. I ran a repair on the other one and it found over 600 pending sector errors, but claimed it was fixed.

Realistically, how reliable would these drives be? I moved the data off one drive and out of ~6,000 files, 5 couldn't be read.

2. Is it possible to automatically save a full log of the repair process? The message said ~600 errors had been fixed and I tried to save the log but it doesn't seem to be in the HDS directory.

And thank you for creating such awesome software. It's been really helpful so far.

Code: Select all

  -- Physical Disk Information - Disk: #1: WDC WD60EFRX-68L0BN1 --

    Hard Disk Summary
   -------------------
    Hard Disk Number . . . . . . . . . . . . . . . . : 1
    Interface  . . . . . . . . . . . . . . . . . . . : LSI  RAID #1/1 [8-0]
    Disk Controller  . . . . . . . . . . . . . . . . : Avago Adapter, SAS3 3008 Fury -StorPort (PCI\CC_010700&DT_0) [VEN: 1000, DEV: 0097] Version: 2.51.24.80, 5-2-2018
    Disk Location  . . . . . . . . . . . . . . . . . : Bus Number 0, Target Id 9, LUN 0, Device: 2
    Hard Disk Model ID . . . . . . . . . . . . . . . : WDC WD60EFRX-68L0BN1
    Firmware Revision  . . . . . . . . . . . . . . . : 82.00A82
    Hard Disk Serial Number  . . . . . . . . . . . . : WD-WX11DC57SPXX
    Total Size . . . . . . . . . . . . . . . . . . . : 5723166 MB
    Power State  . . . . . . . . . . . . . . . . . . : Active
    Current Temperature  . . . . . . . . . . . . . . : 38 °C
    Maximum Temperature (Ever Measured)  . . . . . . : 47 °C, 26/05/2020 21:42:05
    Minimum Temperature (Ever Measured)  . . . . . . : 34 °C, 29/06/2020 03:32:04
    Maximum Temperature (During Entire Lifespan) . . : 51 °C
    Power On Time  . . . . . . . . . . . . . . . . . : 473 days, 6 hours
    Estimated Remaining Lifetime . . . . . . . . . . : more than 1000 days
    Health . . . . . . . . . . . . . . . . . . . . . : ###################- 96 % (Excellent)
    Performance  . . . . . . . . . . . . . . . . . . : #################### 100 % (Excellent)

    There are 6 weak sectors found on the disk surface. They may be remapped any time in the later use of the disk.
    More information: https://www.hdsentinel.com/hard_disk_case_weak_sectors.php
    At this point, warranty replacement of the disk is not yet possible, only if the health drops further.
    It is recommended to examine the log of the disk regularly. All new problems found will be logged there.
      No actions needed.

    ATA Information
   -----------------
    Hard Disk Cylinders  . . . . . . . . . . . . . . : 11628021
    Hard Disk Heads  . . . . . . . . . . . . . . . . : 16
    Hard Disk Sectors  . . . . . . . . . . . . . . . : 63
    ATA Revision . . . . . . . . . . . . . . . . . . : ACS-2, ACS-3 Revision 3b
    Transport Version  . . . . . . . . . . . . . . . : SATA Rev 3.1
    Total Sectors  . . . . . . . . . . . . . . . . . : 1465130646
    Bytes Per Sector . . . . . . . . . . . . . . . . : 4096 [Advanced Format]
    Multiple Sectors . . . . . . . . . . . . . . . . : 16
    Error Correction Bytes . . . . . . . . . . . . . : 0
    Unformatted Capacity . . . . . . . . . . . . . . : 5723167 MB
    Maximum PIO Mode . . . . . . . . . . . . . . . . : 4
    Maximum Multiword DMA Mode . . . . . . . . . . . : 2
    Highest Possible Transfer Rate . . . . . . . . . : S-ATA Gen3 Signaling Speed (6 Gps)
    Negotiated Transfer Rate . . . . . . . . . . . . : S-ATA Gen3 Signaling Speed (6 Gps)
    Minimum Multiword DMA Transfer Time  . . . . . . : 120 ns
    Recommended Multiword DMA Transfer Time  . . . . : 120 ns
    Minimum PIO Transfer Time Without IORDY  . . . . : 120 ns
    Minimum PIO Transfer Time With IORDY . . . . . . : 120 ns
    ATA Control Byte . . . . . . . . . . . . . . . . : Valid
    ATA Checksum Value . . . . . . . . . . . . . . . : Valid

    Acoustic Management Configuration
   -----------------------------------
    Acoustic Management  . . . . . . . . . . . . . . : Not supported
    Acoustic Management  . . . . . . . . . . . . . . : Disabled
    Current Acoustic Level . . . . . . . . . . . . . : Default (00h)
    Recommended Acoustic Level . . . . . . . . . . . : Default (00h)

    ATA Features
   --------------
    Read Ahead Buffer  . . . . . . . . . . . . . . . : Supported, Enabled
    DMA  . . . . . . . . . . . . . . . . . . . . . . : Supported
    Ultra DMA  . . . . . . . . . . . . . . . . . . . : Supported
    S.M.A.R.T. . . . . . . . . . . . . . . . . . . . : Supported
    Power Management . . . . . . . . . . . . . . . . : Supported
    Write Cache  . . . . . . . . . . . . . . . . . . : Supported
    Host Protected Area  . . . . . . . . . . . . . . : Supported
    HPA Security Extensions  . . . . . . . . . . . . : Supported
    Advanced Power Management  . . . . . . . . . . . : Not supported
    Extended Power Management  . . . . . . . . . . . : Not supported
    Power Up In Standby  . . . . . . . . . . . . . . : Supported
    48-Bit LBA Addressing  . . . . . . . . . . . . . : Supported
    Device Configuration Overlay . . . . . . . . . . : Supported
    IORDY Support  . . . . . . . . . . . . . . . . . : Supported
    Read/Write DMA Queue . . . . . . . . . . . . . . : Not supported
    NOP Command  . . . . . . . . . . . . . . . . . . : Supported
    Trusted Computing  . . . . . . . . . . . . . . . : Not supported
    64-Bit World Wide ID . . . . . . . . . . . . . . : 50014EE20D436A63
    Streaming  . . . . . . . . . . . . . . . . . . . : Supported
    Media Card Pass Through  . . . . . . . . . . . . : Not supported
    General Purpose Logging  . . . . . . . . . . . . : Supported
    Error Logging  . . . . . . . . . . . . . . . . . : Supported
    CFA Feature Set  . . . . . . . . . . . . . . . . : Not supported
    CFast Device . . . . . . . . . . . . . . . . . . : Not supported
    Long Physical Sectors (8)  . . . . . . . . . . . : Supported
    Long Logical Sectors . . . . . . . . . . . . . . : Not supported
    Write-Read-Verify  . . . . . . . . . . . . . . . : Not supported
    NV Cache Feature . . . . . . . . . . . . . . . . : Not supported
    NV Cache Power Mode  . . . . . . . . . . . . . . : Not supported
    NV Cache Size  . . . . . . . . . . . . . . . . . : Not supported
    Free-fall Control  . . . . . . . . . . . . . . . : Not supported
    Free-fall Control Sensitivity  . . . . . . . . . : Not supported
    Service Interrupt  . . . . . . . . . . . . . . . : Not supported
    IDLE IMMEDIATE Command With UNLOAD Feature . . . : Supported
    Nominal Media Rotation Rate  . . . . . . . . . . : 5700 RPM

    SSD Features
   --------------
    Data Set Management  . . . . . . . . . . . . . . : Not supported
    TRIM Command . . . . . . . . . . . . . . . . . . : Not supported
    Deterministic Read After TRIM  . . . . . . . . . : Not supported
    Read Zeroes After TRIM . . . . . . . . . . . . . : Not supported

    S.M.A.R.T. Details
   --------------------
    Off-line Data Collection Status  . . . . . . . . : Never Started
    Self Test Execution Status . . . . . . . . . . . : Successfully Completed
    Total Time To Complete Off-line Data Collection  : 3164 seconds
    Execute Off-line Immediate . . . . . . . . . . . : Supported
    Abort/restart Off-line By Host . . . . . . . . . : Not supported
    Off-line Read Scanning . . . . . . . . . . . . . : Supported
    Short Self-test  . . . . . . . . . . . . . . . . : Supported
    Extended Self-test . . . . . . . . . . . . . . . : Supported
    Conveyance Self-test . . . . . . . . . . . . . . : Supported
    Selective Self-Test  . . . . . . . . . . . . . . : Supported
    Save Data Before/After Power Saving Mode . . . . : Supported
    Enable/Disable Attribute Autosave  . . . . . . . : Supported
    Error Logging Capability . . . . . . . . . . . . : Supported
    Short Self-test Estimated Time . . . . . . . . . : 2 minutes
    Extended Self-test Estimated Time  . . . . . . . : 685 minutes
    Conveyance Self-test Estimated Time  . . . . . . : 5 minutes
    Last Short Self-test Result  . . . . . . . . . . : Successfully Completed
    Last Short Self-test Date  . . . . . . . . . . . : 05/12/2019 20:23:37
    Last Short Self-test Duration  . . . . . . . . . : 4 minutes
    Last Extended Self-test Result . . . . . . . . . : Never Started
    Last Extended Self-test Date . . . . . . . . . . : Never Started
    Last Conveyance Self-test Result . . . . . . . . : Never Started
    Last Conveyance Self-test Date . . . . . . . . . : Never Started

    Security Mode
   ---------------
    Security Mode  . . . . . . . . . . . . . . . . . : Supported
    Security Erase . . . . . . . . . . . . . . . . . : Supported
    Security Erase Time  . . . . . . . . . . . . . . : 752 minutes
    Security Enhanced Erase Feature  . . . . . . . . : Supported
    Security Enhanced Erase Time . . . . . . . . . . : 752 minutes
    Security Enabled . . . . . . . . . . . . . . . . : No
    Security Locked  . . . . . . . . . . . . . . . . : No
    Security Frozen  . . . . . . . . . . . . . . . . : No
    Security Counter Expired . . . . . . . . . . . . : No
    Security Level . . . . . . . . . . . . . . . . . : High
    Device Encrypts All User Data  . . . . . . . . . : No
    Sanitize . . . . . . . . . . . . . . . . . . . . : Not supported
    Overwrite  . . . . . . . . . . . . . . . . . . . : Not supported
    Crypto Scramble  . . . . . . . . . . . . . . . . : Not supported
    Block Erase  . . . . . . . . . . . . . . . . . . : Not supported
    Sanitize Antifreeze Lock . . . . . . . . . . . . : Not supported
    ACS-3 Commands Allowed By Sanitize . . . . . . . : No

    Serial ATA Features
   ---------------------
    S-ATA Compliance . . . . . . . . . . . . . . . . : Yes
    S-ATA I Signaling Speed (1.5 Gps)  . . . . . . . : Supported
    S-ATA II Signaling Speed (3 Gps) . . . . . . . . : Supported
    S-ATA Gen3 Signaling Speed (6 Gps) . . . . . . . : Supported
    Receipt Of Power Management Requests From Host . : Supported
    PHY Event Counters . . . . . . . . . . . . . . . : Supported
    Non-Zero Buffer Offsets In DMA Setup FIS . . . . : Not supported
    DMA Setup Auto-Activate Optimization . . . . . . : Supported, Enabled
    Device Initiating Interface Power Management . . : Supported, Disabled
    In-Order Data Delivery . . . . . . . . . . . . . : Not supported
    Asynchronous Notification  . . . . . . . . . . . : Not supported
    Software Settings Preservation . . . . . . . . . : Supported, Enabled
    Native Command Queuing (NCQ) . . . . . . . . . . : Supported
    Queue Length . . . . . . . . . . . . . . . . . . : 32
    NCQ Streaming  . . . . . . . . . . . . . . . . . : Not supported
    NCQ Autosense  . . . . . . . . . . . . . . . . . : Not supported
    Automatic Partial To Slumber Translations  . . . : Not supported
    Rebuild Assist . . . . . . . . . . . . . . . . . : Not supported
    Hybrid Information . . . . . . . . . . . . . . . : Not supported
    Device Sleep (DevSleep)  . . . . . . . . . . . . : Not supported
    DevSleep To ReducedPwrState  . . . . . . . . . . : Not supported

    Disk Information
   ------------------
    Disk Family  . . . . . . . . . . . . . . . . . . : Red
    Form Factor  . . . . . . . . . . . . . . . . . . : 3.5" 
    Capacity . . . . . . . . . . . . . . . . . . . . : 6 TB (6 x 1,000,000,000,000 bytes)
    Number Of Disks  . . . . . . . . . . . . . . . . : ?
    Number Of Heads  . . . . . . . . . . . . . . . . : ?
    Rotational Speed . . . . . . . . . . . . . . . . : 5400 RPM
    Rotation Time  . . . . . . . . . . . . . . . . . : 11.11 ms
    Average Rotational Latency . . . . . . . . . . . : 5.56 ms
    Disk Interface . . . . . . . . . . . . . . . . . : Serial-ATA/600
    Buffer-Host Max. Rate  . . . . . . . . . . . . . : 600 MB/seconds
    Buffer Size  . . . . . . . . . . . . . . . . . . : 65536 KB
    Drive Ready Time (Typical) . . . . . . . . . . . : ? seconds
    Average Seek Time  . . . . . . . . . . . . . . . : ? ms
    Track To Track Seek Time . . . . . . . . . . . . : ? ms
    Full Stroke Seek Time  . . . . . . . . . . . . . : ? ms
    Width  . . . . . . . . . . . . . . . . . . . . . : 101.6 mm (4.0 inch)
    Depth  . . . . . . . . . . . . . . . . . . . . . : 147.0 mm (5.8 inch)
    Height . . . . . . . . . . . . . . . . . . . . . : 26.1 mm (1.0 inch)
    Weight . . . . . . . . . . . . . . . . . . . . . : 750 grams (1.7 pounds)
    Acoustic (Idle)  . . . . . . . . . . . . . . . . : 2.5 Bel
    Acoustic (Min Performance And Volume)  . . . . . : 2.8 Bel
    Acoustic (Max Performance And Volume)  . . . . . : 2.8 Bel
    Required Power For Spinup  . . . . . . . . . . . : 1,750 mA
    Power Required (Seek)  . . . . . . . . . . . . . : 5.3 W
    Power Required (Idle)  . . . . . . . . . . . . . : 3.4 W
    Power Required (Standby) . . . . . . . . . . . . : 0.4 W
    Manufacturer . . . . . . . . . . . . . . . . . . : Western Digital Corporation
    Manufacturer Website . . . . . . . . . . . . . . : http://www.westerndigital.com/en/products

    S.M.A.R.T.
   ------------
No.  Attribute                Thre.. Value  Worst  Data                Status                   Flags                                                  
1    Raw Read Error Rate      51     200    155    39                  OK                       Self Preserving, Error-Rate, Performance, Statistica.. 
3    Spin Up Time             21     219    206    8041                OK                       Self Preserving, Performance, Statistical, Critical    
4    Start/Stop Count         0      100    100    40                  OK (Always passing)      Self Preserving, Event Count, Statistical              
5    Reallocated Sectors Co.. 140    200    200    0                   OK                       Self Preserving, Event Count, Statistical, Critical    
7    Seek Error Rate          0      100    253    0                   OK (Always passing)      Self Preserving, Error-Rate, Performance, Statistical  
9    Power On Time Count      0      85     84     11358               OK (Always passing)      Self Preserving, Event Count, Statistical              
10   Spin Retry Count         0      100    253    0                   OK (Always passing)      Self Preserving, Event Count, Statistical              
11   Drive Calibration Retr.. 0      100    253    0                   OK (Always passing)      Self Preserving, Event Count, Statistical              
12   Drive Power Cycle Count  0      100    100    40                  OK (Always passing)      Self Preserving, Event Count, Statistical              
192  Power off Retract Cycl.. 0      200    200    38                  OK (Always passing)      Self Preserving, Event Count, Statistical              
193  Load/Unload Cycle Count  0      200    200    2602                OK (Always passing)      Self Preserving, Event Count, Statistical              
194  Disk Temperature         0      114    101    38                  OK (Always passing)      Self Preserving, Statistical                           
196  Reallocation Event Count 0      200    200    0                   OK (Always passing)      Self Preserving, Event Count, Statistical              
197  Current Pending Sector.. 0      200    200    6                   OK (Always passing)      Self Preserving, Event Count, Statistical              
198  Off-Line Uncorrectable.. 0      100    253    0                   OK (Always passing)      Self Preserving, Event Count                           
199  Ultra ATA CRC Error Co.. 0      200    200    0                   OK (Always passing)      Self Preserving, Event Count, Statistical              
200  Write Error Rate         0      100    253    0                   OK (Always passing)      Error-Rate                                             

    Transfer Rate Information
   ---------------------------
    Total Data Read  . . . . . . . . . . . . . . . . : 7,338,557 MB,  19,394,134 MB since installation  (05/12/2019)
    Total Data Write . . . . . . . . . . . . . . . . : 20,284 MB,  6,170,228 MB since installation
    Average Reads Per Day  . . . . . . . . . . . . . : 93,241.03 MB
    Average Writes Per Day . . . . . . . . . . . . . : 29,664.56 MB
    Current Transfer Rate  . . . . . . . . . . . . . : 0 KB/s
    Maximum Transfer Rate  . . . . . . . . . . . . . : 598610 KB/s
    Current Read Rate  . . . . . . . . . . . . . . . : 0 KB/s
    Current Write Rate . . . . . . . . . . . . . . . : 369 KB/s
    Current Disk Activity  . . . . . . . . . . . . . : 0 %

[hdsentinel]

> Realistically, how reliable would these drives be? I moved the data off one drive and out of ~6,000 files, 5 couldn't be read.

As the page
https://www.hdsentinel.com/hard_disk_ca ... ectors.php
(suggested in the text description when weak sectors detected) mentions, in most cases the weak sectors are not really related to disk drives: in most cases, something else (cables, connections, power source, etc..) are in the background, resulting weak sectors. In RAID configuration, even the backplane/enclosure/expander can be the problem. Or "just" a minor incompatibility between the controller driver/firmware and the drives, so a driver/firmware update may also help.

If two drives produce similar issue at the same time - then it is also very suspicious and can confirm that the issues may be not really related to the hard disk drives.

So the question is not really how the disk drives are reliable - but how the original operating environment is reliable?

If you now move the disks to a different system and perform (for example) the destructive Disk menu -> Surface test -> Reinitialise disk surface test, I suspect it may completely repair problems and disk drives may work without any issues.

If you keep these drives in the same operating environment then even if now the problems repaired, you may expect further issues too, causing the false assumption that the problem is related to the disk drive.

And if you'd replace these drives and place different drives in the same environment - then there is good chance that you'll see similar with the new drives too....

So the question may be not really (or not only) related to the reliabilty of the hard disks - but the reliability of the complete storage subsystem.


> Is it possible to automatically save a full log of the repair process?
> The message said ~600 errors had been fixed and I tried to save the log but it doesn't seem to be in the HDS directory.

Yes of course: please enable Configuration -> Advanced options -> Automatically save disk test results to folder
option. Then all test results (reports, complete details, surface map images, performance/temperature graphs etc.) will be automatically saved after each completed tests.
Also you can manually save test results in the surface test window and also you can select the text on the bottom below the disk surface map (showing the actual problems) by CTRL+A and then CTRL+C to copy to clipboard which you can then paste to text file, word document etc. and save if required.


> And thank you for creating such awesome software. It's been really helpful so far.

Thanks so much for your kind words

[Piers]

Thank you again for an in-depth reply.

As the page
https://www.hdsentinel.com/hard_disk_ca ... ectors.php
(suggested in the text description when weak sectors detected) mentions, in most cases the weak sectors are not really related to disk drives: in most cases, something else (cables, connections, power source, etc..) are in the background, resulting weak sectors. In RAID configuration, even the backplane/enclosure/expander can be the problem. Or "just" a minor incompatibility between the controller driver/firmware and the drives, so a driver/firmware update may also help.

I have checked the other 22 disks on the backplane (some much older) and found no issues. It's a Supermicro chassis with an LSI HBA card - quite a simple setup - and is only four years old (bought new).

If two drives produce similar issue at the same time - then it is also very suspicious and can confirm that the issues may be not really related to the hard disk drives.

I've googled and found mixed results with that specific model of drive (N1), but it's an oddity for sure. I've moved all data off both drives and am now running the Disk -> Surface Test -> Reinitialise disk surface on both drives at the same time

So the question is not really how the disk drives are reliable - but how the original operating environment is reliable?

As I've only experienced one drive failure (7-year-old ST3000DM001 which was infamous for failures) in four years of 24/7 use, I do find it odd.

If you now move the disks to a different system and perform (for example) the destructive Disk menu -> Surface test -> Reinitialise disk surface test, I suspect it may completely repair problems and disk drives may work without any issues.

Would moving them to a different port on the backplane suffice? Moving them to another system is not an option at the moment.

If you keep these drives in the same operating environment then even if now the problems repaired, you may expect further issues too, causing the false assumption that the problem is related to the disk drive.

But would you not expect to see errors in the other 21 drives in the system if the environment were the cause?

[Piers]

A drive randomly disconnected itself mid-transfer (from a command issued by Windows), so I think there is something else going on. Windows Event Viewer shows:

Code: Select all

Under Errors

22,344 * ID  15
---
"The device, \Device\Harddisk5\DR23, is not ready for access yet."
and 
"The device, \Device\Harddisk5\DR5, is not ready for access yet."
and
"The device, \Device\Harddisk19\DR19, is not ready for access yet."
and
"The device, \Device\Harddisk20\DR20, is not ready for access yet."
and
"The device, \Device\Harddisk18\DR18, is not ready for access yet."
and
"The device, \Device\Harddisk19\DR26, is not ready for access yet."
and
"The device, \Device\Harddisk5\DR5, is not ready for access yet."
and
"The device, \Device\Harddisk5\DR23, is not ready for access yet."

Most of these errors seem to be "The device, \Device\Harddisk5\DR5, is not ready for access yet."

Although I have not checked all 22k reports, no other paths seems to show.

Under Warnings:

1* ID 50
---
"{Delayed Write Failed} Windows was unable to save all the data for the file K:\X... The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere."

4* ID 129
---
"Reset to device, \Device\RaidPort0, was issued."
- Source: LSI_SAS3i

4* ID 140
---
"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: K:, DeviceName: \Device\HarddiskVolume49.
(STATUS_DEVICE_NOT_CONNECTED)"
- Source: Ntfs (Microsoft-Windows-Nfts)

7* ID 141
---"{Delayed Write Failed} Windows was unable to save all the data for the file K:\; the data has been lost. This error may be caused if the device has been removed or the media is write-protected."
- Source: Ntfs (Ntfs)
Note: In this instance the device was removed by the ID 129 (Reset to device being issued)

25* ID 153
---
"The IO operation at logical block address 0x0 for Disk 11 (PDO name: \Device\000000f6) was retried."
- Source: disk

11* ID 157
---
"Disk 5 has been surprise removed."
- Source: disk

Notes: Impacts disks (in desc. order): 5, 18, 0, 13, 18, 20, 19, 11, 6, 5
I have never removed a disk when the system is powered on.

Hardware is four years or less old and was brand new. Guess backplane could an issue, maybe HBA card, maybe even PSU.

[hdsentinel]

> Would moving them to a different port on the backplane suffice? Moving them to another system is not an option at the moment.

Maybe but not sure....
It is possible that if the port was not used for years then it may not provide good contact, so yes, maybe you can try in a different port.
It is possible that the controller firmware and/or the enclosure is not 100% compatible with a particular model (or firmware). This is why it may be better to verify in a completely different system, just to be sure.

> But would you not expect to see errors in the other 21 drives in the system if the environment were the cause?

Not for sure: some drives are more sensitive so it may be related to the drive model / firmware (and if two drives of the same model/firmware works similarly, it may also confirm the situation).

[hdsentinel]

Yes... This is not surprising: generally this also shows that there is a problem now by accessing the disk drive.

But still not 100% sure if the issue is caused by the drive itself or something else which caused that the drive is no longer connected, just like if you'd disconnect it.

You may attempt to re-connect to a different port on the backplane, but ideally the drive should be tested in a different PC. If you experience same there, then you can be sure that the issue is caused by the drive. If not - then there can be a compatibility issue between the disk and the enclosure/controller, as one of them may not 100% work properly with this hard disk model/firmware.

Yes, interesting situation and may hard to diagnose and find the problem for sure....