TrueNAS will drop support of SED (self encrypting drives)

[Jeverett]

Just to update, manually unlocking an SED drive from the command line would be done with a command similar to:
sedutil-cli --setlockingrange 0 rw $SEDPassword $SEDDevice

However, even with hidden SED UI elements, global and individual SED passwords can still easily be set via the command line API, such as:

midclt call system.advanced.update '{"sed_passwd": "<your_SED_password_string>"}' |jq
… for the global SED password.

and

midclt call disk.update "<your_disk_identifer>" '{"passwd": "<your_SED_password_string>"}'
… for an individual drive SED password.

More details (like how to get the disk_identifier) here:

How to manually set up self-encrypted drives (SED)

So, after playing with this a bit, and falling into a crash course in working with the API, I can now attest to the fact that setting SED passwords in the TrueNAS middleware via the API is actually pretty simple – rendering the UI change for SEDs, IMO, not a big deal. Setting system_advanced | adv_sed_password – i.e. the Global SED password – via the API is as simple as, dropping to a shell, and using these commands: midclt call system.advanced.sed_global_password_is_set midclt call system.ad…