gparted says about that /dev/sda1 and there is a (!)Exclamation mark /dev/sda1(!)
Unable to read the contents of this file system!
Because of this some operations may be unavailable.
The cause might be a missing software package.
The following list of software packages is required for fat32 file system support: dosfstools, mtools.
Normally, you would use manjaro-chroot, which will autodetect your EFI partition and mount it in the right place. The error message you’re showing says that the mountpoint does not exist ─ a mountpoint is a directory ─ and it is unclear whether you are doing this from within a chroot environment or not.
From within the live environment, issue the following two commands…
sudo su -
manjaro-chroot -a
If you are presented with a choice, select your Manjaro root partition. Then reinstall GRUB.
I’m guessing that you (re-)installed or updated Microsoft Windows? If so, Windows resizes the EFI partition and, in the process, destroys it. You’re not the first member of this forum who’s run into that.
manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
==> Mounting (ManjaroLinux) [/dev/sda4]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
mount: /mnt/boot/efi: special device /dev/disk/by-uuid/88A3-1B1C does not exist.
--> mount: [/mnt/home]
then
grub-install --recheck --no-rs-codes --modules="part_msdos part_gpt" --target="x86_64-efi"
update-grub
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.9-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.9-x86_64.img
Found initrd fallback image: /boot/initramfs-5.9-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
See if you can remove the flags from the /dev/sda1 partition, and then try deleting it. If it doesn’t work, then I would suggest deleting your swap partition and using that space to create a new EFI partition and a smaller swap partition. And if that does work, then set the boot or efi flag on the new EFI partition and proceed with the advice in post #4.
as i remember displays often when someone installed grub in efi mode first and then “to repair it”, one installed (maybe be accident) grub in BIOS mode. Grub tries to write the MBR at the beginning and that could indeed destroy the first partition @maxemilian .
I guess you have to recreate the efi partition, correct the UUID at /etc/fstab, chroot and reinstall grub in efi mode like @Aragorn has described above.
I didn’t get any error, Disks are completely different which I don’t ruin my main ssd. But all they connected to computer.
Just installed USB HDD manjaro gnome via boot flash memory.
I installed gpt efi second disk and not touched bios.
Now I doesn’t get grub error no longer. I’ll check shortly after
Its working sdb1 which mentioned hdd installed gnome shows more than above value
sudo dosfsck -t -a /dev/sdb1 ✔
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00
Not automatically fixing this.
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
*** Filesystem was changed ***
Writing changes.
/dev/sdb1: 6 files, 74/76643 clusters
Thank you so much guys @megavolt@Aragorn@robin0800 for any help
I’m able to manage this hard core grub error.
I took risk to gpt table repairing first then edited `sda1 with gnome external disk
sudo sfdisk -d /dev/sda > PT_sda.txt
because I can’t manage to deal with reformat /sda1 as fat32 via booting disk. I don’t know exactly why.
First formatted sda1 as ext4 with gpart or sth else Gnome on external disk
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 301M 0 part
├─sda2 8:2 0 195.3G 0 part
├─sda3 8:3 0 163.9G 0 part
├─sda4 8:4 0 98.3G 0 part
└─sda5 8:5 0 8G 0 part
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 300M 0 part /boot/efi
└─sdb2 8:18 0 465.5G 0 part /
sr0 11:0 1 1024M 0 rom
[axe@axe-20aws2t12n ~]$ sudo sfdisk -d /dev/sda > PT_sda.txt
sudo mkfs.vfat /dev/sda1
mkfs.fat 4.2 (2021-01-31)
sudo su
mount /dev/sda1 /run/media/manjaro/1974023c-5c86-4884-a3ce-c8e99ca4bf9e/mnt/boot/efi/
manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
==> Mounting (ManjaroLinux) [/dev/sda4]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
mount: /mnt/boot/efi: special device /dev/disk/by-uuid/23426fd0-0da4-4d80-bbb4-c72d3e3fa473 does not exist.
--> mount: [/mnt/home]
Format sda1 as Fat32 sudo mkfs.msdos -F 32 /dev/sda1
I’ll change wrong UUDI on fstab file with correct one sudo xed /run/media/manjaro/1974023c-5c86-4884-a3ce-c8e99ca4bf9e/etc/fstab
, actually there is but I cant access it
Its come true 
It was great fat32 fantasy 