Problems after system update

Support System Updates
1

I am running a dual boot system with Windows 10 and Manjaro (System runs in Bios mode; the SSDs work with MBR) After a full update the system does not work any more.
Symptoms:

  1. After the start screen of the BIOS is shown the monitor remains black; it seems that Grub does not boot. There is still a signal but nothing is shown. Using the up and down keys I tried to choose an OS. (Just a test to exclude problems of the graphic card.) The screen remained black.
  2. I used SuperGrub2 disk: It found Windows but no bootable Linux.
  3. Maybe this info is useful: After turning the PC off, the corresponding light of the KVM-switch is still on. This is quite unusual.

I have tried to use manjaro-chroot -a but it did not help.

Btw: I have posted relevant infos about my system configuration under the Topic “Dual boot problems with Windows and Manjaro” a few weeks ago.

2
3

Didn’t work. The screen is as black as before.

4

I would try to manjaro-chroot again and to install install-grub

# pacman -S install-grub

Then run (still within chroot environment)

# install-grub
# update-grub

exit chroot and reboot.

1 Like
5

Ok.

I have now switched to the Windows half of the system as I have to do some work. Unfortunatly booting Windows via SuperGrub2 disk is a problem too. So I have to finish work first and this will take some time.

Meanwhile: Is there a way to find out on which disk Grub is installed?

Isn’t it strange that SuperGrub2 disk does not find the Manjaro installation?

6

Pretty unusual. What exact were the messages when restoring, what command did you use?

When you boot into Windoze make sure Fast startup is switched off before you shutdown.

2 Likes
7

Fast startup is always disabled.

I have used all the commands (for Bios/MBR systems) written in the link. I don’t remember the messages any more.

Just thinking: Is there a possibility to roll back the whole update of the system?

8

Only if…

  • you have made a full backup with timeshift; or…
  • you have btrfs and you’ve made a timeshift or snapper snapshot before the update.
9

Can you boot a live ISO and provide

$ sudo fdisk -l

to understand your partition scheme?

Also, please let us know what ISO version you have used when restoring the boot loader. I have never seen it but I could imagine that a very old ISO could cause issues.

1 Like
10

I’ll drop this here in case it’s useful:

1. Boot with the Manjaro Installer USB and enter a chroot environment via the Terminal.

Information on entering chroot can be found here:

2. Once in chroot;
→ start the procedure by first installing the install-grub script:

  • pacman -S install-grub
    (the script may not be installed by default)
  • install-grub
    (replaces the installed grub instance)
  • exit
    (exits the chroot environment)

3. Reboot to your Manjaro system.

Please post your system information here also.

Asking for help with an issue and then expecting others to go searching for possibly relevant information is less than ideal. Please show some consideration, and help others to help you.

Regards.

11

This one (so others can find it easier): Dual Boot Problems with Windows and Manjaro

Out of the 100+ posts there, I do not think we ever got the proper output of:

lsblk -f

When you did before, it did out output properly.

But I believe you have Manjaro installed on:

nvme1n1
  ├─nvme1n1p1 ext4   1.0          7577eecb-23f7-4a07-8eac-a01a3d8d9240    1,3T    21% /
  └─nvme1n1p2 swap   1   swap     8708d9e9-4e5b-490b-b93e-465abbd4a30a        [SWAP]

(And it definitely boots MBR/Legacy.)

@Umbra_noctis with the update, did you install the pacnew for /etc/mkinitcpio.conf, then it would not boot?

Since you had trouble with configuration files, I think this a stretch to say you merged that file.

With manjaro-chroot try it without -a, but mount your root first.

Example:

sudo mount /dev/nvme1n1p1 /mnt
sudo manjaro-chroot /mnt /bin/bash

If that doesn’t work, you will have to do it the Arch Linux way. (Just more mount commands.)

12

manjaro-kde-25.0.10-251013-linux612

13

There are two files mkinitcpio.conf and mkinitcipio.conf.pacnew.

14

I found a programme in the Manjaro menu called “Restore installed system settings” and tried it out. I used the second option and it reinstalled grub but the problems remained. Maybe the new grub version is not compatible with my system?

15

Why not post that here? Yes. Again.
Who is going to hunt that down without so much as a link to it.
I’m not.

1 Like
16

It has been reported that the combination of some buggy UEFI implementations with the new grub leads to the peculiar requirement that the names of the directories and files on the EFI partition would be in all-uppercase — which should not normally be necessary, given that vfat is case-retentive but not case-sensitive.

I would recommend renaming all of the directories and files on the EFI partition to uppercase, and to then run the install-grub script from within the chroot environment.

It’s worth a try. :man_shrugging:

17

To avoid confusion. The infos there have been taken from the working system before the update. So they might be helpful but they could also be misleading.

18

The system works in BIOS mode. There is no EFI Partition.

1 Like
19

Before I try install-grub again, I want to try out a rollback to the former grub installation. The files are still in the /var/cache/pacman/pkg/ directory. But I don’t know all the files that are necessary for a complete rollback of grub.

20

They might be.
Why not provide more current info then?
Here.
… instead of not giving the possibly outdated … not here …