secure erase fails on INTEL SSDSC2BX016T4R
Brought to you by:
ideguy
I'm getting spurious secure erase errors on a device with 25 INTEL SSDSC2BX016T4Rs. A lot of them will complete the secure erase, but certain devices throw the error:
security_password=""
/dev/sdb:
Issuing SECURITY_ERASE command, password="", user=user
The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device.
SECURITY_ERASE: Invalid argument
This is leaves the device in the security enabled, locked state. Unlocking the drive and then running secure erase again seems complete successfully, but upon reboot the secure erase will fail with the same error.
What do you think is going on here? Could this be buggy firmware?
here is hdparm -I /dev/sdp before the any hdparm commands were executed:
/dev/sdp:
ATA device, with non-removable media
Model Number: INTEL SSDSC2BX016T4R
Serial Number: BTHC646103ZE1P6PGN
Firmware Revision: G201DL2B
Media Serial Num:
Media Manufacturer:
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x006d)
Supported: 10 9 8 7 6 5
Likely used: 10
Configuration:
Logical max current
cylinders 16383 0
heads 16 0
sectors/track 63 0
--
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 3125627568
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 1526185 MBytes
device size with M = 1000*1000: 1600321 MBytes (1600 GB)
cache/buffer size = unknown
Form Factor: 2.5 inch
Nominal Media Rotation Rate: Solid State Device
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 1 Current = 1
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
* 48-bit Address feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* IDLE_IMMEDIATE with UNLOAD
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
unknown 119[6]
* unknown 119[8]
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
* NCQ priority information
* unknown 76[15]
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
* reserved 69[2]
* reserved 69[3]
* reserved 69[4]
* Data Set Management TRIM supported (limit 4 blocks)
* Deterministic read ZEROs after TRIM
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
4min for SECURITY ERASE UNIT. 4min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 55cd2e414d86f721
NAA : 5
IEEE OUI : 5cd2e4
Unique ID : 14d86f721
Checksum: correct
I then ran:
hdparm --user-master u --security-set-pass NULL /dev/sdphdparm --user-master u --security-erase-enhanced NULL /dev/sdpand got:
security_password=""
/dev/sdb:
Issuing SECURITY_ERASE command, password="", user=user
The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device.
SECURITY_ERASE: Invalid argument
hdparm -I /dev/sdp then looked liked:
/dev/sdp:
ATA device, with non-removable media
Model Number: INTEL SSDSC2BX016T4R
Serial Number: BTHC646103ZE1P6PGN
Firmware Revision: G201DL2B
Media Serial Num:
Media Manufacturer:
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x006d)
Supported: 10 9 8 7 6 5
Likely used: 10
Configuration:
Logical max current
cylinders 16383 0
heads 16 0
sectors/track 63 0
--
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 3125627568
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 1526185 MBytes
device size with M = 1000*1000: 1600321 MBytes (1600 GB)
cache/buffer size = unknown
Form Factor: 2.5 inch
Nominal Media Rotation Rate: Solid State Device
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 1 Current = 1
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
* Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
* 48-bit Address feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* IDLE_IMMEDIATE with UNLOAD
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
unknown 119[6]
* unknown 119[8]
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
* NCQ priority information
* unknown 76[15]
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
* reserved 69[2]
* reserved 69[3]
* reserved 69[4]
* Data Set Management TRIM supported (limit 4 blocks)
* Deterministic read ZEROs after TRIM
Security:
Master password revision code = 65534
supported
enabled
locked
not frozen
not expired: security count
supported: enhanced erase
Security level high
4min for SECURITY ERASE UNIT. 4min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 55cd2e414d86f721
NAA : 5
IEEE OUI : 5cd2e4
Unique ID : 14d86f721
Checksum: correct
running:
hdparm --user-master u --security-unlock "" /dev/sdphdparm --user-master u --security-erase-enhanced NULL /dev/sdprestored the hdparm -I /dev/sdp to the former state.
Alternatively, after the failure and then a power cycle, the security security section of
hdparm -Ilooks like:running:
hdparm --user-master u --security-unlock "" /dev/sdphdparm --user-master u --security-erase-enhanced NULL /dev/sdprestores the drive to SEC1 and the secure erase is successful on next reboot aswell.
Last edit: Will Szumski 2018-04-05
I see the same error with a Samsung 850 Pro after upgrading to RHEL 7.7 (3.10.0-1062.1.1.el7.x86_64)
hdparm version 9.56
I haven't had this problem before on older CentOS versions.
Last edit: Elliott 2019-09-04
"The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device."
Perhaps complain to your distro provider about that.
Is that error referencing the obsolete IDE standard for hard drives? This is a SATA drive connected through a MegaRAID controller in JBOD mode. I suspect maybe the MegaRAID is causing this issue, but I have done this successfully in the past with the same hardware. I will report it to Red Hat.