El Capitan GM this core storage operation is not allowed on a sparse logical volume group

anyone?

😟

Hi Harlock,

I must have missed your earlier post. I'm guessing you have Windows installed via Bootcamp - if so, the following guide I updated recently should fix the issue for you:

Boot into Recovery Mode (cmd+R).

1. Utilities menu > Terminal > Type:

   csrutil disable

2. Reboot normally

First, download gdisk (sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.0/gdisk-binaries/gdisk-1.0.0.pkg/download) and run the installer package.

Then run gdisk from a terminal window and run the v (verify command).

• sudo gdisk /dev/disk0
• Command (? for help): v

Given what you've said, it'll probably say:

Warning! Mismatched GPT and MBR partition! MBR partition 4, of type 0x07, has no corresponding GPT partition! You may continue, but this condition might cause data loss in the future!

Identified 1 problems!

Next, display the MBR partition table and make note of the start and end sectors for your BOOTCAMP partition.

• Command (? for help): r
• Recovery/transformation command (? for help): o

This should be partition 4 unless you've added additional partition(s), which is not officially supported by Boot Camp. It should show something like this:

Disk size is 1953525168 sectors (931.5 GiB)

MBR disk identifier: 0x7C170CB2

MBR partitions:

Number Boot Start Sector End Sector Status Code

1 1 409639 primary 0xEE

2 409640 975693095 primary 0xAF

3 975693096 976962631 primary 0xAB

4 * 976963584 1952806911 primary 0x07

Next, display the GPT partition table information:

• Recovery/transformation command (? for help): m
• Command (? for help): p

Number Start (sector) End (sector) Size Code Name

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 975693095 465.1 GiB AF00 Customer

3 975693096 976962631 619.9 MiB AB00 Recovery HD

4 976963584 1953523711 465.7 GiB 0700 BOOTCAMP

Compare the start and end sectors for partition 4 to the MBR partition 4 start and end sectors. Most likely the start sectors will match, but the end sectors will be different.

Next, delete the GPT partition 4. (Note: this does not delete the actual partition from disk. It only deletes gdisk's in-memory representation of the GPT).

• Command (? for help): d
• Partition number (1-4): 4

Now, create a new partition 4 using the start and end sector values from the MBR partition 4:

• Command (? for help): n
• Partition number (4-128, default 4): 4
• First sector (34-1953525134, default = 976962632) or {+-}size{KMGTP}: 976963584
• Last sector (976963584-1953525134, default = 1953525134) or {+-}size{KMGTP}: 1952806911
• Current type is 'Apple HFS/HFS+'
• Hex code or GUID (L to show codes, Enter = AF00): 0700
• Changed type of partition to 'Microsoft basic data'

Now, change the name of the new partition 4 to BOOTCAMP:

• Command (? for help): c
• Partition number (1-4): 4
• Enter name: BOOTCAMP

Run the verify command. It should report no problems. If it still reports a problem, quit (q command) and start over.

Command (? for help): v

If everything checks out, write new partition table to disk and exit.

Command (? for help): w

Reboot and test your dual boot setup to verify all is working correctly.

Boot back into Recovery Mode (cmd+R).

1. Utilities menu > Terminal > Type:

   csrutil enable

2. Reboot normally

-Max.

Hi Max,

first of all thanks for your answer.

I have installed Parallels Desktop and Windows 10, I don't have a Bootcamp partition of Windows.

Shall I try your procedure?

Yes, the first half of it will not make changes - you can use it to harmlessly diagnose if this is the underlying cause of the issue for you. In other words, continue with the procedure up to and including:

Compare the start and end sectors for partition 4 to the MBR partition 4 start and end sectors. Most likely the start sectors will match, but the end sectors will be different.

And report back what you find out about the last partition of both MBR and GPT partitions:

• Do they have the same number of partitions?
• Do the final partitions (maybe partitions 4 and 4 of each) have the same end sector

had to find out a soultion because csrutil does not exist in bash..
in another thread I found the right command:

#/Volumes/OSX.10.11/usr/bin/csrutil disable

now I've run gdisk:

Last login: Thu Sep 17 12:49:25 on console

MacBook-Pro-di-Daniele:~ Harlock$ sudo gdisk /dev/disk0

Password:

GPT fdisk (gdisk) version 1.0.0

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

MBR: protective

BSD: not present

APM: not present

GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): v

No problems found. 9 free sectors (4.5 KiB) available in 2

segments, the largest of which is 6 (3.0 KiB) in size.

should I go on?

That's strange. On the GM in Recovery Mode, I can run csrutil disable from Terminal without having to specify the directory of the binary as you mention.

Anyway, yes, keep going as described above because it is necessary to get both partition maps to see what's going on. The commands specified make no changes up to the point mentioned above, they just provide information.

Disk size is 977105060 sectors (465.9 GiB)

MBR disk identifier: 0x00000000

MBR partitions:

Number Boot Start Sector End Sector Status Code

1 1 977105059 primary 0xEE

Recovery/transformation command (? for help): m

Command (? for help): p

Disk /dev/disk0: 977105060 sectors, 465.9 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): AE582AE7-FF6E-44EB-93DB-5D9F78B79D66

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 977105026

Partitions will be aligned on 8-sector boundaries

Total free space is 9 sectors (4.5 KiB)

Number Start (sector) End (sector) Size Code Name

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 975835487 465.1 GiB AF05 Macintosh HD

3 975835488 977105023 619.9 MiB AB00 Recovery HD

Okay everything checks out there. I think you may be approaching this from the wrong angle. It looks like you may have had FileVault enabled at one point. If that's the case, and it is currently disabled, then re-enabling it may allow the install of the GM to complete.

Try that first (try it twice to make sure) and if it doesn't work then turn FileVault off and we can attempt to change the core-storage status of the partition.

ok, as soon as I'll finish I'll give you feedback.

meanwhile, thanks again!

Max,
I'm writing from my brand new El Capitan Golden Master installation..

I had to overcome another issue from FileVault (it was stuck in pause because I hade to move my Mac from one room to another, and unplugging the power creates this problem.. I applied the second solution from this thread http://www.iphonetopics.com/filevault-stuck-encryption-paused-fix-mac/ ).

Now I think that I'll wait till September, 30 for the official release, then update and turn off the encryption.

Thanks for all your support!

Daniele aka Harlock

Glad you got it sorted Daniele 🙂

Good luck with the transition to the official release, and don't hesitate to post a new question if you have any trouble.