How to reformat HDD & SSD to 512B Sector Size

Markess

Well-Known Member
May 19, 2018
729
360
63
Success with HP branded HGST HUS723020ALS640 using the format command in the OP. No modifications required.

These were 520 byte formatted drives I pulled from HP StoreServ 10000 drive magazines (four drives per magazine) I found on Ebay for $32 per magazine. Drives were new, well at this point "old" I suppose, but they were unused. 2TB isn't a lot of space these days, but $8 each for drives with zero hours..not bad..

They're going into a server I'm helping my son put together for a school elective on computer science. So, another big thank you to @azev for saving me money....again.
 
Last edited:
  • Like
Reactions: Fritz and itronin

lian

New Member
Nov 14, 2016
8
0
1
31
Hi, everyone - i have custom maed FW for ST9600204SS - PM for more information.
 
Last edited:

SmilinJoe

New Member
Sep 27, 2021
6
1
3
Checking here to see if my drives are borked or salvageable... I have 6x Seagate ST6000NM0034 that came with 520b sector size. Since I have been down this road, I formatted them to 512b. That part seems to work:


root@truenas[~]# diskinfo -v /dev/da0
/dev/da0
512 # sectorsize
6001175126016 # mediasize in bytes (5.5T)
11721045168 # mediasize in sectors
4096 # stripesize
0 # stripeoffset
729601 # Cylinders according to firmware.
255 # Heads according to firmware.
63 # Sectors according to firmware.
SEAGATE DKS2F-H6R0SS # Disk descr.
Z4D4QWD90000R710TMPJ # Disk ident.
id1,enc@n50016360021ef7bd/type@0/slot@7/elmdesc@DISK06 # Physical path
No # TRIM/UNMAP support
7200 # Rotation rate in RPM
Not_Zoned # Zone Mode
Trying to create a pool in TrueNAS I get this error:

middlewared.service_exception.CallError: [EFAULT] Failed to wipe disk da0: [EFAULT] Command gpart create -s gpt /dev/da0 failed (code 1):
gpart: Input/output error


and the console spits out a bunch of these:

Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): WRITE(6). CDB: 0a 00 00 00 01 00
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): CAM status: SCSI Status Error
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): SCSI status: Check Condition
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): SCSI sense: HARDWARE FAILURE asc:81,0 (LA Check Failed)
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Info: 0
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Command Specific Info: 0x1400
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Descriptor 0xc0: 00 00 00 00 00 00 00 00 55 aa
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Retrying command (per sense data)
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): WRITE(6). CDB: 0a 00 00 00 01 00
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): CAM status: SCSI Status Error
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): SCSI status: Check Condition
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): SCSI sense: HARDWARE FAILURE asc:81,0 (LA Check Failed)
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Info: 0
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Command Specific Info: 0x1400
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Descriptor 0xc0: 00 00 00 00 00 00 00 00 55 aa
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Retrying command (per sense data)
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): WRITE(6). CDB: 0a 00 00 00 01 00
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): CAM status: SCSI Status Error
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): SCSI status: Check Condition
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): SCSI sense: HARDWARE FAILURE asc:81,0 (LA Check Failed)
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Info: 0
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Command Specific Info: 0x1400
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Descriptor 0xc0: 00 00 00 00 00 00 00 00 55 aa
Sep 27 14:17:38 truenas (da0:mpr0:0:13:0): Retrying command (per sense data)
Sep 27 14:17:39 truenas (da0:mpr0:0:13:0): WRITE(6). CDB: 0a 00 00 00 01 00
Sep 27 14:17:39 truenas (da0:mpr0:0:13:0): CAM status: SCSI Status Error
Sep 27 14:17:39 truenas (da0:mpr0:0:13:0): SCSI status: Check Condition
Sep 27 14:17:39 truenas (da0:mpr0:0:13:0): SCSI sense: HARDWARE FAILURE asc:81,0 (LA Check Failed)
Sep 27 14:17:39 truenas (da0:mpr0:0:13:0): Info: 0
Sep 27 14:17:39 truenas (da0:mpr0:0:13:0): Command Specific Info: 0x1400
Sep 27 14:17:39 truenas (da0:mpr0:0:13:0): Descriptor 0xc0: 00 00 00 00 00 00 00 00 55 aa
Sep 27 14:17:39 truenas (da0:mpr0:0:13:0): Retrying command (per sense data)
Sep 27 14:17:40 truenas (da0:mpr0:0:13:0): WRITE(6). CDB: 0a 00 00 00 01 00
Sep 27 14:17:40 truenas (da0:mpr0:0:13:0): CAM status: SCSI Status Error
Sep 27 14:17:40 truenas (da0:mpr0:0:13:0): SCSI status: Check Condition
Sep 27 14:17:40 truenas (da0:mpr0:0:13:0): SCSI sense: HARDWARE FAILURE asc:81,0 (LA Check Failed)
Sep 27 14:17:40 truenas (da0:mpr0:0:13:0): Info: 0
Sep 27 14:17:40 truenas (da0:mpr0:0:13:0): Command Specific Info: 0x1400
Sep 27 14:17:40 truenas (da0:mpr0:0:13:0): Descriptor 0xc0: 00 00 00 00 00 00 00 00 55 aa
Sep 27 14:17:40 truenas (da0:mpr0:0:13:0): Error 5, Retries exhausted
All the drives give me the same errors. I have moved them around in the 12 slot chassis. I can build pools on other drives just fine.

Anyone seen this before?

Thanks.
 

itronin

Well-Known Member
Nov 24, 2018
700
405
63
Denver, Colorado
Checking here to see if my drives are borked or salvageable... I have 6x Seagate ST6000NM0034 that came with 520b sector size. Since I have been down this road, I formatted them to 512b. That part seems to work:

Trying to create a pool in TrueNAS I get this error:

middlewared.service_exception.CallError: [EFAULT] Failed to wipe disk da0: [EFAULT] Command gpart create -s gpt /dev/da0 failed (code 1):
gpart: Input/output error


Anyone seen this before?

Thanks.
First did you check smart(ctl) to make sure you do not have any protection enabled on the drive? Like type 2 protection. Even after changing the block type 2 protection will result in an input/output error when you try and write to the drive.

If you do that needs to be changed.

Did you only change the block size or did you change the block size and perform a low level format after the change?
 

SmilinJoe

New Member
Sep 27, 2021
6
1
3
First did you check smart(ctl) to make sure you do not have any protection enabled on the drive? Like type 2 protection. Even after changing the block type 2 protection will result in an input/output error when you try and write to the drive.

If you do that needs to be changed.

Did you only change the block size or did you change the block size and perform a low level format after the change?
Doesn't look protection is turned on. I used the commands from this page: Henderson's Law. Had issues with sg_format in the beginning, so I went the camcontrol route. Thought it was equivalent.

Thanks.
 

itronin

Well-Known Member
Nov 24, 2018
700
405
63
Denver, Colorado
Doesn't look protection is turned on. I used the commands from this page: Henderson's Law. Had issues with sg_format in the beginning, so I went the camcontrol route. Thought it was equivalent.

Thanks.
so you performed the magic camcontrol command to change the block size to 512 and then performed a camcontrol format?

I don't know whether diskinfo reports protection type. I do know smartctl will. would you mind posting your smartctl output for a couple of the drives just to be sure?

your symptoms are consistent with both type 2 protection being enabled and not low level formatting the drive after changing the block size. Only reason I'm asking.
 

SmilinJoe

New Member
Sep 27, 2021
6
1
3
so you performed the magic camcontrol command to change the block size to 512 and then performed a camcontrol format?

I don't know whether diskinfo reports protection type. I do know smartctl will. would you mind posting your smartctl output for a couple of the drives just to be sure?

your symptoms are consistent with both type 2 protection being enabled and not low level formatting the drive after changing the block size. Only reason I'm asking.
Yeah I ran the commands just like he had.

Here are 3 drives:

root@truenas[~]# smartctl -x /dev/da0
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: SEAGATE
Product: DKS2F-H6R0SS
Revision: 7FA6
Compliance: SPC-3
User Capacity: 6,001,175,126,016 bytes [6.00 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: 0x5000c50086295e6b
Serial number: Z4D4QWD90000R710TMPJ
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Mon Sep 27 15:31:12 2021 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Disabled or Not Supported
Read Cache is: Enabled
Writeback Cache is: Disabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Grown defects during certification = 0
Total blocks reassigned during format = 0
Total new blocks reassigned = 0
Power on minutes since format = 1759
Current Drive Temperature: 47 C
Drive Trip Temperature: 68 C

Manufactured in week 42 of year 2016
Specified cycle count over device lifetime: 10000
Accumulated start-stop cycles: 422
Specified load-unload count over device lifetime: 300000
Accumulated load-unload cycles: 1665
Elements in grown defect list: 0

Vendor (Seagate Cache) information
Blocks sent to initiator = 4568
Blocks received from initiator = 0
Blocks read from cache and sent to initiator = 459
Number of read and write commands whose size <= segment size = 14
Number of read and write commands whose size > segment size = 0

Vendor (Seagate/Hitachi) factory information
number of hours powered up = 30093.93
number of minutes until next internal SMART test = 46

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: 7925747 0 0 7925747 0 0.002 0
write: 0 0 0 0 0 0.010 0

Non-medium error count: 0


[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
No Self-tests have been logged

Background scan results log
Status: no scans active
Accumulated power on time, hours:minutes 30093:56 [1805636 minutes]
Number of background scans performed: 0, scan progress: 0.00%
Number of background medium scans performed: 0

Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 0
number of phys = 1
phy identifier = 0
attached device type: expander device
attached reason: SMP phy control function
reason: loss of dword synchronization
negotiated logical link rate: phy enabled; 12 Gbps
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=1
SAS address = 0x5000c50086295e69
attached SAS address = 0x50016360021ef7bf
attached phy identifier = 2
Invalid DWORD count = 23
Running disparity error count = 22
Loss of DWORD synchronization = 8
Phy reset problem = 6
Phy event descriptors:
Invalid word count: 23
Running disparity error count: 22
Loss of dword synchronization count: 8
Phy reset problem count: 6
relative target port id = 2
generation code = 0
number of phys = 1
phy identifier = 1
attached device type: no device attached
attached reason: unknown
reason: unknown
negotiated logical link rate: phy enabled; unknown
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000c50086295e6a
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0

root@truenas[~]# smartctl -x /dev/da1
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: SEAGATE
Product: DKS2F-H6R0SS
Revision: 7FA6
Compliance: SPC-3
User Capacity: 6,001,175,126,016 bytes [6.00 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: 0x5000c500862a552f
Serial number: Z4D4QKE90000R7093BV6
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Mon Sep 27 15:31:14 2021 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Disabled or Not Supported
Read Cache is: Enabled
Writeback Cache is: Disabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Grown defects during certification = 0
Total blocks reassigned during format = 0
Total new blocks reassigned = 0
Power on minutes since format = 7078
Current Drive Temperature: 46 C
Drive Trip Temperature: 68 C

Manufactured in week 42 of year 2016
Specified cycle count over device lifetime: 10000
Accumulated start-stop cycles: 422
Specified load-unload count over device lifetime: 300000
Accumulated load-unload cycles: 1663
Elements in grown defect list: 0

Vendor (Seagate Cache) information
Blocks sent to initiator = 4184
Blocks received from initiator = 0
Blocks read from cache and sent to initiator = 459
Number of read and write commands whose size <= segment size = 5
Number of read and write commands whose size > segment size = 0

Vendor (Seagate/Hitachi) factory information
number of hours powered up = 30093.83
number of minutes until next internal SMART test = 56

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: 7920127 0 0 7920127 0 0.002 0
write: 0 0 0 0 0 0.007 0

Non-medium error count: 0


[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
No Self-tests have been logged

Background scan results log
Status: no scans active
Accumulated power on time, hours:minutes 30093:50 [1805630 minutes]
Number of background scans performed: 0, scan progress: 0.00%
Number of background medium scans performed: 0

Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 0
number of phys = 1
phy identifier = 0
attached device type: expander device
attached reason: SMP phy control function
reason: unknown
negotiated logical link rate: phy enabled; 12 Gbps
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=1
SAS address = 0x5000c500862a552d
attached SAS address = 0x50016360021ef7bf
attached phy identifier = 3
Invalid DWORD count = 23
Running disparity error count = 22
Loss of DWORD synchronization = 6
Phy reset problem = 6
Phy event descriptors:
Invalid word count: 23
Running disparity error count: 22
Loss of dword synchronization count: 6
Phy reset problem count: 6
relative target port id = 2
generation code = 0
number of phys = 1
phy identifier = 1
attached device type: no device attached
attached reason: unknown
reason: unknown
negotiated logical link rate: phy enabled; unknown
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000c500862a552e
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0

root@truenas[~]# smartctl -x /dev/da2
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: SEAGATE
Product: DKS2F-H6R0SS
Revision: 7FA6
Compliance: SPC-3
User Capacity: 6,001,175,126,016 bytes [6.00 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: 0x5000c50086296f57
Serial number: Z4D4RX7V0000R709YV2P
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Mon Sep 27 15:31:16 2021 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Disabled or Not Supported
Read Cache is: Enabled
Writeback Cache is: Disabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Grown defects during certification = 1
Total blocks reassigned during format = 1
Total new blocks reassigned = 0
Power on minutes since format = 7225
Current Drive Temperature: 42 C
Drive Trip Temperature: 68 C

Manufactured in week 42 of year 2016
Specified cycle count over device lifetime: 10000
Accumulated start-stop cycles: 424
Specified load-unload count over device lifetime: 300000
Accumulated load-unload cycles: 1665
Elements in grown defect list: 1

Vendor (Seagate Cache) information
Blocks sent to initiator = 4552
Blocks received from initiator = 0
Blocks read from cache and sent to initiator = 459
Number of read and write commands whose size <= segment size = 14
Number of read and write commands whose size > segment size = 0

Vendor (Seagate/Hitachi) factory information
number of hours powered up = 30093.30
number of minutes until next internal SMART test = 3

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: 7918964 0 0 7918964 0 0.002 0
write: 0 0 0 0 0 0.011 0

Non-medium error count: 0


[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
No Self-tests have been logged

Background scan results log
Status: no scans active
Accumulated power on time, hours:minutes 30093:18 [1805598 minutes]
Number of background scans performed: 0, scan progress: 0.00%
Number of background medium scans performed: 0

Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 0
number of phys = 1
phy identifier = 0
attached device type: expander device
attached reason: SMP phy control function
reason: unknown
negotiated logical link rate: phy enabled; 12 Gbps
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=1
SAS address = 0x5000c50086296f55
attached SAS address = 0x50016360021ef7bf
attached phy identifier = 6
Invalid DWORD count = 23
Running disparity error count = 22
Loss of DWORD synchronization = 7
Phy reset problem = 6
Phy event descriptors:
Invalid word count: 23
Running disparity error count: 22
Loss of dword synchronization count: 7
Phy reset problem count: 6
relative target port id = 2
generation code = 0
number of phys = 1
phy identifier = 1
attached device type: no device attached
attached reason: unknown
reason: unknown
negotiated logical link rate: phy enabled; unknown
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000c50086296f56
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0
 

itronin

Well-Known Member
Nov 24, 2018
700
405
63
Denver, Colorado
Yeah I ran the commands just like he had.

Here are 3 drives:
strange, no type 2 protection. Its almost like the drive hasn't been formatted with that error... hmmm... hearing hooves but thinking zebras...

but lets continue with horses for a moment.

After I re-block I perform a long format, quick doesn't always work IME. I know I tried quick on some reblocked 16TB seagate exos (512 to 4k) and ended up having to do a long format. no errors on the quick format but no joy using the disks. I'm also going to run BB on used drives too so it just ends up being part of the pre-deployment drive workout.

If its a zebra we're after then could be SED but a quick (and a long format) should have failed. Your drive does support SED according to the specsheet.

If you have the time it might be worth doing a long format on one of the drives while you work different avenues on your other drives.
 

SmilinJoe

New Member
Sep 27, 2021
6
1
3
strange, no type 2 protection. Its almost like the drive hasn't been formatted with that error... hmmm... hearing hooves but thinking zebras...

but lets continue with horses for a moment.

After I re-block I perform a long format, quick doesn't always work IME. I know I tried quick on some reblocked 16TB seagate exos (512 to 4k) and ended up having to do a long format. no errors on the quick format but no joy using the disks. I'm also going to run BB on used drives too so it just ends up being part of the pre-deployment drive workout.

If its a zebra we're after then could be SED but a quick (and a long format) should have failed. Your drive does support SED according to the specsheet.

If you have the time it might be worth doing a long format on one of the drives while you work different avenues on your other drives.
I kicked off a full, slow sg_format last night that should be finishing up shortly. We'll see what happens.

Thanks.
 
  • Like
Reactions: itronin

Dave Corder

Active Member
Dec 21, 2015
160
79
28
39
Following this thread, as I'm adding my first SAS drives to my FreeNAS server (all SATA until now) and have the first camcontrol low level format going right now after converting the first drive to 512 byte
 

Dave Corder

Active Member
Dec 21, 2015
160
79
28
39
why 512 and not 4096? Lots of teeny tiny files? No ISO storage? ;)
Uh...didn't realize that was an option, actually, for my ISO storage.

However, these are 8 TB disks slated to replace some failing 4 TB drives that are already using 512b (pool consists of a bunch of two-drive mirrors). So probably a good idea to stick with 512b to keep my pool happy...
 

SmilinJoe

New Member
Sep 27, 2021
6
1
3
strange, no type 2 protection. Its almost like the drive hasn't been formatted with that error... hmmm... hearing hooves but thinking zebras...

but lets continue with horses for a moment.

After I re-block I perform a long format, quick doesn't always work IME. I know I tried quick on some reblocked 16TB seagate exos (512 to 4k) and ended up having to do a long format. no errors on the quick format but no joy using the disks. I'm also going to run BB on used drives too so it just ends up being part of the pre-deployment drive workout.

If its a zebra we're after then could be SED but a quick (and a long format) should have failed. Your drive does support SED according to the specsheet.

If you have the time it might be worth doing a long format on one of the drives while you work different avenues on your other drives.
Same result. Did the 12 hour sg_format on all the drives, and I still get the input/output errors. Anything else I can try before trying to send these drives back?

Thanks.
 

itronin

Well-Known Member
Nov 24, 2018
700
405
63
Denver, Colorado
Same result. Did the 12 hour sg_format on all the drives, and I still get the input/output errors. Anything else I can try before trying to send these drives back?

Thanks.
Only things I can guess at are (1) that the drives are SED locked but that should have prevented your formats and block changes and you should have seen errors... Or (2) they were used in something like a Vantara and not offboarded with std firmware (vs. the funky vsp firmware).

But

On most Linux flavors this will tell you want's going on SED-wise
Code:
hdparm -I /dev/MyDeviceName
On Truenas
Code:
sedutil-cli --scan
will list the drives that are capable but doesn't tell you if its active:

For example:
Code:
root@redacted[/mnt/Disk/Users/redacted]# sedutil-cli --scan
Scanning for Opal compliant disks
/dev/da0   No      VMware  Virtual disk     2.0 
/dev/da1     E     HGST    HUH721008AL5201  B384
/dev/da10  No      HGST    HUH728080AL5200  A515
/dev/da11  No      HGST    HUH728080AL5200  A515
/dev/da12    E     HGST    HUH721008AL5201  B384
/dev/da13    E     HGST    HUH721008AL5201  B384
/dev/da14    E     HGST    HUH721008AL5201  B384
/dev/da15    E     HGST    HUH721008AL5201  B384
/dev/da16    E     HGST    HUH721008AL5201  B384
/dev/da2   No      HGST    HUH728080AL5200  A515
/dev/da3   No      HGST    HUH728080AL5200  A515
/dev/da4   No      HGST    HUH728080AL5200  A515
/dev/da5   No      HGST    HUH728080AL5200  A515
/dev/da6   No      HGST    HUH728080AL5200  A515
/dev/da7   No      HGST    HUH728080AL5200  A515
/dev/da8   No      HGST    HUH728080AL5200  A515
/dev/da9   No      HGST    HUH728080AL5200  A515
/dev/nvme0     p   INTEL SSDPED1D280GA                      E2010435
No more disks present ending scan
see here: Self-Encrypting Drives |

since you can't use the disks anyway you can always try this:

Code:
sedutil-cli --yesIreallywanttoERASEALLmydatausingthePSID <PSINODASHED> </dev/device>
where the PSID will come from the label on the drive. if there's no psid then not SED capable btw.

FWIW I've seen sort of kind of this type of behavior on 600/900GB SAS spinners (some seagate/some hitachi part #s) that came out of a hitachi vantara . I ended up sending them back ....
 

SmilinJoe

New Member
Sep 27, 2021
6
1
3
Only things I can guess at are (1) that the drives are SED locked but that should have prevented your formats and block changes and you should have seen errors... Or (2) they were used in something like a Vantara and not offboarded with std firmware (vs. the funky vsp firmware).

But

On most Linux flavors this will tell you want's going on SED-wise
Code:
hdparm -I /dev/MyDeviceName
On Truenas
Code:
sedutil-cli --scan
will list the drives that are capable but doesn't tell you if its active:

For example:
Code:
root@redacted[/mnt/Disk/Users/redacted]# sedutil-cli --scan
Scanning for Opal compliant disks
/dev/da0   No      VMware  Virtual disk     2.0
/dev/da1     E     HGST    HUH721008AL5201  B384
/dev/da10  No      HGST    HUH728080AL5200  A515
/dev/da11  No      HGST    HUH728080AL5200  A515
/dev/da12    E     HGST    HUH721008AL5201  B384
/dev/da13    E     HGST    HUH721008AL5201  B384
/dev/da14    E     HGST    HUH721008AL5201  B384
/dev/da15    E     HGST    HUH721008AL5201  B384
/dev/da16    E     HGST    HUH721008AL5201  B384
/dev/da2   No      HGST    HUH728080AL5200  A515
/dev/da3   No      HGST    HUH728080AL5200  A515
/dev/da4   No      HGST    HUH728080AL5200  A515
/dev/da5   No      HGST    HUH728080AL5200  A515
/dev/da6   No      HGST    HUH728080AL5200  A515
/dev/da7   No      HGST    HUH728080AL5200  A515
/dev/da8   No      HGST    HUH728080AL5200  A515
/dev/da9   No      HGST    HUH728080AL5200  A515
/dev/nvme0     p   INTEL SSDPED1D280GA                      E2010435
No more disks present ending scan
see here: Self-Encrypting Drives |

since you can't use the disks anyway you can always try this:

Code:
sedutil-cli --yesIreallywanttoERASEALLmydatausingthePSID <PSINODASHED> </dev/device>
where the PSID will come from the label on the drive. if there's no psid then not SED capable btw.

FWIW I've seen sort of kind of this type of behavior on 600/900GB SAS spinners (some seagate/some hitachi part #s) that came out of a hitachi vantara . I ended up sending them back ....
Well the drives have returned for a refund. That was a learning experience!