System Nuked itself after upgrade (Missing Boot Image)

Seems so, but at the same time, it doesn't yet look like it's actually in the Arch Linux official repos, testing maybe?
My systems, that are currently up-to-date, still have mkinitcpio-install and mkinitcpio-remove scripts individually.

Definitely would need to promptly, immediately, checking old vs new, to insure a seamless crossover.

1 Like

You're definitely right, the commit is after the latest package update...
Sometimes when I start with an idea in my head I stop thinking :wink:

Well, for the mkinitcpio-{install,remove} hook issue, I have a merge-request in:

3 Likes

Even still, it's a good catch, and we get an early path to keep this from being a Garuda problem. :slight_smile:

2 Likes

Can you also now provide the output you get from:

ls -l /usr/share/libalpm/scripts/

Yes, here is the output.

==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 6.0.2-zen1-1-zen
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Starting build: 6.0.2-zen1-1-zen
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen-fallback.img
==> Image generation successful

It only works because I manually backed up the linux-zen.preset file and placed it back after the upgrade, and it only builds for 6.0.2 instead of 6.0.7. I manually passed the -k flag to try and build from 6.0.7, but when i tried to boot that image my computer locked. Heres an output of ls /usr/lib/modules:

drwxr-xr-x - root 17 Oct 19:41  .old
drwxr-xr-x - root  9 Nov 21:54  6.0.2-zen1-1-zen
drwxr-xr-x - root  9 Nov 22:47  6.0.7-arch1-1
drwxr-xr-x - root  9 Nov 23:56  6.0.7-zen1-1-zen

and /etc/mkinitcpio.d:

λ ls /etc/mkinitcpio.d/
.rw-r--r-- 391 root  9 Nov 22:01  linux-zen.preset

Here's what that looks like:

.rwxr-xr-x  207 root 21 Oct 11:15  40-fontconfig-config
.rwxr-xr-x  103 root 12 Mar  2021  dconf-update
.rwxr-xr-x  350 root  1 Nov 06:46  depmod
.rwxr-xr-x 1.3k root 29 May 02:49  detect-old-perl-modules.sh
.rwxr-xr-x 8.7k root  6 Nov 02:23  dkms
.rwxr-xr-x 6.3k root  9 Nov 17:18  garuda-hooks-runner
.rwxr-xr-x 4.2k root  4 Sep 14:16  garuda-migrations-runner
.rwxr-xr-x  128 root 25 Oct 07:19  gio-querymodules
.rwxr-xr-x  131 root 25 Oct 07:22  gio-querymodules-32
.rwxr-xr-x  233 root 15 Apr 08:56  grub-initrd-generation-fix
.rwxr-xr-x  213 root 25 Oct 07:59  gtk-update-icon-cache
.rwxr-xr-x 1.1k root 26 Oct 02:35  mkinitcpio-install
.rwxr-xr-x 1.7k root 26 Oct 02:35  mkinitcpio-remove
.rwxr-xr-x 7.4k root  3 Jun  2021  snap-pac
.rwxr-xr-x 1.1k root  3 Nov 10:18  systemd-hook

Thank you for the merge request, it really is amazing how fast you all are.

Hmm. So, not the mkinitcpio upstream coming issue, just wanted to make sure on that front. And I really shouldn't be making MR's on too low of caffienation levels, but I got everything squared away, finally.

I'm looking at the rest of the details you've provided and thinking on what's going on.

Hi, after fighting with this half a day I found that the real problem is that the garuda-hooks-runner script never actually calls the Mkinitcpio-Install function

3 Likes

Yeah, I'm looking into this as well, but how are you determining that this is not happening?

Any possible relation with the last commit?

I'm thinking so. But, I'm looking at it.... not seeing an issue, so far... But, obviously there is, if it's not running mkinitcpio-install.

Actually... I think I'm finding the issue now....

1 Like

Yes, my suggestion earlier today started checking that commit and for the little I know, everything seemed ok... So I checked in the hook upstream.

So, yeah. Mkinitcpio-Install was not being called because there was not a catch for it in Main()
My MR fixes that issue now as well.

6 Likes

Yeah, that :slight_smile:

Alrighty. Merge-Request that fixed both future mkinitcpio-install hook issues AND current lack of running Mkinitcpio-Install has been merged and deployed and should be out to mirrors in a matter of minutes, to resolve this issue.

12 Likes

I'm grateful for your help, thank you. As soon as I'm home I'll test it.

1 Like

The upgrade went smooth, all is well. Thank you all for your help!

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.