Hot answers tagged

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

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

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

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

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

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

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 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

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.


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

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

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

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

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 ...


3

Please try the following: Get the disk identifier of your external 3 TB drive diskutil list Below I assume the disk identifier is disk6 unmount the disk: diskutil umountDisk disk6 Overwrite the first 40 blocks: sudo dd if=/dev/zero of=/dev/disk6 bs=512 count=40 Create a new gpt: sudo gpt create /dev/disk6 Check the disk info with: diskutil info ...


3

This is not an answer, but rather an example of how to extract the GPT partition information from the data you presented. The secondary (backup) GPT partition entries were used because you did not post the contents of the primary GPT partition entries. The document "GUID Partition Table" was used to interpret the data. Last usable LBA can be found in the ...


3

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: ...


3

Update: IOReg gives the partition UUID, not the volume UUID, as it operates below the HFS layer. I had incorrectly assumed that the device UUID was required rather than the volume UUID because it was substituting for a device node. To get the volume UUID, use hfs.util. For example: /System/Library/Filesystems/hfs.fs/Contents/Resources/hfs.util -k disk0s3 ...


2

After resizing the VM disk (in my example I added 24 GiB to the default 40 GiB) you will get following listings after opening the VM's Terminal.app and executing the commands diskutil/gpt in the VM: Initial VM-Mac:~ VMuser$ sudo gpt -r show disk0 listing: VM-Mac:~ VMuser$ sudo gpt -r show disk0 start size index contents 0 1 ...


2

Under certain circumstances a deleted external HFS+ encrypted volume can be recovered after the disk has been formatted to a FAT32 volume: The whole disk has been encrypted (to one volume). The whole disk has been formatted to one FAT32 volume. The GUID partition table has not been replaced by an MBR. The disk still has an MBR (instead of a PMBR) though. ...


2

You have not actually installed Windows. Your image shows the BOOTCAMP partition is MS-DOS (FAT) formatted. If Windows installed, the partition would be NTFS formatted. At some point during the installation, did you tell Windows to format the BOOTCAMP partition? See step 4 here and "Format the Windows partition" step here. If you skip this step, you will ...


2

Remove all external disks (just for safety reasons). If possible also remove all internal disks except the boot disk or "refresh" your backups. The proposed command (dd) used improperly can be deadly for your data. Open Terminal.app and get the disk identifier of the disk containing the DVD partition: diskutil list Unmount the disk: #replace diskX by ...


2

(Optional:) backup the content of the volume "Backup". If the volume is empty don't backup anything. Boot to Recovery Mode by pressing cmdR. Open Terminal from the menubar -> Utilities Enter diskutil list to get an overview. Determine the sequence of the partitions on the RAID. Quit Terminal and open Disk Utility If the sequence is (1: EFI) - 2: Parallels ...


2

Update 9 Good news, your "Recovery HD" volume has the correct identifier of disk0s3. So there is nothing to fix. I would not assume the "Boot Camp Support Software", you can download using the Boot Camp Assistant application, is the same as the Boot Camp Support Software 5.1.5621" required for Windows 7. Although, for my (21.5-inch, Mid 2011) iMac, I ...



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