I bought a bunch of the drives in the title and they came with type 2 protection on them and reported 9.93TB in lsscsi/smartctl. I'm using RHEL 8.5, a SAS2308 controller, and a NetApp DS4243
I have dealt with this in the past as discussed in this thread on 8TB sun/oracle HGST drives: https://forums.servethehome.com/ind...ing-as-7-9tb-and-not-8-0tb-like-others.25725/
These are 4Kn drives (says it right on the label), but re-sectoring them to 4096 and disabling type2 using sg_format or HUGO results in the drives continuing to report 9.93TB in smartctl/lsscsi, even after re-powering the drives. The workaround I found was to format to 512E using HUGO fastformat (presumably 512E with sg_format would work too) to get them to report full 10TB.
If anyone has an example of a retail version of this drive (e.g. not sun/netapp/ibm) and has it formatted to be 4Kn, do you have the issue with them reporting 9.93TB?
The workaround does work, but I want to open discussion to see if anyone knows why/how to properly resolve this and keep it set as 4Kn. In my case, the workaround doesn't cause a problem because ashift=12 with zfs will work fine without performance penalty.
HUGO utility in this post https://forums.servethehome.com/ind...t-hgst-he10-and-he12-to-4kn.27668/post-289494
I have dealt with this in the past as discussed in this thread on 8TB sun/oracle HGST drives: https://forums.servethehome.com/ind...ing-as-7-9tb-and-not-8-0tb-like-others.25725/
These are 4Kn drives (says it right on the label), but re-sectoring them to 4096 and disabling type2 using sg_format or HUGO results in the drives continuing to report 9.93TB in smartctl/lsscsi, even after re-powering the drives. The workaround I found was to format to 512E using HUGO fastformat (presumably 512E with sg_format would work too) to get them to report full 10TB.
If anyone has an example of a retail version of this drive (e.g. not sun/netapp/ibm) and has it formatted to be 4Kn, do you have the issue with them reporting 9.93TB?
The workaround does work, but I want to open discussion to see if anyone knows why/how to properly resolve this and keep it set as 4Kn. In my case, the workaround doesn't cause a problem because ashift=12 with zfs will work fine without performance penalty.
HUGO utility in this post https://forums.servethehome.com/ind...t-hgst-he10-and-he12-to-4kn.27668/post-289494