From: Ondrej Kozina <okozina@redhat.com>
To: Cryptsetup <cryptsetup@lists.linux.dev>
Cc: Nikolai Grigoriev <nikolai@grigr.xyz>
Subject: Re: OPAL setup for a new drive without sedutil initial setup
Date: Mon, 18 Mar 2024 14:45:29 +0100 [thread overview]
Message-ID: <186111b2-f007-4812-8c62-0a8676d9528c@redhat.com> (raw)
In-Reply-To: <NtGgb5H--3-9@grigr.xyz>
On 18/03/2024 14:13, Nikolai Grigoriev wrote:
> I tried to enter a password expecting it to become my new Admin1 password. That did not work. The message was something like "Invalid Admin1 password or permission denied". I ran it with "--hw-opal-only" against /dev/nvme0n1p3. The drive us brand-new Crucial T500 2Tb. Never used sedutil on it. I will try sedutil now to see what is going on and to set my password.
Well, sedutils will ask for the Admin1 pin as well before it can report
anything interesting (e.g.: list existing/active locking ranges).
Feel free to open an issue on upstream tracker:
https://gitlab.com/cryptsetup/cryptsetup/-/issues, just add --debug
parameter in luksFormat command.
Also the device model would be nice to further debug the issue provided
it's this very device it does not work with (e.g. "nvme list" command
output)
Kind regards
O.
next prev parent reply other threads:[~2024-03-18 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 2:21 OPAL setup for a new drive without sedutil initial setup Nikolai Grigoriev
2024-03-18 8:36 ` Ondrej Kozina
[not found] ` <c238a50b-e382-4dec-9b4b-9c33e420b541@redhat.com-NtFh9t5--7-9>
2024-03-18 13:13 ` Nikolai Grigoriev
2024-03-18 13:45 ` Ondrej Kozina [this message]
2024-03-19 0:14 ` Nikolai Grigoriev
[not found] ` <NtJ2omI--3-9@grigr.xyz-NtJ2rJc--N-9>
2024-03-21 21:55 ` Nikolai Grigoriev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=186111b2-f007-4812-8c62-0a8676d9528c@redhat.com \
--to=okozina@redhat.com \
--cc=cryptsetup@lists.linux.dev \
--cc=nikolai@grigr.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).