Hot answers tagged

19

After gaining some experience with CoreStorage volumes, I reworked my first answer to generalize and facilitate it by adding some scenarios and deleting some dispensable steps. Basically there is one undocumented command to resize or expand a CoreStorage volume group and an inherent logical volume: diskutil cs resizeStack LVUUID size The command ...


6

The method to repair your disk and recover the GUID partition table is related to my answers to similar questions: HFS+ invalid number of allocation blocks and Hard drive no longer accessible. Basically you have to find characteristic strings of JHFS+ volumes, use some simple math and common sense and have some luck to fix the GUID. And don't loose sight of ...


6

By default, HFS+ in OS X is case-insensitive. You have to specifically erase a partition and select case-sensitive for a partition to be case-sensitive. It's not that common, but there is software which requires case-insensitive HFS+. It's more common for legacy software to require case-sensitive HFS+. Of course, software should work on both, and most newer ...


6

Booted to Internet Recovery Mode you have to remove all non-OS X partitions, modify the partition types and then resize your main volume. The reason why you can't boot your Mac is the bogus partition type (FFFF-FFF....) of your main partition (i=2/sda2). Additionally the Recovery HD partition (i=3/sda3) has the wrong type. Preparation: Restart to Internet ...


4

Your new 512 GB disk has about 260 GB of unallocated disk space (starting at block 409640 and ending at block 511933959). The on-board OS X tools don't allow you to move the beginning of a partition (the second partition starting at block 511933960) to smaller block numbers (like 409640). My advice: create a new partition in the unallocated disk space. ...


4

You can format any drive to FAT16 with newfs_msdos Command 1) Launch Terminal 2) Find The Drive you Want to Format #mount /dev/disk2 on / (hfs, local, journaled) devfs on /dev (devfs, local, nobrowse) /dev/disk4s1 on /Volumes/USB_Disk (msdos, local, nodev, nosuid, noowners) In this case, my disk is disk4. Your disk will most likely be different! Be ...


4

With Apple's OS X tools you can't expand the start sector of a partition to lower sector numbers. You have to choose another method. You may accomplish your objective if less then one half of the net capacity of your hard drive ((~disk size - size of Recovery HD - size of EFI)/2) or less then one half of the main volume is occupied. If you miss the ...


4

Considering the comments and the results of the different listings above, Yosemite probably was installed with a hack to enable a Windows MBR only install. I assume it was the Yosemite MBR Patch 10.10 (14A389). The patch allows you to install Yosemite to a disk with a pure MBR partition table and not the default GUID partition table with a pMBR or hybrid ...


4

Your internal disk is a Fusion Drive combining an SSD (disk0) and a HDD (disk1). It uses a Core Storage partition scheme. The superior "Macintosh HD" is the name of the Logical Volume Group build by the compound of the two Physical Volumes (disk0s2/disk1s2) of your Fusion Drive. It's used instead of the name of the physical device in a non-Core Storage ...


3

According to this article you can get OS X to read and write to NTFS, so if you are planning on using the disk for both, then go with NTFS. The one thing you need to check is if Time Machine will write to NTFS. It writes to NAS's which are not using an Apple proprietary file system, so it may work okay, just check before you commit to it. As for partitions, ...


3

I'm assuming you have nothing on the new disk and essentially want to mirror what is on the old disk to the new disk. You can use the following command line, substituting the proper names for Source-Disk (old) and Destination-Disk (new). rsync -xavH /Volumes/Source-Disk/ /Volumes/Destination-Disk/ Note: The slash at the end of each path has significance, ...


3

This Ask Different post has what you're looking for. Don't go looking for an "answer," the author for some reason decided to write his own answer in the "question" post. The method worked perfectly (and non-destructively, but you should always take a backup anyway, just in case) for me! Paraphrased: Reboot in Recovery Mode by holding down Command-R ...


3

To delete CoreStorage volumes you have to use the CLI: please backup your volume "mainHD" boot to Internet Recovery Mode (hit altcmdR immediately after the start-up chime) open Disk Utility and check/repair mainHD quit Disk Utility , open in the menubar Utilities/Terminal.app and enter diskutil cs deleteVolume LVUUID to delete the Logical Volume in your ...


3

This is an example of a procedure to erase an external disk containing a single encrypted partition. Open the Disk Utility application and highlight the "Logical Volume Group" representing your external disk. An example is shown below. (Hint: click on image for a better view.) Next, click the Info icon to get the pop up window. Note, in the example shown ...


3

To rename the Recovery Partition, falsely named "EFI Boot", I first mounted the Recovery HD, by showing all partitions in Disk Utility. To show all partitions: 1.) quit Disk Utility 2.) In Terminal write or paste: defaults write com.apple.DiskUtility DUShowEveryPartition 1 and hit 'enter'. Launch Disk Utility and mount the hidden, but now showing "Recovery ...


3

Just because you can, doesn't mean you should. Why not just back up your data and wipe the entire partition? I suppose if you want to learn how to move things around and you already have a bootable backup that you've tested, the plan of action you propose might be an interesting learning experience. For anyone that's not sure they can pull off this, Apple ...


3

To expand your CoreStorage Logical Volume Macintosh HD you have to delete the blocking NO NAME EFI partition (disk1s5). The two unnamed parts (138.62 GB and 99.9 GB) are no partitions but unallocated disk space. To remove the second EFI partition (and expand Macintosh HD) you have to boot to Internet Recovery Mode or an OS X system on an external device. ...


3

To get some additional un-allocated disk space on disk0 to create a new partition you have to shrink your CoreStorage Volume Group and all subsequent CoreStorage items. To resize the CoreStorage Volume Group in your case you have to use the Terminal booted to an external boot drive. Preparation: Backup your data. Detach any external drive (especially ...


3

Download OS X from the App Store and create a USB Installer. Boot the Mac from the OS X USB Installer and use Disk Utility to create a single Mac OS Extended (Journaled) partition and then install OS X. After the installation and the setup of the first user were finished boot to Recovery Mode Disable System Integrity Protection with csrutil disable entered ...


3

Make sure you have version 14.0.382, previous 14 versions had that problem. I had this problem with the version I downloaded from the Paragon free upgrade link. I solved that problem by downloading the 14.0.382 from their website. Strangely the new version didn't show up clicking the "check for update" button on Paragon NTFS preference pane.


3

You can't simply merge a Bootcamp partition or empty space and a FileVault volume with Disk Utility (Boot Camp Assistant should handle this though). You first have to remove the Bootcamp partition and then expand the FileVault volume. To remove the Bootcamp partition and resize the CoreStorage Volume Group (containing the FileVault volume) the Mac has to be ...


3

Windows' Disk Management has overwritten the GUID partition table with something unknown. This usually only effects the partition table but not the content of your disk (though it seems to be gone)! A proper GUID partition table has to be restored. The particular obstacle here is: the OP neither has a thumb drive nor a second Mac. Preparation: Backup the ...


2

If you have your data safely backed up or don't care about losing it, you can follow these instructions to recreate your Fusion Drive. Boot into Internet Recovery or an OS X bootable drive. From the Utilities menu, open Terminal. Run diskutil cs delete 654B2807-197B-46D1-9919-B75C0290D33A to destroy your current Fusion Drive. This WILL lose all of your ...


2

Open Disk Utility and select the disk in the sidebar (not a partition). Click Partition in the toolbar. Enter the first partition information. Click the + button to add a second partition. Enter the second partition information. The size will be entered automatically from the remaining space. Click Apply.


2

The formatting should last undefined amount of time, as there are many factors potentially involved, such as disk encryption or using slow external USB drives. Before cancelling the task, you should verify if there is no progress indicated by the app, for example by marking the position of progress bar with some other window or mouse cursor, and checking ...


2

An alternative to the disabling encryption is to use command diskutil cs resizeStack The details on how it works has been documented by Klanomath here One thing I wanted to add is that it also works with FileVault. I have tried and the performance was pretty good. It took me 5-8 minutes to resize the 230GB partition to 250GB. To sum it up: Firstly: Boot ...


2

Windows' Disk Management has overwritten the GUID partition table with an MBR partition table. This usually only effects the partition table but not the content of your disk (though it seems to be gone)! To restore a proper GUID partition table, the MBR has to be deleted and a proper GUID partition table has to be restored. The particular obstacle here is: ...


2

a) how to get bootcamp startup disk back? You have an additional 24.9 GB partition between the "Mackintosh HD" and the "DATA" partitions. This means you have 5 partitions (if you include the hidden EFI partition). The "BOOTCAMP" partition is the 5th and last partition. The Apple software is designed by default to search for Windows on only the first 4 ...


2

As discussed in fuse-ext2 / OSX 10.11 "El Capitan" make fails, installation of fuse-ext2 fails on OS X 10.11, El Capitan, due to System Integrity Protection (SIP). The recommended solution right now is to disable SIP.


2

Disk Utility won’t let you erase or repartition an encrypted CoreStorage volume until you unlock or decrypt. This can be an issue for a CoreStorage volume that will not let you either unlock or decrypt. To help with this, the diskutil tool provides a way to quickly delete CoreStorage volumes. This includes the ability to erase encrypted CoreStorage volumes ...



Only top voted, non community-wiki answers of a minimum length are eligible