Determining File System of volume

disk-utilitydisk-volumefilesystemhard drivepartition

I would like to know the FileSystem is used by Hard Disk/Volume

Here one List with some FileSystems:

HFS+
APFS
NTFS
exFAT
extFS
Ext4

Here the pictures…

For me that information is not clear.

According to Pictures What File System (from the List) I need to assume?

EDIT:

sh-3.2# diskutil list /dev/disk7
/dev/disk7 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk7
   1:                        EFI EFI                     209.7 MB   disk7s1
   2:                  Apple_HFS HD710A                  999.9 GB   disk7s2
sh-3.2#

Other command

sh-3.2# diskutil info /dev/disk7
   Device Identifier:         disk7
   Device Node:               /dev/disk7
   Whole:                     Yes
   Part of Whole:             disk7
   Device / Media Name:       HD710A

   Volume Name:               Not applicable (no file system)
   Mounted:                   Not applicable (no file system)
   File System:               None

   Content (IOContent):       GUID_partition_scheme
   OS Can Be Installed:       No
   Media Type:                Generic
   Protocol:                  USB
   SMART Status:              Not Supported

   Disk Size:                 1.0 TB (1000204886016 Bytes) (exactly 1953525168 512-Byte-Units)
   Device Block Size:         512 Bytes

   Read-Only Media:           No
   Read-Only Volume:          Not applicable (no file system)

   Device Location:           External
   Removable Media:           Fixed

   Solid State:               Info not available
   Virtual:                   No

sh-3.2#

OTHER EDIT:

sh-3.2# diskutil listFilesystems
Formattable file systems

These file system personalities can be used for erasing and partitioning.
When specifying a personality as a parameter to a verb, case is not considered.
Certain common aliases (also case-insensitive) are listed below as well.

-------------------------------------------------------------------------------
PERSONALITY                     USER VISIBLE NAME                               
-------------------------------------------------------------------------------
Case-sensitive APFS             APFS (Case-sensitive)                           
  (or) APFSX
APFS                            APFS                                            
  (or) APFSI
ExFAT                           ExFAT                                           
Free Space                      Free Space                                      
  (or) FREE
MS-DOS                          MS-DOS (FAT)                                    
MS-DOS FAT12                    MS-DOS (FAT12)                                  
MS-DOS FAT16                    MS-DOS (FAT16)                                  
MS-DOS FAT32                    MS-DOS (FAT32)                                  
  (or) FAT32
HFS+                            Mac OS Extended                                 
Case-sensitive HFS+             Mac OS Extended (Case-sensitive)                
  (or) HFSX
Case-sensitive Journaled HFS+   Mac OS Extended (Case-sensitive, Journaled)     
  (or) JHFSX
Journaled HFS+                  Mac OS Extended (Journaled)                     
  (or) JHFS+
UFSD_NTFS                       Microsoft NTFS                                  
UFSD_EXTFS                      extFS 2                                         
UFSD_EXTFS3                     extFS 3                                         
UFSD_EXTFS4                     extFS 4                                         
sh-3.2#

diskutil info disk7s2

sh-3.2# diskutil info disk7s2
   Device Identifier:         disk7s2
   Device Node:               /dev/disk7s2
   Whole:                     No
   Part of Whole:             disk7

   Volume Name:               HD710A
   Mounted:                   Yes
   Mount Point:               /Volumes/HD710A

   Partition Type:            Apple_HFS
   File System Personality:   Journaled HFS+
   Type (Bundle):             hfs
   Name (User Visible):       Mac OS Extended (Journaled)
   Journal:                   Journal size 81920 KB at offset 0x1d1c000
   Owners:                    Disabled

   OS Can Be Installed:       Yes
   Media Type:                Generic
   Protocol:                  USB
   SMART Status:              Not Supported
   Volume UUID:               E70BFAA0-6059-3E92-91D1-0C9B603E682D
   Disk / Partition UUID:     9864BEC6-897D-4D4F-A8DA-60A7594D5222
   Partition Offset:          209735680 Bytes (409640 512-Byte-Device-Blocks)

   Disk Size:                 999.9 GB (999860912128 Bytes) (exactly 1952853344 512-Byte-Units)
   Device Block Size:         512 Bytes

   Volume Total Space:        999.9 GB (999860912128 Bytes) (exactly 1952853344 512-Byte-Units)
   Volume Used Space:         752.1 GB (752090554368 Bytes) (exactly 1468926864 512-Byte-Units) (75.2%)
   Volume Free Space:         247.8 GB (247770357760 Bytes) (exactly 483926480 512-Byte-Units) (24.8%)
   Allocation Block Size:     4096 Bytes

   Read-Only Media:           No
   Read-Only Volume:          No

   Device Location:           External
   Removable Media:           Fixed

   Solid State:               Info not available

sh-3.2#

Best Answer

In the upper image, a drive is highlighted. This drive is using a "GUID Partition Map". In the lower image, a partition on the drive is highlighted. I see the file system is "Mac OS Extended (Journaled)". The label is "HD710A".

User Gordon Davisson has suggested the following (in a comment):

One source of confusion: "Mac OS Extended (Journaled)" is the user-friendly name for Journaled HFS+ (sometimes abbreviated JHFS+). You can get a list of name equivalences with diskutil listFilesystems.

Below is the output from diskutil listFilesystems when entered in a Big Sur (macOS 11.2) Terminal application window.

Formattable file systems

These file system personalities can be used for erasing and partitioning.
When specifying a personality as a parameter to a verb, case is not considered.
Certain common aliases (also case-insensitive) are listed below as well.

-------------------------------------------------------------------------------
PERSONALITY                     USER VISIBLE NAME                               
-------------------------------------------------------------------------------
Case-sensitive APFS             APFS (Case-sensitive)                           
  (or) APFSX
APFS                            APFS                                            
  (or) APFSI
ExFAT                           ExFAT                                           
Free Space                      Free Space                                      
  (or) FREE
MS-DOS                          MS-DOS (FAT)                                    
MS-DOS FAT12                    MS-DOS (FAT12)                                  
MS-DOS FAT16                    MS-DOS (FAT16)                                  
MS-DOS FAT32                    MS-DOS (FAT32)                                  
  (or) FAT32
HFS+                            Mac OS Extended                                 
Case-sensitive HFS+             Mac OS Extended (Case-sensitive)                
  (or) HFSX
Case-sensitive Journaled HFS+   Mac OS Extended (Case-sensitive, Journaled)     
  (or) JHFSX
Journaled HFS+                  Mac OS Extended (Journaled)                     
  (or) JHFS+

The Disk Utility application does not always display all partitions and/or volumes. The drive in your example probably has an "FAT32" formatted EFI partition and may have a "Mac OS Extended (Journaled)" formatted macOS Recovery partition.

To get a better idea of all partitions and volumes, you should enter the command diskutil list in a Terminal application window. Additional information can be obtained by using the diskutil info device command, where device can be an identifier or label.

Note: After using the Disk Utility application to perform a drive operation, you may need to quit (or Force Quit) and open the Disk Utility to see the correct results.

Also, the Disk Utility and diskutil commands show cached information about unmounted volumes. For example, if you were to use the newfs_msdos command to format and change the label of an unmounted EFI volume, the Disk Utility and diskutil command would not show the change until after the EFI partition was mounted or macOS was restarted.

Update:

After reading the addition input provided when the OP edited the question, I can add the information being sought can be output by entering the following commands. Here, device should to be replaced by either an identifier or label.

diskutil info -plist device | grep -A1 -e FilesystemName -e Content

These commands can be placed in a function, as shown below.

fs() { diskutil info -plist $1|grep -A1 -e FilesystemName -e Content; }

The Content is the name assigned by macOS to the partition type stored in the drive partition table. The FilesystemName is the name assign by macOS to volume format.

Here is an example from a 2011 iMac with a Windows 10, High Sierra, Ubuntu triple boot setup. Below is the output from diskutil list.

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:       Microsoft Basic Data Coelacanth              100.0 GB   disk0s2
   3:       Microsoft Basic Data COELACANTH2             48.9 GB    disk0s3
   4:                  Apple_HFS Marlin                  250.0 GB   disk0s4
   5:                 Apple_Boot Recovery HD             650.0 MB   disk0s5
   6:                  Apple_HFS Linux HFS+ ESP          209.7 MB   disk0s6
   7:           Linux Filesystem                         82.7 GB    disk0s7
   8:                 Linux Swap                         16.4 GB    disk0s8
   9:                  Apple_HFS UBUNTU                  939.5 MB   disk0s9
  10:       Microsoft Basic Data REFIND                  134.2 MB   disk0s10

The commands below will provide the desired information for all the partitions.

for i in  {1..10};do echo disk0s$i;fs disk0s$i;done

The output is given below. The no FilesystemName match was found identifier disk0s7 because normally macOS can not mount ext4 formatted Linux partitions.

disk0s1
    <key>Content</key>
    <string>EFI</string>
--
    <key>FilesystemName</key>
    <string>MS-DOS FAT32</string>
disk0s2
    <key>Content</key>
    <string>Microsoft Basic Data</string>
--
    <key>FilesystemName</key>
    <string>NTFS</string>
disk0s3
    <key>Content</key>
    <string>Microsoft Basic Data</string>
--
    <key>FilesystemName</key>
    <string>ExFAT</string>
disk0s4
    <key>Content</key>
    <string>Apple_HFS</string>
--
    <key>FilesystemName</key>
    <string>Journaled HFS+</string>
disk0s5
    <key>Content</key>
    <string>Apple_Boot</string>
--
    <key>FilesystemName</key>
    <string>Journaled HFS+</string>
disk0s6
    <key>Content</key>
    <string>Apple_HFS</string>
--
    <key>FilesystemName</key>
    <string>HFS+</string>
disk0s7
    <key>Content</key>
    <string>Linux Filesystem</string>
disk0s8
    <key>Content</key>
    <string>Linux Swap</string>
--
    <key>FilesystemName</key>
    <string>Linux Swap</string>
disk0s9
    <key>Content</key>
    <string>Apple_HFS</string>
--
    <key>FilesystemName</key>
    <string>Journaled HFS+</string>
disk0s10
    <key>Content</key>
    <string>Microsoft Basic Data</string>
--
    <key>FilesystemName</key>
    <string>MS-DOS FAT16</string>

Here is another example from a VirtualBox virtual machine with a Big Sur and Windows 10 dual boot setup. Below is the output from diskutil list.

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *274.9 GB   disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         224.3 GB   disk0s2
   3:       Microsoft Basic Data ⁨BOOTCAMP⁩                50.4 GB    disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +224.3 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨BigSurNVMe - Data⁩       2.3 GB     disk1s1
   2:                APFS Volume ⁨Preboot⁩                 292.5 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                613.6 MB   disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk1s4
   5:                APFS Volume ⁨BigSurNVMe⁩              15.1 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.1 GB    disk1s5s1
   7:                APFS Volume ⁨MyStuff⁩                 802.8 KB   disk1s7

The commands below will provide the desired information for all the physical partitions.

for i in {1..3}; do echo disk0s$i;fs disk0s$i;done

The output is given below. The no FilesystemName match was found identifier disk0s2 because this partition has an APFS container.

disk0s1
    <key>Content</key>
    <string>EFI</string>
--
    <key>FilesystemName</key>
    <string>MS-DOS FAT32</string>
disk0s2
    <key>Content</key>
    <string>Apple_APFS</string>
disk0s3
    <key>Content</key>
    <string>Microsoft Basic Data</string>
--
    <key>FilesystemName</key>
    <string>NTFS</string>

The command below will provide the desired information for all the APFS volumes.

for i in {1..5} 5s1 7; do echo disk1s$i;fs disk1s$i;done

The output is given below. These volumes reside in an APFS container and therefore do have a partition type stored in a drive partition table. Internally, macOS uses the UUID of 41504653-0000-11AA-AA11-00306543ECAC for the Context. Eventually, macOS has not assigned a name to this UUID.

disk1s1
    <key>Content</key>
    <string>41504653-0000-11AA-AA11-00306543ECAC</string>
--
    <key>FilesystemName</key>
    <string>APFS</string>
disk1s2
    <key>Content</key>
    <string>41504653-0000-11AA-AA11-00306543ECAC</string>
--
    <key>FilesystemName</key>
    <string>APFS</string>
disk1s3
    <key>Content</key>
    <string>41504653-0000-11AA-AA11-00306543ECAC</string>
--
    <key>FilesystemName</key>
    <string>APFS</string>
disk1s4
    <key>Content</key>
    <string>41504653-0000-11AA-AA11-00306543ECAC</string>
--
    <key>FilesystemName</key>
    <string>APFS</string>
disk1s5
    <key>Content</key>
    <string>41504653-0000-11AA-AA11-00306543ECAC</string>
--
    <key>FilesystemName</key>
    <string>APFS</string>
disk1s5s1
    <key>Content</key>
    <string>41504653-0000-11AA-AA11-00306543ECAC</string>
--
    <key>FilesystemName</key>
    <string>APFS</string>
disk1s7
    <key>Content</key>
    <string>41504653-0000-11AA-AA11-00306543ECAC</string>
--
    <key>FilesystemName</key>
    <string>Case-sensitive APFS</string>

Related Solutions

Fusion Drive – Repairing Possible Mess-Up on 1TB iMac with BootCamp

Theoretically everything is fine with your Fusion Drive. Fusion Drives look like this. Disk0 is your SSD with 121 GB and disk1 is your HDD with ~1 TB (~1.121 TB summed up).

The larger parts of your SSD (disk0s2) and your HDD (disk1s2) are pooled to a CoreStorage LVG (Fusion Drive: disk3) with a size of 967.8 GB. The rest is reserved for EFIs, a Recovery HD (alltogether ~1.3 GB) and your old Windows partition - now probably free space (~152 GB).

The logical volume 'Macintosh HD' (967.8 GB) spans disk0s2 and disk1s2. This is the first 'Macintosh HD' in picture 1. The volume 'Macintosh HD' - it's the one visible on the desktop - should ideally also have about 967.8 GB. This is the second 'Macintosh HD' in picture 1.
In fact it has only 852.67 GB (see picture 3).

In the second picture the logical volume 'Macintosh HD' is the first listed in black, the volume 'Macintosh HD' is the second listed in black, the other two 'Macintosh HD's listed in grey are the parts of your SSD and HDD dedicated to the logical volume 'Macintosh HD'.

In my opinion something went wrong after deleting various partitions with the Bootcamp Assistant/Disk Utility or in Windows.

Preparation:

Detach any external drive (especially your external Time Machine backup drive)
Restart to Internet Recovery Mode by pressing alt cmd R at startup.
The prerequisites are the latest firmware update installed, either ethernet or WLAN (WPA/WPA2) and a router with DHCP activated.
On a 50 Mbps-line it takes about 4 min (presenting a small animated globe) to boot into a recovery netboot image which usually is loaded from an apple/akamai server.

I recommend ethernet because it's more reliable. If you are restricted to WIFI and the boot process fails, just restart your Mac until you succeed booting.

Alternatively you may start from a bootable installer thumb drive (preferably Mavericks or Yosemite) or a thumb drive containing a full system (preferably Mavericks or Yosemite).

Now you may either repair CoreStorage or rebuild your Fusion Drive:

'Repair CoreStorage' (not recommended):

First i would try to check the volume 'Macintosh HD' with Disk Utility. If the volume is corrupted consider a reinstall of Mac OS X.
If the volume is ok quit Disk Utility
Open Terminal and enter diskutil unmountDisk /dev/LVIdentifier and both diskutil unmountDisk /dev/DiskContainingApple_CoreStorageIdentifier
In your case: first diskutil unmountDisk /dev/disk3 then diskutil unmountDisk /dev/disk0 and diskutil unmountDisk /dev/disk1
remove the EFI NO NAME partition with gpt remove -i IndexNumberOfEFINoName DiskIdentifier:
gpt remove -i 4 disk1
Remount the CoreStorage disks and then the Logical Volume:
In your case: first diskutil mountDisk /dev/disk0 and diskutil mountDisk /dev/disk1 and then diskutil mount /dev/disk3.

enter gpt -r -vvv show /dev/diskIdentfierOfApple_CoreStorage to get infos of your HDD CoreStorage disk.
In your case: gpt -r -vvv show /dev/disk1
It should look like this:

-bash-3.2# gpt -r -vvv show /dev/disk1
gpt show: /dev/disk1: mediasize=1000204886016; sectorsize=512;         blocks=1953525168
gpt show: /dev/disk1: PMBR at sector 0
gpt show: /dev/disk1: Pri GPT at sector 1
gpt show: /dev/disk1: GPT partition: type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, start=40, size=409600
gpt show: /dev/disk1: GPT partition: type=53746F72-6167-11AA-AA11-00306543ECAC, start=409640, size=1671210848
gpt show: /dev/disk1: GPT partition: type=426F6F74-0000-11AA-AA11-00306543ECAC, start=1671620488, size=1269760
gpt show: /dev/disk1: Sec GPT at sector 1953525167                               
     start          size  index contents                                        
         0             1        PMBR                                            
         1             1        Pri GPT header                                  
         2            32        Pri GPT table                                   
        34             6
        40        409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
    409640    1671210848      2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
1671620488       1269760      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
1672890248     280634887
1953525135            32        Sec GPT table
1953525167             1        Sec GPT header

The free space on your HDD has 280634887 blocks. Please calculate the biggest block number dividable through 8. That's 280634880 blocks (á 512 bytes) which equals 143685058560 B or ~143.7 GB. Add the size of your HDD CoreStorage Physical Volume (852666400768 B) The result is 143685058560 B + 852666400768 B = 996351459328 B
Resize your HDD CoreStorage physical volume with diskutil cs resizeDisk HDDPVUUID newsize
In your case: diskutil cs resizeDisk 93892BE8-2B7F-4ABD-A4C3-984495DCD98D 996351459328b
Calculate the maximal size of your CoreStorage Logical Volume in diskutil cs list: (size disk0s2) + (size disk1s2) In your case that's 120988852224 B + 996351459328 B = 1117340311552 B. That should be the size of your refreshed Logical Volume Group.
Resize your Logical Volume with diskutil cs resizeVolume LVUUID LVGSize-128 MB In your case that's diskutil cs resizeVolume D237FFDC-7DA4-41D7-AC13-4CC7E5E8C0A0 1117212311552b. If you get an error (There is not enough free space...) choose a smaller size like 1117148311552b.
Quit Terminal and open Disk Utility.
Check your expanded CoreStorage Volume for errors.
Quit Disk Utility, choose your CS volume as startup disk and restart your Mac

'Rebuild Fusion Drive' (recommended if you have a Time Machine backup)

Booted to Internet Recovery Mode open Utilities → Terminal in the menubar and enter:
diskutil cs list to get the CoreStorage listing.
Copy the Logical Volume UUID, it's the fifth listed.
Now delete the Logical Volume with diskutil cs deleteVolume LVUUID.
In your case: diskutil cs deleteVolume D237FFDC-7DA4-41D7-AC13-4CC7E5E8C0A0.
Copy the Logical Volume Group UUID, it's the first listed in the listing of diskutil cs list.
Then delete the Logical Volume Group with diskutil cs delete LVGUUID.
In your case: diskutil cs delete 1EFE58BC-3613-44C4-86EE-D816F3B66E3E
Enter exit and quit 'Terminal'
Open 'Disk Utility'. Enter 'Ignore' if you are asked to fix the drives.
Choose your SSD and partition it: 1 Partition Mac OS X Extended (Journaled), hit the Options button and choose GUID Partiton table and hit OK and Apply.
Please check that the size is ~121 GB

Example:
Choose your HDD and partition it: 1 Partition Mac OS X Extended (Journaled), hit the Options button and choose GUID Partiton table and hit OK and Apply.
Please check that the size is ~1 TB

Example:
Quit Disk Utility and open Terminal
Enter diskutil list

Example (your disk identifiers and sizes are different of course: Your volume SSD probably has the Identifier disk0s2 and the size 121 GB and your volume HDD probably has the Identifier disk1s2 and the size 1.0 TB):
Enter diskutil cs create "Name" IdentifierSSD IdentifierHDD
In your case probably diskutil cs create "Macintosh HD" disk0s2 disk1s2.

Copy the resulting LVGUUID

Example:
Enter diskutil cs CreateVolume LVGUUID jhfs+ "Macintosh HD" 100%.

Example:
Enter diskutil cs list
Check the size of your Logical Volume. It should have the size ~1.121 TB

Example:
Quit Terminal
Open 'Disk Utility' and check your newly created volume for errors
Quit 'Disk Utility'
Attach your external Time Machine backup drive or check this answer if you use NAS or another network share.
Open 'Restore from Time Machine Backup'
Choose the appropriate Time Machine backup and restore your system
Reboot to your restored system.
Unmount and detach your Time Machine backup drive
Open 'Terminal' and enter 'diskutil list'
Check if your 'Recovery HD' is listed.
If your 'Recovery HD' is missing, usually reinstalling your current system with the latest available system installer (e.g. 'Install OS X Mavericks (10.9.5)' if Mavericks is currently installed) will recreate it without loosing any data. AFAIK Recovery Partition Creator 3.8 will NOT create a Recovery HD on CoreStorage volumes.
After reinstalling the system with the latest available system installer open App Store and install the latest security fixes.

MacOS – EFI automounts on startup

Since El Capitan this is the behavior of Workgroupmanager for local accounts if you enable to manage internal harddrives to be only readable for some users. It doesn't matter which user logs in. If there is only one user managed, the EFI partition will show up on start for all useres. Disabling this in Workgroupmanager again hides the EFI partition, too. Since Workgroupmanager was lastly updated on Mavericks it is still possible to manage e.g. USB shares to be only readable without having to install a OSX Server, as there is no on board solution for managing user accounts more differentiated than with System preferences.

Best Answer

Update:

Related Solutions

Fusion Drive – Repairing Possible Mess-Up on 1TB iMac with BootCamp

MacOS – EFI automounts on startup

Related Question