On November 3, 2014 9:36:49 AM EST, Michael Biebl <bi...@debian.org> wrote:
>Am 03.11.2014 um 15:06 schrieb John Holland:
>> It seems like it is unable to mount a zfs volume given in fstab
>during boot. Strangely the presence of such an entry in fstab also
>seems to cause the password entry problem. With no zfs in fstab I can
>enter the passwords and the zfs volumes with non legacy mount points
>mount ok.
>> It sounds like maybe I need to try a Plymouth theme as well as just
>plymouth as I do not get a graphical start screen. However if a fix is
>coming for systemd maybe I should wait for that to see if it clears it
>up.
>>
>> On November 3, 2014 8:09:44 AM EST, "Zbigniew Jędrzejewski-Szmek"
><zjedr...@gmu.edu> wrote:
>>> On Mon, Nov 03, 2014 at 05:51:57AM -0500, John Holland wrote:
>>>> I created luks volumes, installed zfsonlinux.org packages, created
>a
>>> zpool out of the luks volumes. When ZFS is managing the mounting of
>the
>>> fs's it works. If I put a zfs filesystem in /etc/fstab the prompts
>to
>>> enter passwords for the luks volumes during boot are mixed in with
>>> output.
>>>
>>> So actually its not the ZFS volumes, but simply the luks unlocking
>that
>>> is the problem?
>>> You say that the prompts are mixed with output, but do things work
>if
>>> you type in
>>> the password "blind"?
>>>
>>> You can either wait until systemd-217 (which fixes the overlapping
>>> output) or install
>>> plymouth (which provides a graphical prompt which is not interrupted
>by
>>> text output).
>>
>
>http://changelog.complete.org/archives/9241-update-on-the-systemd-issue
>might be relevant for you.
>--
>Why is it that all of the instruments seeking intelligent life in the
>universe are pointed away from Earth?
