After updating windows/bios, this OS no longer appears as a boot option

[julsvern]

Just as it sounds, does no even go into GRUB if it even is there anymore. I think I know how to fix this, somebody just please show me how to reinstall grub properly with chroot.
I tried this:

Grub fails after update

chroot steps in garuda linux from live garuda usb sudo mkdir /mnt sudo mount /dev/sdxy /mnt sudo garuda-chroot /mnt/@ now you should be chrooted in garuda if the system is installed in legacy bios then do the following in the chroot grub-install /dev/sda if its installed on efi first mount the efi partition ie fat32 partition from inside the chroot mount /dev/sdxy /boot/efi then grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck then updat…

But it just gives me:
mount: /mnt: mount failed: Operation not permitted.

What am I supposed to do? All I want to do is chroot

[SGS]

Search in forum, please.
There is more than one thread about.

[julsvern]

I know, I've looked at them as well, that was the most informative of the half-dozen

[SGS]

BTW, I fixed it with petsam's "wiki" post, after booting in Garuda I must use

sudo update-grub

it dos not work from chroot.

[julsvern]

Grub was over-written by the windows update, how is updating going to help when it doesn't exist? I'll try what you said but it doesn't make much sense to me...

[filo]

@julsvern

But it just gives me:
mount: /mnt: mount failed: Operation not permitted.

When? Please provide the exact input and output

[SGS]

@julsvern

But it just gives me:
mount: /mnt: mount failed: Operation not permitted.

You post here a text without value, out of context, we are not psychics, how about you post everything?

[SGS]

BTW, this is why we discourage and do not support dual boot. Those who can't fix it should delete M$ or do without Linux.

[julsvern]

Like I had said, I was following this solution, right here:

Grub fails after update

chroot steps in garuda linux from live garuda usb sudo mkdir /mnt sudo mount /dev/sdxy /mnt sudo garuda-chroot /mnt/@ now you should be chrooted in garuda if the system is installed in legacy bios then do the following in the chroot grub-install /dev/sda if its installed on efi first mount the efi partition ie fat32 partition from inside the chroot mount /dev/sdxy /boot/efi then grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck then updat…

I know you’re not psychics but you can infer.

I inputted (as the solution suggested):

sudo mount /dev/sdxy /mnt

[filo]

What did you use for /dev/sdxy?

[julsvern]

Show me how to run Excel without Microsoft and fix Pipewire, but until then, no, I cannot get rid of M$

[SGS]

Thats normal

sudo mount /dev/sdxy /mnt
mount: /mnt: Spezialgerät /dev/sdxy ist nicht vorhanden.
       dmesg(1) könnte nach einem fehlgeschlagenen mount-Systemaufruf
       weitere Informationen liefern.

[filo]

Please check this

How to chroot Garuda Linux

From Grub fails after update - #3 by librewish Some unlucky times that your system is not bootable and the only advised option is to use chroot from a Live ISO to repair the installed system (for example, to (re)install the bootloader), here is the suggested method: steps required to chroot to your installed Garuda installation (btrfs) Boot to a Garuda usb Live ISO Start a terminal and Find your installed system (btrfs) partition, you need the /dev/<something> part. lsblk -f Warning: Remem…

[julsvern]

Thank you but I'm stuck at one final place, I cannot install grub do to a read-only file system.

sh-5.1# sudo grub-install /dev/sda
Installing for x86_64-efi platform.
grub-install: error: cannot backup `/boot/grub/x86_64-efi/acpi.mod': Read-only file system.
sh-5.1# sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
Installing for x86_64-efi platform.
grub-install: error: cannot backup `/boot/grub/x86_64-efi/acpi.mod': Read-only file system.
sh-5.1# sudo update-grub
/usr/bin/grub-mkconfig: line 262: /boot/grub/grub.cfg.new: Read-only file system
sh-5.1#

Any ideas on how to fix this?

EDIT:
Never mind actually... it's probably just fast boot enabled that's causing this (although I'm unsure)