HGST 6TB SAS Hard Drive $90 or cheaper ->$50;) - Sold Out -

Discussion in 'Great Deals' started by Rand__, Jun 21, 2019.

  1. Rand__

    Rand__ Well-Known Member

    Joined:
    Mar 6, 2014
    Messages:
    3,542
    Likes Received:
    526
    Have not found anything wrt drive trip temperature, but if it's the max acceptable then it should be identical on all drives @MortenB
     
    #81
  2. MortenB

    MortenB Member

    Joined:
    Jul 3, 2017
    Messages:
    63
    Likes Received:
    19
    Yes, they all say 85C so I assume thats the max value it can handle..

    Running Extended SMART test on 4 drives now with HD Sentinel.
     
    #82
  3. Rand__

    Rand__ Well-Known Member

    Joined:
    Mar 6, 2014
    Messages:
    3,542
    Likes Received:
    526
    Ok, will check when i get mine... Saturday or so...
     
    #83
  4. Psycho_Robotico

    Joined:
    Nov 23, 2014
    Messages:
    31
    Likes Received:
    11
    Some of my disks won't show up properly, i.e. can be seen but not used.
    The first drive listed below is an example of this issue, while the second one works without any issues.

    Code:
    sudo smartctl -T permissive -a /dev/disk/by-id/scsi-35000cca2715bbc8c
    smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-54-generic] (local build)
    Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Vendor:               HGST
    Product:              HUS726060AL5215
    Revision:             DDD5
    Compliance:           SPC-4
    LU is fully provisioned
    Rotation Rate:        7200 rpm
    Form Factor:          3.5 inches
    Logical Unit id:      0x5000cca2715bbc8c
    Serial number:        K8HMG07D
    Device type:          disk
    Transport protocol:   SAS (SPL-3)
    Local Time is:        Sat Jul  6 19:23:26 2019 CEST
    device is NOT READY (e.g. spun down, busy)
    SMART support is:     Available - device has SMART capability.
    SMART support is:     Enabled
    Temperature Warning:  Enabled
    
    === START OF READ SMART DATA SECTION ===
    SMART Health Status: OK
    Current Drive Temperature:     0 C
    Drive Trip Temperature:        0 C
    
    Error Counter logging not supported
    
    Device does not support Self Test logging
    
    Code:
    sudo smartctl -T permissive -a /dev/disk/by-id/scsi-35000cca2715bbce8
    smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-54-generic] (local build)
    Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Vendor:               HGST
    Product:              HUS726060AL5215
    Revision:             DDD5
    Compliance:           SPC-4
    User Capacity:        6.001.175.126.016 bytes [6,00 TB]
    Logical block size:   512 bytes
    Physical block size:  4096 bytes
    LU is fully provisioned
    Rotation Rate:        7200 rpm
    Form Factor:          3.5 inches
    Logical Unit id:      0x5000cca2715bbce8
    Serial number:        K8HMG0ZD
    Device type:          disk
    Transport protocol:   SAS (SPL-3)
    Local Time is:        Sat Jul  6 19:23:29 2019 CEST
    SMART support is:     Available - device has SMART capability.
    SMART support is:     Enabled
    Temperature Warning:  Enabled
    
    === START OF READ SMART DATA SECTION ===
    SMART Health Status: OK
    
    Current Drive Temperature:     34 C
    Drive Trip Temperature:        85 C
    
    Manufactured in week 28 of year 2018
    Specified cycle count over device lifetime:  50000
    Accumulated start-stop cycles:  4
    Specified load-unload count over device lifetime:  600000
    Accumulated load-unload cycles:  7
    Elements in grown defect list: 0
    
    Vendor (Seagate) cache information
      Blocks sent to initiator = 7815666073600
    
    Error counter log:
               Errors Corrected by           Total   Correction     Gigabytes    Total
                   ECC          rereads/    errors   algorithm      processed    uncorrected
               fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
    read:          0        0         0         0      33806       1268,729           0
    write:         0        4         0         4        755      12192,487           0
    verify:        0        0         0         0        888          0,000           0
    
    Non-medium error count:        0
    
    No self-tests have been logged
    

    Maybe it has some strange formatting of sectors as used be e.g. EMC? At least that's what I suspect after checking dmesg:
    Code:
    [    2.836460] sd 0:0:32:0: [sdaf] Spinning up disk...
    [  103.196662] sd 0:0:32:0: [sdaf] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  103.196664] sd 0:0:32:0: [sdaf] Sense Key : Not Ready [current] [descriptor]
    [  103.196665] sd 0:0:32:0: [sdaf] Add. Sense: Logical unit not ready, initializing command required
    [  103.197229] sd 0:0:32:0: [sdaf] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  103.197231] sd 0:0:32:0: [sdaf] Sense Key : Not Ready [current] [descriptor]
    [  103.197232] sd 0:0:32:0: [sdaf] Add. Sense: Logical unit not ready, initializing command required
    [  103.197604] sd 0:0:32:0: [sdaf] 0 512-byte logical blocks: (0 B/0 B)
    [  103.197605] sd 0:0:32:0: [sdaf] 0-byte physical blocks
    [  103.197920] sd 0:0:32:0: [sdaf] Write Protect is off
    [  103.197922] sd 0:0:32:0: [sdaf] Mode Sense: f7 00 10 08
    [  103.198405] sd 0:0:32:0: [sdaf] Write cache: disabled, read cache: enabled, supports DPO and FUA
    [  103.199982] sd 0:0:32:0: [sdaf] Spinning up disk...
    [  203.583716] sd 0:0:32:0: [sdaf] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  203.583718] sd 0:0:32:0: [sdaf] Sense Key : Not Ready [current] [descriptor]
    [  203.583720] sd 0:0:32:0: [sdaf] Add. Sense: Logical unit not ready, initializing command required
    [  203.584280] sd 0:0:32:0: [sdaf] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  203.584282] sd 0:0:32:0: [sdaf] Sense Key : Not Ready [current] [descriptor]
    [  203.584283] sd 0:0:32:0: [sdaf] Add. Sense: Logical unit not ready, initializing command required
    [  203.586138] sd 0:0:32:0: [sdaf] Attached SCSI disk
    [  398.872800] sd 0:0:32:0: [sdaf] Spinning up disk...
    [  499.209677] sd 0:0:32:0: [sdaf] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  499.209680] sd 0:0:32:0: [sdaf] Sense Key : Not Ready [current] [descriptor]
    [  499.209682] sd 0:0:32:0: [sdaf] Add. Sense: Logical unit not ready, initializing command required
    [  499.210245] sd 0:0:32:0: [sdaf] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  499.210246] sd 0:0:32:0: [sdaf] Sense Key : Not Ready [current] [descriptor]
    [  499.210248] sd 0:0:32:0: [sdaf] Add. Sense: Logical unit not ready, initializing command required
    [  612.449703] sd 0:0:32:0: [sdaf] Spinning up disk...
    [  712.786398] sd 0:0:32:0: [sdaf] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  712.786417] sd 0:0:32:0: [sdaf] Sense Key : Not Ready [current] [descriptor]
    [  712.786420] sd 0:0:32:0: [sdaf] Add. Sense: Logical unit not ready, initializing command required
    [  712.787010] sd 0:0:32:0: [sdaf] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  712.787014] sd 0:0:32:0: [sdaf] Sense Key : Not Ready [current] [descriptor]
    [  712.787017] sd 0:0:32:0: [sdaf] Add. Sense: Logical unit not ready, initializing command required
    
    Anyone here got the same issue or even a solution?
     
    #84
    Samir likes this.
  5. Rand__

    Rand__ Well-Known Member

    Joined:
    Mar 6, 2014
    Messages:
    3,542
    Likes Received:
    526
    I have 2 with the same issue.
    I don't think that these were used any differently than the other drives, so for now I have contacted the seller to provide a solution or further debugging guidelines. O/c have not heard back but we will see what they come up with :)
     
    #85
    Samir and Psycho_Robotico like this.
  6. Psycho_Robotico

    Joined:
    Nov 23, 2014
    Messages:
    31
    Likes Received:
    11
    Good to know I'm not the only one affected :)

    sg_format doesn't seem to help:

    Code:
    sudo sg_format --format --size=512 --six -v /dev/sg4
        HGST      HUS726060AL5215   DDD5   peripheral_type: disk [0x0]
          PROTECT=1
          << supports protection information>>
          Unit serial number:         K8HMEWYD
          LU name: 5000cca2715bbaf4
        mode sense (6) cdb: 1a 00 01 00 fc 00
    Mode Sense (block descriptor) data, prior to changes:
    Mode sense number of blocks maxed out, set longlba
        mode sense (10) cdb: 5a 10 01 00 00 00 00 00 fc 00
    Mode Sense (block descriptor) data, prior to changes:
      <<< longlba flag set (64 bit lba) >>>
      Number of blocks=11721045168 [0x2baa0f4b0]
      Block size=512 [0x200]
    
    A FORMAT UNIT will commence in 15 seconds
        ALL data on /dev/sg4 will be DESTROYED
            Press control-C to abort
    
    A FORMAT UNIT will commence in 10 seconds
        ALL data on /dev/sg4 will be DESTROYED
            Press control-C to abort
    
    A FORMAT UNIT will commence in 5 seconds
        ALL data on /dev/sg4 will be DESTROYED
            Press control-C to abort
        format unit cdb: 04 18 00 00 00 00
    format unit:
    Descriptor format, current; Sense key: Not Ready
    Additional sense: Logical unit not ready, initializing command required
      Descriptor type: Information:    >> descriptor too short
        00 00 00 00 00 00 00 00 00 00
      Descriptor type: Command specific: 0x0000000000000000
      Descriptor type: Sense key specific: Progress indication: 0.00%
      Descriptor type: Field replaceable unit code: 0x0
      Descriptor type: Block commands: Incorrect Length Indicator (ILI) clear
      Descriptor type: Vendor specific [0x80]
        f5Format unit command: Not ready sense key
    FORMAT UNIT failed
    
     
    #86
    Samir likes this.
  7. Psycho_Robotico

    Joined:
    Nov 23, 2014
    Messages:
    31
    Likes Received:
    11
    The seller got back to me and is offering a refund, refering to HDD firmware issues. Does anyone know about the process to change the drives' firmware? I'd prefer to have them working instead of getting refunded :)
     
    #87
    Samir likes this.
  8. nephri

    nephri Active Member

    Joined:
    Sep 23, 2015
    Messages:
    498
    Likes Received:
    82
    be careful, i already had issues when formatting disks from 520 to 512 sector size using sg_format !
    Until a reboot, even if report tools said "512" after the format, i was unable to use formatted disks (on freebsd)
    After a reboot, all worked fine
     
    #88
    Samir likes this.
  9. DavidB

    DavidB Member

    Joined:
    Aug 31, 2018
    Messages:
    38
    Likes Received:
    11
    If the vendor does not require you to send them back you may attempt to flash them with original firmware. The disks probably have vendor specific firmware that prevent them from working as normal disks.

    Maybe you'll have more luck with the official HGST utility in identifying what's wrong and if possible flash them back (for example R907 firmware) https://www.westerndigital.com/cont...ssets/support/CheckDriveFitness/WinDFT095.zip

    Recently WD has disabled the HGST website so unfortunately you can't easily download any original HGST firmware anymore
     
    #89
    Samir likes this.
  10. Psycho_Robotico

    Joined:
    Nov 23, 2014
    Messages:
    31
    Likes Received:
    11
    Thanks for the insight! :) Unfortunately sg_format had no effect - at least so far.


    Do you know if there's a linux version of WinDFT? Yesterday I could only find the Windows version, however my headless box is running linux.
    Yeah, since WD started phasing out HGST their documentation went down the drain :(
     
    #90
    Samir likes this.
  11. Rand__

    Rand__ Well-Known Member

    Joined:
    Mar 6, 2014
    Messages:
    3,542
    Likes Received:
    526
    Same here, only that I thankfully got enough drives;)
     
    #91
  12. Psycho_Robotico

    Joined:
    Nov 23, 2014
    Messages:
    31
    Likes Received:
    11
    There is no such thing as enough drives ;) 12 of mine are affected :(
     
    #92
    Samir likes this.
  13. Rand__

    Rand__ Well-Known Member

    Joined:
    Mar 6, 2014
    Messages:
    3,542
    Likes Received:
    526
    Ouch :( Only 2 here
     
    #93
  14. MortenB

    MortenB Member

    Joined:
    Jul 3, 2017
    Messages:
    63
    Likes Received:
    19
    How do you provoke this error? Try to create a partition in Windows Server for example?
    I didnt do that to all my drives, only a few. Rest was checked without partition in HD Sentinel... Maybe I have to recheck..
     
    #94
  15. Rand__

    Rand__ Well-Known Member

    Joined:
    Mar 6, 2014
    Messages:
    3,542
    Likes Received:
    526
    For me it was visible in smart: 'device could not be started/ is not ready'
     
    #95
  16. MortenB

    MortenB Member

    Joined:
    Jul 3, 2017
    Messages:
    63
    Likes Received:
    19
    OK, Will go over mine again now. Reporting back in a bit :p
     
    #96
  17. MortenB

    MortenB Member

    Joined:
    Jul 3, 2017
    Messages:
    63
    Likes Received:
    19
    Seems like mine are working as they should. I did notice 1 or 2 disks that had higher noise than the rest. Anything to worry about?
     
    #97
  18. Rand__

    Rand__ Well-Known Member

    Joined:
    Mar 6, 2014
    Messages:
    3,542
    Likes Received:
    526
    Good for you :)

    Noise - dont think so, but make sure to test them properly and run smart every now and then just in case
     
    #98
  19. nthu9280

    nthu9280 Well-Known Member

    Joined:
    Feb 3, 2016
    Messages:
    1,418
    Likes Received:
    357
    I just got 4 and they tested good with few passes of badblocks using bht script. They were practically new with less than 100 power on hours. Would have preferred 6 months or so usage.
     
    #99
    Samir likes this.
  20. Psycho_Robotico

    Joined:
    Nov 23, 2014
    Messages:
    31
    Likes Received:
    11
    No need to provoke anything - the affected drives simply don't show up using "df" and are listed without any capacity in other tools. Gparted doesn't show them as well, though they are listed in /dev/. These drives simply can't be accessed.
     
    #100
    Samir likes this.

Share This Page