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

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

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.


4

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.


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

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


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


3

When you don't use the Boot Camp utility to remove Windows, the Windows boot image on your EFI partition is not removed. This is what you see when you hold down ⌥ during boot. The procedure to solve this is not for the faint of heart. You need to mount the EFI partition in OS X (normally, it only gets mounted for system updates). Mounting the EFI partition ...


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

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


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

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

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

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

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


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


3

After some trial and error, I finally figured out what the problem was and found a solution. Hopefully this will help those who come across this thread with the same problem. The problem: Reformatting using Disk Utility did not create a child partition, but only formatted the whole drive as FAT. In Disk Utility one can derive this from the "Partition" ...


3

To most easily resolve this, you need to erase your USB drive with a "Master Boot Record" scheme. Steps: Open Disk Utility Select the USB drive Click "Erase" Choose Format "MS-DOS (FAT)" MOST IMPORTANT: Choose Scheme "Master Boot Record" Click Erase button Many thanks to nholtappels for figuring out the problem!


2

While you could technically use dd to image a smaller partition onto a larger partition and it still show using the space of the smaller partition you'll not be able to resize the NTFS partition using Disk Utility. Also the GPT and PMBR will not be synced and that will need to be resolved. Windows 7 will also need to be reactivated. That said, using ...


2

Take a look at Time Machine, it may be keeping local snapshots. From Apple Support: Because Time Machine removes local snapshots as needed, Finder and Get Info windows don't include them in their calculations. To see how much storage space local snapshots are using, choose About This Mac from the Apple menu, then click Storage. The space used by local ...


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

Just a point on scratch drives - SSD's are not recommended for scratch (virtual memory) in 2015 for two reasons (there may be more) - SSD's don't enjoy constant overwrite and data swappping and it will reduce the life of an expensive drive. Using a clean partition set aside on an internal Sata drive such as a WD Black (with 64MB on board cache) will be more ...


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

As a test, I formatted and external USB drive as exFAT (wrongly shown as ExFAT in Disk Utility) and then ascertained its UUID. Then ejected and unplugged the disk. I then added the following to my /etc/fstab file: UUID=402894E4-03EE-3CF7-80D2-A4EC74048C2F none exfat rw,noauto Note: Use the UUID assigned to the exFAT partition on your device. These ...



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