Potential new GRUB version issue?

I've just ran garuda-update very recently a few times today and just came across this now so I don't think there is much info on this yet but I thought I would ask considering how the last GRUB update went.
Output from my last garuda-update:

:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
:: libretro-meta and libretro-mame-git are in conflict. Remove libretro-mame-git? [y/N] y

Packages (5) discord-0.0.22-1  garuda-hooks-2.9.2-1  grub-2:2.06.r403.g7259d55ff-1
libretro-mame-git-84544.5526dd0fbf6-1 [removal]  libretro-meta-1-7

Total Download Size:     64.43 MiB
Total Installed Size:   214.75 MiB
Net Upgrade Size:      -241.67 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
libretro-meta-1-7-any                   2.8 KiB  4.08 KiB/s 00:01 [------------------------------------] 100%
garuda-hooks-2.9.2-1-any                7.7 KiB  11.5 KiB/s 00:01 [------------------------------------] 100%
grub-2:2.06.r403.g7259d55ff-1-x86_64    6.8 MiB  1375 KiB/s 00:05 [------------------------------------] 100%
discord-0.0.22-1-x86_64                57.6 MiB  9.17 MiB/s 00:06 [------------------------------------] 100%
Total (4/4)                            64.4 MiB  10.2 MiB/s 00:06 [------------------------------------] 100%
(4/4) checking keys in keyring                                     [------------------------------------] 100%
(4/4) checking package integrity                                   [------------------------------------] 100%
(4/4) loading package files                                        [------------------------------------] 100%
(4/4) checking for file conflicts                                  [------------------------------------] 100%
(5/5) checking available disk space                                [------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Performing snapper pre snapshots for the following configurations...
==> root: 487
:: Processing package changes...
(1/1) removing libretro-mame-git                                   [------------------------------------] 100%
(1/4) upgrading discord                                            [------------------------------------] 100%
(2/4) upgrading grub                                               [------------------------------------] 100%
warning: /etc/default/grub installed as /etc/default/grub.pacnew
:: To use the new features provided in this GRUB update, it is recommended
to install it to the MBR or UEFI. Due to potential configuration
incompatibilities, it is advised to run both, installation and generation
of configuration:
$ grub-install ...
$ grub-mkconfig -o /boot/grub/grub.cfg
(3/4) upgrading garuda-hooks                                       [------------------------------------] 100%
(4/4) upgrading libretro-meta                                      [------------------------------------] 100%
:: Running post-transaction hooks...
( 1/14) Enabling os-prober...
( 2/14) Arming ConditionNeedsUpdate...
( 3/14) Refreshing PackageKit...
( 4/14) Foreign/AUR package notification
blasphemer-wad 0.1.7-1
chexquest3-wad 1.4-1
deutex 5.2.2-3
doom1-wad 1.9-3
firestorm-bin 6.6.3.67470-1
frozen-bubble 2.2.1beta1-17
guiscrcpy-git 1:2022.7.1.r17.gbb2bf8e-1
hacx-wad 1.2-2
harmony-wad 1.1-3
heretic1-wad 1.2-2
hexen1-wad 1.1-1
itch 1:1.26.0-2
kipi-plugins 21.12.3-1
lib32-openssl-1.0 1.0.2.u-2
libkipi 21.12.3-1
metis 5.1.0.p10-2
perl-alien-sdl 1.446-12
perl-sdl 2.548-6
replay-sorcery 0.6.0-1
rootactions-servicemenu 2.7.3-1
samba-mounter-git 186.29ebad4-1
sdl_pango 0.1.2-8
spotube-bin 2.6.0-1
square1-wad 2.0-1
strife0-wad 1.1-1
urbanbrawl-wad 1.0-1
( 5/14) Updating grub binary in EFI


The GRUB bootloader at EFI/Garuda is being updated!


Installing for x86_64-efi platform.
Installation finished. No error reported.
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-lts-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Detecting snapshots ...
Found snapshot: 2022-12-09 23:18:42 | @/.snapshots/487/snapshot | pre  | pacman -Su --ignore libretro-mame-git|
Found snapshot: 2022-12-09 17:31:02 | @/.snapshots/486/snapshot | post | spotube-bin                          |
Found snapshot: 2022-12-09 17:31:01 | @/.snapshots/485/snapshot | pre  | pacman -U /tmp/bauh@ace/arch/build_1670625054/spotube-bin/spotube-bin-2. |
Found snapshot: 2022-12-09 17:28:40 | @/.snapshots/484/snapshot | post | ananicy-rules                        |
Found snapshot: 2022-12-09 17:28:39 | @/.snapshots/483/snapshot | pre  | pacman -Su                           |
Found snapshot: 2022-12-09 15:39:43 | @/.snapshots/482/snapshot | post | akonadi-contacts akonadi-mime ark baloo-widgets bomber bovo colord-kde d |
Found snapshot: 2022-12-09 15:39:39 | @/.snapshots/481/snapshot | pre  | pacman -Su                           |
Found snapshot: 2022-12-09 15:17:17 | @/.snapshots/480/snapshot | post | audacious-plugins beautyline binutilsblender blosc candy-icons-git dnsm |
Found snapshot: 2022-12-09 15:16:13 | @/.snapshots/479/snapshot | pre  | pacman -Su                           |
Found snapshot: 2022-12-04 16:41:21 | @/.snapshots/478/snapshot | post | adwaita-cursors adwaita-icon-theme alsa-card-profiles bluedevil breeze b |
Found snapshot: 2022-12-04 16:38:33 | @/.snapshots/477/snapshot | pre  | pacman -Su                           |
Found 11 snapshot(s)
Unmount /tmp/grub-btrfs.G1NurugYFv .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
( 6/14) Orphaned package notification...
asciidoc 10.2.0-2
bluetooth-autoconnect 1.3-1.2
deutex 5.2.2-3
ethtool 1:6.0-1
geocode-glib 3.26.4-2
gtest 1.12.1-1
js78 78.15.0-4
kfiredragonhelper 5.0.6-1.1
lib32-json-glib 1.6.6-2
lib32-openssl-1.0 1.0.2.u-2
lib32-pcre 8.45-3
lib32-rest 0.8.1-4
lib32-smpeg 2.0.0-1
libcmis 0.5.2-12
metis 5.1.0.p10-2
ntp 4.2.8.p15-2
pv 1.6.20-2
python-beaker 1.11.0-8
python-importlib-metadata 5.0.0-1
python-nspektr 0.4.0-2
qt5-webkit 5.212.0alpha4-18
wayland-protocols 1.31-1
( 7/14) Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/locale.gen.pacnew
/etc/default/grub.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.d/mirrorlist.pacnew
/etc/paru.conf.pacnew
/etc/retroarch.cfg.pacnew
Please check and merge
( 8/14) GRUB update after transactions...
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-lts-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Detecting snapshots ...
Found snapshot: 2022-12-09 23:18:42 | @/.snapshots/487/snapshot | pre  | pacman -Su --ignore libretro-mame-git|
Found snapshot: 2022-12-09 17:31:02 | @/.snapshots/486/snapshot | post | spotube-bin                          |
Found snapshot: 2022-12-09 17:31:01 | @/.snapshots/485/snapshot | pre  | pacman -U /tmp/bauh@ace/arch/build_1670625054/spotube-bin/spotube-bin-2. |
Found snapshot: 2022-12-09 17:28:40 | @/.snapshots/484/snapshot | post | ananicy-rules                        |
Found snapshot: 2022-12-09 17:28:39 | @/.snapshots/483/snapshot | pre  | pacman -Su                           |
Found snapshot: 2022-12-09 15:39:43 | @/.snapshots/482/snapshot | post | akonadi-contacts akonadi-mime ark baloo-widgets bomber bovo colord-kde d |
Found snapshot: 2022-12-09 15:39:39 | @/.snapshots/481/snapshot | pre  | pacman -Su                           |
Found snapshot: 2022-12-09 15:17:17 | @/.snapshots/480/snapshot | post | audacious-plugins beautyline binutilsblender blosc candy-icons-git dnsm |
Found snapshot: 2022-12-09 15:16:13 | @/.snapshots/479/snapshot | pre  | pacman -Su                           |
Found snapshot: 2022-12-04 16:41:21 | @/.snapshots/478/snapshot | post | adwaita-cursors adwaita-icon-theme alsa-card-profiles bluedevil breeze b |
Found snapshot: 2022-12-04 16:38:33 | @/.snapshots/477/snapshot | pre  | pacman -Su                           |
Found 11 snapshot(s)
Unmount /tmp/grub-btrfs.IOmjcOdFAM .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
( 9/14) Updating Garuda specific hooks...
(10/14) Fix 'grub' and 'os-prober'
(11/14) Updating the info directory file...
(12/14) Updating the desktop file MIME type cache...
(13/14) Performing snapper post snapshots for the following configurations...
==> root: 488
(14/14) Syncing all file systems...

Checking for plugin updates
Nothing to install / update

System updated! 🐧
Update notices:
The GRUB bootloader at /EFI/Garuda was updated, but it seems like you are not using the Garuda Linux bootloader by default. If you are using 'rEFInd' bootloader, you can safely ignore this. Otherwise, please change your EFI boot priorities to prioritize the "Garuda" bootloader. Running 'grub-install' will do this automatically.

of course I've tried the grub-install command, but it returned with this:

λ grub-install
Installing for x86_64-efi platform.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: error: disk `hostdisk//dev/nvme0n1p1' not found.

Is this a cause for concern or should I just try restarting now?

also, garuda-inxi:

System:
Kernel: 6.0.11-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=aeeebb79-d062-4a59-877a-095da6a50a70 rw rootflags=subvol=@
quiet
cryptdevice=UUID=8d0e5b99-fedf-4a62-a1fc-96db970ac127:luks-8d0e5b99-fedf-4a62-a1fc-96db970ac127
root=/dev/mapper/luks-8d0e5b99-fedf-4a62-a1fc-96db970ac127 splash
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.26.4 tk: Qt v: 5.15.7 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: X370 SLI PLUS (MS-7A33) v: 2.0
serial: <superuser required> UEFI: American Megatrends LLC. v: 3.L4
date: 07/12/2022
CPU:
Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3 gen: 4
level: v3 note: check built: 2021-22 process: TSMC n7 (7nm)
family: 0x19 (25) model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 4605 high: 4628 min/max: 2200/4650 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 4601 2: 4599
3: 4610 4: 4596 5: 4599 6: 4610 7: 4628 8: 4597 9: 4599 10: 4610 11: 4599
12: 4618 bogomips: 88797
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: ASUSTeK driver: nvidia
v: 525.60.11 alternate: nouveau,nvidia_drm non-free: 520.xx+
status: current (as of 2022-10) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 31:00.0 chip-ID: 10de:1b81 class-ID: 0300
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5
compositor: kwin_x11 driver: N/A display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 92 s-size: 530x301mm (20.87x11.85")
s-diag: 610mm (24")
Monitor-1: DP-0 res: 1920x1080 dpi: 92 size: 531x299mm (20.91x11.77")
diag: 609mm (23.99") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.60.11 renderer: NVIDIA GeForce GTX
1070/PCIe/SSE2 direct render: Yes
Audio:
Device-1: NVIDIA GP104 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel bus-ID: 3-1:2 v: kernel pcie: chip-ID: 0c76:122e
class-ID: 0300 gen: 3 serial: <filter> speed: 8 GT/s lanes: 16
bus-ID: 31:00.1 chip-ID: 10de:10f0 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 33:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: JMTek LLC. USB PnP Audio Device type: USB
driver: hid-generic,snd-usb-audio,usbhid
Device-4: SteelSeries ApS Arctis 5 type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-3:3 chip-ID: 1038:12aa
class-ID: 0300 serial: <filter>
Sound API: ALSA v: k6.0.11-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.61 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 29:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp41s0 state: down mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 2d:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp45s0 state: up mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-9:2
chip-ID: 8087:0029 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 1.7 TiB used: 457.64 GiB (26.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 2B2QEXM7 temp: 40.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SV300S37A120G
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: BBF0 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10EZEX-00BN5A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 1A01 scheme: MBR
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 750 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1B6Q scheme: MBR
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 359.22 GiB (77.2%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-8d0e5b99-fedf-4a62-a1fc-96db970ac127
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 736 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 359.22 GiB (77.2%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-8d0e5b99-fedf-4a62-a1fc-96db970ac127
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 359.22 GiB (77.2%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-8d0e5b99-fedf-4a62-a1fc-96db970ac127
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 359.22 GiB (77.2%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-8d0e5b99-fedf-4a62-a1fc-96db970ac127
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.54 GiB used: 232.2 MiB (1.5%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 55.2 C mobo: N/A gpu: nvidia temp: 37 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 378 Uptime: 5h 55m wakeups: 1 Memory: 15.54 GiB
used: 6.9 GiB (44.4%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 2196
pm: pacman pkgs: 2186 libs: 589 tools: octopi,paru pm: flatpak pkgs: 10
Shell: fish v: 3.5.1 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.23
Garuda (2.6.10-1):
System install date:     2022-03-15
Last full system update: 2022-12-09 ↻
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:            plymouth-deactivate.service
1 Like

(I couldn't seem to edit my main post again because of that random forum bug so I will post this here)
Oops, digging around other posts on this, I should probably include
sudo fdisk -l output just in case.

Disk /dev/sda: 111.79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SV300S3
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 51104DA4-D8CF-C047-9155-C910F574FBCC

Device      Start       End   Sectors   Size Type
/dev/sda1    4096    618495    614400   300M EFI System
/dev/sda2  618496 234436544 233818049 111.5G Linux filesystem


Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00B
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x8ae66a76

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdb1        2048 1953521663 1953519616 931.5G  7 HPFS/NTFS/exFAT


Disk /dev/sdc: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 750
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x258782ba

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdc1        2048 488390655 488388608 232.9G 83 Linux


Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 970 EVO Plus 500GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 37F7D8B4-3573-904C-AA4D-5C9A285FF63D

Device          Start       End   Sectors   Size Type
/dev/nvme0n1p1   4096    618495    614400   300M EFI System
/dev/nvme0n1p2 618496 976768064 976149569 465.5G Linux filesystem


Disk /dev/mapper/luks-8d0e5b99-fedf-4a62-a1fc-96db970ac127: 465.46 GiB, 499786482176 bytes, 976145473 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 15.54 GiB, 16685989888 bytes, 4073728 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Yes, please, reboot and let use know if everything works.
That message is due to the fact that we just implemented a new way to automate the grub update and "return" to the new version from Arch, so that we stop holding it back to the old version in our repo.
The additional grub-install shouldn`t be necessary.

1 Like

Thanks, filo. I will do that and report back.
(finding issues relating to grub on the forums are a bit hard considering how the forums exploded last time so I really appreciate it!)

2 Likes

Looks like the dreaded error: symbol 'grub_debug_malloc' not found issue is back after I put in my LUKS pass. I'll have to take a look on my prior posts about this issue to see how I fixed it last time.

1 Like

How about some sudo? Duh? Can you still boot a snapshot at this time? What name is your bootloader registered under? efibootmgr output?

3 Likes

Ya I know my head is somewhere esle today feeling so sick lol.
Anyways...
Somehow my bios settings were wrong, so the prior message about Garuda not being in the top priority spot in efi was right (looks like it was trying to boot disk directly instead of the loader).
Boots now. Probably error on my part after a beta bios update I had to do to install a more reliable CPU.

1 Like

I made sure to make this more robust now :slight_smile:

This probably won't work for a lot of long-standing power-user installs, but it'll work for a lot of installs where grub was never updated (via grub-install) before.

3 Likes

So, is it ok to upgrade Grub now? I've had grub in IgnorePkg ever since the August snafu.

1 Like

I've updated 2 other machines since (one being a Wayfire one, and another dragonized gaming KDE [with an older system installation date of 2021-08-24] on my "main" tower with better hardware) and haven't ran into any issues other than memtest being missing in the options at boot for some reason now.

It at least seems as long as you aren't doing any advanced boot configurations and booting into the "Garuda" bootloader, it should be fine.

4 Likes

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