You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to use a Samsung PM981 NVME disk MZVLB512HAJQ-000L7 - which it seems I can not PSID revert it.
It was used in a notebook where an encryption password was set and the password was forgotten, there is no important data on it so it can safely be cleared.
According to linux/PSIDRevert_LINUX.txt the verbose output should be given, so here it is.
Interestingly, an user told in issue #241 that it worked for exactly this drive, with exact the same firmware that my drive has.
So I am wondering, why it does not work for me?
# uname -a
Linux 5.15.143-1-pve #1 SMP PVE 5.15.143-1 (2024-02-08T18:12Z) x86_64 GNU/Linux
# chmod 0744 /sys/module/libata/parameters/allow_tpm
# echo "1" > /sys/module/libata/parameters/allow_tpm
-bash: echo: write error: Input/output error
# # I booted with 'libata.allow_tpm=1' but since it is a nvme drive, I guess libata is not required and allow_tpm setting not relevant?
dmesg:
# dmesg | grep -i nvme
[ 3.260904] nvme nvme0: pci function 0000:01:00.0
[ 3.273690] nvme nvme0: Shutdown timeout set to 8 seconds
[ 3.281492] nvme nvme0: 4/0/0 default/read/poll queues
[ 3.301677] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.301714] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.313760] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.313789] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.325857] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.325868] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.337860] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.337869] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.349858] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.349868] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.362072] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.362100] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.374158] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.374170] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.374183] Dev nvme0n1: unable to read RDB block 0
[ 3.386442] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.386488] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.399463] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.399495] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 3.412463] blk_update_request: operation not supported error, dev nvme0n1, sector 24 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3.412496] Buffer I/O error on dev nvme0n1, logical block 3, async page read
[ 3.439027] nvme0n1: unable to read partition table
[ 17.155978] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
[ 18.210268] blk_update_request: operation not supported error, dev nvme0n1, sector 1000215040 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 18.222473] blk_update_request: operation not supported error, dev nvme0n1, sector 1000215040 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 18.222511] Buffer I/O error on dev nvme0n1, logical block 125026880, async page read
[ 19.316536] blk_update_request: operation not supported error, dev nvme0n1, sector 32 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
[ 19.318519] blk_update_request: operation not supported error, dev nvme0n1, sector 32 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0
[ 19.340542] blk_update_request: operation not supported error, dev nvme0n1, sector 544 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 19.342520] blk_update_request: operation not supported error, dev nvme0n1, sector 544 op 0x0:(READ) flags 0x0 phys_seg 3 prio class 0
[ 19.364646] blk_update_request: operation not supported error, dev nvme0n1, sector 1000214048 op 0x0:(READ) flags 0x0 phys_seg 5 prio class 0
[ 19.366649] blk_update_request: operation not supported error, dev nvme0n1, sector 1000214048 op 0x0:(READ) flags 0x0 phys_seg 6 prio class 0
[ 19.388727] blk_update_request: operation not supported error, dev nvme0n1, sector 1000214560 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0
[ 2914.791955] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 2914.804616] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2914.804657] Buffer I/O error on dev nvme0n1, logical block 0, async page read
[ 2914.817533] blk_update_request: operation not supported error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2914.817555] Buffer I/O error on dev nvme0n1, logical block 0, async page read
# fdisk -l /dev/nvme0n1
fdisk: cannot open /dev/nvme0n1: Input/output error
smartctl:
# smartctl -A /dev/nvme0
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.143-1-pve] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF SMART DATA SECTION ===
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 32 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 7,438,046 [3.80 TB]
Data Units Written: 6,901,530 [3.53 TB]
Host Read Commands: 122,576,562
Host Write Commands: 121,248,668
Controller Busy Time: 536
Power Cycles: 840
Power On Hours: 542
Unsafe Shutdowns: 209
Media and Data Integrity Errors: 0
Error Information Log Entries: 878
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 32 Celsius
Temperature Sensor 2: 39 Celsius
# fdisk -l /dev/nvme0n1
fdisk: cannot open /dev/nvme0n1: Input/output error
sedutil scan:
# ./sedutil-cli --scan
Scanning for Opal compliant disks
/dev/nvme0 2 SAMSUNG MZVLB512HAJQ-000L7 4L2QEXA7
The Kernel flag libata.allow_tpm is not set correctly
Please see the readme note about setting the libata.allow_tpm
/dev/sda No SanDisk SSD PLUS 2000GB UP4504RL
The Kernel flag libata.allow_tpm is not set correctly
Please see the readme note about setting the libata.allow_tpm
/dev/sdb No SanDisk SSD PLUS 2000GB UP4504RL
No more disks present ending scan
sedutil query:
# ./sedutil-cli --query /dev/nvme0
/dev/nvme0 NVMe SAMSUNG MZVLB512HAJQ-000L7 4L2QEXA7 S3TNNF0K477440
TPer function (0x0001)
ACKNAK = N, ASYNC = N. BufferManagement = N, comIDManagement = N, Streaming = Y, SYNC = Y
Locking function (0x0002)
Locked = N, LockingEnabled = N, LockingSupported = Y, MBRDone = N, MBREnabled = N, MBRAbsent = N, MediaEncrypt = Y
Geometry function (0x0003)
Align = Y, Alignment Granularity = 8 (4096), Logical Block size = 512, Lowest Aligned LBA = 0
DataStore function (0x0202)
Max Tables = 9, Max Size Tables = 10485760, Table size alignment = 1
OPAL 2.0 function (0x0203)
Base comID = 0x1004, Initial PIN = 0x00, Reverted PIN = 0x00, comIDs = 1
Locking Admins = 4, Locking Users = 9, Range Crossing = N
Block SID Authentication function (0x0402)
SID Blocked State = N, SID Value State = N, Hardware Reset = N
Namespace function (0x0403)
Maximum Key Count = 9, Unused Key Count = 8, Maximum Ranges Per Namespace = 8
TPer Properties:
MaxComPacketSize = 66048 MaxResponseComPacketSize = 66048
MaxPacketSize = 66028 MaxIndTokenSize = 65540 MaxPackets = 1
MaxSubpackets = 1 MaxMethods = 1 MaxAuthentications = 5
MaxSessions = 1 MaxTransactionLimit = 1 DefSessionTimeout = 0
Host Properties:
MaxComPacketSize = 2048 MaxResponseComPacketSize = 2048
MaxPacketSize = 2028 MaxIndTokenSize = 1992 MaxPackets = 1
MaxSubpackets = 1 MaxMethods = 1
The Kernel flag libata.allow_tpm is not set correctly
It's not clear whether you set the kernel parameter or not. It is relevant (its name is misnomer some not especially bright Linux developer came up with).
Trying to use a Samsung PM981 NVME disk
MZVLB512HAJQ-000L7
- which it seems I can not PSID revert it.It was used in a notebook where an encryption password was set and the password was forgotten, there is no important data on it so it can safely be cleared.
According to linux/PSIDRevert_LINUX.txt the verbose output should be given, so here it is.
Interestingly, an user told in issue #241 that it worked for exactly this drive, with exact the same firmware that my drive has.
So I am wondering, why it does not work for me?
dmesg:
smartctl:
but still:
sedutil scan:
sedutil query:
verbose output:
The text was updated successfully, but these errors were encountered: