I recently reinstalled arch but I have a problem with efi partition, user can acces it and the fstab is fucked up

Static information about the filesystems.

See fstab(5) for details.

>

/dev/nvme0n1p2

UUID=e085a3ed-42c6-4329-ae32-9fe68d6ea02f >/ ext4 rw,relatime 0 1

/dev/nvme0n1p1

UUID=81F6-B0FD /boot vfat >rw,relatime,fmask=0022,dmask=0022,codepage=>437,iocharset=ascii,shortname=mixed,utf8,errors>=remount-ro 0 2

/dev/nvme0n1p2

UUID=e085a3ed-42c6-4329-ae32-9fe68d6ea02f >/ ext4 rw,relatime 0 1

/dev/nvme0n1p1

UUID=81F6-B0FD /boot/grub vfat >rw,relatime,fmask=0022,dmask=0022,codepage>=437,iocharset=ascii,shortname=mixed,utf8,erro>rs>=remount-ro 0 2

/dev/nvme0n1p2

UUID=e085a3ed-42c6-4329-ae32-9fe68d6ea02f / ext4 rw,relatime 0 1

/dev/nvme0n1p1

UUID=81F6-B0FD /boot/grub vfat >rw,relatime,fmask=0022,dmask=0022,codepage=>437,iocharset=ascii,shortname=mixed,utf8,error>s=remount-ro 0 2

I have tried modifying and regenerating fstab but it dosen’t work. Also grub can’t be accessed when I’m booted, nor does grub theme. How to I fix this?

  • yianiris@kafeneio.social
    0·
    9 months ago

    When I had an /efi mount just as arch said on wiki I didn’t have problems. /boot stayed with root system, so it can be booted with efi or mbr.

    If you have 2+ disks and one has mbr the other is gpt you can boot from either bootloader.

    You should also try limine, less headaches than grub.

    @Hiro8811

    • Hiro8811@lemmy.worldOP
      1·
      9 months ago

      I have windows with broken efi partition on another disk but that’s not important, or is it?

        • Hiro8811@lemmy.worldOP
          1·
          9 months ago

          Dosen’t work. At first the partition was dirty no I managed to run chxdisk(or whatever its called) and can mount it without hassle but it still dosen’t appear in boot menu. I think there’s something wrong with grub.cfg since the theme is not displaying but I don’t know how to solve it

          • yianiris@kafeneio.social
            0·
            9 months ago

            The theme itself is defined in grub.cfg, but it may be the case that it is stored in your root partition not in efi, so during bootloading the drive can’t be read from.
            So if you manually change the location of the theme directory and copy it inside efi it may work, and change the position of in grub.cfg

            @Hiro8811

            • Hiro8811@lemmy.worldOP
              1·
              9 months ago

              I was looking through commands history and I noticed something. If I’m mounting efi in /efi but I save grub-mkconfig -o to /boot/grub/grub.cfg during boot grub won’t even notice the config file since root is not mounted. Should I save changes to /efi/grub/grub.cfg instead? Or /boot/grub/grub.cfg is the place it should be?

              • yianiris@kafeneio.social
                0·
                9 months ago

                root must always be mounted if you have a system, either by booting or chroot. If you mount just efi from another system .
                On my setup /efi/EFI/grub only has the grub efi binary no config, /boot and therefore /boot/grub is on /root partition

                Now if you have the entire /boot in the /efi partition then it would be /efi/boot/grub/grub.cfg?

                @Hiro8811

                • Hiro8811@lemmy.worldOP
                  1·
                  9 months ago

                  What I meant is that during boot efi partition gets mounted before root so it wouldn’t be able to get config files from root partition. But that’s not the problem, I tried regenerating grub. Most likely it’s something wrong with the theme I applied. It keeps saying that it dosent found grub and that it should be mounted either in /efi or /boot but it is mounted. I’ll try with grub-customizer.

                • Hiro8811@lemmy.worldOP
                  1·
                  9 months ago

                  Managed to get grub theme work so the grub is set up right. I guess I should stop being a help vampire. Anyway thanks for the help