Error formating HDD from 4k Type 2 protection to 512

BulgarianHealer

Dabbler
Joined
Jul 16, 2022
Messages
17
Yesterday in another thread(where @Daisuke tried to help me) i posted a problem with formatting IBM 6TB HDD SAS from 4k with TP10 protection(type 2).

The thread: https://www.truenas.com/community/t...warnings-in-bluefin.106051/page-4#post-734528

The problem is:

Code:
root@truenas[~]# time sg_format -vFf 0 -s 512 /dev/sda     
    IBM-D050  ST6000NM0014      BC7B   peripheral_type: disk [0x0]
      PROTECT=1
      << supports protection information>>
      Unit serial number: S4D090ZD0000K601HQC0
      LU name: 5000c5008e58e757
    mode sense(10) cdb: [5a 00 01 00 00 00 00 00 fc 00]
Mode Sense (block descriptor) data, prior to changes:
number of blocks will max out, set <<longlba>>
    mode sense(10) cdb: [5a 10 01 00 00 00 00 00 fc 00]
  <<< longlba flag set (64 bit lba) >>>
  Number of blocks=1465130646 [0x57541e96]
  Block size=4096 [0x1000]
    mode select(10) cdb: [55 11 00 00 00 00 00 00 24 00]
mode select(10):
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
  Field replaceable unit code: 17
  Sense Key Specific: Error in Data parameters: byte 21 bit 7
Try MODE SELECT again with SP=0 this time
    mode select(10) cdb: [55 10 00 00 00 00 00 00 24 00]
mode select(10):
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
  Field replaceable unit code: 17
  Sense Key Specific: Error in Data parameters: byte 21 bit 7
MODE SELECT command: Illegal request, type: sense key, apart from Invalid opcode
sg_format -vFf 0 -s 512 /dev/sda  0.00s user 0.00s system 1% cpu 0.139 total


Output for: openSeaChest_Info -id /dev/sda
The output:
Code:
root@truenas[~]# openSeaChest_Info -id /dev/sda
==========================================================================================
 openSeaChest_Info - openSeaChest drive utilities - NVMe Enabled
 Copyright (c) 2014-2022 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 openSeaChest_Info Version: 2.0.0-2_2_1 X86_64
 Build Date: Dec 13 2022
 Today: Thu Jan  5 00:38:31 2023        User: root
==========================================================================================

/dev/sg2 - ST6000NM0014 - S4D090ZD0000K601HQC0 - SCSI
        Vendor ID: IBM-D050
        Model Number: ST6000NM0014   
        Serial Number: S4D090ZD0000K601HQC0
        Firmware Revision: BC7B
        World Wide Name: 5000C5008E58E757
        Drive Capacity (TB/TiB): 6.00/5.46
        Temperature Data:
                Current Temperature (C): 37
                Highest Temperature (C): Not Reported
                Lowest Temperature (C): Not Reported
        Power On Time:  5 years 19 days 8 hours 36 minutes
        Power On Hours: 44264.60
        MaxLBA: 1465130645
        Native MaxLBA: Not Reported
        Logical Sector Size (B): 4096
        Physical Sector Size (B): 4096
        Sector Alignment: 0
        Rotation Rate (RPM): 7200
        Form Factor: 3.5"
        Last DST information:
                Time since last DST (hours): 0.60
                DST Status/Result: 0x0
                DST Test run: 0x1
        Long Drive Self Test Time:  10 hours 43 minutes
        Interface speed:
                Port 0 (Current Port)
                        Max Speed (GB/s): 12.0
                        Negotiated Speed (Gb/s): 6.0
                Port 1
                        Max Speed (GB/s): 12.0
                        Negotiated Speed (Gb/s): Not Reported
        Annualized Workload Rate (TB/yr): 82.63
        Total Bytes Read (TB): 311.36
        Total Bytes Written (TB): 106.15
        Encryption Support: Not Supported
        Cache Size (MiB): Not Reported
        Read Look-Ahead: Not Supported
        Write Cache: Disabled
        SMART Status: Good
        ATA Security Information: Not Supported
        Firmware Download Support: Full, Segmented, Deferred
        Number of Logical Units: 1
        Specifications Supported:
                SPC-4
                SAM-5
                SAS-3
                SPL-3
                SPC-4
                SBC-3
        Features Supported:
                Protection Type 1
                Protection Type 2 [Enabled]
                Application Client Logging
                Self Test
                Automatic Write Reassignment [Enabled]
                Automatic Read Reassignment [Enabled]
                EPC
                Informational Exceptions [Mode 4]
                Translate Address
                Format Unit
                Sanitize
        Adapter Information:
                Vendor ID: 1000h
                Product ID: 0087h
                Revision: 0005h


Because my SAS does not support SBC4, @Daisuke gave me this command:
Code:
root@truenas[~]# openSeaChest_FormatUnit -d /dev/sda --stopOnListError --protectionType 0 --formatUnit 512 --poll --confirm this-will-erase-data
==========================================================================================
 openSeaChest_Format - openSeaChest drive utilities - NVMe Enabled
 Copyright (c) 2014-2022 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 openSeaChest_Format Version: 2.2.1-2_2_1 X86_64
 Build Date: Dec 13 2022
 Today: Thu Jan  5 01:22:34 2023        User: root
==========================================================================================

/dev/sg2 - ST6000NM0014 - S4D090ZD0000K601HQC0 - SCSI
Format Unit
Format Unit Failed!


After that @jgreco give an idea to attach the HDD to the controller and open a thread.

Because it's a custom server/chassis is gonna be a mess and time-eater to attach/reattach cable to the LSI Controller. So i have take out the HDD and put it in a new server(Supermicro with the same backplane which is connected to a "newer" LSI card, currently this server was just going online so i can play with the HDD). I tried to perform the same commands, but the error its still the same as in the other forum thread.
 

sdooweloc

Dabbler
Joined
Jan 2, 2023
Messages
19
I am also having an extremely similar issue with my drives and made a post since I hadnt seen you make one yet haha.
Hopefully one or both of us can find an answer for how best to resolve the issue.

 

BulgarianHealer

Dabbler
Joined
Jul 16, 2022
Messages
17
I am also having an extremely similar issue with my drives and made a post since I hadnt seen you make one yet haha.
Hopefully one or both of us can find an answer for how best to resolve the issue.

What i can see as common is the brand IBM and the exact error, maybe they did some "shit" in the firmware.
 

sdooweloc

Dabbler
Joined
Jan 2, 2023
Messages
19
Okay so I have a test drive going now with some information that a buddy from Discord found me.
He managed to track down a blogger who had a similar issue with being unable to use Protection type 2 devices for storage (not in truenas but should be similar enough) http://talesinit.blogspot.com/2015/11/formatted-with-type-2-protection-huh.html
Basically boils down to running
Code:
sg_format --format --fmtpinfo=0 /dev/sd*


I have 1 drive running now but being 14TB it is going to take a while. Will update here when it finishes as this should clear out the protection and make the drive useable.
 

BulgarianHealer

Dabbler
Joined
Jul 16, 2022
Messages
17
Okay so I have a test drive going now with some information that a buddy from Discord found me.
He managed to track down a blogger who had a similar issue with being unable to use Protection type 2 devices for storage (not in truenas but should be similar enough) http://talesinit.blogspot.com/2015/11/formatted-with-type-2-protection-huh.html
Basically boils down to running
Code:
sg_format --format --fmtpinfo=0 /dev/sd*


I have 1 drive running now but being 14TB it is going to take a while. Will update here when it finishes as this should clear out the protection and make the drive useable.
Your command is working, but i just found from STH (https://forums.servethehome.com/index.php?threads/anyone-used-t10-pi-update-it-works.30875/) and their command also works, but i will use yours :D let's see what will happen tomorrow/today.
 
Top