Super Cheap Hitachi UltraStar C10k600 450GB 2.5" TCG Encryption Hard Drives

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

Evan

Well-Known Member
Jan 6, 2016
3,344
599
113
2.5 years old they still have that life again on them before you should see any significant increase of failures. Remember they are enterprise drives you would assuming in a environmental and power controller DC which is going to make it better than used random retail type drives.
 

ttabbal

Active Member
Mar 10, 2016
753
209
43
47
I tested the adapter. The one I printed, the newer version, doesn't quite work for the exact reason mentioned. The plastic on the side pushes the drive just a little too far. I cut it off as a quick and dirty hack, it worked. The drive is detected by the system and it mounts nicely. I'm printing the older version now, to see if it's a better starting point, but it takes about 40min to print. For some reason, the filename on thingiverse is "polysoup.stl".

Evan, thanks for the info on longevity. That was my suspicion, but I'm not as familiar with enterprise drives. I'm used to consumer level, might as well mount it to a degausser, type drives. :)

Update: The polysoup.stl file does work better. There's not much holding the drive on the connector side, as the holes in the sled don't line up with the 2.5" drive. Not much to be done about that. I'll post a pic over in the DIY forum as we are kind of hijacking this one. :)
 
Last edited:

Patrick

Administrator
Staff member
Dec 21, 2010
12,521
5,840
113
Seems like we have a good discussion for the DIY forum.
 

nthu9280

Well-Known Member
Feb 3, 2016
1,629
503
113
San Antonio, TX
Are folks getting the drives with netapp trays/caddies? Thought I made the offer for the listing that said no trays. No biggie other than it will take couple of hours to swap out all the drives into my intel trays and I don't have a use for the netapp ones.

Sent from my Nexus 6 using Tapatalk
 

J Hart

Active Member
Apr 23, 2015
145
100
43
44
What kind of data shows up with this "-x"? Coul you please post output of one of your disks?


Do you really print the adapters? Never thought about that...perhaps I should check if can get access to a printer... Would you share your printing draft? :)

EDIT: Did anybody try to flash untouched HGST firmware on these?
Sorry forgot to post this. Here is a drive I picked at random.

Code:
sudo smartctl -x /dev/sdd
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-21-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HITACHI
Product:              HUC106045CSS601
Revision:             MS03
Compliance:           SPC-4
User Capacity:        450,098,159,616 bytes [450 GB]
Logical block size:   512 bytes
Formatted with type 2 protection
Rotation Rate:        10020 rpm
Form Factor:          2.5 inches
Logical Unit id:      0x5000cca025a82b18
Serial number:        PRJZH2PB
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Wed Apr 27 13:55:19 2016 PDT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled
Read Cache is:        Enabled
Writeback Cache is:   Disabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     30 C
Drive Trip Temperature:        55 C

Manufactured in week 21 of year 2012
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  10
Specified load-unload count over device lifetime:  300000
Accumulated load-unload cycles:  159
Elements in grown defect list: 0

Vendor (Seagate) cache information
  Blocks sent to initiator = 1674373253562368

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:   445635372   443487         0  446078859     826090      60276.911           0
write:         0     1481         0      1481     140379      10068.726           0
verify:    35343        3         0     35346       1232          0.000           0

Non-medium error count:        0

No self-tests have been logged

Background scan results log
  Status: waiting until BMS interval timer expires
    Accumulated power on time, hours:minutes 22686:20 [1361180 minutes]
    Number of background scans performed: 121,  scan progress: 0.00%
    Number of background medium scans performed: 121

Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 2
  number of phys = 1
  phy identifier = 0
    attached device type: SAS or SATA device
    attached reason: unknown
    reason: unknown
    negotiated logical link rate: phy enabled; 6 Gbps
    attached initiator port: ssp=1 stp=1 smp=1
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca025a82b19
    attached SAS address = 0x590b11c035bedf02
    attached phy identifier = 3
    Invalid DWORD count = 17
    Running disparity error count = 17
    Loss of DWORD synchronization = 5
    Phy reset problem = 0
    Phy event descriptors:
     Invalid word count: 17
     Running disparity error count: 17
     Loss of dword synchronization count: 5
     Phy reset problem count: 0
relative target port id = 2
  generation code = 2
  number of phys = 1
  phy identifier = 1
    attached device type: no device attached
    attached reason: unknown
    reason: power on
    negotiated logical link rate: phy enabled; unknown
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca025a82b1a
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization = 0
    Phy reset problem = 0
    Phy event descriptors:
     Invalid word count: 0
     Running disparity error count: 0
     Loss of dword synchronization count: 0
     Phy reset problem count: 0
 

ttabbal

Active Member
Mar 10, 2016
753
209
43
47
Interesting.. Being less well versed in enterprise drives, are those error counts typical? I don't think consumer drives report that, or I just haven't done a "-x" in a while. :)
 

J Hart

Active Member
Apr 23, 2015
145
100
43
44
Interesting.. Being less well versed in enterprise drives, are those error counts typical? I don't think consumer drives report that, or I just haven't done a "-x" in a while. :)
I'm not sure what the deal is with those errors exactly. I suspect I did it. I think when the drives were complaining about data integrity flag errors from the 512/520 byte mismatch it logged all of those. The numbers have not increased since I have started using the drives.
 

nthu9280

Well-Known Member
Feb 3, 2016
1,629
503
113
San Antonio, TX
Got mine in and I had one hell of a time getting these running. Somehow the drives were reporting to the linux kernel that they were 512 sectors, but that data integrity was on(520 sectors). This led to lots of fun I/O errors. I ended up reformatting them using
Code:
sg_format -F --fmtpinfo=3 --pfu=0
which worked after rebooting. You can format a bunch of these by using the "-e" flag which will exit after issuing the command and allow you to format them all in parallel. It took about 2 hours to format them.
What is the --fmtpinfo=3 option for?
--pfu=0 appears to be to be default.

I noticed it after I initiated the format with the following options
sg_format --format --size=512 -e /dev/sg<xx>
 

whitey

Moderator
Jun 30, 2014
2,766
868
113
41
4 disk raid-10 btrfs = 250iops haha, right where it should be but I laugh as it REALLY does make you appreciate SSD's. Clone of a 30GB VM is taking FOREVER heh
 

Emulsifide

Active Member
Dec 1, 2014
212
93
28
Interesting.. Being less well versed in enterprise drives, are those error counts typical? I don't think consumer drives report that, or I just haven't done a "-x" in a while. :)
All hard drives have errors that are corrected constantly. When they're non-correctable is when you know your hard drive is going bad.
 
  • Like
Reactions: Sleyk

J Hart

Active Member
Apr 23, 2015
145
100
43
44
What is the --fmtpinfo=3 option for?
--pfu=0 appears to be to be default.

I noticed it after I initiated the format with the following options
sg_format --format --size=512 -e /dev/sg<xx>
It turns on the data integrity checking. The whole storage system will check checksums including the OS, controller and drive. These drives support it so I thought I'd turn it on. You can also do it completely off by setting it to 0 (which is the default).
 

Xamayon

New Member
Jan 7, 2016
25
14
3
Anyone tried these on a RAID controller yet?
I have been using mine on two cards, a super old LSI Megaraid 8888elp with a supermicro SAS2 expander (overkill, I know), and with a 9271-8i also with SAS2 expander.

They have been working great so far on both as far as I can tell. No modifications or sg_format-ting needed. One nice thing is that they apparently support the T10 data protection 512+8bit sector stuff, which the newer 92xx+ LSI cards support. Have been testing that out on one system, and have not had it bite me yet. ;)

Mine were also delivered with the caddies, even thought the listing said they were excluded. Those netapp caddies sure are beefy. Near-unlimited budgets sure do result in some nice stuff...
 
  • Like
Reactions: Emulsifide

svt3391

Member
Feb 11, 2016
113
17
18
Mine were also delivered with the caddies, even thought the listing said they were excluded. Those netapp caddies sure are beefy. Near-unlimited budgets sure do result in some nice stuff...
I wonder if that would add on overall weight and hence increase the shipping cost? Without the caddies the weight could be shaved in half.
 

Boddy

Active Member
Oct 25, 2014
772
144
43
I wonder if that would add on overall weight and hence increase the shipping cost? Without the caddies the weight could be shaved in half.
I expect weight and size would be factors in shipping cost.
Shipito has a calculator on their website.
 

nthu9280

Well-Known Member
Feb 3, 2016
1,629
503
113
San Antonio, TX
Just accepted my offer. So will be getting a bunch of these in as well.

These are from the Hitachi C10K600 line. Models;
Code:
HUC106060CSS600
HUC106060CSS601
HUC106045CSS600
HUC106045CSS601
HUC106030CSS600
HUC106030CSS601
In the PDF you can see what systems these came in. Bunch of Dell R series and ProLiant.
Dell has firmware listed for 300 and 600GB models HERE. And the firmware update tool as posted earlier.
No idea if the firmware would also work on the 450GB models though, or if it will even be possible.

Perhaps one of the other compatible systems will have the firmware for a 450GB model listed. However something tells me they won't be.

I'll have a few spares so thinking about giving it a try. What's the worst that could happen? Brick them? Does anyone know if we have access to the firmware that is currently on them?

Dell has an updated firmware than the one I posted earlier. These are Cobra-D and their FW A440.
Dell Nautilus Firmware Update Utility for SAS and SATA Disk and Solid State Drive - *PLEASE SEE RELEASE_NOTES.TXT FILE FOR A LIST OF DRIVES THIS UPDATE APPLIES TO* Driver Details | Dell US
However, the EFI tool did not see any of the drives. Not sure if it's looking for Dell system
Has anyone tried /successful in updating the FW on these?
 

Fritz

Well-Known Member
Apr 6, 2015
3,444
1,447
113
70
If you don't mind me asking, what are you guys using these low capacity drives for?
 

nthu9280

Well-Known Member
Feb 3, 2016
1,629
503
113
San Antonio, TX
Just for grins, I also tried the HP firmware linked on this thread using a live CentOS7. Needed to install couple of libraries to get the executable work. It also didn't find compatible drives to update.
 

Xamayon

New Member
Jan 7, 2016
25
14
3
If you don't mind me asking, what are you guys using these low capacity drives for?
I for one am using them in systems which have 'too many' hot swap bays. I tend to buy 24 or more bay chassis, and most systems don't actually need that many. Super cheap, but high quality small disks in raid 10 should hopefully provide the kind of performance and reliability I need for the random systems I use. In the event any one system needs more storage in the future, and runs out of bays, LSI controllers at least make replacing with higher capacity disks very easy.