[T10] Determining an SED Drive

[Gerry Houlder]

If you get drive not ready, then the drive is not spun up yet.
If you get invalid command, then the drive is not SED.
There may be exceptions where an SED uses vendor specific protocols (not
SECURITY PROTOCOL IN and SECURITY PROTOCOL OUT commands) that you can't
determine from this method.

On Thu, Apr 7, 2016 at 10:31 AM, Otte, Olga <olga.otte at hpe.com> wrote:

> Do we expect “drive not ready” or “Invalid command” check condition if
> drive is not spin up yet? I think I am getting timing issue and not sure
> what is expected behavior.
>
>
>
> Olga Otte HPE
>
>
>
> *From:* t10-bounces at t10.org [mailto:t10-bounces at t10.org] *On Behalf Of *Saha,
> Soumit
> *Sent:* Thursday, April 07, 2016 7:35 AM
> *To:* Amir Dagan1
> *Cc:* T10, Reflector
> *Subject:* Re: [T10] Determining an SED Drive
>
>
>
> You have to send SPC trusted receive (IF-RECV) SCSI primary command with
> discovery payload and handle illegal requests if the drive is not an SED.
>
> There are no vital data pages for SED specific attributes.
>
> On 7 Apr 2016 12:39, Amir Dagan1 <AMIRDA at il.ibm.com> wrote:
>
> Hello,
>
> Is there a "SCSI" way (non vendor specific) to tell whether a device is an
> SED one (Self Encrypting Drive)?
> I do not mean by P/N etc., but a designated field in a logpage, inquiry,
> etc.
>
> Thanks,
> Amir Dagan
> IBM
>
> _______________________________________________
> T10 mailing list
> T10 at t10.org
> http://www.t10.org/mailman/listinfo/t10
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.t10.org/pipermail/t10/attachments/20160407/628a48a7/attachment.html>