From: Jipok <Jipok@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] "linux6.5: configured successfully" without initramfs
Date: Sun, 10 Sep 2023 19:18:41 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46006@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3203 bytes --]
New issue by Jipok on void-packages repository
https://github.com/void-linux/void-packages/issues/46006
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_1 x86_64 GenuineIntel uptodate rrFFF
### Package(s) Affected
linux6.5-6.5.2_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
It must either build successfully or fail without initramfs.
### Actual behaviour
After update my server couldn't boot due to missing initramfs. How can it be "configured successfully." with such a fatal error?
You can't expect the user to meaningfully review every line of logs for every update.
```
xbps-install -S linux6.5-6.5.2_1 linux6.5-headers-6.5.2_1
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/nonfree/x86_64-repodata' ...
Name Action Version New version Download size
linux6.5 install - 6.5.2_1 -
linux6.5-headers install - 6.5.2_1 -
Size required on disk: 206MB
Space available on disk: 16GB
Do you want to continue? [Y/n]
[*] Verifying package integrity
linux6.5-6.5.2_1: verifying RSA signature...
linux6.5-headers-6.5.2_1: verifying RSA signature...
[*] Collecting package files
linux6.5-6.5.2_1: collecting files...
linux6.5-headers-6.5.2_1: collecting files...
[*] Unpacking packages
linux6.5-6.5.2_1: unpacking ...
linux6.5-headers-6.5.2_1: unpacking ...
[*] Configuring unpacked packages
linux6.5-6.5.2_1: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: zfs-2.1.12.
Building DKMS module: zfs-2.1.12... FAILED!
Generating kernel module dependency lists... done.
Executing post-install kernel hook: 20-initramfs ...
dracut-install: Failed to find module 'zfs'
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.RJG7bp/initramfs --kerneldir /lib/modules/6.5.2_1/ -m zfs
dracut: installkernel failed in module zfs
Executing post-install kernel hook: 50-bootsize ...
Executing post-install kernel hook: 50-efibootmgr ...
Executing post-install kernel hook: 50-grub ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.5.2_1
Found linux image: /boot/vmlinuz-6.4.15_1
Found initrd image: /boot/initramfs-6.4.15_1.img
Found linux image: /boot/vmlinuz-6.3.13_1
Found initrd image: /boot/initramfs-6.3.13_1.img
Found linux image: /boot/vmlinuz-6.1.51_1
Found initrd image: /boot/initramfs-6.1.51_1.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
linux6.5-6.5.2_1: installed successfully.
linux6.5-headers-6.5.2_1: configuring ...
linux6.5-headers-6.5.2_1: installed successfully.
0 downloaded, 2 installed, 0 updated, 2 configured, 0 removed.
```
### Steps to reproduce
Just install linux6.5 with zfs.
next reply other threads:[~2023-09-10 17:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 17:18 Jipok [this message]
2023-09-10 18:47 ` dkwo
2023-09-10 19:04 ` classabbyamp
2023-09-10 22:07 ` Jipok
2023-09-16 15:19 ` ahesford
2023-09-16 15:19 ` [ISSUE] [CLOSED] " ahesford
2023-09-16 16:13 ` Jipok
2023-09-16 16:21 ` ahesford
2023-09-16 16:48 ` Jipok
2023-09-16 16:56 ` classabbyamp
2023-09-16 16:56 ` ahesford
2023-09-16 17:01 ` Duncaen
2023-09-16 17:09 ` Jipok
2023-09-16 17:15 ` ahesford
2023-09-16 18:11 ` Duncaen
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-46006@inbox.vuxu.org \
--to=jipok@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).