Github messages for voidlinux
 help / color / mirror / Atom feed
From: aNTDwcDqvXR4h2PH <aNTDwcDqvXR4h2PH@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] XBPS ordering problem with ZFS (root on zfs)
Date: Mon, 17 Jun 2024 12:00:25 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50859@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2662 bytes --]

New issue by aNTDwcDqvXR4h2PH on void-packages repository

https://github.com/void-linux/void-packages/issues/50859

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.33_1 x86_64 AuthenticAMD notuptodate rF

### Package(s) Affected

zfs-2.2.4_2, xbps-0.59.2_3, linux-6.6_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

I am aware that the issue was discussed in #22817 however this issue is related to the same problem but different.

### Expected behaviour

If I remember correctly on fresh install xbps does the following:
1. Download/verify packages
2. Extract packages
3. Build DKMS
4. Include DKMS in kernel
5. Generate initramfs

### Actual behaviour

Issue begins when you have 2 kernel versions and update system with `xbps-install -Su`

What happens:
1. `xbps` downloads/verifies packages
2. `xbps` extracts some packages
2.1. When zfs package is extracted `xbps` doesn't build DKMS and runs `dracut`
2.2. `dracut` shows error about missing zfs module
2.3. Rest of the packages is extracted
3. DKMS is built.
4. initramfs is generated without zfs kernel module.

Note: I'm not entirely sure if zfs module is missing in newest kernel or all of them.

### Steps to reproduce

1. Follow zfsbootmenu installation guide: https://docs.zfsbootmenu.org/en/v2.3.x/guides/void-linux/uefi.html
1.1. Set up: Single SATA Disk, Encrypted (I only omitted "-o compatibility"), zfsbootmenu package, refind in `/boot/efi/EFI/BOOT`
2. Setup Xorg, dwm, startx, zsh, apparmor (complain mode) and some other packages.
2.1. Right now there should be only one kernel version.
3. Wait for new kernel version.
4. Update system with `xbps-install -Su`
4.1. Now there should be 2 kernel versions.
5. See step 3.
6. See step 4.
6.1. Now there should be 3 kernel versions and the isssue should occur.
6.2. Dracut will run too soon and not include zfs module.

You can however mitigate this issue if you run `xbps-reconfigure -f zfs` after step 6.2. 

## System information:
### Users:
  - root
  - user

### ZFS pool
```
NAME                     USED  AVAIL  REFER  MOUNTPOINT
zroot                   7.39G   892G   192K  none
zroot/DATA              1.32G   892G   192K  none
zroot/DATA/home         1.32G   892G  1.32G  /home
zroot/DATA/root          480K   892G   480K  /root
zroot/ROOT              6.07G   892G   192K  none
zroot/ROOT/void         4.22G   892G  4.22G  /
zroot/ROOT/void-backup  1.85G   892G  1.85G  /
```
Note: This affects all my installations that have multiple kernel versions

### Kernel
- zbm-kcl: quiet apparmor=1 security=apparmor


             reply	other threads:[~2024-06-17 10:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 10:00 aNTDwcDqvXR4h2PH [this message]
2024-06-17 13:47 ` XBPS ordering problem with ZFS and multiple kernel versions " classabbyamp
2024-06-17 15:27 ` ahesford
2024-06-17 18:07 ` aNTDwcDqvXR4h2PH
2024-06-17 18:12 ` aNTDwcDqvXR4h2PH
2024-06-30 14:27 ` aNTDwcDqvXR4h2PH
2024-06-30 14:28 ` [ISSUE] [CLOSED] " aNTDwcDqvXR4h2PH
2024-07-01  9:05 ` aNTDwcDqvXR4h2PH

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50859@inbox.vuxu.org \
    --to=antdwcdqvxr4h2ph@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).