Hello, i tried installing EndeavourOS (after trying CachyOS which had the same issue), so after the install, I can’t boot into EndeavourOS it shows: error: unknown filesystem.
I had this issue prior on CachyOS, hence I had done a grub-install and a grub-mkconfig through arch-chroot, but it resulted in a default arch grub config, due to which, everytime I boot, GRUB shows “Arch Linux” instead of “Endeavour OS”, and “Advanced Options for Arch Linux” instead of “Advanced Options for Endeavour OS”, for which I think the latter should be the default, but it isn’t in this case
This occurred every time I tried to install EndeavourOS with no desktop, also, I’m trying to dual boot with Windows 10. Hence, I went with manual partioning, here is my config
/dev/sda1: System Reserved (Windows) 50MiB
/dev/sda2: Windows 10 (FS:NTFS)
/dev/sda3: EndeavourOS (FS:XFS) mounted to / with FS flags root
/dev/sda4: Extra Swap (linux swap) with FS flags swap
Also os-prober seems to be broken due to the latest version of GRUB, hence I need to add a manual entry for Windows 10.
I don’t think it’s possible to do that on the grub rescue menu. After doing a grub-install and grub-mkconfig, through arch-chroot I could boot into EndeavourOS, the issue, which is a very small issue, consists of the GRUB menu showing Arch Linux and Advanced Options for Arch Linux instead of EndeavourOS or something, referring to /etc/default/grub, I see that the distributor parameter is set to Arch, instead of something like EndeavourOS perhaps. It’s just a decorative issue, but I don’t understand why the error: unknown filesystem issue on the grub rescue menu persists on arch-based distros like Cachy and Endeavour (even after multiple tries of troubleshooting why it occurs) which can’t be fixed without chrooting into the install.
Yes, I can boot to my system, and it functions properly, I added the rootfstype=xfs parameter, nothing changed.
Upon changing the GRUB_DISTRIBUTOR value to EndeavourOS, it shows EndeavourOS and Advanced Options for EndeavourOS, the issue has been fixed! But is there any reason to why calamares might have failed to do so before?
I guess it might be a calamares issue, or a grub issue since it occurs on CachyOS too which uses calamares, or its just an user error (i.e setting the root flag instead of adding the boot flag)
