nvme-cli prefers drives to have no partition table.
If partition table was present before wipe, after the wipe is done it might trigger error or warning for failing to update kernel with new partition table data.
It could be beneficial to clear partition tables and flush write buffers before using nvme-cli.
Please note that GPT partition tables also reside (as backup copy) at end of drive.
Some older nvme devices have hard-coded limits on number of secure erase rounds and when that count is used-up device can only do non-secure erase.
Hello,
Recent discovery:
nvme-cli prefers drives to have no partition table.
If partition table was present before wipe, after the wipe is done it might trigger error or warning for failing to update kernel with new partition table data.
It could be beneficial to clear partition tables and flush write buffers before using nvme-cli.
Please note that GPT partition tables also reside (as backup copy) at end of drive.
Some older nvme devices have hard-coded limits on number of secure erase rounds and when that count is used-up device can only do non-secure erase.
Found this while looking for the limit - hope it helps: /www.nvmedevelo perdays. com/English/ Collaterals/ Proceedings/ 2018/20181204_ PRECON2_ Hands.pdf
https:/
Regards,
Igor