IBM Support

Revert of a nonvolatile memory express (NVMe) self-encrypting drive (SED) is incomplete

Flashes (Alerts)


Abstract

When a SED Opal device is reverted by using the "nvme sed revert" command without the -e flag, then the drive is not fully reverted. In this case, any attempt to re-initialize the device by using the "nvme sed initialize" command results in a failure.

Content

Linux Releases Affected
Red Hat Enterprise Linux (RHEL) 9.4
SUSE Linux Enterprise Server (SLES) 15, Service Pack 6
 
IBM Systems Affected
All systems that support NVMe drives
Symptoms
NVMe SED drive cannot be re-initalized after it is reverted by using the following command without the 
-e flag: 
nvme sed revert
Workaround
The only workaround for this issue is to revert the NVMe SED drive by using the following command:
nvme sed revert -e
When the NVMe SED drive is reverted by using the revert -e option, then the contents of the 
NVMe SED drive is erased. You must take full backup of the NVMe SED drive before the 
nvme sed revert -e command is issued.

After the nvme sed revert -e command is issued, it is possible to re-initialize the NVMe SED drive 
and restore the backed up data.
Fix Outlook
Fix will be included in the upcoming maintenance releases.
I/O device impacted
All SED compliant NVMe drives.

[{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SGMV157","label":"IBM Support for Red Hat Enterprise Linux Server"},"ARM Category":[{"code":"a8m0z000000Gnl7AAC","label":"Red Hat Enterprise Linux"},{"code":"a8m0z000000GnlCAAS","label":"SUSE Linux Enterprise Server"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
15 July 2024

UID

ibm17156925