As others have stated, exfat is almost always the best choice for an external data drive that you need to share between multiple OSes. It is generally a better choice than fat32/vfat.
I try to follow the CLI example from the turtorial.
sudo fdisk -l
sudo mkfs.exfat -n LABEL /dev/sdXn
But I do not know why I receive this message :
sudo: mkfs.exfat: command not found
I did replace the /dev/sdXn with my model PSSD T7.
[TemplePusher@jonas-bloch-riisgaard ~]$ sudo fdisk -l
[sudo] password for TemplePusher:
Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 870
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x314eed62
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2099199 2097152 1G 83 Linux
/dev/sda2 2099200 1953523711 1951424512 930,5G 83 Linux
Disk /dev/mapper/luks-3c0c1315-ade4-4e2f-a5d0-936d7fb734f5: 930,5 GiB, 999112572928 bytes, 1951391744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/loop2: 55,42 MiB, 58114048 bytes, 113504 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop0: 99,46 MiB, 104288256 bytes, 203688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop5: 162,87 MiB, 170778624 bytes, 333552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop4: 55,44 MiB, 58130432 bytes, 113536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop3: 98,59 MiB, 103378944 bytes, 201912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop6: 164,76 MiB, 172761088 bytes, 337424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop8: 218,99 MiB, 229629952 bytes, 448496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop7: 219 MiB, 229638144 bytes, 448512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop9: 65,1 MiB, 68259840 bytes, 133320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop11: 32,1 MiB, 33660928 bytes, 65744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop12: 32,31 MiB, 33878016 bytes, 66168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop10: 65,21 MiB, 68378624 bytes, 133552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop13: 226,23 MiB, 237223936 bytes, 463328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sdb: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: PSSD T7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 4A47AB00-717F-49ED-96EA-D67DAF1C98CC
Device Start End Sectors Size Type
/dev/sdb1 40 409639 409600 200M EFI System
/dev/sdb2 409640 1953525127 1953115488 931,3G Apple APFS
[TemplePusher@jonas-bloch-riisgaard ~]$ sudo mkfs.exfat -n LABEL PSSD T7
[sudo] password for TemplePusher:
sudo: mkfs.exfat: command not found
[TemplePusher@jonas-bloch-riisgaard ~]$
This should get you there:
sudo dnf install exfatprogs
Ah now I get it. There was no exfat program installed. Thanks
I receive an error message when trying the Method 1 which Format disk as exFAT using GNOME Disks tool
But it did work by not filling any name or initials in.
But after the ExFat formation I can not enter the disk because the files are not reconized
I donât think it actually worked because your second screenshot still says âunknown filesystem type: apfsâ, so it looks to still be formatted in APFS, not ExFAT.
I donât remember if mkfs.exfat
will format a partition if itâs already formatted.
Follow the directions in the following article: first the âDeleting existing partitionsâ section to delete the existing APFS partition, then the âCreating new partitionsâ section to make a new ExFAT partition.
Use gparted
Great! Seems like it worked. Now the Samsung T7 1 TB SSD is ExFat.
Thank you all for your patiences and help.
I also tried to do the formating in Gparted bout with out succes. The disk is encrypted and I couldnât get acces to format it.
Maybe there is a possibility that APFS is somehow blocking the formating of a new ExFat. It also appear busy. It could also be (now Iâm guessing. No facts of prove) the issue of Apple protects their fileformat as you further concluded. But formating means erasing everything on the disk but it can be writeprotected by standard of APFS perhaps.
After I succeed formating to ExFat by the graphical example Format SSD to ExFat graphical example I discover that there became an exstra partipation of a 210 MB Volume in Places under my Home folder.
Be very careful! You are looking at /dev/sda# here, not /dev/sdb#, you can easily lose data if youâre not careful about which disk you are working on.
You have an extra partition (/dev/sdb1), which you can see in your screenshot above (itâs the section colored in blue):
I"m assuming thatâs the EFI partition that was put on there when it was originally formatted on the Mac. You can get rid of it if you want, since this isnât going to be a boot disk.
That was /dev/sda. I am sure you did not want to format your system disk.
Maybe you have encrypted the drive with luks
As @computersavvy already mentioned you forgot to select the Hard-drive. On the top right you have a pull-down menu where you can select it.
/dev/sda
indicates the first drive and the number the partition on the drive.
lsblk
shows you the block-devices nicely.
Btw, good practice is also to set a label to identify it easily. In your case data-exfat would make sense to indicate that it is accessible with all your OSâes you mentioned in the Topic.
This label is also the name you see in the file manager.
A easy way to set a label is to do it with gparted. You just have to
In Gparted >> View >> File System Support
you will get an idea what you can use gparted for and what packages you need for it
as @guiltydoggy told you for exfat.
NOOOO!
But I did not
Will have a try on that one
Could be. But I think It was writeprotected
Now living with a splited partion in 2. After doing the ExFat 2 partions occure. Even that I can acces the files on both Linux and Mac