On 10/7/25 06:21, Greg wrote:
On 2025-10-06, David Christensen <dpchrist@holgerdanske.com> wrote:
I tried with only two computers and still am not certain if it was a
bug, a feature, or PEBKAC. Look up the SED standards if it matters.
I did a little bit, and you'd need to reveal at least the drive model,
how it was locked, the OS on the target computer, and maybe something I
haven't thought of in order to eliminate the uncertainty.
Computer #1: Intel DQ67SW motherboard
Computer #2: Dell Latitude E6520
SSD: Intel SSD 520 Series
https://www.dell.com/community/en/conversations/locked-topics-laptops-
general/hdd-ata-password-via-bios-same-hdd-but-pw-doesnt-work-in-new-
dell/647f16f9f4ccf8a8de9a6cf7?utm
So, my experience was not unique.
I am curious what happens when a password protected SED is moved to
another computer of the same make, model, and BIOS/UEFI version.
That's all I could find after a cursory examination of the Net. I don't
know whether you've said exactly what occurs when unlocking the drive
fails
on computer #2; are you prompted for a password? I guess you are and
it fails to unlock the drive.
I forget the POST console session details. The bottom line is that the
SED would not unlock in the other computer, so it would not boot or run.
You've tried on two computers. Are they both Dells?
#2 is a Dell. #1 is a retail box Intel motherboard.
David