List disks, including internal and external disks, whole disks and partitions, and various kinds of virtual or offline disks. If no argument is given, then all whole disks and their partitions are listed. You can limit the number of disks shown by specifying filtering arguments such as internal above, and/or a device disk.
Disk Utility in Mac OS X 10.4 (Tiger) will not let the user choose third party file systems such as Tuxera NTFS for Mac when creating and formatting volumes, but in Mac OS X 10.5 (Leopard) this has been fixed. The command line utility diskutil (a command line version of Disk Utility) works with Tuxera NTFS for Mac in 10.4 and above. Description diskutil manipulates the structure of local disks. It provides information about, and allows the administration of, the partitioning schemes, layouts, and formats of disks. This includes hard disks, solid state disks, optical discs, disk images, APFS volumes, CoreStorage volumes, and AppleRAID sets. Manage hidden volumes on your Mac While Disk Utility will allow you to partition, repair, erase, and manage drives that you’ve attached and mounted on your Mac, it can also show those that are. I'm on Mac OS X 10.6.8 and bought NTFS 4TB Seagate USB3.0 drive. Plugged in, Mac allowed me to read files from it, but not write to it. When I select 'Get Info' for the volume/disk, I see 'You can read only' under 'Sharing & Permissions'. I copied a large file from Windows 10 to the USB Drive, worked fine.
The final commands should be modified appropriate to your disk and partition. Enter:
diskutil list
Check the number of disk and partition. Then X and Y in diskXsY parameters in commands from further steps must be replaced with appropriate values (for example disk1s1)
Format:
First it is required to unmount volume with
sudo diskutil unmount diskXsY
Then format the partition:
sudo diskutil eraseVolume “<filesystem>” “LABEL” /dev/diskXsY
or format the whole disk:
sudo diskutil eraseDisk “<filesystem>” “LABEL” /dev/diskX
Possible values for <filesystem>:
UFSD_NTFS – Windows NT File System*
UFSD_EXTFS – Linux Extended File System 2**
UFSD_EXTFS3 – Linux Extended File System 3**
UFSD_EXTFS4 – Linux Extended File System 4**
* for NTFS for Mac
** for ExtFS for Mac
“LABEL” – specify volume label.
To change partition table format, please add the following value after “LABEL”:
GPTFormat – GUID Partition Table
MBRFormat – Master Boot Record
APMFormat – Apple Partition Map
OS9Drivers – Apple Partition Map (for Mac OS 9)
To verify the volume:
diskutil verifyVolume /dev/diskXsY
To repair the volume:
diskutil repairVolume /dev/diskXsY
ExtFS for Mac, General, NTFS for Mac OS X
Tags: extf, format, mac, ntfs, terminal
Has this article been helpful for your request?
(32 votes, average: 1.94 out of 5)
Disk utilities - Format, Verify, Repair (local disks.) This includes options not available in the Disk utility GUI.
Each verb is listed below with its description and individual arguments.
List disks, including internal and external disks, whole disks and partitions, and various kinds of virtual or offline disks.
If no argument is given, then all whole disks and their partitions are listed.
You can limit the number of disks shown by specifying filtering arguments such as internal above, and/or a device disk. When limiting by a disk, you can specify either a whole disk, e.g. disk0, or any of its slices, e.g. disk0s3, but filtering is only done at the whole disk level (disk0s3 is a synonym for disk0 in this case).
If -plist is specified, then a property list will be emitted instead of the normal user-readable output.
A script could interpret the results of diskutil list -plist and use diskutil info -plist as well as diskutil listFilesystems -plist for more detailed information.
The top-to-bottom appearance of all whole disks is sorted in numerical order by unit (whole disk) number. However, within each whole disk's 'sublist' of partitions, the ordering indicates actual on-disk location. The first disk item listed represents the partition which is located most near the beginning of its encompassing whole disk, and so on.
When viewed this way, the slice (partition) parts of the BSD disk identifiers may, in certain circumstances, not appear in numerical order. This is normal and is likely the result of a recent partition map editing operation in which volumes were kept mounted.
Note that both human-readable and plist output are sorted as described above.
See the DEVICES section below for the various forms that the device specification may take for this and all of the other diskutil verbs.
Get detailed information about a specific whole disk or partition. If -plist is specified, then a property list instead of the normal user-readable output will be emitted. If -all is specified, then all disks (whole disks and their partitions) are processed.
Continuously display system-wide disk manipulation activity as reported by the Disk Arbitration framework until interrupted with a signal (e.g. by typing Control-C).
This can be useful to watch system-wide activity of disks coming on-line or being ejected, volumes on disks being mounted or unmounted, volumes being renamed, etc. However, this output must never be parsed; programs should become Disk Arbitra tion clients instead.
For debugging information, such as the monitoring of applications dissenting (attempting to deny) activities for disks for which they have registered an interest, you must use the logging features of the diskarbitrationd daemon. Programs needing this information must become Disk Arbitration clients.
Show the file system personalities available for formatting in diskutil when using the erasing and partitioning verbs. This
is a subset of the complete set of personalities exported by the various file system bundles that may be installed in the system. Also shown are some shortcut aliases for common personalities. See the FORMAT section below for more details. If -plist is specified, then a property list instead of the normal user-readable output will be emitted.
Unmount a single volume. Force will force-unmount the volume (less kind to any open files; see also umount (8)).
Unmount an entire disk (all volumes). Force will force unmount the volumes (less kind to any open files; see also umount (8)). You should specify a whole disk, but all volumes of the whole disk are attempted to be unmounted even if you specify a partition.
Eject a disk. Media will become offline for the purposes of being a data store for file systems or being a member of constructs such as software RAID or direct data. Additionally, removable media will become eligible for safe manual removal; automatically-removable media will begin its physical (motorized) eject sequence.
Mount a single volume. If readOnly is specified, then the file system is mounted read-only, even if the volume's underlying file system and/or device and/or media supports writing; even the super-user may not write to it; this is the same as the rdonly option to mount (8). If a -mountPoint is specified, then that path, rather than the standard path of /Volumes/VolumeName, will be used as the view into the volume file
content; a directory at that path must already exist.
Mount all mountable and UI-browsable volumes on the given partition map; that is, a mount is attempted on the directly mountable volume, if any, on each of the whole disk's partitions. However, 'virtual' volumes, such as those are implied by e.g. Core Storage Physical Volumes, AppleRAID Members, etc., are not handled. You should specify a whole disk, but all volumes of the whole disk are attempted to be mounted even if you specify a partition.
Rename a volume. Volume names are subject to file system-specific alphabet and length restrictions.
Repair a split Fusion Drive, see HT207584
Enable journaling on an HFS+ volume. This works whether or not the volume is currently mounted (the volume is temporarily
mounted if necessary). Ownership of the affected disk is required.
Disable journaling on an HFS+ volume. This normally works whether or not the volume is currently mounted (the volume is
temporarily mounted if necessary). If the -force option is specified, then journaling is disabled directly on disk; in this case, the volume must not be mounted. Ownership of the affected disk is required.
Create a 512MB Apple_Journal partition using the journalDevice partition to serve as a journal for the volume device. For best results, journalDevice should be a partition on a different whole-disk than the volume itself.
The journal for device will be moved externally onto the newly created Apple_Journal partition.
Since the journalDevice you specify will invariably be larger than 512MB, a new HFS+ partition will be created following the Apple_Journal partition to fill the remaining space.
Moving the journal works whether or not the volume is mounted, provided journaling is enabled on that volume. No errors are
currently supported to flag attempts to move journals on volumes that do not have journaling enabled. If you have multiple volumes for which you want external journals, each must have its own external Apple_Journal partition. Ownership of the affected disks is required.
Move the journal for device back locally (onto that same device). Ownership of the affected disk is required.
Enable ownership of a volume. Download yandere simulator mac. The on-root-disk Volume Database at /var/db/volinfo.database is manipulated such that the User and Group ID settings of files, directories, and links (file system objects, or 'FSOs') on the target volume are taken into account.
This setting for a particular volume is persistent across ejects and injects of that volume as seen by the current OS, even across reboots of that OS, because of the entries in this OS's Volume Database. Note thus that the setting is not kept on the target disk, nor is it in-memory.
For some locations of devices (e.g. internal hard disks), consideration of ownership settings on FSOs is the default. For others (e.g. plug-in USB disks), it is not.
When ownership is disabled, Owner and Group ID settings on FSOs appear to the user and programs as the current user and group instead of their actual on-disk settings, in order to make it easy to use a plug-in disk of which the user has physical possession.
When ownership is enabled, the Owner and Group ID settings that exist on the disk are taken into account for determining access, and exact settings are written to the disk as FSOs are created. A common reason for having to enable ownership is when a disk is to contain FSOs whose User and Group ID settings, and thus permissions behavior overall, is critically important, such as when the plug-in disk contains system files to be changed or added to.
See also the vsdbutil(8) command. Running as root is required.
(re)Partition a disk, removing all volumes. All volumes on this disk will be destroyed. The device parameter specifies which whole disk is to be partitioned. The optional numberOfPartitions parameter specifies the number of partitions to create; if given then the number of parameter
triplets (see below) is expected to match; else, the number of triplets alone given will determine the number of partitions created.
The optional partitioning scheme parameter forces a particular partitioning scheme; if not specified, a suitable default is chosen. They are:
• APM[Format] specifies that an Apple Partition Map scheme should be used. This is the traditional Apple partitioning scheme used to start up a PowerPC-based Macintosh computer, to use the disk as a non-startup disk with any Mac, or to create a multiplatform compatible startup disk.
• MBR[Format] specifies that a Master Boot Record scheme should be used. This is the DOS/Windows-compatible partitioning scheme.
• GPT[Format] specifies that a GUID Partitioning Table scheme should be used. This is the partitioning scheme used to start up an Intel-based Macintosh computer.
For each partition, a triplet of the desired file system format, volume name, and size must be specified. Several other diskutil verbs allow these triplets as well (and for them, the numberOfPartitions parameter is also optional). The triplets must be as follows:
• Format names are of the form jhfs+, HFS+, MS-DOS, etc.; a list of formattable file systems (more precisely, specific file system personalities exported by the installed file system bundles) and common aliases is available from the listFilesystems verb.
Format guides diskutil both in what partition type to set for the partitions (slices) as well as what file system structures to initialize therein, using the file system bundle's plist's FormatExecutable setting which usually points to the appropriate formatter program such as ewfs_hfs(8).
You can specify a format of Free Space to skip an area of the disk.
You can specify the partition type manually and directly with a format of %
• Names are the initial volume names; they must conform to file system specific restrictions.
If a name of %noformat% is specified, then the partition is left blank such that the partition space is carved out, the partition type is set according to the file system format name or explicit type, the partition space is partially erased ('wiped'), but a file system structure is not initialized with any file system's formatter program (e.g. newfs_hfs(8);
this is useful for setting up partitions that will contain user-defined (not necessarily file system) data.
For a triplet whose format is Free Space or a directly-specified partition type, its name is ignored but a dummy name must nevertheless be
present.
• Sizes are floating point numbers followed by a letter or percent sign as described in the SIZES section at the end of this page (e.g. 165536000, 55.3T, 678M, 75%, R).
In addition to explicitly-requested partitions, space (gaps) might be allocated to satisfy certain filesystems' position
and length alignment requirements; space might be allocated for possible future booter partition insertion; and indeed,
actual booter partitions might be implicitly created.
In particular, there is a rule that unrecognized partitions 1GiB or larger automatically acquire booters. Thus, if you create an arbitrary partition with e.g. diskutil partitionDisk disk0 gpt %11112222-1111-2222-1111-111122221111% %noformat% 3gib jhfs+ Untitled r, then a booter partition will also be created. You can always delete that booter with diskutil eraseVolume 'Free Space' dummy disk0s3.
The last partition is usually automatically lengthened to the end of the partition map (disk). You can specify an exact size for your last partition by specifying it as the penultimate triplet and specifying an additional (last) triplet as Free Space. Or you can use the R (remainder) size specifier for one of your middle partitions while specifying an exact size for your last partition.
Ownership of the affected disk is required.
Non-destructively resize a volume (partition); you may increase or decrease its size. Alternatively, takes no action and prints some info.
A size of limits takes no action, but instead will print the range of valid values for the target partition, taking into account current file system and partition map conditions such as files in use and other (immovable) partitions following the target.
A size of mapsize takes no action, but instead will print the size of the encompassing whole-disk device, as well as the size of the entire partition map (all partitions less map overhead). The whole-disk device might be larger than the partition map if the whole-disk device has grown since the partition map was created. Growing a whole-disk device is possible with certain enterprise disk (RAID) systems.
You can grow a volume (partition) (back) to its maximum size possible, provided no new partitions have been created that are in the way, by specifying R for the new volume size. You should use R instead of attempting an absolute value such as 100% because the latter cannot count partition map overhead.
When decreasing the size, new partitions may optionally be created to fill the newly-freed space. To do this, specify the numberOfPartitions, format, name, and size parameters in the same manner as the triplet description for the partitionDisk verb.
Resizing a volume that is currently set as the computer's startup disk will invalidate that setting; use the Startup Disk System Preferences panel or bless (8) to reset the resized volume as the startup disk.
Device refers to a volume; the volume's file system must be journaled HFS+. Valid sizes are a number followed by a capital letter multiplier or percent sign suffix as described in the SIZES section at the end of this page (e.g. 1.5T, 128M, 50%). Ownership of the affected disk is required.
Destructively split a volume into multiple partitions. You must supply a list of new partitions to create in the space of
the old partition; specify these with the numberOfPartitions, format, name, and size parameters in the same manner as the
triplet description for the partitionDisk verb.
For one of your triplets, you can optionally specify the R meta-size in lieu of a constant number value for the size
parameter: the substituted value will be exactly the amount of space necessary to complete the re-filling of the original
partition with all of your triplets.
Device refers to a volume. Ownership of the affected disk is required.
Diskutil Mount
Merge two or more partitions on a disk. All data on merged partitions other than the first will be lost. Data on the first partition will be lost as well if the force argument is given.
If force is not given, and the first partition has a resizable file system (e.g. JHFS+), the file system will be preserved and grown in a by which an APFS Container is identified is by its APFS Container Reference disk (device). You should treat this as an opaque reference token.
The Container Reference disk is a synthesized whole disk which is exported by APFS for identification purposes only; it has no storage. It is associated with the AppleAPFSContainerScheme node in the IO Registry. While APFS Volume device identifiers appear to be of a related form, you should never use the Container Reference as a basis to create device identifiers yourself; use the listing verbs with their plist options instead.
• Physical Store - An APFS Physical Store is a disk which is imported into (that is, which backs, indeed defines) an APFS Container. An APFS Container can import more than one Physical Store.
An APFS Physical Store disk is not necessarily a disk from a partition map; it could be e.g. an AppleRAID Set disk. Therefore, you must never assume that an APFS Physical Store's disk identifier is a 2-part form such as disk0s2.
• Volume - An APFS Volume is an [un]mountable file system volume which is exported from an APFS Container. Zero or more APFS Volumes may be exported out of an APFS Container.
APFS Volumes have no specified 'size' (capacity). Instead, all APFS Volumes consume capacity out of the remaining free space of their parent APFS Container, consuming or returning such capacity as user file data is added or deleted. Note that this means
that all Volumes within a Container compete for the Container's remaining capacity. However, you can manage Volume allocation with the optional reserve and quota size values.
The optional reserve size requests an assured minimum capacity for an APFS Volume. If successfully created, the Volume is guaranteed to be able to store at least this many bytes of user file data. Note that beyond this, the Volume might be able to store even more until constrained by reaching zero free space in its parent Container or by reaching a quota, if any. You can use a reserve to prevent running out of capacity due to competition from other Volumes or from a Container shrink attempt.
The optional quota size applies a maximum capacity to an APFS Volume, placing a limit on the number of bytes of user file data which can be stored on the Volume. Note that you might not be able to reach this limit if its parent Container becomes full first. You can use a quota to enforce accounting or to manage against 'unfair' premature filling-up of the parent Container due solely to this Volume at the expense of sibling Volumes.
Efficient file copy cloning (copy-on-write) is supported (see copyfile (3)'s COPYFILE_CLONE).
Optional file-level encryption is supported.
The format of an APFS Volume's device identifier is that of a slice disk of a special whole-disk; both disks are synthesized by APFS. The 'whole' identifier number (a positive possibly-multi-digit integer) is arbitrary, and the 'slice' numbers (positive possibly-multi-digit integers) count up from 1 with each new Volume. Deleting Volumes may cause gaps in the numbering until the next eject/attach cycle.
This form appears the same as a partition (map) scheme and partitions, but it is completely unrelated. For example: If 'disk3s2' is a Physical
Store defining a Container, then 'disk5s1','disk5s2', and 'disk5s3' might be the Container's Volumes; 'disk5' exists but is never used directly.
Although it has a device node, an APFS Volume's data may only be accessed through its files; you cannot open an APFS Volume device node to 'directly' access its on-disk bytes.
• Snapshot - An APFS Volume can have zero or more associated APFS Snapshots. An APFS Snapshot appears as a read-only copy of its parent APFS Volume at a frozen moment in time. Snapshots are neither listed nor discoverable when their Volume is not mounted.
APFS itself has no provision for backing up your data. Backups should be always be performed on a regular basis and before modifying any APFS Container using these commands.
The following is a list of APFS sub-verbs with their descriptions and individual arguments.
Devices
A device parameter to any of the above commands (except where explicitly required otherwise) can usually be any of the following:
• The disk identifier (see below). Any entry of the form of disk*, e.g. disk1s9.
• The device node entry containing the disk identifier. Any entry of the form of /dev/disk*, e.g. /dev/disk2.
• The volume mount point. Any entry of the form of /Volumes/*, e.g. /Volumes/Untitled. In most cases, a 'custom' mount point e.g. /your/custom/mountpoint/here is also accepted.
• The URL form of any of the volume mount point forms described above. E.g. file:///Volumes/Untitled or file:///.
• A UUID. Any entry of the form of e.g. 11111111-2222-3333-4444-555555555555. The UUID can be a 'media' UUID which IOKit places in an IOMedia node as derived from e.g. a GPT map's partition UUID, or it can be an AppleRAID (or CoreStorage) set (LV) or member (PV) UUID.
Disk Identifier
The disk identifier string variously identifies a device unit, a session upon that device, or a partition (slice) upon that session. It may take
the form of diskU, diskUsS, diskUsQ, or diskUsQsS, where U, S, and Q are positive decimal integers (possibly multi-digit), and where:
• U is the device unit. It may refer to hardware (e.g. a hard drive, optical drive, or memory card) or a 'drive' constructed by software (e.g. an AppleRAID set or a disk image).
• Q is the session and is only included for optical media; it refers to the number of times recording has taken place on the currently-inserted medium (disc).
• S is the slice; it refers to a partition. Upon this partition, the raw data that underlies a user-visible file system is usually present, but it may also contain specialized data for certain 3rd-party database programs, or data required for the system software (e.g. EFI or booter partitions, or APM partition map data).
Some units (e.g. floppy disks, RAID sets) contain file system data upon their 'whole' device instead of containing a partitioning scheme with
partitions.
Note that the forms diskUsQ and diskUsS appear the same and must be distinguished by context. For non-optical media, this two-part form identifies a slice upon which (file system) data is stored. For optical media, it identifies a session upon which a partitioning scheme (with its slices with file systems) is stored.
Sizes
Mac Disk Utility Manual
Wherever a size is emitted as an output, it is presented as a base-ten approximation to the precision of one fractional decimal digit and a
base-ten SI multiplier, often accompanied by a precise count in bytes. Scripts should refrain from parsing this human-readable output and use the -plist option instead.
Wherever a size is to be supplied by you as an input, you can provide values in several different ways, some absolute and some context-sensi tive. All suffixes described below are interpreted in a case-insensitive manner. The B is optional.
The most common way is to specify absolute values as a decimal number, possibly followed by a period and a decimal fraction, followed without whitespace with a suffix as follows:
• B is bytes (not blocks) where the multiplier is 1. This suffix may be omitted.
• K[B] is power of ten kilobytes where the multiplier is 1000 (1 x 10^3).
• M[B] is power of ten megabytes where the multiplier is 1000000 (1 x 10^6).
• G[B] is power of ten gigabytes where the multiplier is 1000000000 (1 x 10^9).
• T[B] is power of ten terabytes where the multiplier is 1000000000000 (1 x 10^12).
• P[B] is power of ten petabytes where the multiplier is 1000000000000000 (1 x 10^15).
• E[B] is power of ten exabytes where the multiplier is 1000000000000000000 (1 x 10^18).
You can also use the following suffixes:
• S | UAM ('sectors') is 512-byte units (device-independent) where the multiplier is always 512.
• DBS ('device block size') is the device-dependent native block size of the encompassing whole disk, if applicable, where the
multiplier is often 512, but not always; indeed it might not be a power of two.
• Ki[B] is power of two kibibytes where the multiplier is 1024 (1 x 2^10).
• Mi[B] is power of two mebibytes where the multiplier is 1048576 (1 x 2^20).
• Gi[B] is power of two gibibytes where the multiplier is 1073741824 (1 x 2^30).
• Ti[B] is power of two tebibytes where the multiplier is 1099511627776 (1 x 2^40).
• Pi[B] is power of two pebibytes where the multiplier is 1125899906842624 (1 x 2^50).
• Ei[B] is power of two exbibytes where the multiplier is 1152921504606846976 (1 x 2^60).
In certain contexts (e.g. when specifying partition triplets) you can provide a relative value as follows:
• % (with a preceding number) is a percentage of the whole-disk size, the partition map size, or other allocatable size, as
appropriate by context. Use of % is not supported in all situations.
• R (with no preceding number) specifies the remainder of the whole-disk size or other allocatable size after all other
triplets in the group are taken into account. It need not be in the last triplet. It must only appear in at most one
triplet among all triplets. Use of R is not supported in all situations.
You can provide an operating system-defined constant value as follows:
• %recovery% (with no preceding number) is the customary size of macOS Recovery Partitions.
Note again that B refers to bytes and S and UAM refer to a constant multiplier of 512; the latter are useful when working with tools such as gpt (8) or df (1). Note also that this multiplier is not a 'block' size as actually implemented by the underlying device driver and/or hardware, nor
is it an 'allocation block', which is a file system's minimum unit of backing store usage, often formatting-option-dependent.
Examples: 10G (10 gigabytes), 4.23tb (4.23 terabytes), 5M (5 megabytes), 4GiB (exactly 2^32 bytes), 126000 (exactly 126000 bytes), 25.4% (25.4 percent of whole disk size).
FORMAT
The format parameter of erase and partitioning (and RAID creation) is the filesystems name. You can determine this name by looking in /System/Library/Filesystems/<fs>.fs/Contents/Info.plistor by using the listFilesystems verb, which also lists shortcut aliases for common per- sonalities (these shortcuts are defined by diskutil for use with it only).
Some examples include: HFS+, HFS, JournaledHFS+, UFS, MS-DOS, etc.
Beginning with macOS El Capitan, system file permissions are automatically protected. It's no longer necessary to verify or repair permissions with Disk Utility (source).
Fl studio vst download. If diskutil list returns one or more extra disks named: Apple UDIF read-only compressed (bzip2)
These are often old Adobe 'Flash Player' installers - they can be safely ejected using eject or with Disk Utility.
Diskutil replaces the disktool utility found in earlier versions of macOS. (disktool is now deprecated)
Examples
List all attached disks and partitions - device names and partition identifiers (equivalent to lsblk on unix):
$ diskutil list
Get the Volume UUID (disk must already be mounted)
$ diskutil info disk0s2
Get the Volume ID of an IPOD
$ diskutil list |grep 'IPOD' |grep -o '(disk[0-9s]*)'
Mount a disk using its Volume ID
$ diskutil mount Disk1
Mount a disk using its UUID
$ diskutil mount B172F107-06D4-39E3-9F7C-57466CD6489B
Erase a disk
$ diskutil eraseDisk UFS UntitledUFS disk3
$ diskutil eraseDisk JHFS+ Untitled disk3
Erase a volume
$ diskutil eraseVolume HFS+ UntitledHFS /Volumes/SomeDisk
Partition a disk
Important: you cannot create non-HFS partitions on a disk if you intend to boot macOS on it.
Use these partitioning commands on a second (or third) disk that you mount after booting.
Resize a volume and create a volume after it, using all remaining space
$ diskutil resizeVolume /Volumes/SomeDisk 50g MS-DOS DOS 0b
Resize a volume and leave all remaining space as unused
$ diskutil resizeVolume /Volumes/SomeDisk 12g
Convert a disk to Core Storage and encrypt it
$ diskutil coreStorage convert disk3s2 -passphrase
Shrink your Core Storage PV in order to make space for a Boot Camp volume
subtract desired Windows size from LV size, to be new LV size, i.e. 150g
$ diskutil coreStorage list
$ diskutil coreStorage resizeStack LVUUID PVUUID 150g ms-dos BOOTCAMP 0
Revert a disk from Core Storage back to plain HFS, possibly decrypting
$ diskutil coreStorage revert disk5
Remove a partition diskutil eraseVolume Free Space not disk0s4
Merge two partitions into a new partition
$ diskutil mergePartitions JHFS+ not disk1s3 disk1s5
Split a partition into three new ones:
$ diskutil splitPartition /Volumes/SomeDisk JHFS+ vol1 12g MS-DOS VOL2 8g JHFS+ vol3 0b
Create a RAID
$ diskutil createRAID mirror MirroredVolume JHFS+ disk disk2
Destroy a RAID
$ diskutil destroyRAID /Volumes/MirroredVolume
Repair a damaged RAID
$ diskutil repairMirror /Volumes/MirroredVolume disk3
Convert volume into RAID volume
$ diskutil enableRAID mirror /Volumes/ExistingVolume
Diskutil Delete
Erase a partition and shrink to add an associated Recovery Partition
$ diskutil splitPartition disk8s2 JHFS+ MacHD R %Apple_Boot% %noformat% %recovery%
“What you want, what you're hanging around in the world waiting for, is for something to occur to you” - Robert Frost
Related macOS commands: Download virtual dj 9 for pc.
asr - Apple Software Restore.
authopen(1).
bless - Set volume bootability and startup disk options.
drutil - Interact with CD/DVD burners.
Disk Utility (GUI) - The 'Info' button displays the disk identifier, UUID etc.
diskarbitrationd(8).
hdid(8).
hdiutil - Manipulate iso disk images.
hfs.util - HFS/HFS+ file system utility (Mount/unmount).
mount - Mount a file system.
ntfs.util - NTFS file system utility.
ufs.util - UFS file system utility (Mount/unmount).
SetFile(1) - Set extended attributes (Developer Tools).
Some rights reserved