From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zfs 0.8.3_2, linux5.5 may fail to boot with encryption (tracking issue)
Date: Tue, 07 Apr 2020 05:02:00 +0200 [thread overview]
Message-ID: <20200407030200.wVj2jaEQoahFm4HUgl58TTo9YEpDiS4kdBkzE4je9Yo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20711@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/20711#issuecomment-610146442
Comment:
Looks like this may have been a fluke... some testing shows that removing and reinstalling `zfs` (after trying a few modified versions of the package) eliminated the problem on a system known to demonstrate the problem earlier. I suspect `dracut` was not pulling the ZFS kernel modules into the initramfs during `xbps-reconfigure` but have no proof yet.
I'll try to get a little more information from the original reporter before closing this issue.
next prev parent reply other threads:[~2020-04-07 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 0:35 [ISSUE] " ahesford
2020-04-07 3:02 ` ahesford [this message]
2020-04-07 15:29 ` ahesford
2020-04-07 15:29 ` [ISSUE] [CLOSED] " ahesford
2020-04-07 15:29 ` ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200407030200.wVj2jaEQoahFm4HUgl58TTo9YEpDiS4kdBkzE4je9Yo@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).