it should be disabled i have never enabled it and everything worked before this
update
Edit: I checked and it was disabled
it should be disabled i have never enabled it and everything worked before this
update
Edit: I checked and it was disabled
I’m very much out of my depth here - perhaps reinstall grub
(again from within chroot)
I have never experienced anything like it as a fallout from a simple update.
There is a howto or wiki or root tip or whatever it is called here on this forum.
Probably the easiest is to install install-grub within chroot (should work). Then use that to (hopefully) automatically fix GRUB issues.
can you explain that a bit more detailed, i am trying to pacman -Syu grub and then grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck tho my current efi folder is that normal
It would be:
pacman -S install-grub
then
install-grub
as far as I know. I’ll check on this as I don’t have that package or its man page on my system yet.
ok so now when i try to install /grub i get this>
WARNING: EFI directory not found! Grub couldn’t be installed.
Are you in chroot when you do this?
cat /etc/fstab
ls -al /boot
ls -al /boot/efi
Yes I was in chroot. I will be in a meeting for the next hour or so. I will try afterwards and if nothing works I suppose i will have to reinstall the os
That is always an option - if you can’t figure out what went wrong and we, from a distance, with our questions, can’t either.
There is also snapshots (timeshift …) which would enable you to just go back to when it was working and have a go again …
Wild guess. Could .pacnew files be causing an issue…?
Wild guess. Could .pacnew files be causing an issue…?
idk how that would work since the update installed fine but maybe idk
results of cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=432A-4DB1 /boot/efi vfat umask=0077 0 2
UUID=51546615-7685-41a9-8157-1da13074770b / ext4 defaults,noatime 0 1
UUID=d16bd066-002c-42d8-a784-057b66d73f4f swap swap defaults,noatime 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
/dev/disk/by-uuid/dc4d844f-b794-4916-abb1-e984f60cea90 /home/symeonkasidis/SteamDrive auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=SteamDrive 0 0
results of ls -al /boot
ls -al /boot
total 312944
drwxr-xr-x 5 root root 4096 Mar 5 16:57 .
drwxr-xr-x 18 root root 4096 Dec 3 08:46 ..
-rw-r--r-- 1 root root 153600 Feb 12 01:25 amd-ucode.img
drwxr-xr-x 3 root root 4096 Jan 1 1970 efi
drwxr-xr-x 7 root root 4096 Mar 5 17:41 grub
-rw------- 1 root root 130099250 Mar 5 16:57 initramfs-6.13-x86_64-fallback.img
-rw------- 1 root root 44614304 Mar 5 16:57 initramfs-6.13-x86_64.img
-rw------- 1 root root 78062807 Mar 5 16:57 initramfs-6.6-x86_64-fallback.img
-rw------- 1 root root 40544961 Mar 5 16:57 initramfs-6.6-x86_64.img
-rw-r--r-- 1 root root 21 Mar 4 14:20 linux613-x86_64.kver
-rw-r--r-- 1 root root 21 Feb 27 14:05 linux66-x86_64.kver
drwxr-xr-x 2 root root 4096 Feb 5 23:46 memtest86+
-rw-r--r-- 1 root root 13877760 Mar 5 15:10 vmlinuz-6.13-x86_64
-rw-r--r-- 1 root root 13029888 Mar 5 15:10 vmlinuz-6.6-x86_64
results of ls -al /boot/efi
total 12
drwxr-xr-x 3 root root 4096 Jan 1 1970 .
drwxr-xr-x 5 root root 4096 Mar 5 16:57 ..
drwxr-xr-x 5 root root 4096 Mar 5 16:29 EFI
i dont see an easy way to fix you can mark this as closed i will have to salvage what i can and install the os again
mkay
noted -
won’t try to advise on possible fixes anymore.
except:
(you already know)
save the contents of /home/$user
and perhaps any system configurations in /etc/*
not having to start from scratch has some value