Return to site

Apple Apfs Media Erase

broken image


Disk Utility Tool (Mac OS X )

We're not done yet - you have to go to that disk, e.g. , then click erase in APFS format named Macintosh HD (or any name you wish), in order to set up the correct APFS container structure ready for you to install the OS back in place. Click Erase and Done. APFS is designed to be compatible with SSD drives; however, after the release of the file system, many people lose their data due to bugs & corruption in the APFS. Since then, Apple has brought several updates addressing the issues in APFS. Nevertheless, users are still unable to access their data. The new APFS (Apple File System) was introduced with macOS High Sierra and continued for later versions of macOS such as Mojave and Catalina. Known for its efficient data management, APFS has been the preferred file system over the previous HFS or HFS+ versions.

Command line Utility to manage local disks and volumes.

Options which make changes require ownership or root and most are DESTRUCTIVE!

Manipulates the volume-level structure of local disks.

Provides information about, and allows the administration of, thepartitioning scheme of disks, optical discs, and RAID sets.

diskutil

  • list partitions APFS
  • information
  • monitor activity
    • disk
    • repair verify
    • mountDisk / unmountDisk all mountable volumes
    • verifyDisk repairDisk
    • eject
    • erase zero secureEraseeraseOptical randomDisk (writing random data to the media)secureErase
    • partitionDisk removing all volumes
    • partition:
    • split
    • merge
    • delete partition (not available!)
    • volume : resize rename repair erase reformat
    • verifyVolume
    • repairVolume
    • eraseVolume
    • newVolume :format unallocated space as FAT32, then erase (which creates new!)
  • enableJournal/disableJournal/moveJournal HFS+
  • enableOwnership/ disableOwnership
  • RAID
    • createRAID
    • enableRAID Convert a disk to a degraded RAID mirror set
    • convertRAID Convert a RAID 1.x pre-Tiger to a RAID 2.x Tiger
    • updateRAID Update settings
    • addToRAID Add a spare or member disk
    • removeFromRAID Remove a spare or member disk
    • checkRAID
    • repairMirror Repair damaged set
    • destroyRAID

diskutil verbprovides help

volreference

  • disk identifier disk*, e.g. disk1s9.
  • device node entry containing the disk identifier. disk*, e.g. /dev/disk2s0.
  • volume mount point. /Volumes/*, e.g. /Volumes/Untitled.
  • Universally Unique Identifier or UUID. e.g. 85D67001-D93E-3687-A1C2-79D677F0C2E0

Disk Identifier

Device unit, session on that device, or a partition (slice) .

Form : diskU, diskUsS, diskUsQ, or diskUsQsS, where U, S, and Qare decimal integers .

  • Uis the device unit. It may refer to hardware (e.g. a hard drive, optical drive, or memory card) or a 'drive' constructed by software (For Example: an AppleRAID set or a disk image).
  • Sslice; aka partition. The area that contains a file system .
    It may contain specialized data for database programs, or data required for thesystem software (e.g. EFI or booter partitions, or APM partition map data).
  • Qsession for optical media; (number of times recording has taken place).

The forms for optical session and partition are the same and are distinguished by context.

Some units (e.g. floppy disks, RAID sets) contain filesystem data upon their 'whole' device instead of containing a partitioning schemewith partitions.

The top-to-botom appearance of partitions shows the on-disk ordering.
Disk identifiers need not appear in slice-numerical order.

list [-plist ] diskU
[internal | external]
[physical | virtual]
i.e. virtual

-->

info [-plist] vol | -all-->
activityContinuously display system-wide disk manipulation activity as reported by the Disk Arbitration framework,Coming on-line, being ejected, volumes being mounted or unmounted, volumes being renamed, etc.
until interrupted with a intsignal (^C).
For debugging such as the monitoring of applications dissenting (attempting to deny) activitiesfor disks for which they have registered an interest, use the logging features of the diskarbitrationd
mount [readOnly]
[-mountPoint vol_mt_pt]
disknsm
Mount a single volume.
vol_mt_ptrather than the standard path of /Volumes/VolumeName,
directory at that path must already exist.
mountDisk disku Mount all mountable volumes.
umount [force] volforcemay break open files; see umount.
umountDisk [force] disku
eject disku Media becomes offline .
Removable media will eject or become eligible for safe manual removal.
verifyDisk disku Partition Table, EFI integriey, Core Storage Physical Volumes and space for boot loaders.
repairDisk disku
verifyVolume volfile System of a volume (e.g. fsck).
repairVolume volRepair the data structure of a volume (e.g. fsck). Example:
renameVolume vol new_nameVolume names are subject to file system-specific alphabet and length restrictions.Must be mounted
enableJournal vol on an HFS+ volume.
disableJournal [force] volOn an HFS+ volume, Volume need not be mounted
Force: journaling is disabled directly on disk, the volume must not be mounted.
moveJournal external|internal
[journalDevice] vol
externalcauses the creation of a 512MB Apple_Journal partition out of journalDevice and an HFS+ partition will be created out of the remaining space if available; journalDevice must be a partition. The journal for device will then be moved externally onto the newly created Apple_Journal partition.

internalwill move the journal for device back locally.

enableOwnership volThe Database at /var/db/volinfo.databaseis modified as perUser and Group ID settings of files, directories, and links (file system objects, or 'FSOs')

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 enabled, the Owner and Group ID settings that exist on the disk are taken into account for determiningaccess, and exact settings are written to the disk as FSOs are created.
When ownership is disabled, Owner and Group ID settings on FSOs appear to the user and programs as the current user andgroup instead of their actual on-disk settings.

Enable ownership where a disk contains FSOs whose User and Group, and permissions, is critically important, such as when the plug-in disk contains system files to be changed or added .


Settings are persistent See vsdbutil .
disableOwnership device
verifyPermissions [-plist] vol Verify the permissions of boot volume, written during the installation .
Deprecated as of El Captian
listFilesystems [-plist]Show personalities available for formating when using the eraseVolume and partitioning verbs.
This is a subset of personalities exported by the various filesystem bundles installed.
Also shown are some shortcut aliases for common personalities.
-plistoutput is in xml.

File Systems formats
These (case insensative) personalities can be used for erasing and partitioning.

eraseVolume format name vol and write out an empty filesystem. See Format.
Use %noformat%to skip initialization (to skip newfs).
A format of Free Space will cause removal of the partition from the partition table.
The boot volume cannot be erased.
Operations modifying the entire disk (which may result in disaster).

Did you back up the partition table? See gdisk

partitionDisk diskU [numberOfPartitions]
[APM[fmt]]|MBR[Fmt]| GPT[Fmt]
[PTFormat]
[FSFormat1 vName1 pSize1
FSFormat2 vName2 pSize2
FSFormat2 vName3 pSize3
…]
Re-partition a disk. All volumes on this disk will be destroyed.
The device parameter specifies that a whole disk is to be partitioned.
The optional PTformatforces a particular Partitioning Table Format
  • APM Apple Partition Map , for a start up disk on PowerPC-based, a non-startup disk with any Mac, or a multiplatform compatible startup disk.
  • MBR Master Boot Record . DOS/Windows-compatible
  • GPTGUID Partitioning Table. for start up disk on Intel-based Mac.
For each partition, a triplet of the desired File System format, volume name, and size must be specified.
  • FSFormatare shown at listFilesystems and are created with the appropriate newfs_* (example newfs_hfs).
    The partition type is set according to the filesystem.
  • vName: volume names must conform to file system specific restrictions.
    %noformat%: the partition is left uninitalized.
    Names are ignored but dummy names must be present.
  • pSizeare floating point numbers followed by a letter or percent sign
    (example: 16G, 55.3T, 678M, 75%, R). Rwill use the Remainder of space on disk

    The last partition will be lengthened to the end of the disk.
    To create a partition of a specific size, include an additional partition with size of R

File System blocksize will be 4,096.
To change block size after creating a partition use: newfs
newfs_hfs -v VolumeName -b 8192 /dev/disk0s2

This will cause the average unused space per file to be 4,096 (i.e. 1/2 block).

When determing size:
( 3/18/16 DATA vol has 189,624 files
df reports 21,014,072 1k blocks used of 44,384,728 This is a space accounting only.However ( 21,014,072 1k blocks / 189,624 files total = 110 blk/file average aka ) means 2048*nfiles = unused space, (4096-2048)*nfiles will require ADDITIONAL unused space)

resizeVolume vol
[ size|limits|mapsize|R
[numberOfPartitions]
[p1Format p1Name p1Size
p2Format p2Name p2Size
p3Format p3Name p3Size …
]
Only supported on GPT partition tables with a Journaled HFS+ volume filesystem .

A size of limits displays the range of valid values for the current filesystem.
A size of mapsize displays:
A size of R will ATTEMPT to resize the partition to the maximun available. (DGG: didn't work )

Valid pnSizeare in the format of n.f units
Valid unitsare B(ytes), K(ilobytes), M(egabytes), G(igabytes), T(erabytes)
Example: 10G(10 gigabytes), 4.23T(4.23 terabytes), 5M(5 megabytes)

When decreasing size, optionally supply a list of new partitions to create.

Example:

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 as with partitionDisk

Resizing a volume that is currently set as the computer's startup disk will invalidate that setting; use the Startup DiskSystem Preferences panel or bless to reset the resized volume as the startup disk.

splitPartition vol
[numberOfPartitions]
[p1Format…
Destructively split a volume into multiple partitions.
mergePartitions [force] format name fromDevice toDeviceMerge two or more partitions on a disk.
All data on merged partitions other than the first will be lost. The first will beerased if it doesn't have a resizable type (e.g. JHFS+) or if forceis given.
Format and name apply only when the first partition is being erased.
Merged partitions are required to be ordered sequentially on disk (see diskutil list for the actual on-disk ordering).
reformat volwrite an empty file system using the same type and name
eraseDisk
[[APM]Format |
[MBR]Format |
[GPT]Format] disknsm
Removing all volumes and writing a new partitioning scheme containing one new empty filesystem volume.
If the partitioning scheme is not specified, then an appropriate one for the current machine is chosen.
See Format .
zeroDisk diskUErase a device, writing zeros to the media. The device can be a whole-disk or a partition. In either case, in order to beuseful again, zero'd whole-disks will need to be partitioned, or zero'd partitions will need to be erased (newfs'd), e.g. byusing the partitionDisk or eraseDisk verbs. If you desire a more sophisticated erase algorithm or if you need to erase onlyfree space not in use for files, use the secureErase verb.
randomDisk [times] diskUErase a whole disk, writing random data to the media. Times is the optional (defaults to 1) number of times to write randominformation. device can be a whole-disk or a partition. In either case, in order to be useful again, randomized wholedisks will need to be partitioned, or randomized partitions will need to be erased (newfs'd), e.g. by using thepartitionDisk or eraseDisk verbs. If you desire a more sophisticated erase algorithm or if you need to erase only freespace not in use for files, use the secureErase verb.
secureErase [freespace] level diskUErase, using a secure method, either a whole-disk (including any and all partitions), or, only the free space (not in usefor files) on a currently-mounted volume. Erasing a whole-disk will leave it useless until it is partitioned again. Erasing freespace on a volume will leave it exactly as it was from an end-user perspective, with the exception that it will notbe possible to recover deleted files or data using utility software. If you need to erase all contents of a partition butnot its hosting whole-disk, use the zeroDisk or randomDisk verbs.
Level :
  1. Single-pass zero-fill erase.
  2. Single-pass random-fill erase.
  3. US DoD 7-pass secure erase.
  4. Gutmann algorithm 35-pass secure erase.
  5. US DoE algorithm 3-pass secure erase.
eraseOptical [quick] diskU

APFS

Container imports one or more APFS Physical Store disks and exports APFS Volume disks.

While attached, the 'handle' by which a Container is identified is its Reference disk (device).

Reference disk is a synthesized whole-disk which is exported by APFS for identification purposes only; it has no storage. Apple shortcuts on mac. It is associated with the AppleAPFSContainerScheme node in the IO Registry.
An APFS Volume device identifiers appear to be of a related form, do not use the Container Reference as a basis to create device identifiers ; use the listingverbs with plist options

Physical Store a disk which is imported into an APFS Container. An APFS Container can import more than one Physical Store, e.g. for Fusion-style Containers.

An APFS Physical Store disk is not necessarily a disk from a partition map; it could be e.g. anAppleRAID Set disk. Do not assume that an APFS Physical Store's disk identifier is a 2-part form such as disk0s2.

Volume an [un]mountable file system volume which is exported from an APFS Container.
APFS | ap apfsVerb [..]
APFS Volumes have no specified 'size' (capacity), they consume capacity out ofthe remaining free space of their parent Container, consuming or returning such capacity asuser file data is added or deleted.
This means that all Volumes within a Container compete for the Container's remaining capacity. Manage Volume allocation with reserve and quota.

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.beyond this, the Volume might be able to store even more until constrained by reachingzero free space in its parent Container or by reaching a quota, if any.
Use a reserve to prevent running out of capacity due to competition from other Volumes or from a Container shrink attempt.

Quota size applies a maximum capacity to a Volume, limiting the numberof bytes of user file data which can be stored on the Volume.
It may not be able to reach this limit if its parent Container becomes full first.
Quota enforces accounting or to manage against 'unfair' premature filling-up of the parent Container due solely to thisVolume at the expense of sibling Volumes.

Efficient file copy cloning (copy-on-write) is supported (see copyfile (3)'s COPYFILE_CLONE).

File-level encryption is supported.

Snapshot represents a read-only copy of its parent APFS Volume, frozen at the moment of its creation.

Snapshots are neither listed nor discoverable when their Volume is not mounted.
Snapshots are uniquely identified within their parent Volume's namespace by either a numeric identifier (preferred) or by their name; Snapshots can be renamed.

Snapshots are mountable; provide a read-only historic version of the Volume

You can revert the present state of an APFS Volume back to equality with a Snapshot in its history.
This is a destructive reset/restore operation: Once a Volume is reverted, it cannot be brought forward.
Any Snaphots between the revert point and the present are lost as well.

Deleting a Snapshot; removes the possibility of ever reverting to that Snapshot's state,

Snapshot mount point's 'source device' is the Snapshot name followed by '@' and the 'parent' Volume's device node,
e.g. SnapName123@/dev/disk2s1 '. See mount_apfs -s (8) and fs_snapshot_create (2).

list [-plist] [containerReferenceDevice]Display APFS objects as a tree. AFPS Container(s) are shown with their imported Physical Store(s) and exported Volume(s).

All currently-attached APFS Containers in the system are listed unless you specify acontainerReferenceDevice, which limits the output to that specific APFS Container family.

If -plist is specified, then a property list will be emitted

-->
convert device [-dryrun] Non-destructively convert an HFS volume to an APFS Container with a single APFS Volume.
The APFS Container can then be manipulated (e.g. adding and deleting APFS Volumes) as usual.
The source HFS volume can be located on a partition or on a CoreStorage logical volume (LV); in the latter case, the CoreStorage logical volume group (LVG) is dismantled.
create device [device] namecreates an empty APFS Container and then adds one APFS Volume with the given name.
The Volume will have default attributes i.e. no encryption, no capacity reserve nor quota, etc.
This is a combination of createContainer and addVolume .
createContainer [-main] device [-secondary] [device] Create an empty APFS Container. The device(s) specified become APFS Physical Stores. Specifing more than one device creates a Fusion Container -main and -secondary performance algorithms to be on 'slower' hardware.
usually not solid solid state, is usually larger, and is used to store associated 'auxiliary' data such as any Windows partition(s) for Boot Camp Assistant.
deleteContainer [-force] containerReferenceDevice | physicalStoreDevice [name]Destroy a Container including all of its Volumes.

Volumes are unmounted first. If one or more is busy the operation is aborted.

Container's former Physical Store disks will be reformatted as HFS.

New name, default :Untitled .

If there were multiple Physical Stores, a space and a number suffix is added for each.

If Container is damaged, a Container Reference for it might not exist or it might not befunctional. reclaim former APFS Physical Store disk(s) by specifying -force ;
this activates an alternate last-resort mode.
In this mode, if you had more than onePhysical Store (e.g. the Fusion case) and the Container is sufficiently damaged, you might have todelete each Physical Store manually. avoid

resizeContainer containerReferenceDevice | physicalStoreDevice limits [-plist] | size
[part1Format part1Name part1Size
part2Format part2Name part2Size
part3Format part3Name part3Size …]
The operation is live, non-destructive, and does not mount or unmount any APFS Volumes.

size of limits outputs a range of valid values.

size of 0 to grow the targeted Physical Store such that all remaining space is filled to the next partition or the end of the partition map.

Shrinks are constrained by the amount of data usage by all APFS Volumes on the targeted or impliedContainer. Contributing to this includes quotas, reserves, the usage of Snapshots (e.g. by Time Machine), and metadata overhead.

When shrinking, new partitions may be created to fill the newly-freed spaceby specifing the format, name, and size parameters as for partitionDisk

Grows are constrained by the amount of partition map free space trailing the targeted or implied Physical Store partition.

All Volumes on the Container must be unlocked.

addVolume ?containerReferenceDevice filesystem name
[-passprompt] | [-passphrase passphrase] | [-stdinpassphrase] [-passphraseHint passphraseHint]
[-reserve reserve] [-quota quota] [-role roles]
[-nomount] [-mountpoint mountpoint]
The filesystem parameter sets the permanent APFS personality for this new APFS Volume; you should specify APFS or Case-sensitive APFS.

The new Volume will be unencrypted unless one of the passphrase options is specified
the user which is added will be the 'Disk User'.
passphraseHint can be displayed while Volume is locked.

volume's file usage to a maximum amount; no more than that many bytes will be available for filedata, even if there is otherwise enough space in the parent Container.
the reserve is not larger than quota.

Volumes carry certain metadata hint flags;
supply the role parameter with any combination of one or more of B R V or 0 as a no-op for scripting convenience.The new Volume is mounted after creation; unless -nomount is specified.
If mountpoint is specified it must exist

deleteVolume volumeDevice Remove the Volume from its Container. All of the Volume's data will be lost.
eraseVolume volumeDevice
-name newName
[-passprompt] | [-passphrase passphrase] |
[
-stdinpassphrase] [-passphraseHint passphraseHint]
Erase the contents of a Volume. the Volume is not removed from its Container.

The 'new' Volume will inherit the file system type (Case-sensitiveness ) but not attributes such as name, reserve, quota, or encryption status.

If you need more control, delete;add the Volume.

changeVolumeRole |
chrole volumeDevice roles
Change the role metadata flags
The roles should be any combination of b r v B R Vi unspecified flags are unchanged, lower-case flags are cleared, and UPPER-CASE sets flags.
clear will remove all flags, 0 no-op for scripting convenience.
unlockVolume |
unlock volumeDevice
[-user disk| -user cryptoUserUUID|
-recoverykeychain file]
[-passphrase passphrase] | [-stdinpassphrase]
[-nomount | -mountpoint mountpoint]
[-verify] [-plist]
Unlock and mount an encrypted and locked Volume or verify a passphrase. WIthout -user all cryptographic users on that Volume are searched for a match;

-user disk then the Disk UUID (which equals the Volume UUID) user is assumed;
-user UUID that specific user is assumed;

-recoverykeychain then the Institutional Recovery user (see below) is assumed.
-recoverykeychain filefull path to a keychain file if an Institutional Recovery Key has been previously set up on the Volume.
The keychain must be unlocked; see security(1) and fdesetup(8) for more information.

-verify will test passphrase correctness without affecting the locked or unlocked state.

To re-lock the volume, unmount it, e.g. with diskutil unmount or diskutil apfs lockVolume.

lockVolume |
lock volumeDevice
Unmount and lock a Volume.
listCryptoUsers |
listUsers |
listCryptoKeys |
listKeys
[-plist]volumeDevice
Show all cryptographic users and special-purpose (e.g. recovery) 'users' (keys) associated with the Volume, each by their Cryptographic User UUID and usage 'type'.

The usual purpose of an APFS Cryptographic User is to authenticate for unlocking its APFS Volume; any of its users can do so.

An APFS Volume need not be encrypted in order to contain crypto users; other than the Disk User, they should be added before encrypting.

Types of Cryptographic Users include 'Disk' user, whose UUID value always matches its Volume's UUID;
iCloud or personal 'Recovery Keys', which store partial crypto keys and are associated with corresponding
'Recovery Users' and have fixed-constant UUID values; and
'Open Directory' users, whose UUID values match corresponding local macOS Open Directory account user GUIDs.

changePassphrase | changeCryptoUserPassphrase | passwd volumeDevice -user disk | cryptoUserUUID
[-oldPassphrase oldPassphrase | -oldStdinpassphrase] [-newPassphrase newPassphrase | -newStdinpassphrase]
Change the passphrase of the given cryptographic user associated with the given Volume.
setPassphraseHint | setCryptoUserPassphraseHint | hint volumeDevice -user disk | cryptoUserUUID -hint hintMessage | -clear Set an arbitrary hint string to aid recall of a passphrase for the given cryptographic user associated with the given APFS Volume. Specifying -clear will clear any existing hint (no hint is the default).
encryptVolume | encrypt | enableFileVault volumeDevice -user disk | existingCryptoUserUUID [-passphrase existingOrNewPassphrase | -stdinpassphrase] Start encryption of a currently-unencrypted APFS Volume ('Enable FileVault').
The operation may be accomplished immediately or in the background'.

Supply an existing cryptographic user UUID, in which case you must supply its corresponding passphrase, or
disk (or the Disk/Volume UUID) and the corresponding passphrase of the 'Disk User'

if no users exist on this Volume, supply disk (or the Disk/Volume UUID), and a 'Disk User' will be created with a new passphrase .
Use this acquire the first such user if a volume has no cryptographics users .

decryptVolume | decrypt | disableFileVault volumeDevice [-user disk | existingCryptoUserUUID] [-passphrase existingPassphrase | -stdinpassphrase]Start decryption of a currently-encrypted APFS Volume ('Disable FileVault').
The operation may be accomplished immediately, or 'in the background'.

The APFS Volume must be unlocked before beginning.

listSnapshots |
list[Volume]Snaps[hots] [-plist]volume
Show all snapshots that are currently associated with the Volume, including its numeric XID identifier and name.
deleteSnapshot volumeDevice -xid xid | -name nameRemove the given Snapshot
Apple RAID
appleRAID raidVerb […]
Create, manipulate and destroy AppleRAID volumes (Software RAID).
  • stripe- Striped Volume (RAID 0)
  • mirror- Mirrored Volume (RAID 1)
  • concat- Concatenated Volume (ining)
Only the 'mirror' type increases fault-tolerance. may have more than two disks to increase fault-tolerance.
Striped and concatentated volumes are, in fact, more vulnerable to faults than single disk volumes.

From these basic types, 'stacked' or 'nested' RAID volumes can be created.
Stacked RAID sets that make use of mirrored RAID sets are fault-tolerant.
More common combinations of stacked RAID sets:

  • RAID 50 - striped RAID set of hardware RAID 5 disks.
  • RAID 10 - striped RAID set of mirrored RAID sets.
  • RAID 0+1 - mirrored RAID set of striped RAID sets.
  • Concatenated Mirror - A concatenation of mirrored RAID sets.
When creating new RAID sets or adding disks, it is better to specify the entire disk. This allows the software to reformat the entire disk using the most current partition layouts.

In addition to whole disk and partition device names, AppleRAID uses UUIDs to refer to existing RAID sets and their members.They may be specified by mount point (e.g. /Volume/raidset). Using the UUID is preferred because disk device names may change over time when disks are added, disks are removed or whenthe system is rebooted.
If RAID members have been physically disconnected from the system or are no longer responding, youmust use the member's UUID as the command argument. Messages in the system log will refer to RAID sets and their memberdisks by UUID.

RAID is not a replacement for backing up data. Backups should be always be performed on a regular basis andbefore modifying any RAID.

list [UUID]Display volumes with current status and associated member disks.
If UUID is specified, only list that RAID. diskutil listRAID is a deprecated synonym for diskutil appleRAID list.
create mirror|stripe|concat setName format devices …Create a new RAID set consisting of multiple disks and/or RAID sets.
setNameis used for both the name of the created RAID volume and the RAID set itself (as displayed in list). Example: diskutil createRAID stripe MyArray JHFS+ disk1 disk2 disk3 disk4
delete raidVolumeDestroy an existing RAID set. If the RAID set is a mirror with a resizable filesystem, delete will attempt toconvert each of the member partitions back into a non-RAID volume while retaining the contained filesystem.
For concatenated RAID sets with a resizable filesystem, delete will attempt to shrink the filesystem to fit on thefirst member partition and convert that to a non-RAID volume.
repairMirror raidVolume newDeviceRepair a degraded mirror by replacing a broken or missing member. Broken devices in the mirrored set can also berebuilt by specifying newDevice. When replacing members of a mirrored set, the new disk must be the same size orlarger than the existing disks in the RAID set.
add type newDevice raidVolumeAdd a new member or hot spare to an existing RAID set.
Typecan be either member or spare. New disks are addedlive, the RAID volume does not need to be unmounted.
Mirrored volumes support adding both members and hot spares,
When adding to a mirrored RAID set, the new disk mustbe the same size or larger than the existing disks in the RAID set. Adding a hot spare to a mirror will enableautorebuilding for that mirror.

Concatenated volumes only support adding members. Adding a new member to a concatenated RAID set appends the member and expands the RAID volume.

remove oldDevice raidVolumeRemove a member or spare from an existing RAID set. Old disks are removed live, the RAID volume does not need tobe unmounted. For missing devices, oldDevice must be device's UUID. Online mirror members with a resizablefilesystem will be converted to non-RAID volumes, spare and offline members will be marked free. For concatenated RAID sets, only the last member can be removed. For resizable filesystems remove will first aiempt toshrink the concatenated RAID set so that the filesystem fits on the remaining disks.
enable mirror|concat deviceConvert a non-RAID disk partition containing a resizable filesystem (like JHFS+) into an unpaired mirror or single disk concatenated RAID set. Disks that were originally partitioned on Mac OS X 10.2 Jaguar or earlier orwere partitioned to be Mac OS 9 compatible may not be resizable.
update key value raidVolumeUpdate the key value parameters of an existing RAID set. Valid keys are:
  • AutoRebuild 0|1- If true, the system attempts to rebuild degraded mirrored volumes automatically. When looking for devices for rebuild, AppleRAID first looks for hot spares and then degraded members.
  • Settingtimeout ssseconds system waits (in seconds) for a missing device before degrading a mirrored raid set. Also controls the amount of time you have to disconnect all devices from an unmounted mirror without degrading it.
  • coreStorage
    cs coreStorageVerb […] CoreStorage verbs can be used to create, manipulate and destroy CoreStorage volumes.

    CoreStorage maintains a world of virtual disks, somewhat like RAID, in which one can easily add or remove imported backing store disks, as well as exported usable volumes, to or from a pool (or several pools). This provides the user with flexibility in allocating their hardware; user or operating system data can span multiple physical disks seamlessly, for example.

      Types of objects, instances of which are uniquely represented by a UUID:
    • Logical Volume Group (LVG)
    • Physical Volume (PV)
    • Logical Volume Family (LVF)
    • Logical Volume (LV)
    The Logical Volume Group (LVG) is the top or 'pool' level; zero or more may exist during any OS boot time session.

    An LVG imports one or more Physical Volumes (PVs). A PV represents a device that feeds the LVG storage space; a PV is normally real media but it can be a disk image or even an AppleRAID Set. A disk offered to be a PV must be a partition and the encompassing scheme must be GPT.

    An LVG exports zero or more Logical Volume Families (LVFs). An LVF contains properties which govern and bind together all of its descendant Logical Volumes (LVs). These properties provide settings for Full Disk Encryption (FDE) (such as whether the LVG is encrypted, which users have access, etc) and other services. However, at the present time, for new LVF creation, only zero or one LVF per LVG is supported.

    A Logical Volume Family (LVF) exports one or more Logical Volumes (LVs). However, at the present time, only and exactly one LV per LVF is supported.

    A Logical Volume (LV) exports a dev node, upon which a file system (such as Journaled HFS+) resides.

    For more information on specifying device arguments, see the DEVICES section below. CoreStorage is not a replacement for backing up your data. Backups should be always be performed on a regular basis and before modifying any CoreStorage volumes using these commands.

    CoreStorage sub-verbs :

    list [-plist | UUID]Display tree view of the CoreStorage world for all current logical volume groups (LVGs) with member disks (PVs) and exported volumes (LVFs and LVs), with properties and status for each level.
    With -plista property list will be emitted instead of the formatted tree output;
    the UUIDs can be used with the diskutil coreStorage information verb to get properties for the object represented by that UUID.
    With UUIDlist only that UUID
    info | information [-plist] UUID | device

    HISTORY

    Starting with Mac OS X 10.6, the input and output notation of disk and partition sizes use power-of-10 suffixes.
    In the past this has been power-of-2, for display or accepted as input.

    See also

    booting OS X utility partition

    Disk Utility (Graphic User Interface) application

    Apple apfs media erase shortcut

    See bless, gpt
    HDIutil for disk images.

    Apple file system apfs

    See bless, gpt
    HDIutil for disk images.

    Posted by Tim to Mac Data Recovery Tips on November 3rd, 2018

    I have a 2TB external hard drive with APFS encrypted. One day I inserted it into Mac computer and find encrypted APFS media is uninitialized in disk utility. There are many important documents stored in it, how to recover lost data from uninitialized APFS drive?

    Although Apple has released APFS file sysem several month, but up to now, there are a few software which can support APFS data recovery in market due to technical difficulty, M3 Data Recovery for Mac is such a APFS data recovery software which can undelete files from APFS drive, recover lost data from formatted, corrupted, unreadable, unmountable, uninitialized APFS drive, recover lost data from deleted, lost, misssing, disappeared APFS partition, recover deleted or lost files from encrypted APFS drive, etc. on macOS Catalina 10.15/Mojave 10.14/High Sierra 10.13/Sierra 10.12/10.11/10.10/10.9/10.8.

    Tutorial to recover lost data from uninitialized AppleAPFSMedia

    Apple Apfs Media Erase Markers

    Step 1: Download and install this APFS Data Recovery software on your Mac computer.

    Step 2: Run this APFS Data Recovery software - M3 Data Recovery for Mac.

    Apple Apfs Media Erase Apps

    Step 3: Click 'Find Lost APFS Partitions' in M3 Data Recovery for Mac.

    Step 4: Select uninitialized AppleAPFSMedia and click Next to find previously existing APFS partition.

    Step 5: Once the previously existing APFS partition is found, please select it and click Next to scan lost data. If the APFS drive is encrypted, the password is required at this step.

    Step 6: After the lost data found, we can preview them or click Recover to recover them.





    broken image