Endless NVMe Sanitize Block Erase

[kersh1337228]

I have an INTEL SSDPEKNW010T8 M.2 NVMe SSD in my laptop. I wanted to securely erase it so I launched sanitize with block erase action A WEEK AGO (23-12-2025) using:

$ nvme sanitize -a 2 /dev/nvme0n1

and it's still in progress.
Here is a sanitize log which is always the same since the moment I issued a sanitize (30-12-2025):

$ nvme sanitize-log /dev/nvme0n1

Sanitize Progress                      (SPROG) :  655
Sanitize Status                        (SSTAT) :  0x2
Sanitize Command Dword 10 Information (SCDW10) :  0x2
Estimated Time For Overwrite                   :  4294967295 (No time period reported)
Estimated Time For Block Erase                 :  4294967295 (No time period reported)
Estimated Time For Crypto Erase                :  4294967295 (No time period reported)
Estimated Time For Overwrite (No-Deallocate)   :  0
Estimated Time For Block Erase (No-Deallocate) :  0
Estimated Time For Crypto Erase (No-Deallocate):  0
Estimated Time For Post-Verification Deallocation:  0
Sanitize State Information               (SSI) : 0

no error messages were produced.
I also tried to abort this operation using

$ nvme admin-passthru /dev/nvme0n1 -O 0x08h

Admin Command Abort is Success and result: 0x00000001

and

$ nvme reset /dev/nvme0
$ echo $?

0

and also

$ nvme sanitize -a 1 /dev/nvme0n1

NVMe status: Sanitize In Progress: The requested function is prohibited while a sanitize operation is in progress(0x1d)

I tried to reboot the system, tried to issue the same commands from another system booted -- no changes.

[ikegami-t]

Looks the issue caused by the drive behavior but not nvme-cli itself so probably you need to ask this to the drive vendor I think.
Note: The admin command abort by admin-passthru was not performed for the sanitize command as the result was 0x00000001 since already the sanitize command itself completed to start the sanitization and CID is not specified then 0 was used.

[kersh1337228]

After plugging it out and in several times it finally shows:

$ nvme sanitize-log /dev/nvme0n1

Sanitize Progress                      (SPROG) :  65535
Sanitize Status                        (SSTAT) :  0x101
Sanitize Command Dword 10 Information (SCDW10) :  0x2
Estimated Time For Overwrite                   :  4294967295 (No time period reported)
Estimated Time For Block Erase                 :  4294967295 (No time period reported)
Estimated Time For Crypto Erase                :  4294967295 (No time period reported)
Estimated Time For Overwrite (No-Deallocate)   :  0
Estimated Time For Block Erase (No-Deallocate) :  0
Estimated Time For Crypto Erase (No-Deallocate):  0
Estimated Time For Post-Verification Deallocation:  0
Sanitize State Information               (SSI) : 0

So the issue is resolved.

P.S. It seems to me that the cause of this problem was that M.2 fixing screw was not tightened enough.