Stephan Schindel s...@tp1.rub.de wrote:
i've got a problem attaching a geli device on boot. My setup:
ada0 and ada1 full geli setup (no partition schemes). ZFS on both. ada0
is my root device. I can boot into the system there is no problem with
it. But now I want to attach ada1 on boot as
Thank you for your answer.
Are you sure that It is the geli rc script and not the kernel
itself which could happen if the BOOT flag was set on ada1.
I tried (un)setting the BOOT flag. With boot flag no key files are
defined in loader.conf, which is fine:
ada1 at ata5 bus 0 scbus5 target 0
This is the output at boot time:
Configuring Disk Encryption for ada1.
geli: Cannot read metadata from ada1: Inappropriate file type or format.
Attach failed; attempt 1 of 3.
...
And the Configuring... part is from /etc/rc.d/geli. One the system is
ready the same attempt works fine:
OK I found the issue:
I reinitialized the provider, same problem. Then I put a partition
scheme (BSD) on it here it works fine. My guess is this is not
intended and might be a bug. Geli should work fine for the whole disk
(no scheme at all). It works fine for the root device, but fails when
