r0m30
commented
7 years ago The product spec sheet for the Micron drives does not mention OPAL or encryption at all and the Toshiba spec sheet says that TCG is optional. Are you're drives SEDs? SSD != SED.
On systems with SAS SED drives, sedutil does not find the SAS drives at all - it appears that sensing is failing. The Micron drive we are using below is a SED drive and we are unable to set the password on it since the drive is not being detected.
System
Dell FC630 connected to two drives. First is a dual ported Micron SAS drives and the second is a dual Toshiba SAS drive. Drives are behind PERC 12 Gbps SAS controllers. However, the controllers are in HBA mode, not RAID mode, so the drives are being directly passed through to the OS. We also tried the same experiment with a Supermicro system with an LSI controller in HBA mode with the same results. Both the Micron and the Toshiba SAS drives are failing detection, but the SATA boot drive (non SED) is at least being detected. This appears to be a SAS issue.
OS
CentOS 7.2 with all patches - Redhat 3.10 kernel. We also tried this with mainline 4.4 kernel (same CentOS 7.2 distro) with the same results.
Here's the output from sedutil-cli (sedutil-cli version is 1.12)
[root@primary GNU-Linux]# ./sedutil-cli --scan
Scanning for Opal compliant disks /dev/sda No INTEL SSDSC2BB120G6R G201DL2B /dev/sdb No
/dev/sdc No
No more disks present ending scan
With debugging [root@primary GNU-Linux]# ./sedutil-cli -vvvvv --scan
Scanning for Opal compliant disks
This is the output of sginfo [root@primary GNU-Linux]# sginfo -T /dev/sdb nothing selected so do a short INQUIRY cdb: 12 00 00 00 24 00 INQUIRY response (cmd: 0x12)
Device Type 0 Vendor: MICRON
Product: S610DC-1920SED
Revision level: MA13
[root@primary GNU-Linux]# sginfo -T /dev/sdc nothing selected so do a short INQUIRY cdb: 12 00 00 00 24 00 INQUIRY response (cmd: 0x12)
Device Type 0 Vendor: TOSHIBA Product: PX04SRB192
Revision level: AM04