Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk no more recognized as opal compliant under Windows #423

Open
RiantAnda opened this issue Jan 26, 2023 · 0 comments
Open

Disk no more recognized as opal compliant under Windows #423

RiantAnda opened this issue Jan 26, 2023 · 0 comments

Comments

@RiantAnda
Copy link

I'm using a Seagate ST16000NM003G-2KH113 disk with sedutil.
Around end of 2020, it was no problem to unlock this disk under Windows 10 and Linux.
I have been using Linux exclusively since then without issues, but found out just now, that I'm no more able to unlock the disk under Windows 10.

Here is a comparison of the --scan command
Linux:
Scanning for Opal compliant disks
/dev/nvme0 2 Samsung SSD 970 EVO Plus 2TB 2B2QEXM7
/dev/sda No Samsung SSD 840 PRO Series DXM06B0Q
/dev/sdb E ST16000NM003G-2KH113 SS02
No more disks present ending scan
Windows:
Scanning for Opal compliant disks
\\.\PhysicalDrive0 No Samsung SSD 840 PRO Series DXM06B0Q
\\.\PhysicalDrive1 No ST16000NM003G-2KH113 SS02
\\.\PhysicalDrive2 No
No more disks present ending scan

My M2 SSD isn't recognized at all, which is not a problem.
But why is the ST16000NM003G-2KH113 listed as 'No' under windows, when it is properly recognized under Linux?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant