By the way I do know there are other forums that talk about this issue, but I honestly just didn’t understand anything said in them, and I’ve already broken my Distros a few times by just messing around so yea.. that’s why I’m posting in this category after all.
Anyways, I had dual-booted both Windows 10 and EndeavorOS, and everything was fine for a few weeks, but when I turned off my laptop today (and then turned it on a few hours later) Windows 10 decided to update. I didn’t really have a choice to not update, as it just started right after I turned my device on, but when I restarted it to boot into EndeavorOS, its boot option wasn’t there; in fact there was two Windows 10 boots (not sure why to be honest).
I kind of need my old EndeavorOS Distro back, as it had a few important files I still need (it’s alright if there isn’t a way to recover it, I can just re-do those files anyways). I’d also like to know if there is a way to make so Windows 10 doesn’t erase - or deletes from the Boot Loader - the EndeavorOS Distro, while still keeping Windows 10, as I still need it for a few things.
Of course you can recover this is Linux not Windows.
Start by telling us what boot loader do you have installed? Systemd-boot or grub or another?
Windows more than likely reset your UEFI you can chroot from a live cd to fix the issue.
Boot off the ISO, mount your partition and look in /mnt/etc/fstab. If your ESP is mounted at /efi, it is systemd-boot. If it is mounted at /boot/efi, it is grub.
Not sure why, but when I tried executing the command sudo mount /dev/sda1 /mnt/efi it gave this response: mount: /mnt/efi: WARNING: source write-protected, mounted read-only.
I tried searching how to not make it just read-only, but all I found was a forum in Fedora, and some other sites, but none seemed to really help me, do any of you know what I could do to change it so it isn’t read-only?
One possible reason is if you haven’t disabled “fast startup” in Windows settings. This causes Windows to leave the disk dirty and then it gets mounted read only.
Had to do some things, so I didn’t try anything else other than that. I did also try the command sudo chmod +w /mnt/efi but it didn’t seem to work..? It just gave the response: chmod: changing permissions of '/mnt/efi': Read-only file system, which as far as I know should change the directory’s writing privileges (do note that I’m still unfamiliar with Linux commands, so maybe chmod doesn’t do that..?)
I’ll probably try some more commands until I get it work.
When I try using sudo mount -o remount,rw /mnt/efi after using dosfsck -a /mnt/efi it gives another response, which I think says /dev/sda1 is write-protected..? Not sure why though, also here’s the response, in case you want to see it: mount: /mnt/efi: cannot remount /dev/sda1 read-write, is write-protected.
looks like the windows ESP (efi partition) is used fro EndeavourOS too.
Is something like BitLocker or secure Boot in use?
FastBoot is in most cases what would cause such issue.. to make sure thats a Windows option not something in Bios/Firmware