Hi Tomas,
Tomas Volf <[email protected]> skribis:
> Yeah, it is for my storage drives, so the message is printed ten times,
> once for every disk. That is where my confusion stems from. GRUB does
> not touch these disks at all, they do not participate in the boot
> process. So I am confused how would GRUB be able to provide
> instructions to unlock them.
>
> Relevant parts of my configuration are:
>
> --8<---------------cut here---------------start------------->8---
> (define %storage-disks-mapped-devices
> (map (match-lambda
> ((disk/name . disk/uuid)
> (mapped-device
> (source (uuid disk/uuid))
> (target disk/name)
> (type luks-device-mapping)
> (arguments (list #:key-file "xxCENSOREDxx")))))
> '(("storage01" . "xxCENSOREDxx")
> ("storage02" . "xxCENSOREDxx")
> ("storage03" . "xxCENSOREDxx")
> ("storage04" . "xxCENSOREDxx")
> ("storage05" . "xxCENSOREDxx")
> ("storage06" . "xxCENSOREDxx")
> ("storage07" . "xxCENSOREDxx")
> ("storage08" . "xxCENSOREDxx")
> ("storage09" . "xxCENSOREDxx")
> ("storage10" . "xxCENSOREDxx"))))
> --8<---------------cut here---------------end--------------->8---
Oh I see. The /etc/luks_script logic should definitely be skipped in
this case.
[...]
> I *think* just swapping order in mapped-devices.scm (to try keyfile
> first) should solve my problem. I will try whether that works and if it
> does, send a patch.
Cool, thanks!
Ludo’.
