staging.inyokaproject.org

Safe Erase mit nvme-cli klappt nicht

Status: Gelöst | Ubuntu-Version: Ubuntu 21.04 (Hirsute Hippo)
Antworten |

Stefan03

Anmeldungsdatum:
9. April 2011

Beiträge: 27

Hallo zusammen, ich würde gerne meine NVME mittels nvme-cli sicher löschen und bin nach folgender Anleitung vorgegangen: http://forum.notebookreview.com/threads/secure-erase-hdds-ssds-sata-nvme-using-hdparm-nvme-cli-on-linux.827525/

Leider kommt im letzten Schritt:

sudo nvme format /dev/nvme0 --ses=1
Invalid namespace ID, specify a namespace to format or use '-n 0xffffffff' to format all namespaces on this controller.

Die Ausgabe von nvme id-ctrl -H /dev/nvme0 zeigt aber an, dass safe erase möglich ist?!?

NVME Identify Controller:
vid       : 0x144d
ssvid     : 0x144d
sn        : S35FNA0K713921      
mn        : SAMSUNG MZVLW128HEGR-000L2              
fr        : 4L1QCXB7
rab       : 2
ieee      : 002538
cmic      : 0
  [3:3] : 0    ANA not supported
  [2:2] : 0    PCI
  [1:1] : 0    Single Controller
  [0:0] : 0    Single Port

mdts      : 0
cntlid    : 0x2
ver       : 0x10200
rtd3r     : 0x186a0
rtd3e     : 0x4c4b40
oaes      : 0
[14:14] : 0    Endurance Group Event Aggregate Log Page Change Notice Not Supported
[13:13] : 0    LBA Status Information Notices Not Supported
[12:12] : 0    Predictable Latency Event Aggregate Log Change Notices Not Supported
[11:11] : 0    Asymmetric Namespace Access Change Notices Not Supported
  [9:9] : 0    Firmware Activation Notices Not Supported
  [8:8] : 0    Namespace Attribute Changed Event Not Supported

ctratt    : 0
  [9:9] : 0    UUID List Not Supported
  [7:7] : 0    Namespace Granularity Not Supported
  [5:5] : 0    Predictable Latency Mode Not Supported
  [4:4] : 0    Endurance Groups Not Supported
  [3:3] : 0    Read Recovery Levels Not Supported
  [2:2] : 0    NVM Sets Not Supported
  [1:1] : 0    Non-Operational Power State Permissive Not Supported
  [0:0] : 0    128-bit Host Identifier Not Supported

rrls      : 0
crdt1     : 0
crdt2     : 0
crdt3     : 0
oacs      : 0x17
  [9:9] : 0    Get LBA Status Capability Not Supported
  [8:8] : 0    Doorbell Buffer Config Not Supported
  [7:7] : 0    Virtualization Management Not Supported
  [6:6] : 0    NVMe-MI Send and Receive Not Supported
  [5:5] : 0    Directives Not Supported
  [4:4] : 0x1    Device Self-test Supported
  [3:3] : 0    NS Management and Attachment Not Supported
  [2:2] : 0x1    FW Commit and Download Supported
  [1:1] : 0x1    Format NVM Supported
  [0:0] : 0x1    Security Send and Receive Supported

acl       : 7
aerl      : 3
frmw      : 0x16
  [4:4] : 0x1    Firmware Activate Without Reset Supported
  [3:1] : 0x3    Number of Firmware Slots
  [0:0] : 0    Firmware Slot 1 Read/Write

lpa       : 0x3
  [3:3] : 0    Telemetry host/controller initiated log page Not Supported
  [2:2] : 0    Extended data for Get Log Page Not Supported
  [1:1] : 0x1    Command Effects Log Page Supported
  [0:0] : 0x1    SMART/Health Log Page per NS Supported

elpe      : 63
npss      : 4
avscc     : 0x1
  [0:0] : 0x1    Admin Vendor Specific Commands uses NVMe Format

apsta     : 0x1
  [0:0] : 0x1    Autonomous Power State Transitions Supported

wctemp    : 342
cctemp    : 345
mtfa      : 0
hmpre     : 0
hmmin     : 0
tnvmcap   : 128035676160
unvmcap   : 0
rpmbs     : 0
 [31:24]: 0    Access Size
 [23:16]: 0    Total Size
  [5:3] : 0    Authentication Method
  [2:0] : 0    Number of RPMB Units

edstt     : 35
dsto      : 0
fwug      : 0
kas       : 0
hctma     : 0
  [0:0] : 0    Host Controlled Thermal Management Not Supported

mntmt     : 0
mxtmt     : 0
sanicap   : 0
  [31:30] : 0    Additional media modification after sanitize operation completes successfully is not defined
  [29:29] : 0    No-Deallocate After Sanitize bit in Sanitize command Supported
    [2:2] : 0    Overwrite Sanitize Operation Not Supported
    [1:1] : 0    Block Erase Sanitize Operation Not Supported
    [0:0] : 0    Crypto Erase Sanitize Operation Not Supported

hmminds   : 0
hmmaxd    : 0
nsetidmax : 0
anatt     : 0
anacap    : 0
  [7:7] : 0    Non-zero group ID Not Supported
  [6:6] : 0    Group ID does not change
  [4:4] : 0    ANA Change state Not Supported
  [3:3] : 0    ANA Persistent Loss state Not Supported
  [2:2] : 0    ANA Inaccessible state Not Supported
  [1:1] : 0    ANA Non-optimized state Not Supported
  [0:0] : 0    ANA Optimized state Not Supported

anagrpmax : 0
nanagrpid : 0
sqes      : 0x66
  [7:4] : 0x6    Max SQ Entry Size (64)
  [3:0] : 0x6    Min SQ Entry Size (64)

cqes      : 0x44
  [7:4] : 0x4    Max CQ Entry Size (16)
  [3:0] : 0x4    Min CQ Entry Size (16)

maxcmd    : 0
nn        : 1
oncs      : 0x1f
  [7:7] : 0    Verify Not Supported
  [6:6] : 0    Timestamp Not Supported
  [5:5] : 0    Reservations Not Supported
  [4:4] : 0x1    Save and Select Supported
  [3:3] : 0x1    Write Zeroes Supported
  [2:2] : 0x1    Data Set Management Supported
  [1:1] : 0x1    Write Uncorrectable Supported
  [0:0] : 0x1    Compare Supported

fuses     : 0
  [0:0] : 0    Fused Compare and Write Not Supported

fna       : 0
  [2:2] : 0    Crypto Erase Not Supported as part of Secure Erase
  [1:1] : 0    Crypto Erase Applies to Single Namespace(s)
  [0:0] : 0    Format Applies to Single Namespace(s)

vwc       : 0x1
  [0:0] : 0x1    Volatile Write Cache Present

awun      : 255
awupf     : 0
nvscc     : 1
  [0:0] : 0x1    NVM Vendor Specific Commands uses NVMe Format

nwpc      : 0
  [2:2] : 0    Permanent Write Protect Not Supported
  [1:1] : 0    Write Protect Until Power Supply Not Supported
  [0:0] : 0    No Write Protect and Write Protect Namespace Not Supported

acwu      : 0
sgls      : 0
 [1:0]  : 0    Scatter-Gather Lists Not Supported

mnan      : 0
subnqn    : 
ioccsz    : 0
iorcsz    : 0
icdoff    : 0
ctrattr   : 0
  [0:0] : 0    Dynamic Controller Model

msdbd     : 0
ps    0 : mp:7.60W operational enlat:0 exlat:0 rrt:0 rrl:0
          rwt:0 rwl:0 idle_power:- active_power:-
ps    1 : mp:6.00W operational enlat:0 exlat:0 rrt:1 rrl:1
          rwt:1 rwl:1 idle_power:- active_power:-
ps    2 : mp:5.10W operational enlat:0 exlat:0 rrt:2 rrl:2
          rwt:2 rwl:2 idle_power:- active_power:-
ps    3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
          rwt:3 rwl:3 idle_power:- active_power:-
ps    4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
          rwt:4 rwl:4 idle_power:- active_power:-

Kann ich auch einfach -n 0xffffffff aufrufen? Aber damit werden wohl die Daten nicht sicher gelöscht? Vielen Dank

Stefan03

(Themenstarter)

Anmeldungsdatum:
9. April 2011

Beiträge: 27

Ah, mit sudo nvme format /dev/nvme0n1 --ses=1 hat es funktioniert.

Antworten |