Update Kernel 515 doesn't finish

MaMicha · 21 April 2023 07:37

Today got the message to update pipewire and linux 515. I started this using pamac GUI. Now its running since more than 15 Minutes without any progress in Post-Transaction-Hooks 4/5:

Vorbereitung...
Synchronisiere Paketdatenbanken...
Aktualisierung von AUR...
Warnung: libreoffice-fresh-rpm: ignoriere Paket-Upgrade (6.4.7-2 => 7.4.1-1)
Abhängigkeiten werden aufgelöst...
Interne Konflikte werden überprüft...
Herunterladen von lib32-libpipewire (1:0.3.70-0) gestartet
Herunterladen von libpipewire (1:0.3.70-0) gestartet
Herunterladen von lib32-libpipewire (1:0.3.70-0) beendet
Herunterladen von grub-theme-manjaro (20.2-15) gestartet
Herunterladen von libpipewire (1:0.3.70-0) beendet
Herunterladen von grub-theme-manjaro (20.2-15) beendet
Herunterladen von pipewire (1:0.3.70-0) gestartet
Herunterladen von lib32-pipewire (1:0.3.70-0) gestartet
Herunterladen von lib32-pipewire (1:0.3.70-0) beendet
Herunterladen von linux510 (5.10.178-1) gestartet
Herunterladen von pipewire (1:0.3.70-0) beendet
Herunterladen von linux510-virtualbox-host-modules (7.0.6-21) gestartet
Herunterladen von linux510-virtualbox-host-modules (7.0.6-21) beendet
Herunterladen von linux515 (5.15.108-1) gestartet
Herunterladen von linux510 (5.10.178-1) beendet
Herunterladen von linux515-virtualbox-host-modules (7.0.6-24) gestartet
Herunterladen von linux515-virtualbox-host-modules (7.0.6-24) beendet
Herunterladen von linux54 (5.4.241-1) gestartet
Herunterladen von linux515 (5.15.108-1) beendet
Herunterladen von linux54-virtualbox-host-modules (7.0.6-17) gestartet
Herunterladen von linux54-virtualbox-host-modules (7.0.6-17) beendet
Herunterladen von linux54 (5.4.241-1) beendet
Überprüfe Schlüsselring...
Integrität wird überprüft...
Paketdateien werden geladen...
Dateikonflikte werden überprüft...
Überprüfe verfügbaren Speicherplatz...
Starte Pre-Transaction-Hooks...
Removing linux initcpios...
Save Linux kernel modules
Erneuere grub-theme-manjaro (20.2-13 -> 20.2-15)...
Erneuere libpipewire (1:0.3.68-1 -> 1:0.3.70-0)...
Erneuere lib32-libpipewire (1:0.3.68-1 -> 1:0.3.70-0)...
Erneuere pipewire (1:0.3.68-1 -> 1:0.3.70-0)...
Erneuere lib32-pipewire (1:0.3.68-1 -> 1:0.3.70-0)...
Erneuere linux510 (5.10.177-1 -> 5.10.178-1)...
Erneuere linux510-virtualbox-host-modules (7.0.6-20 -> 7.0.6-21)...
In order to use the new version, reload all virtualbox modules manually.
Erneuere linux515 (5.15.106-1 -> 5.15.108-1)...
Erneuere linux515-virtualbox-host-modules (7.0.6-22 -> 7.0.6-24)...
In order to use the new version, reload all virtualbox modules manually.
Erneuere linux54 (5.4.240-1 -> 5.4.241-1)...
Erneuere linux54-virtualbox-host-modules (7.0.6-16 -> 7.0.6-17)...
In order to use the new version, reload all virtualbox modules manually.
Starte Post-Transaction-Hooks...
Arming ConditionNeedsUpdate...
Updating module dependencies...
Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: '5.10.178-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.10-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: '5.10.178-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.10-x86_64-fallback.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.108-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: '5.15.108-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64-fallback.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: '5.4.241-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.4-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: '5.4.241-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.4-x86_64-fallback.img'
==> Image generation successful
Updating Grub-Bootmenu
GRUB-Konfigurationsdatei wird erstellt …
Thema gefunden: /usr/share/grub/themes/manjaro/theme.txt
Linux-Abbild gefunden: /boot/vmlinuz-5.15-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Linux-Abbild gefunden: /boot/vmlinuz-5.10-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Linux-Abbild gefunden: /boot/vmlinuz-5.4-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Warnung: Zur Erkennung anderer bootfähiger Partitionen wird os-prober ausgeführt.
Dessen Ausgabe wird zur Erkennung bootfähiger Programmdateien und Erzeugen neuer Boot-Einträge verwendet.

Now what?

freggel.doe · 21 April 2023 09:15

Contrary to post title the kernel update did finish, initramfs were built for multiple kernels and it looks fine to me.
If the output correlates to your problem grub’s os-prober seems to stall.
If you don’t need it (no other operating systems on the machine), disable it in /etc/default/grub.
Try killing the os-prober process to let the update finish and re-generate your grub.cfg afterwards:

$ sudo update-grub

Friendly reminder: do not reboot or power off your machine until this is solved as grub.cfg is kinda important for booting up again.

Keruskerfuerst · 21 April 2023 09:17

Can you post fdisk -l or blkid ?

MaMicha · 21 April 2023 09:52

Thank you, first your request:

$ sudo fdisk -l or blkid
fdisk: or kann nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
fdisk: blkid kann nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden

and

f sudo fdisk -l
Festplatte /dev/nvme0n1: 1,82 TiB, 2000398934016 Bytes, 3907029168 Sektoren
Festplattenmodell: Samsung SSD 970 EVO Plus 2TB            
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: A848537D-B25C-A346-881C-D1AA4A1BBCC3

Gerät              Anfang       Ende   Sektoren Größe Typ
/dev/nvme0n1p1       2048    1050623    1048576  512M EFI-System
/dev/nvme0n1p2    1050624  135268351  134217728   64G Linux Swap
/dev/nvme0n1p3  135268352  202377215   67108864   32G Linux-Dateisystem
/dev/nvme0n1p4  202377216  269486079   67108864   32G Linux-Dateisystem
/dev/nvme0n1p5  269486080  898631679  629145600  300G Linux-Dateisystem
/dev/nvme0n1p6  898631680 1318062079  419430400  200G Linux-Dateisystem
/dev/nvme0n1p7 1318062080 3907028991 2588966912  1,2T Linux-Dateisystem


Festplatte /dev/sda: 14,55 TiB, 16000900661248 Bytes, 31251759104 Sektoren
Festplattenmodell: My Book 25ED    
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Größe (minimal/optimal): 4096 Bytes / 4096 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner:#######

Gerät      Anfang        Ende    Sektoren Größe Typ
/dev/sda1    2048 31251757055 31251755008 14,6T Linux-Dateisystem

and

$ blkid
/dev/nvme0n1p7: LABEL="Daten" UUID="##### BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Daten" PARTUUID="#####"
/dev/nvme0n1p5: LABEL="Virtual" UUID="##### BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Virtual" PARTUUID="#####"
/dev/nvme0n1p3: LABEL="Manjaro" UUID="#####" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Manjaro" PARTUUID="#####"
/dev/nvme0n1p1: LABEL_FATBOOT="UEFI-ESP" LABEL="UEFI-ESP" UUID="F8E8-132F" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="UEFI-ESP" PARTUUID="#####"
/dev/nvme0n1p6: LABEL="TimeShift" UUID="#####" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="TimeShift" PARTUUID="#####"
/dev/nvme0n1p4: LABEL="home" UUID="#####" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="home" PARTUUID="#####"
/dev/nvme0n1p2: LABEL="Swap" UUID="#####" TYPE="swap" PARTLABEL="Swap" PARTUUID="#####"
/dev/sda1: LABEL="myBook16" UUID="#####" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="myBook16" PARTUUID="#####"

Hope, this is close to what you’d like to see …

brahma · 21 April 2023 10:10

is it still stuck?
if yes, cancel it, and rerun it again:

sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syyu

mithrial · 21 April 2023 10:38

If the above command tells you that there’s nothing to do, I would still regenerate the initramfs and grub:

sudo mkinitcpio -P
sudo update-grub

MaMicha · 21 April 2023 11:34

Thank you!
@brahma: pamac-GUI is still running, the close-X does nothing. The screen from here did not change.

@mithrial: I fired this:

$ sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: '5.10.178-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.10-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: '5.10.178-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.10-x86_64-fallback.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.108-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: '5.15.108-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64-fallback.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: '5.4.241-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.4-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: '5.4.241-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.4-x86_64-fallback.img'
==> Image generation successful

But pamac-GUI is still as decribed above answering @brahma.
What are my next steps?

mithrial · 21 April 2023 11:35

How about update-gub?

MaMicha · 21 April 2023 12:45

Now this:

$ sudo update-grub
GRUB-Konfigurationsdatei wird erstellt …
Thema gefunden: /usr/share/grub/themes/manjaro/theme.txt
Linux-Abbild gefunden: /boot/vmlinuz-5.15-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Linux-Abbild gefunden: /boot/vmlinuz-5.10-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Linux-Abbild gefunden: /boot/vmlinuz-5.4-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Warnung: Zur Erkennung anderer bootfähiger Partitionen wird os-prober ausgeführt.
Dessen Ausgabe wird zur Erkennung bootfähiger Programmdateien und Erzeugen neuer Boot-Einträge verwendet.
rmdir: konnte '/var/lib/os-prober/mount' nicht entfernen: Das Gerät oder die Ressource ist belegt
rmdir: konnte '/var/lib/os-prober/mount' nicht entfernen: Das Gerät oder die Ressource ist belegt
rmdir: konnte '/var/lib/os-prober/mount' nicht entfernen: Das Gerät oder die Ressource ist belegt
rmdir: konnte '/var/lib/os-prober/mount' nicht entfernen: Das Gerät oder die Ressource ist belegt
Bootmenü-Eintrag für UEFI-Firmware-Einstellungen wird hinzugefügt …
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: Warnung: Unbekannter Gerätetyp nvme0n1.
abgeschlossen

My guess: The USB-drive

/dev/sda1: LABEL="myBook16" UUID="#####" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="myBook16"

may be the problem. It started running (noise) after $ sudo update-grub. The drive is connected, but not mounted:

 sudo umount /media/myBook16/
umount: /media/myBook16/: is not mounted.

@freggel.doe mentioned os-prober …
What’s next?

mithrial · 21 April 2023 13:16

Do you actually need os-prober?

If you’re familiar with chroot and live USB, I would try a reboot. However, it might be dangerous

Keruskerfuerst · 21 April 2023 16:01

You have no Windows installation: you can disable os-prober in /etc/default/grub.

MaMicha · 21 April 2023 16:21

I modified /etc/default/grub:

# Uncomment this option to enable os-prober execution in the grub-mkconfig command
# GRUB_DISABLE_OS_PROBER=false
GRUB_DISABLE_OS_PROBER=true

and

$ sudo update-grub
GRUB-Konfigurationsdatei wird erstellt …
Thema gefunden: /usr/share/grub/themes/manjaro/theme.txt
Linux-Abbild gefunden: /boot/vmlinuz-5.15-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Linux-Abbild gefunden: /boot/vmlinuz-5.10-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Linux-Abbild gefunden: /boot/vmlinuz-5.4-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Warnung: Zur Erkennung anderer bootfähiger Partitionen wird os-prober nicht ausgeführt.
Die darauf befindlichen Systeme werden nicht zur GRUB-Bootkonfiguration hinzugefügt.
Schauen Sie in den Dokumentationseintrag GRUB_DISABLE_OS_PROBER.
Bootmenü-Eintrag für UEFI-Firmware-Einstellungen wird hinzugefügt …
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: Warnung: Unbekannter Gerätetyp nvme0n1.
abgeschlossen

Then I tried to kill the os_process to let the update finalize, as described here

There were three, I stopped all three, now I have:

Pamac-GUI stiill looks as before, I can’t close “X” it. Should I stopp also the 30_os-prober?

Keruskerfuerst · 21 April 2023 16:44

Try to kill os-prober.

MaMicha · 21 April 2023 16:52

What do you mean, the actual os-prober processes are shown here Shall I kill 30_os-prober?

MaMicha · 21 April 2023 17:19

I disabled it, ref. below. Reboot worked. I change /etc/default/grub back to what I had. Reboot worked too.
Thanks everybody for the support!

freggel.doe · 21 April 2023 17:29

grub-mount needs to be killed at that point in time in order to continue.

system · 24 April 2023 07:29

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