![]() disk_1 and disk_2 are the device identifiers of the 24GB SSD and 1TB HDD respectively that can be obtained by typing diskutil list in Terminal. The Terminal command for creating a new logical volume group is diskutil cs create logical_volume_group_name disk_1 disk_2. Note the difference between the Terminal command for creating the logical volume group: diskutil cs create and the command for creating the logical volume: diskutil cs createVolume. First we create a new logical volume group followed by a new logical volume. Having deleted the existing Fusion Drive and secure erased the 1TB HDD, the final step is to create a new Fusion Drive. NOTE: The Security Options button in Disk Utility is not available when erasing an SSD or Fusion Drive as it is not possible to secure erase either type of drive. Selecting Security Options… in Disk Utility No CoreStorage logical volume groups foundĪt this point we can quit Terminal and secure erase the 1TB HDD using the Security Options in Disk Utility. To confirm the Fusion Drive no longer exists, in Terminal type: Initialized /dev/rdisk1s2 as a 931 GB case-insensitive HFS Plus volume with a 81920k journal Initialized /dev/rdisk0s2 as a 22 GB case-insensitive HFS Plus volume with a 8192k journal To delete a logical volume group with a UUID of CE7D4BA0-BF9E-446F-83AC-8080A77D1AE4, in Terminal type:ĭiskutil cs delete CE7D4BA0-BF9E-446F-83AC-8080A77D1AE4 The Terminal command is diskutil cs delete logical_volume_group_uuid Having deleted the logical volume, the next step is to delete the logical volume group. Removing Logical Volume from Logical Volume Groupįinished CoreStorage operation on disk2 Macintosh HD Started CoreStorage operation on disk2 Macintosh HD The Core Storage Logical Volume UUID is 3BAEF8EE-B7F1-4094-88D4-58CECD811A72 To delete a logical volume with a UUID of 3BAEF8EE-B7F1-4094-88D4-58CECD811A72, in Terminal type:ĭiskutil cs deleteVolume 3BAEF8EE-B7F1-4094-88D4-58CECD811A72 The Terminal command is diskutil cs deleteVolume logical_volume_uuid. Note the difference between the Terminal command for deleting the logical volume: diskutil cs deleteVolume and the command for deleting the logical volume group: diskutil cs delete.Īs mentioned, the first task is to delete the logical volume. The logical volume needs to be deleted first followed by the logical volume group. When breaking apart a Fusion Drive the two pieces of information needed are the logical volume universally unique identifier (UUID): 3BAEF8EE-B7F1-4094-88D4-58CECD811A72 and the logical volume group UUID: CE7D4BA0-BF9E-446F-83AC-8080A77D1AE4. Information similar to the following is displayed:ĬoreStorage logical volume groups (1 found) To display details of a Fusion Drive, in Terminal type: To ensure you’re targeting the correct one I would suggest ejecting or disconnecting any additional drives first. However, other connected non-Fusion Drives – both internal and external – may also be displayed as logical volume groups. ![]() WARNING A Fusion Drive is classed as a logical volume group in CoreStorage. Opening Terminal from the Utilities menu in macOS Recovery Mode Once started, open Terminal from the Utilities menu: Quit and then re-open Disk Utility to see the correct disk configuration:Īt this point you have a Fusion Drive formatted as HFS+ and can continue with the steps in the remainder of this article.Container disk 2 is deleted and the sidebar will show something similar to: At the prompt, enter Macintosh HD for the Name – it will likely be pre-populated with Preboot – and select Mac OS Extended (Journaled) for the Format.Select Container disk 2 in the sidebar and click the Erase icon in the toolbar.The Mac’s startup Fusion Drive should be listed in the Disk Utility sidebar:ġ The disk identifier may be another number. In the top-left corner of Disk Utility, click the View dropdown and select Show All Devices.Having started your Mac in Recovery Mode, open Disk Utility.IMPORTANT: Performing these steps will erase all the data on your Fusion Drive. However, they are still relevant when running macOS Mojave with an APFS-formatted Fusion Drive providing you first perform these extra steps: The instructions detailed in this article are only applicable to HFS+ Fusion Drives. Since the release of Mojave, installing or updating macOS from an earlier version has forced startup Fusion Drives formatted as HFS+ to be automatically converted to APFS as part of the install process. Information for Fusion Drive Macs Running macOS Mojave (10.14)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |