So I have 12 2TB SAS HGST netapp drives from 2017 everything was fine until upgrade they have level 2 protection were already sg_format to 512 a year ago anyway...
I offline 1 drive /dev/sda and remove protection.
I re sg_format to 512
I try to online the drive back into the pool and get a FAILED 3 errors
I do a LONG smart scan no errors
I zpool clear maintank
This time i try to replace the drive with this newly formatted drive and get error
Code:
Error: [EFAULT] Disk: 'sda' is incorrectly formatted with Data Integrity Feature (DIF).
This is the output for the drive
Code:
root@truenas[~]# sg_readcap -l /dev/sda
Read Capacity results:
Protection: prot_en=0, p_type=0, p_i_exponent=0
Logical block provisioning: lbpme=0, lbprz=0
Last LBA=3907029167 (0xe8e088af), Number of logical blocks=3907029168
Logical block length=512 bytes
Logical blocks per physical block exponent=0
Lowest aligned LBA=0
Hence:
Device size: 2000398934016 bytes, 1907729.1 MiB, 2000.40 GB, 2.00 TB
What am I missing doing wrong ?
Thanks for your time
(edit) I am reformating to 512 using openSeaChest since I read it's for SAS in the thread /shrug at 14% ATM.
(edit) If you forget (like me) to "tmux" and the page closes during your format you can use
Code:
sg_format -v /dev/<your drive>
and it will give you the % of your on going format. ( I don't remember reading that in this thread)
(edit) Last post of this thread
https://www.truenas.com/community/threads/drives-with-error-data-integrity-feature.106633/page-2 said a reboot worked for him.
After the openSeaChest format I still could not replace drive.
I REBOOTED and I am reslivering.
I am guessing I didn't need to reformat a second time using openSeaChest. I will check on the next one.
You may want to add a REBOOT at end of your branded guide before replacing.
(edit) I just did another HGST SAS Disk, I followed the guide (skipped openSeaChest) and I could NOT replace disk (force) until I rebooted (gave above error). Once rebooted I replaced (using force) the disk and it started. Hope this helps anyone running into this
(LAST EDIT) So I guess I need to work on reading comprehension. As I was formating my drives I became aware that (because my "branded drives" had already been reformated from 520 to 512 last year) I could JUST remove Protection and Reboot and then Replace saving alot of time. I think my confussion came from not understanding my need to reboot when doing the first couple of drives (they would throw errors when trying to replace after removing protection) and I thought removing protection required reformat. That was not the case.
Removing protection on already 512 formated disk only required a reboot before replacing (for me) Did all 12 drives and all is well.