I almost changed the configuration (from Intel to AMD) and therefore, from a bootable Manjaro flash, I did a Grub repair. Everything went OK, but I didn’t notice that the system gave me a GRUB error during the repair (and even like this), which I don’t know how it happened and even less know how to fix it
Namely, the Grub repair did the job and restored my boot menu to its previous state (win 11 pro, Manjaro KDE, in that order) and it all works, however, I updated the Kernel to KDE and then updated GRUB which is on KDE disk, however, GRUB booting from the KDE disk does not register any changes but always throws the following error during repair:
~ > sudo update-grub
[sudo] password for neogeo:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.9-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.9-x86_64.img
Found initrd fallback image: /boot/initramfs-6.9-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.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found Manjaro Linux (24.0.8) on /dev/sda3
Found linux image: /boot/vmlinuz-6.9-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.9-x86_64.img
Found initrd fallback image: /boot/initramfs-6.9-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.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found Manjaro Linux (24.0.8) on /dev/sda3
Found linux image: /boot/vmlinuz-6.9-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.9-x86_64.img
Found initrd fallback image: /boot/initramfs-6.9-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.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found Manjaro Linux (24.0.8) on /dev/sda3
Adding boot menu entry for UEFI Firmware Settings ...
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.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found Manjaro Linux (24.0.8) on /dev/sda3
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"
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 241
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
~ > _
Can HELP me to return this GRUB on the KDE disk to “normal”/initial correct state and register all changes on disks/partitions as before (i have not any BTRFS jobs before and after and have no more XFCE installation)?!
Check the contents of these files for syntax errors:
/etc/default/grub
/etc/grub.d/*
The syntax should be VAR=value pairs, or comments starting with a hash / # character.
For example:
# GRUB boot loader configuration
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor resume=UUID=9c73e731-a0a2-40cf-a875-feb92ff30bed udev.log_priority=3"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
# [...SNIP...]
Your issue is likely related to this. Grub-Customizer makes changes to configuration files etc. which are hard to reverse unless you are really familiar with what it does.
My suggestion is to remove all traces of it and then reinstall GRUB from scratch.
I have updated my distro to 6.10 Kernel and have removed old 6.9 but ‘update-grub’ refuses to load new Kernel and give me (now after 6.9 moving) an error of a missing 6.9 Kernel. When i manually edit grub boot parameter with ‘e’ and have a change 6.9 to 6.10 then hit F10 , distro loads like a charm with 6.10Kernel
You can also remove quiet splash there (to get rid of plymouth).
Do your changes again what you did earlier after pressing E, save the file and then:
sudo grub-mkconfig -o /boot/grub/grub.cfg
How you did remove 6.9 any logs? Did you do that with manjaro settings manager?
@neogeo
There is also the option to use install-grubScript that may could automatical repair your broken grub, with reinstalling (included newest Grub version) the whole grub instead just repair/update, check this article out if you want:
In short download install-grub and then:
sudo pacman -S grub
Should be enough.
Restart and when you look inside your Grub Menue a new version should show up 2.12-4 that you have the latest Grub Version.
I think you hopefully learned a valuable lesson: do not just click and install anything you find out there, without understanding what it does. And the more customization you make, the harder it will be to debug and troubleshoot.
If that is of any consolation, i have been there. Managed to completely break Ubuntu 7 in under a week, then i returned to windows for a couple more years, before i tried the transition to linux again. I just was not ready to invest time in learning back then.
To not be completely offtopic: i also see i mix of gpt and mbr disks, which might be a part of the problem. And it seems you have more than one manjaro installs. And i suspect when you update grub you update it on the wrong disk, so it is not updated at all actually, on the disk you boot from.
I post this for reference
Obviously you need to adapt the commands, because you have 3 disks and a mix of mbr and uefi, which does not work together out of the box anyway.
I read all Your advice and did something on my own to solve problem.
I uninstalled a Grub Customizer which deleted all its files, after that I deleted the existing Grub files, uninstalled Grub, reinstalled it and updated it. After that, I restarted the system and everything works as it should and should be.
Thank you all for your selfless help!
P.S. I just don’t understand how such a stupid idea didn’t occur to me at the beginning…
THANKS TO ALL OF YOU!
I was going to suggest the linux69 kernel as being part of the issue, but it seems the latest .ISO still has that? … this really needs to be changed, IMHO.
I imagine most behind the scenes are waiting for Plasma 6.1 to be ready (it’s in Testing now); which promises to be a great improvement for Manjaro KDE users.
A newer kernel, along with improvements and fixes for other editions, will probably coincide with the release of the next generally available ISOs.
NEVER USE THIS TRASH 
IT WILL BREAK THINGS 