Github messages for voidlinux
 help / color / mirror / Atom feed
From: g4s8 <g4s8@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] XBPS doesn't fail kernel installation if post-install kernel hook failed
Date: Thu, 02 Feb 2023 23:18:25 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42047@inbox.vuxu.org> (raw)

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

New issue by g4s8 on void-packages repository

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

Description:
The problem: I updated kernel version, it successfully generated initramfs using drakut and copied kernel vmlinuz file to boot partition but failed to copy initramfs due to "No space left on device" error. Then xbps continued to execute configuration hooks and generated new grub config. Grub has found vmlinux file for new kernel, so it generated new entry for this version. But during boot initramfs was not found, so boot failed with kernel panic.

I'm suggesting to stop configuration execution if any hook fails and skip other hooks to avoid it.

xbps log:
```
[*] Configuring unpacked packages
linux6.1-6.1.7_1: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: wireguard-1.0.20220627.
Building DKMS module: wireguard-1.0.20220627... skipped!
Generating kernel module dependency lists... done.
Executing post-install kernel hook: 10-mount ...
INFO: boot already mounted
Executing post-install kernel hook: 20-dracut ...
cp: error writing '/boot/initramfs-6.1.7_1.img': No space left on device
dracut: Creation of /boot/initramfs-6.1.7_1.img failed
Executing post-install kernel hook: 50-efibootmgr ...
Executing post-install kernel hook: 50-grub ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.7_1
Found initrd image: /boot/early_ucode.cpio
Found linux image: /boot/vmlinuz-6.1.3_1
Found initrd image: /boot/early_ucode.cpio /boot/initramfs-6.1.3_1.img
Found linux image: /boot/vmlinuz-5.16.20_1
Found initrd image: /boot/early_ucode.cpio
Found linux image: /boot/vmlinuz-5.16.16_1
Found initrd image: /boot/early_ucode.cpio /boot/initramfs-5.16.16_1.img
Found linux image: /boot/vmlinuz-5.16.7_1
Found initrd image: /boot/early_ucode.cpio
Found linux image: /boot/vmlinuz-5.15.82_1
Found initrd image: /boot/early_ucode.cpio
Found linux image: /boot/vmlinuz-5.4.66-gentoo-x86_64
Found initrd image: /boot/early_ucode.cpio /boot/initramfs-5.4.66-gentoo-x86_64.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
Executing post-install kernel hook: 99-umount ...
INFO: skip boot umount
linux6.1-6.1.7_1: installed successfully.
```

             reply	other threads:[~2023-02-02 22:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 22:18 g4s8 [this message]
2023-02-02 22:19 ` Duncaen
2023-05-04  1:51 ` github-actions
2023-05-12  9:49 ` g4s8
2023-05-25 18:42 ` 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42047@inbox.vuxu.org \
    --to=g4s8@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).