[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: boot error: zfs + luks + grub

From: James
Subject: Re: boot error: zfs + luks + grub
Date: Mon, 11 Jul 2016 23:17:12 -0400

As an aside, if I manually attempt to unlock one of the ahciX devices it
fails with this error:

grub rescue>
grub rescue> cryptomount ahci5
alloc magic is broken at 0x3ff8e30: 5016608
Aborted. Press any key to exit.FATAL: INT18: BOOT FAILURE

I suspect this is because I no longer have a separate boot partition and
/boot lives in my root ZFS pool. I did, however, think that configuration
this was supported. Am I mistaken?

On Mon, Jul 11, 2016 at 11:07 PM, James <address@hidden> wrote:

> Thanks Andrei -- I sincerely appreciate all of your help.
> I attempted to install grub with the --disk-module=native flag. Here's
> the output:
> error: no device connected.
> error: no device connected.
> error: no device connected.
> error: variable 'prefix' isn't set.
> error: PATA passthrough failed.
> error: no such cryptodisk found.
> Entering rescue mode...
> grub rescue> ls
> (ahci5) (ahci4) (ahci3) (ahci2) (ahci1) (ahci0) (ata2) (proc)
> It seems that grub detects all of the disks when I use the
> --disk-module=native flag, but it does not seem to notice that these
> disks are encrypted.
> I've slightly modified my partition tables to simplify the process, so the
> output from BIS script:
> Hopefully I'm missing something completely obvious.
> On Mon, Jul 11, 2016 at 12:17 PM, Andrei Borzenkov <address@hidden>
> wrote:
>> 11.07.2016 19:01, James пишет:
>> > Andrei,
>> >
>> > Many thanks - this does indeed appear to be the problem.
>> >
>> > grub rescue> ls
>> > (hd0) (hd0,msdos2) (hd0,msdos1) (hd1) (hd1,msdos2) (hd1,msdos1) (hd2)
>> > (hd2,msdos2) (hd2,msdos1) (hd3) (hd3,msdos2) (hd3,msdos1) (crypto3)
>> > (crypto2) (crypto1) (crypto0) (proc)
>> >
>> > I've attached the dmesg output here:
>> >
>> > Any thoughts on why GRUB doesn't see all of the disks?
>> >
>> Because BIOS does not show them. GRUB is using BIOS services by default
>> to access devices so it can see only what BIOS shows. You are better off
>> asking this question on VirtualBox support list.
>> You could try to install GRUB using "grub-install --disk-module=native
>> ...". This will use AHCI driver instead of asking BIOS. It may work,
>> although there were reports that VirtualBox crashes in this case.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]