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?

  • IriYan@lemmy.world
    1·
    5 months ago

    Have you tried/installed nvme-cli and/or xnvme

    I wonder if your issues come from buggy nvme modules

    • Hiro8811@lemmy.worldOP
      1·
      5 months ago

      No that wasn’t the problem. I should edit it as solved. What I did was delete the partitions and regenerate mkinicpio, delete all arguments and some grub configs. The efi partition still gets mounted but at least I need root privileges to modify and that’s good enough

  • may_nya@lemmy.blahaj.zone
    1·
    5 months ago

    idk mybe your drive is fucked up so you should try a new one. also did you use fdisk or the graphical one ? and did you generate a new gpt/mbr tab ?

    • Hiro8811@lemmy.worldOP
      1·
      5 months ago

      I solved it somewhat. There’s only two entries in fstab now but for some reason the efi partition still gets automatically mounted and the grub theme dosen’t work

      • yianiris@kafeneio.social
        0·
        5 months ago

        1 are you using systemd-boot?

        2 is your efi mounted as efi or boot?

        3 depending on 2, manually unmount efi and see what you have on boot, maybe you have grub.cfg in 2 places.

        @Hiro8811 @may_nya

        • Hiro8811@lemmy.worldOP
          1·
          5 months ago
          1. I think so, it ships with arch, right?
          2. I had it mounted in more places. First on /boot then in /grub and now it’s in /efi.
          3. The grub.cfg config has always been in the same folder but I’ll check it to make sure.
          • yianiris@kafeneio.social
            0·
            5 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·
              5 months ago

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

                • Hiro8811@lemmy.worldOP
                  1·
                  5 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