GRUB reinstallation issue

Support
, ,
1

Precondition: Dual-boot Windows 11 + Manjaro
What was done: In Manjaro accepted updates from UI
Results: Was not able to reach Manjaro login screen after reboot

After that tried to follow steps from the https://forum.manjaro.org/t/latest-update-resulted-in-black-screen-grub-seems-broken/132711 without any success, after that even not able to reach the GRUB by itself.

So I decided to try from scratch as it guided in the https://wiki.manjaro.org/index.php/GRUB/Restore_the_GRUB_Bootloader

manjaro-chroot -a                                                                                   ✔ 
==> Mounting (ManjaroLinux) [/dev/nvme0n1p7]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
 --> mount: [/mnt/home]

pacman -Syu grub
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
warning: grub-2.12-3 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) grub-2.12-3

Total Installed Size:  47.86 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                                        [#######################################] 100%
(1/1) checking package integrity                                      [#######################################] 100%
(1/1) loading package files                                           [#######################################] 100%
(1/1) checking for file conflicts                                     [#######################################] 100%
(1/1) checking available disk space                                   [#######################################] 100%
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
:: Processing package changes...
(1/1) reinstalling grub                                               [#######################################] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Refreshing PackageKit...
Error connecting: Could not connect: No such file or directory
error: command failed to execute correctly
(3/3) Updating the info directory file...

BTW it is strange from my point of view that if I try to execute the command above again it will produce same output. I would expect something like “system up to date”
Next step I did:

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
Installing for x86_64-efi platform.
Installation finished. No error reported.

grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.6-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.6-x86_64.img
Found initrd fallback image: /boot/initramfs-6.6-x86_64-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.
ERROR: mkdir /var/lock/dmraid
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

After reboot same behavior: not able to even reach the GRUB. I think because of either ERROR: mkdir /var/lock/dmraid or two grub-probe related errors. Also from second run of the same command the error ERROR: mkdir /var/lock/dmraid disappeared by some reason.

But still the same result - black screen after startup instead of GRUB

Additional Info:

efibootmgr 
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0001,0002,0000,0003
Boot0000* Windows Boot Manager  HD(2,GPT,43c62341-e98d-4be8-85f1-e83ddd32488d,0x109000,0x32000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000006f000100000010000000040000007fff0400
Boot0001* manjaro       HD(2,GPT,43c62341-e98d-4be8-85f1-e83ddd32488d,0x109000,0x32000)/\EFI\manjaro\grubx64.efi
Boot0002* UEFI: General UDisk 5.00      PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/CDROM(1,0x74e2c4,0x8000)0000424f
Boot0003* UEFI: General UDisk 5.00, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/HD(2,MBR,0x0,0x74e2c4,0x2000)0000424f

lsblk under manjaro-chroot -a context:

lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,MOUNTPOINT,PARTTYPENAME
PATH           PTTYPE PARTTYPE FSTYPE MOUNTPOIN PARTTYPENAME
/dev/loop0                                      
/dev/loop1                                      
/dev/loop2                                      
/dev/loop3                                      
/dev/sda                                        
/dev/sda1                                       
/dev/sda2                                       
/dev/nvme0n1                                    
/dev/nvme0n1p1                                  
/dev/nvme0n1p2                        /boot/efi 
/dev/nvme0n1p3                                  
/dev/nvme0n1p4                                  
/dev/nvme0n1p5                                  
/dev/nvme0n1p6                                  
/dev/nvme0n1p7                        /         
/dev/nvme0n1p8                        /home   

sudo fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 970 EVO Plus 1TB            
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: FF539F50-CA2F-4D83-B1AB-F97BD2366474

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048    1085439    1083392   529M Windows recovery environment
/dev/nvme0n1p2    1085440    1290239     204800   100M EFI System
/dev/nvme0n1p3    1290240    1323007      32768    16M Microsoft reserved
/dev/nvme0n1p4    1323008  208525311  207202304  98.8G Microsoft basic data
/dev/nvme0n1p5  208525312  209745919    1220608   596M Windows recovery environment
/dev/nvme0n1p6  209747968 1743806463 1534058496 731.5G Microsoft basic data
/dev/nvme0n1p7 1743806464 1848664063  104857600    50G Linux filesystem
/dev/nvme0n1p8 1848664064 1953525134  104861071    50G Linux filesystem
2

I suspect that after re-install attempts it is just a GRUB with single entry for load, so I immediately step on the initial issue of the black screen during Manjaro boot.

Part of the grub.cfg

menuentry 'Manjaro Linux' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-s>
        savedefault
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_gpt
        insmod ext2
        search --no-floppy --fs-uuid --set=root 22d1cb49-d17e-41df-814b-ab4d3858c61d
        linux   /boot/vmlinuz-6.6-x86_64 root=UUID=22d1cb49-d17e-41df-814b-ab4d3858c61d rw  quiet splash udev.log_p>
        initrd  /boot/intel-ucode.img /boot/initramfs-6.6-x86_64.img
}
submenu 'Advanced options for Manjaro Linux' $menuentry_id_option 'gnulinux-advanced-22d1cb49-d17e-41df-814b-ab4d38>
        menuentry 'Manjaro Linux (Kernel: 6.6.16-2-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --cl>
        savedefault
                load_video
                set gfxpayload=keep
                insmod gzio
                insmod part_gpt
                insmod ext2
                search --no-floppy --fs-uuid --set=root 22d1cb49-d17e-41df-814b-ab4d3858c61d
                linux   /boot/vmlinuz-6.6-x86_64 root=UUID=22d1cb49-d17e-41df-814b-ab4d3858c61d rw  quiet splash ud>
                initrd  /boot/intel-ucode.img /boot/initramfs-6.6-x86_64.img
        }
        menuentry 'Manjaro Linux (Kernel: 6.6.16-2-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-l>
                load_video
                set gfxpayload=keep
                insmod gzio
                insmod part_gpt
                insmod ext2
                search --no-floppy --fs-uuid --set=root 22d1cb49-d17e-41df-814b-ab4d3858c61d
                linux   /boot/vmlinuz-6.6-x86_64 root=UUID=22d1cb49-d17e-41df-814b-ab4d3858c61d rw  quiet splash ud>
                initrd  /boot/initramfs-6.6-x86_64-fallback.img
        }
}
3

By removing from GRUB entry was able to boot into my local Manjaro installation. But the question is why it didn’t restore Windows GRUB entry?

4

Great, you have succesffully disabled plymouth soft/mal-ware.
I dont see any windoze entries.
Do you have os-prober enabled and re-run sudo grub-mkconfig -o /boot/grub/grub.cfg ?

1 Like
5

Just did it from local Manjaro installtion. It restored initial Windows entry but together with the quiet splash for Manjaro :smiley: So had to boot from the live image again and manually delete it from grub.cfg

After action described above in this message it was added but in the separate section further in the grub.cfg

6

Don’t edit grub.cfg, it’s regenerated every time you run update-grub or grub-mkconfig -o /boot/grub/grub.cfg.

Instead you edit /etc/default/grub to remove quiet splash, then sudo grub-mkconfig -o /boot/grub/grub.cfg

7
1 Like
8

Thanks, nice to know the source of that parameters :+1:

1 Like
9

PS… you probably dont want this?

10

What I’ve read so far it is fine. But I’ll watch for it and probably remove at some point.

11

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