Re: Intel Optane SSD mounting problem
|
Farrell, Patrick Arthur <patrick.farrell@...>
Gert,
Thanks for the further information. Something I don't quite follow:
"The product specification lists both Pyrite as Opal support, what is less clear in the documentation is that Opal is not enable."
Then, can Opal be enabled? Or is it permanently disabled on this model?
A general question for you:
Is SPDK simply totally unable to manage some current Intel SSDs if they don't have the full Opal support?
Separately, I'm going to dig a little, and I also plan to try older versions of DAOS/SPDK to see what I can figure out.
Thanks,
-Patrick
From: daos@daos.groups.io <daos@daos.groups.io> on behalf of Gert Pauwels (intel) <gert.pauwels@...>
Sent: Thursday, June 25, 2020 12:05 PM To: daos@daos.groups.io <daos@daos.groups.io> Subject: Re: [daos] Intel Optane SSD mounting problem Patrick, Colin,
I verified with the NSG Business Unit that builds the 905P SSD. The product specification lists both Pyrite as Opal support, what is less clear in the documentation is that Opal is not enable. This is causing the behavior you are seeing. The Identify command correctly returns the Security Send/Receive is supported as this is needed for both Opal and Pyrite. It is correct that SPDK returns “No Opal support” for the 905P SSD. I verified on my system you do not have this with the Intel Optane SSD P4800X as this support Opal 2.0
What I cannot explain right now is why the drive was working with DAOS in the past.
Regards,
Gert,
From: daos@daos.groups.io <daos@daos.groups.io>
On Behalf Of Farrell, Patrick Arthur
Recall that we have used this SSD with DAOS in the past. Whatever is preventing this now is a change, perhaps in SPDK but possibly in how DAOS is invoking it.
Regards, -Patrick From:
daos@daos.groups.io <daos@daos.groups.io> on behalf of Nabarro, Tom <tom.nabarro@...>
We probably need to get further information from NSG folks on product specifics regarding Opal support in 905p SSDs. This seems to be a prerequisite for device management through SPDK.
Tom
From: daos@daos.groups.io <daos@daos.groups.io>
On Behalf Of Farrell, Patrick Arthur
Gert,
We're seeing this when we run identify on our 905p SSDs: " NVMe Controller at 0000:1a:00.0 [8086:2700] [...] Serial Number: PHM29226005S480BGN [...] Admin Command Set Attributes ============================ Security Send/Receive: Supported "
However, when I run nvme_manage, I get an error stating that Opal is not supported (the same error DAOS is spitting out, incidentally):
"Please Input PCI Address(domain:bus:dev.func): 0000:1a:00.00 Opal General Usage:
[1: scan device] [2: init - take ownership and activate locking] [3: revert tper] [4: setup locking range] [5: list locking ranges] [6: enable user] [7: set new password] [8: add user to locking range] [9: lock/unlock range] [10: erase locking range] [0: quit] 1 [2020-06-24 14:37:34.452086] nvme_opal.c: 828:opal_discovery0_end: *ERROR*: Opal Not Supported. "
Any thoughts?
Regards, -Patrick From:
daos@daos.groups.io <daos@daos.groups.io> on behalf of Gert Pauwels (intel) <gert.pauwels@...>
Hi Tom, Colin,
I also compiled the latest master as of yesterday, but it did not make a difference.
--------------------------------------------------------------------- This e-mail and any attachments may contain confidential material for Intel Corporation NV/SA This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. |
|
|