Re: boot error: zfs + luks + grub

[Andrei Borzenkov]

18.06.2016 01:03, James пишет:
> Thanks Andrei, this helped. I rebuilt my initramfs and updated grub.
> Definitely a step in the right direction.
> 
> Now when I reboot my system GRUB will prompt me for a master key. I provide
> the password and successfully unlock (presumably) one of the crypto disks.
> 
> It then prompts me for another password. It says that it opens slot 0, but
> then GRUB immediately fails.
> 
> Please see attached screenshot.
> 
> Any thoughts on why this is happening?
> 

Not really. When you run grub-install, it creates
/boot/grub/i386-pc/load.cfg (I assume you are using legacy BIOS
platform; substitute for x86_64-efi otherwise) that is then enbedded in
core.img. Could you post content of this file? Alternatively, if you are
using legacy BIOS, could you run
https://github.com/arvidjaar/bootinfoscript and make results available?

> On Wed, Jun 15, 2016 at 11:28 PM, Andrei Borzenkov <address@hidden>
> wrote:
> 
>> 16.06.2016 00:52, James пишет:
>>> Hello,
>>>
>>> Hoping to get some help with a (seemingly basic) setup I'm struggling
>> with.
>>>
>>> I'm using Ubuntu Xenial (16.04) and installing on ZFS on LUKS which, as
>> far
>>> as I have read, is supported. A reboot after going through the
>> installation
>>> process results in an ugly error:
>>>
>>> error: no such cryptodisk found.
>>> Entering rescue mode...
>>> grub rescue>
>>>
>> ...
>>
>>>
>>> # cat /etc/default/grub
>>> GRUB_DEFAULT=0
>>> GRUB_HIDDEN_TIMEOUT=0
>>> GRUB_HIDDEN_TIMEOUT_QUIET=true
>>> GRUB_TIMEOUT=10
>>> GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
>>> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
>>> GRUB_CMDLINE_LINUX=""
>>>
>>
>> For historical reasons grub does not add support for cryptodisk unless
>>
>> GRUB_ENABLE_CRYPTODISK=y
>>
>> is present. Please add it and re-run grub-install and grub-mkconfig.
>>
>> I begin to think that at least grub-install should unconditionally probe
>> for cryptodisk.
>>
>>
>