HGST 8TB SAS HUH728080AL5200

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

UhClem

just another Bozo on the bus
Jun 26, 2012
469
279
63
NH, USA
SirCrest said:
Update, just needed to do

sg_format --format --size=4096 /dev/da12

and

=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: H7280A520SUN8.0T
Revision: PD51
Compliance: SPC-4
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
Logical block size: 4096 bytes
LU is fully provisioned
...

I see no reason to use 512e in my use-case since I'm working with 4K ashift anyways.
Click to expand...
Was anyone able to get full capacity (8.0TB [vs 7.86TB]) with 512e format?

I did a
sg_format --format --size=512 /dev/sdX
and (13 hours later) the only change was that the "protection information" was no longer reported. The original (pre- sg_format) smartctl reported:
...
User capacity: 7,865,536,647,168 [7.86TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
>> Formatted with type 1 protection
>> 8 bytes of protection information per logical block
LU is fully provisioned
...
Click to expand...
Following the sg_format, the smartctl report was the same except that the 2 >> lines were absent. [but capacity remained 7.86TB]

I'd really like to get that additional 1.5% capacity (and performance), but unlike @SirCrest , I need to stay 512e.

Thanks!
 
  • Like
Reactions: epicurean and Samir
Fritz

Fritz

Well-Known Member
Apr 6, 2015
3,537
1,495
113
70
I had to format 3 of mine to 4096 to get full capacity. Took a day each.
 
  • Like
Reactions: Samir
S

Samir

Post Liker and Deal Hunter Extraordinaire!
Jul 21, 2017
3,581
1,677
113
49
HSV and SFO
Fritz said:
I had to format 3 of mine to 4096 to get full capacity. Took a day each.
Click to expand...
Do you think formatting them back to 512e would still yield the same capacity? Or do you think it would go back to 7.86 again?
 
U

UhClem

just another Bozo on the bus
Jun 26, 2012
469
279
63
NH, USA
Samir said:
Do you think formatting them back to 512e would still yield the same capacity? Or do you think it would go back to 7.86 again?
Click to expand...
I thought of trying that, but for me, I'm concerned that I might get stuck at 4Kn. And, I want/need 512e (a little) more than I desire the extra space/speed.

If anyone does try that, please report back.
 
  • Like
Reactions: Samir
Fritz

Fritz

Well-Known Member
Apr 6, 2015
3,537
1,495
113
70
UhClem said:
I thought of trying that, but for me, I'm concerned that I might get stuck at 4Kn. And, I want/need 512e (a little) more than I desire the extra space/speed.

If anyone does try that, please report back.
Click to expand...
Why do you need 512e?
 
  • Like
Reactions: Samir
Fritz

Fritz

Well-Known Member
Apr 6, 2015
3,537
1,495
113
70
Samir said:
Do you think formatting them back to 512e would still yield the same capacity? Or do you think it would go back to 7.86 again?
Click to expand...
Don't know but it would take a whole day to find out and 4096 works for me.
 
  • Like
Reactions: Samir
U

UhClem

just another Bozo on the bus
Jun 26, 2012
469
279
63
NH, USA
Fritz said:
Why do you need 512e?
Click to expand...
I often/occasionally make image copies of partitions [between drives] (with dd) and all my other drives are 512e. At that (relatively) low level, I'm pretty sure that the LBA #s need to have the same "geometry" (ie not differ by x8). Anyone have experience that says different?
 
  • Like
Reactions: Samir
Fritz

Fritz

Well-Known Member
Apr 6, 2015
3,537
1,495
113
70
Samir said:
I know if I needed to know I'd be willing to compensate you for your time if you could run the test for me. ;)
Click to expand...
Shoulda asked earlier. At present I'm copying my entire media collection to a spanned volume consisting of all 4 drives. It's 30 percent into the copy so too late now.
 
  • Like
Reactions: Samir
E

epicurean

Active Member
Sep 29, 2014
786
81
28
Using i
UhClem said:
Was anyone able to get full capacity (8.0TB [vs 7.86TB]) with 512e format?

I did a
sg_format --format --size=512 /dev/sdX
and (13 hours later) the only change was that the "protection information" was no longer reported. The original (pre- sg_format) smartctl reported:

Following the sg_format, the smartctl report was the same except that the 2 >> lines were absent. [but capacity remained 7.86TB]

I'd really like to get that additional 1.5% capacity (and performance), but unlike @SirCrest , I need to stay 512e.

Thanks!
Click to expand...
Intending to use my drives for Napp It storage. DO I need to stay 512e or format to 4k?
 
  • Like
Reactions: Samir
S

SirCrest

Member
Sep 5, 2016
21
26
13
34
Texas
If you give me a day or so I can format one of mine back to 512e.

I don't have spare bays right now, so I offlined my ZFS pool replaced a bunch of disks with the new HGST SAS disks to format them in bulk. Then put back in the old disks to resilver one by one. Just finished formatting them all to 4Kn, but now 6 are sitting idle on my desk as I resilver.

I can format one of them to 512e in the meantime to see if it stays at 8TB.
 
  • Like
Reactions: UhClem and Samir
S

Samir

Post Liker and Deal Hunter Extraordinaire!
Jul 21, 2017
3,581
1,677
113
49
HSV and SFO
Fritz said:
Shoulda asked earlier. At present I'm copying my entire media collection to a spanned volume consisting of all 4 drives. It's 30 percent into the copy so too late now.
Click to expand...
All good! How's the transfer rates?
 
E

eroji

Active Member
Dec 1, 2015
280
56
28
41
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
 
  • Like
Reactions: Samir
C

curley

New Member
May 3, 2020
6
6
3
eroji said:
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
Click to expand...
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
E

eroji

Active Member
Dec 1, 2015
280
56
28
41
curley said:
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]
Click to expand...
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
S

SirCrest

Member
Sep 5, 2016
21
26
13
34
Texas
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
You must log in or register to reply here.
Top Bottom