So, I’ve been having some bugs when I turn on my PC since I installed my GPU, and I figured a possible reason might be that it uses bios instead of uefi, although my motherboard supports uefi.

So I’ve been trying to change that, following the instructions from this reddit comment, cross-referenced with relevant arch wiki articles, all from the archiso key I used to install the OS in the first place. But I’m having trouble with the second-to last step: Mounting the newly created partition at /efi. I added the line

PARTLABEL=esp /efi fat32 defaults 0 2 In /etc/fstab Then I created the /efi directory and tried doing mount /dev/nvme0n1p4 /efi I get an error message telling me it can’t find an ext4 filesystem I don’t know why it’s expecting an ext4, several tutorials agreed it had to be a fat32. Then I try mount -t fat32 /dev/nvme0n1p4 /efi And get mount: /efi: unknown filesystem type ‘fat32’

So… Is it impossible to mount a fat32 system from the arch installation device ? If so, what’s the workaround? If not, is it something else I’m doing wrong?

This had taken me my whole afternoon, and in hindsight I would’ve saved more time reinstalling the whole system. This is not off the table, but the fact that I might be really close to success kinda dissuades me from doing that…

OS: Arch Linux x86_64 Kernel: 6.6.8-arch1-1

  • Skull giver@popplesburger.hilciferous.nl
    2·
    10 months ago

    If the partition isn’t damaged or made by some weird semi-compliant tool, you can probably skip the partition type all together in your mount command (sudo mount /dev/nvme0n1p4 /efi). mount should do some basic preliminary checks and try to auto-mount the file system if it recognises the type.

    mount -t vfat is how you would normally specify the FAT filesystem when mounting.

    • loaExMachina@sh.itjust.worksOP
      2·
      10 months ago

      I tried that. But yeah, seems like the partition was damaged. The tools I used were gdisk to convert my partition table from mbr to gpt and parted to make this partition in particular. But I think I did the first part wrong. Regardless, at this point I just assumed the whole thing was corrupted and I did a clean reinstall. Thank you for answering tho!