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
More a question than an issue. I configured an Opal drive w/sedutil-cli and installed it in the secondary internal drive bay. When I boot the system, the Dell system asks for the password - not the PBA. I can press enter three times, it complains, then proceeds to show me the PBA. I suspect the power-on sequence is activating the Opal drive, which is returning a code to the BIOS that "I am locked," and the BIOS "helpfully" intervenes and asks for the password. I don't want it to do that, I want all passwords to go through my PBA image.
My question is, how can I stop the Dell BIOS from asking for the password, and instead let the PBA handle it? Is it a case of setting the SID and Admin passwords to something different, or is there some flag I can set with sedutil-cli to disable that behavior of the Opal drive, maybe some setting in Samsung Magician, or something else? I'm using a Samsung SSD 980 drive.
The text was updated successfully, but these errors were encountered:
My bad - the shadow MBR was not enabled; therefore, the BIOS decided that intervention was necessary and supplied its own password collector. Pretty helpful to know, in case anyone else runs into this.
More a question than an issue. I configured an Opal drive w/sedutil-cli and installed it in the secondary internal drive bay. When I boot the system, the Dell system asks for the password - not the PBA. I can press enter three times, it complains, then proceeds to show me the PBA. I suspect the power-on sequence is activating the Opal drive, which is returning a code to the BIOS that "I am locked," and the BIOS "helpfully" intervenes and asks for the password. I don't want it to do that, I want all passwords to go through my PBA image.
My question is, how can I stop the Dell BIOS from asking for the password, and instead let the PBA handle it? Is it a case of setting the SID and Admin passwords to something different, or is there some flag I can set with sedutil-cli to disable that behavior of the Opal drive, maybe some setting in Samsung Magician, or something else? I'm using a Samsung SSD 980 drive.
The text was updated successfully, but these errors were encountered: