(edit: I deleted the partitions as instructed on the last reply/8, tried all I could, didn’t succeed. In the end, I deleted them again after the re-installation of windows, and EOS boots fine now.)
Greetings, EOS Community.
I wanted to dual boot windows, so I resized my main disk using gparted. I installed windows on the new partition, and it made a few more partitions, and turned the main one to NTFS. After successfully installing windows, I changed the boot stuff accordingly, firstly with bcdedit on windows, then I confirmed it was good for bios and, it would bring me to my Linux bootloader on startup. However, when trying to boot to EOS, it fails to start file system check on /dev/by-uuid/2ebefd1f-5007-489d-96d3-b050f9b1ffc
Along with dependency fails for /sysroot, initrd file system, and mountpoints configured in real boot, and it brings up an emergency shell.
I tried following some fixes from other similar issues related to fstab, tried using /dev/EOSpartition rather than it’s uuid. I also believe there are 2 partitions with the same uuid now so that may be the reason it fails. I would also like to note that I tried chrooting to the partition and everything is still there, thankfully and so, I don’t know what else to do to fix this.
This is a bit confusing.
By the size of it, it cannot be your EnOS system partition.
By the filesystem (EXT4), it cannot be a Microsoft reserved partition.
Lets check the UUIDs in your fstab (I assume nvme0n1p4 is where EnOS resides):
The 300gb one/0n1p4 is EOS and the 100gb one/0n1p3 is Windows
[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/nvme0n1p4 /mnt
[liveuser@eos-2023.05.28 ~]$ cat /mnt/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=E7C9-43C1 /efi vfat defaults,noatime 0 2
/dev/nvme0n1p4 / ext4 defaults,noatime 0 1
UUID=66428c42-d59c-4a23-b344-bb337c06b03f swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
Alright, your system partition in fstab is referenced by disk id and not UUID so for now I don’t think the same UUID on two different partitions is a problem.
With your system partition still mounted at /mnt:
sudo mount /dev/nvme0n1p1 /mnt/efi
Now chroot into your system:
sudo arch-chroot /mnt
In chroot, run:
reinstall-kernels
When it is done, type exit followed by enter to quit chroot.
Just an Update: I tried dual booting windows again, of course, I got the same issues, but, I managed to fix it myself by chrooting into the boot entries (arch.conf). I modified the root= option to boot from the specific /dev/nvme0n1p4 partition rather than it’s UUID (which was the same for 2 separate partitions, for some reason), and now both EOS and Windows boot properly. I remember editing /etc/fstab, which didn’t work out, but here I am, for anyone else having this issue.
