an old self contained manjaro install that has files but not been used for a long while as it has issues but did not use it as multiboot
It was always left it as “just another partition”
Im guessing at some point it has got involved
Then remove that partition after you have backed up, if you have anything to back up. Not sure WHY but that is most likely the problem here.
After that you have to redo the chroot, but this time you should use manjaro-chroot -a because now there should only be one.
Reinstall grub just like before and THEN it should work.
But to be honest, since it does not seem you run this system very often. why not remove both and then reinstall with btrfs and use your old home as mountpoint for home in the installer, that will keep your settings and your home intact but the benefits of btrfs and a FRESH install with fresh kernels.
If you want that, I can help you over dm:s, because that is a whole other thing and the forum should not be used like that.
It may take some time as its 200gb and Im transferring it to a HDD
It used to be my only pc and I used to use it for many hours a day
but since it died I have not used it in around 15 months
When I accidentally pressed update from the GUI, I guessed I was screwed as every time (actually 100% of the time) the GUI has been used for an update it has caused some issue with something and has become unusable.
Even the laptop I am using to reply is almost dead (different issue) but I want to try and fix and learn from it.
I seem to kill manjaro very frequently and in different ways but I hope this reduces as I learn
That is a very strong reason for a reinstall.
Well, IF you want me to help you, send me a dm.
waiting for dd to finish so I hope I don’t but I do appreciate it.
[manjaro manjaro]# manjaro-chroot -a
==> Mounting (ManjaroLinux) [/dev/nvme0n1p11]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
--> mount: [/mnt/home]
[manjaro /]#
If you now install grub like I showed you and reboot and it still gives that error, I have nothing more.
You never answered if you formatted the boot partition or not, but that would be the only thing I can think of making it not working.
But I still recommend a reinstall where you keep home.
Partition up the drive so you dont have a bunch of unallocated space on it.
Was going back through and now saw this.
I there and article or document on how to change this, as searching did not come back with great results (I may not know the correct search terms).
I don’t think so
Well, if it does not work now, all I have left is format the boot drive and flag it esp,boot, chroot and then reinstall grub.
I has not worked.
Is the thought that it may be so broken that the reinstall will not fix it as it will be corrupted and the format will destroy everything?
.
.
.
So just to check I will do the following?
I have deleted then apply-ed nvme0n1p1 in gparted,
then created it as fat32,4096MiB,boot,esp and applied, and it now has nvme0n1p1
sudo mount /dev/nvme0n1p11 /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
sudo manjaro-chroot /mnt /bin/bash
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
grub-mkconfig -o /boot/grub/grub.cfg
update-grub
exit
You don’t need to do the whole mount procedure now, you can just type sudo manjaro-chroot -a.
Also, the boot partition is crazy big, since you do it manually here, 100MB is enough imho. If you install, calamares demands 300 IIRC.
But otherwise, yes.
You also should not need update-grub
Edit
But keep in mind, since you format the partition, the UUID most likely will change, do not forget that.
so I need to add that from gparted to fstab?
Full output after changing fstab
UUID=DBEE-4861 /boot/efi vfat umask=0077
~ sudo manjaro-chroot -a ✔
==> Mounting (ManjaroLinux) [/dev/nvme0n1p11]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
--> mount: [/mnt/home]
[manjaro /]# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
Installing for x86_64-efi platform.
EFI variables are not supported on this system.
EFI variables are not supported on this system.
grub-install: error: efibootmgr failed to register the boot entry: No such file or directory.
[manjaro /]# 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-5.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.19-x86_64.img
Found initrd fallback image: /boot/initramfs-5.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-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
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.
done
[manjaro /]# exit
exit
--> umount: [/mnt/home]
--> umount: [/mnt/boot/efi]
--> umount: [/mnt]
~
Not sure about the
EFI variables are not supported on this system.
but then again I don’t know what I’m talking about anyway
If it does not work now, I have no idea.
Doing a quick search on the full error seems to indicate you have things in bios not set correctly.
Make sure fast boot is disabled and that efi is actually the system your bios is trying to boot into.
nope still grub
only difference is the option for
UEFI OS (WDS500G2X0C-00L350)
has gone and the one remaining is
WDS500G2X0C-00L350
which is the one that gives grub
fast boot is enabled but i remember disabling that long ago so i must have re-enabled it
have now disabled it but it is still not working
Did you reinstall grub AFTER you disabled fast boot?
If so. Sorry, I have nothing else.
Well, you havent shown your grub though.
Chroot and cat /etc/default/grub
no I have not, so fast boot could block access to the fat32 file system and prevent install?
will do
~ sudo manjaro-chroot -a ✔
==> Mounting (ManjaroLinux) [/dev/nvme0n1p11]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
--> mount: [/mnt/home]
[manjaro /]# cat /etc/default/grub
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=8a065abc-8719-4231-9f15-03d795b01065 udev.log_priority=3"
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true
[manjaro /]# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
Installing for x86_64-efi platform.
EFI variables are not supported on this system.
EFI variables are not supported on this system.
grub-install: error: efibootmgr failed to register the boot entry: No such file or directory.
[manjaro /]# 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-5.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.19-x86_64.img
Found initrd fallback image: /boot/initramfs-5.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-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
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.
done
[manjaro /]# exit
exit
--> umount: [/mnt/home]
--> umount: [/mnt/boot/efi]
--> umount: [/mnt]
~
Change this to GRUB_TIMEOUT_STYLE=menu to show menu instead of a black screen for 5s each boot.
AND the fact the fat32 partition is at its absolute limit max wise. Shrink it and retry.
But idk. Sorry, I am out of ideas.
My recommendation is to clean up your drive and reinstall. (and by that I mean get rid of that unallocated space on the drive. If you want unallocated space left, leave it at the end.)
But I guess you can try to run updates and whatnot, chroot obv works now. Maybe it was a bug in efibootmgr or grub. Idk.
But no matter what, 15 months without updates on a rolling release, yeah, no…
sudo manjaro-chroot -a ✔
==> Mounting (ManjaroLinux) [/dev/nvme0n1p11]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
--> mount: [/mnt/home]
[manjaro /]# 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.
[manjaro /]# grub-mkconfig -o /boot/grub/grub.cfg
update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.19-x86_64.img
Found initrd fallback image: /boot/initramfs-5.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-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
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.
done
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.19-x86_64.img
Found initrd fallback image: /boot/initramfs-5.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-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.
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.
done
[manjaro /]#
So, after seeing the efi messages
EFI variables are not supported on this system.
EFI variables are not supported on this system.
grub-install: error: efibootmgr failed to register the boot entry: No such file or directory.
and nothing else was working my thoughts turned to it having to be hardware/firmware and while I had tried this in the past I could not think of another way.
I messed around with the motherboard, going through a bunch of the setting and changing a bunch, but could not find anything that worked after reinstalling grub and rebooting cycles
I then tried cmos reset, reinstalling grub and rebooting cycle but no dice
I then re-seated RAM, CPU, NVME and all cable’s and then reinstalling grub and rebooting cycle but still no luck
So I decided to RTFM and go through every setting in the bios 1 by 1 and after many hours got a boot after changing many things.
The issue seems to be with (Launch CSM) being set as either [Auto] or [Enabled] as it seems auto does not detect and/or select it correctly and must go to straight to legacy, but setting it to [Disabled] works fine.
This has never been an issue in the past so I don’t know if it became a problem or I changed it during trouble shooting but Im surprised auto did not work.
So now I have got passed this I have an output of
/dev/nvme0n1p11: clean, 570531/7692288 files, 15227792/30738946 blocks
[FAILED] Failed to start pkgfile database update.
And it wont go any further, and while I have not searched for this yet I believe I will have to open another thread if I cant find a solution.
For anyone curious here is the link to the manual and it is on
3-27
I have changed this
I greatly appreciate all the time, help and patience I have received from everyone.
If anyone has any useful links to resources for learning more about this then please let me know.