How can I enable hardware encryption on a Samsung 980 Pro

[gctwnl]

I am using a NUC10i5FNHN2 with proxmox installed (virtualisation solution based on a Debian Linux). I need to enable the hardware encyption (that is: use a password of the built-in hardware encryption) of my OPAL-compatible Samsung 980 Pro.

The BIOS recognises that Samsung and that it can be secured. But whatever I try, I am unable to get the BIOS to tell me the encryption is turned on.

I have a set a User Password and a HDD Master Password.

What can I do to get this working? I also have installed sedutil on proxmox's Debian, but the exact way to use that is unclear to me.

[AlHill]

Sounds like a good question for....  SAMSUNG.

Doc (not an Intel employee or contractor)
[Maybe Windows 12 will be better]

[gctwnl]

No, this is not a good question for Samsung. The question is about the BIOS of the Intel NUC. It has all kinds of options to set passwords and they do not work. The drive itself is OPAL compatible and works with this kind of encryption with many systems. The question is: how do I use the BIOS on my Intel NUC to set (and use) a boot drive password.

So, if I ask Samsung, they will direct me — and rightly so — to Intel (or AMI)

[gctwnl]

Maybe I should have simply asked: where can I find good instructions for setting up pre-boot authorisation in the BIOS of my NUC?

[gctwnl · Accepted solution]

OK, I was able to do this.

I first updated the BIOS to  the latest version (0058).

Then instead of trying to use the mouse pointer in the BIOS interface (I used to click on menu elements), I used arrow-up/arrow-down until I got the User Password entry of the HDD menu for this drive. When I entered return, I was able to set a password on the drive and this is now asked during boot.

The text in the BIOS says that if "Set User Password" is greyed out, you need to boot. But it seems that "greyed out" also is what you see when it is the currently selected element. A bit confusing. I do not know if the BIOS update was really necessary as it might have been simple BIOS UI confusion in the previous version anyway.