HGST 8TB SAS HUH728080AL5200

curley

New Member
May 3, 2020
5
4
3
What capacity are you guys seeing after format? I tried both 4k and 512 but the drive is still showing as 7.15TB in TrueNAS.

This is the diskinfo
Code:
        512             # sectorsize
        7865536647168   # mediasize in bytes (7.2T)
        15362376264     # mediasize in sectors
        4096            # stripesize
        0               # stripeoffset
        956263          # Cylinders according to firmware.
        255             # Heads according to firmware.
        63              # Sectors according to firmware.
        HGST H7280A520SUN8.0T   # Disk descr.
        001703PXB1WV        VLKXB1WV    # Disk ident.
        id1,enc@n5001c45000957abd/type@0/slot@3/elmdesc@Slot_002        # Physical path
        No              # TRIM/UNMAP support
        7200            # Rotation rate in RPM
        Not_Zoned       # Zone Mode
Versus the 8TB I currently have in the vdev.
Code:
        512             # sectorsize
        8001563222016   # mediasize in bytes (7.3T)
        15628053168     # mediasize in sectors
        4096            # stripesize
        0               # stripeoffset
        972801          # Cylinders according to firmware.
        255             # Heads according to firmware.
        63              # Sectors according to firmware.
        ATA WDC WD80EMAZ-00W    # Disk descr.
        7HK49B3F                # Disk ident.
        id1,enc@n5001c45000957abd/type@0/slot@4/elmdesc@Slot_003        # Physical path
        No              # TRIM/UNMAP support
        5400            # Rotation rate in RPM
        Not_Zoned       # Zone Mode
Mine show 7.28TB in the Freenas 11.3 GUI after it was added to a pool. I did notice that same thing and the size of 7.15TB did not change until I put the disk into a pool. The first one I used, I created a dummy pool with one disk and after it was created the GUI updated to the correct size of 7.28TB.

This is what is says now.
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
 
  • Like
Reactions: Samir

eroji

Active Member
Dec 1, 2015
268
44
28
37
Mine show 7.28TB in the Freenas 11.3 GUI after it was added to a pool. I did notice that same thing and the size of 7.15TB did not change until I put the disk into a pool. The first one I used, I created a dummy pool with one disk and after it was created the GUI updated to the correct size of 7.28TB.

This is what is says now.
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
Interesting. I'll try pulling the drive and re-insert it again to see if it sees the extra space. Unfortunately I started another format with added flag so I need to wait for that to finish first.
 
  • Like
Reactions: Samir

SirCrest

New Member
Sep 5, 2016
18
20
3
30
Florida
You do need to power cycle the disk for the new sector size to be reported. Usually just unplugging and replugging works.

@Samir

I did end up formatting back to 512 logical sectors and the space went back down. I'm not sure what the exact situation is with this though.


=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: H7280A520SUN8.0T
Revision: PD51
Compliance: SPC-4
User Capacity: 7,865,536,647,168 bytes [7.86 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: 0x5000cca23bad86b0
Serial number: 001551P2EEBV 2EK2EEBV
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Wed Sep 23 14:10:45 2020 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled

2020-09-23 14_12_37.png
 
  • Like
Reactions: Samir and UhClem

UhClem

Member
Jun 26, 2012
55
22
8
NH, USA
... I did end up formatting back to 512 logical sectors and the space went back down. I'm not sure what the exact situation is with this though.

=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: H7280A520SUN8.0T
Revision: PD51
Compliance: SPC-4
User Capacity: 7,865,536,647,168 bytes [7.86 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is fully provisioned
...
Thanks very much for your effort. While it's disappointing that it didn't result in 8.0TB @ 512e, at least (for my situation), it doesn't get "stuck" @4Kn. Given this, I'll probably format one drive @4Kn just to play/experiment with for a while (never had a 4Kn drive).

P.S. There's more of these available [as of 23Sep20;3pm et] - @OP link
 
  • Like
Reactions: Samir

SirCrest

New Member
Sep 5, 2016
18
20
3
30
Florida
These disks appear to be from SUN/Oracle. I wonder if the firmware is automatically applying some sort of internal 520b when formatted to 512e since the user-space is the same as before but the drive doesn't specify the protection it did before. Meanwhile on 4Kn it doesn't bother with it.
 
  • Like
Reactions: Samir and Fritz

eroji

Active Member
Dec 1, 2015
268
44
28
37
I pulled the formatted disk and plugged it back, but it still didn't show the increase capacity. I also tried creating a dummy pool with the single disk after. That didn't change the size too. Is there something else I can try?

I used the following command for the formatting
Code:
sg_format --format --size=512 --six -v /dev/da10
 
Last edited:
  • Like
Reactions: Samir

wildpig1234

Well-Known Member
Aug 22, 2016
1,833
273
83
45
I am using used enterprise 4TB as direct download/storage save to back up. it would be nice to have 8TB. but the cost is still high. the 4TB i use is only 30-35$. When these 8TB enterprisse hdd gets to $60 or less then i can buy them. I usually buy in packs of 10
 
  • Like
Reactions: Samir

SpamMeDeeper

New Member
Mar 19, 2019
13
3
3
So I finally got around to putting my 8TB drives into my test box to zero test for defect. As promised, sharing some data for those thinking of getting some (if they come back in stock).

These are for sure Sun/Oracle drives. My white labels were all sanded (?) to remove branding. I ordered two different times, 3 in one order, 2 in another for a total of 5. All seem pretty healthy and working. In my server they all show 7.86TB formatted as 512E.

Here are the stats on the drives:

Dec 2015
Start Stop Cycle: 9
Power on Hours: 37380

Aug 2016
Start Stop Cycle: 40
Power on Hours: 31103

Dec 2015
Start Stop Cycle: 8
Power on Hours: 37254

June 2015
Start Stop Cycle: 12
Power on Hours: 7318

Dec 2015
Start Stop Cycle: 9
Power on Hours: 37377

Let me know if there is anything else you'd like me to check. Thanks again to OP for finding this deal.
 
  • Like
Reactions: Samir and Fritz

wildpig1234

Well-Known Member
Aug 22, 2016
1,833
273
83
45
what's the read/write amount?
So I finally got around to putting my 8TB drives into my test box to zero test for defect. As promised, sharing some data for those thinking of getting some (if they come back in stock).

These are for sure Sun/Oracle drives. My white labels were all sanded (?) to remove branding. I ordered two different times, 3 in one order, 2 in another for a total of 5. All seem pretty healthy and working. In my server they all show 7.86TB formatted as 512E.


Let me know if there is anything else you'd like me to check. Thanks again to OP for finding this deal.
What's the read/write amount?
 
  • Like
Reactions: Samir

SirCrest

New Member
Sep 5, 2016
18
20
3
30
Florida
Well all done migrating to the new disks. My drive's 'smartctl -a' if desired.


Code:
Manufactured in week 26 of year 2015
Accumulated start-stop cycles:  12
Accumulated load-unload cycles:  313

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     176040       5977.421           0
write:         0        0         0         0    1364022     128887.688           0
verify:        0        0         0         0       7578          0.000           0
Code:
Manufactured in week 51 of year 2015
Accumulated start-stop cycles:  17
Accumulated load-unload cycles:  1560

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       39         0        39    7371366     150309.296           0
write:         0       62         0        62     841089     123965.939           0
verify:        0        0         0         0     106626          0.000           0
Code:
Manufactured in week 51 of year 2015
Accumulated start-stop cycles:  10
Accumulated load-unload cycles:  1552


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       29         0        29    7371937     152101.744           0
write:         0        5         0         5     479184     114649.799           0
verify:        0        0         0         0      56600          0.000           0

Code:
Manufactured in week 51 of year 2015
Accumulated start-stop cycles:  11
Accumulated load-unload cycles:  1547

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    5186598      98493.252           0
write:         0       10         0        10     991276      88677.738           0
verify:        0        0         0         0      92551          0.000           0
Code:
Manufactured in week 51 of year 2015
Accumulated start-stop cycles:  8
Accumulated load-unload cycles:  1540

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        4         0         4    7285046     154879.286           0
write:         0        2         0         2    1501589     108864.267           0
verify:        0        0         0         0     171915          0.000           0

Code:
Manufactured in week 51 of year 2015
Accumulated start-stop cycles:  10
Accumulated load-unload cycles:  1544

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        1         0         1    5011479     104911.920           0
write:         0        0         0         0     502271      84959.130           0
verify:        0        0         0         0      27625          0.000           0
Code:
Manufactured in week 21 of year 2017
Accumulated start-stop cycles:  49
Accumulated load-unload cycles:  180

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      36300      60908.270           0
write:         0        1         0         1     383963      96660.315           0
verify:        0        0         0         0       2715          7.805           0
Code:
Manufactured in week 51 of year 2015
Accumulated start-stop cycles:  8
Accumulated load-unload cycles:  1542

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        1         0         1    7219733     159783.264           0
write:         0        0         0         0     536599     106770.321           0
verify:        0        0         0         0      29311          0.000           0
Considering what these drives could go through, I think they look fine. I'm on ZFS so they work great. Some look to be in the 160TB read range. And considering they're probably rated for 180TB atleast per year, not bad.
 
Last edited:

wildpig1234

Well-Known Member
Aug 22, 2016
1,833
273
83
45
Considering what these drives could go through, I think they look fine. I'm on ZFS so they work great. Some look to be in the 160TB read range. And considering they're probably rated for 180TB atleast per year, not bad.
As long as you don't have anything super important on them.

are you using them as a direct to storage/back up to file away immediately once drive is filled or are you using them in a regular manner?
 

SpamMeDeeper

New Member
Mar 19, 2019
13
3
3
what's the read/write amount?


What's the read/write amount?
Updated with Read/Writes for the five drives I have:

Dec 2015
Start Stop Cycle: 9
Power on Hours: 37380
Read Processed: 163.4TB
Write Processed: 118.5TB


Aug 2016
Start Stop Cycle: 40
Power on Hours: 31103
Read Processed: 357.6TB
Write Processed: 124.6TB

Dec 2015
Start Stop Cycle: 8
Power on Hours: 37254
Read Processed: 119.2TB
Write Processed: 91.8TB

June 2015
Start Stop Cycle: 12
Power on Hours: 7318
Read Processed: 22.2TB
Write Processed: 149.9TB

Dec 2015
Start Stop Cycle: 9
Power on Hours: 37377
Read Processed: 114.7TB
Write Processed: 96.7TB

Also back in stock!
 

JoshDi

Active Member
Jun 13, 2019
158
53
28
This is very tempting.... I probably should go to sleep instead of buying 10 of theses to replace my 3tb WD red array....
 

SpamMeDeeper

New Member
Mar 19, 2019
13
3
3
I pulled the formatted disk and plugged it back, but it still didn't show the increase capacity. I also tried creating a dummy pool with the single disk after. That didn't change the size too. Is there something else I can try?

I used the following command for the formatting
Code:
sg_format --format --size=512 --six -v /dev/da10
Did you ever get 512 to show full 8TB? I'd prefer to stick with 512 so I can move drives around between FreeNAS and other boxes, but will format as 4K if needed. TIA.
 

eroji

Active Member
Dec 1, 2015
268
44
28
37
Did you ever get 512 to show full 8TB? I'd prefer to stick with 512 so I can move drives around between FreeNAS and other boxes, but will format as 4K if needed. TIA.
Nope. None of the steps mentioned works. I just settled with the slightly lower size.
 

Iaroslav

Member
Aug 23, 2017
84
17
8
34
Kyiv
Some misfortune maybe, but I've got 3 of 10 drives with defects (thus not even formatting) or not spinning up at all. Waiting for a reply from the seller.
UPD - the seller was kind to accept a return, so the case is clear, the rest of the disks are ok under the regular write load now.
UPD2 for one guy who doesn't believe, just two screens, as the third one was clicking endlessly during startup
 

Attachments

Last edited:

mmbtrumpet

New Member
May 20, 2020
1
1
3
I bought some of these before from a different seller. The first batch I got had a serial number that were 0015* and the second batch were 0017*. The first batch had protection turned on and the second batch did not. The first batch I had to reformat to remove the protection and the use the resize command, the second batch I was able to just run the resize command.

To reformat the drives.
sg_format --format --fmtpinfo=0 /dev/sXX

To resize the drives.
sg_format --resize --count=-1 /dev/sXX
 
  • Like
Reactions: SirCrest