Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Question:

Question: Lost space after removing Bootcamp using bootcamp assistance

Lost about ~125GB of space after removing Bootcamp using bootcamp assistance.

Any ideas?

Posted on

Reply

Mar 1, 2018 12:49 PM in response to Loner T In response to Loner T

I'm using the latest 27inch 5k iMac with 1tb fusion drive.


Result:


diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB
disk0s1

2: Apple_CoreStorage Macintosh HD 861.0 GB
disk0s2

3: Apple_Boot Recovery HD 650.0 MB
disk0s3


/dev/disk1 (internal):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme 28.0 GB disk1

1: EFI EFI 314.6 MB
disk1s1

2: Apple_CoreStorage Macintosh HD 27.6 GB disk1s2

3: Apple_Boot Boot OS X 134.2 MB
disk1s3


/dev/disk2 (internal, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD +887.6 GB
disk2

Logical Volume on disk1s2, disk0s2

5CD0DA04-089D-4DA3-A30D-61F40B21D0F7

Unencrypted Fusion Drive



diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group 71DFF05B-D4C1-466A-B406-08775ADEF408

=========================================================

Name: Macintosh HD

Status: Online

Size: 888565661696 B (888.6 GB)

Free Space:
24576 B (24.6 KB)

|

+-< Physical Volume A3BE1D6D-F4BD-4732-8C7B-2F8CC1FF08B8

|
----------------------------------------------------

|
Index: 0

|
Disk: disk1s2

|
Status:
Online

|
Size: 27551166464 B (27.6 GB)

|

+-< Physical Volume 490784A4-50F5-44AC-9F4E-18443CD90186

|
----------------------------------------------------

|
Index: 1

|
Disk: disk0s2

|
Status:
Online

|
Size: 861014495232 B (861.0 GB)

|

+-> Logical Volume Family FDC9DBCE-29DD-4F54-AEB5-56891A50DFBD

----------------------------------------------------------

Encryption Type: None

|

+-> Logical Volume 5CD0DA04-089D-4DA3-A30D-61F40B21D0F7

---------------------------------------------------

Disk: disk2

Status: Online

Size (Total): 887649992704 B (887.6 GB)

Revertible: No

LV Name: Macintosh HD

Volume Name: Macintosh HD

Content Hint: Apple_HFS

LVG Type: Fusion, Sparse

I'm also running the latest MacOS High Sierra.

Mar 1, 2018 12:49 PM

Reply Helpful

Mar 1, 2018 11:30 PM in response to Loner T In response to Loner T

After running it on recovery mode the output is:


gpt -vv -r show disk0

gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168

gpt show: disk0: PMBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 1953525167

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 1681668936 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

1682078576 1269528 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

1683348104 270177031

1953525135 32 Sec GPT table

1953525167 1 Sec GPT header

Mar 1, 2018 11:30 PM

Reply Helpful

Mar 2, 2018 3:09 AM in response to EtayCohen In response to EtayCohen

The command sequence in Internet Recovery -> Utilities -> Terminal, should be


diskutil unmountDisk disk0

gpt add -i 4 -b 1683348104 -s 270177031 -t windows /dev/disk0

gpt -vv -r show /dev/disk0

diskutil repairDisk disk0


Please post the output of the entire terminal session so we can check for errors. You can use Select, Copy and Paste to post the output using Safari (Get Help Online).

Mar 2, 2018 3:09 AM

Reply Helpful

Mar 2, 2018 6:33 AM in response to Loner T In response to Loner T

-bash-3.2# diskutil unmountDisk disk0

Unmount of all volumes on disk0 was successful

-bash-3.2# gpt add -i 4 -b 1683348104 -s 270177031 -t windows /dev/disk0

gpt add: /dev/disk0: error: no space available on device

-bash-3.2# gpt -vv -r show /dev/disk0

gpt show: /dev/disk0: mediasize=28000002048; sectorsize=4096; blocks=6835938

gpt show: /dev/disk0: PMBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 6835937

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 4 Pri GPT table

6 76800 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

76806 6726359 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

6803165 32768 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

6835933 4 Sec GPT table

6835937 1 Sec GPT header

-bash-3.2# diskutil repairDisk disk0

Repairing the partition map might erase disk0s1, proceed? (y/N) y

Started partition map repair on disk0

Checking prerequisites

Checking the partition list

Adjusting partition map to fit whole disk as required

Checking for an EFI system partition

Checking the EFI system partition's size

Checking the EFI system partition's file system

Checking the EFI system partition's folder content

Checking all HFS data partition loader spaces

Checking booter partitions

Checking booter partition disk0s3

Verifying file system

Volume is already unmounted

Performing fsck_hfs -fn -x /dev/rdisk0s3

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Checking multi-linked files

Checking catalog hierarchy

Checking extended attributes file

Checking volume bitmap

Checking volume information

The volume Boot OS X appears to be OK

File system check exit code is 0

Restoring the original state found as unmounted

Reviewing boot support loaders

Checking Core Storage Physical Volume partitions

Verifying storage system

Performing fsck_cs -n -x --lv --uuid 71DFF05B-D4C1-466A-B406-08775ADEF408

Checking volume

disk1s2: Scan for Volume Headers

disk0s2: Scan for Volume Headers

disk1s2: Scan for Disk Labels

disk0s2: Scan for Disk Labels

Logical Volume Group 71DFF05B-D4C1-466A-B406-08775ADEF408 spans 2 devices

disk0s2+disk1s2: Scan for Metadata Volume

Logical Volume Group has a 62 MB Metadata Volume with no redundancy

Start scanning metadata for a valid checkpoint

Load and verify Segment Headers

Load and verify Checkpoint Payload

Load and verify Transaction Segment

Incorporate 0 newer non-checkpoint transactions

Load and verify Virtual Address Table

Load and verify Segment Usage Table

Load and verify Metadata Superblock

Load and verify Logical Volumes B-Trees

Logical Volume Group contains 1 Logical Volume

Load and verify FDC9DBCE-29DD-4F54-AEB5-56891A50DFBD

Load and verify 5CD0DA04-089D-4DA3-A30D-61F40B21D0F7

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Live Virtual Addresses

Newest transaction commit checkpoint is valid

Load and verify Segment Cleaning

The volume 71DFF05B-D4C1-466A-B406-08775ADEF408 appears to be OK

Storage system check exit code is 0

Repairing storage system

Performing fsck_cs -y -x --lv --uuid 71DFF05B-D4C1-466A-B406-08775ADEF408

The volume disk1s2+disk0s2 cannot be repaired when it is in use

Checking volume

disk1s2: Scan for Volume Headers

disk0s2: Scan for Volume Headers

disk1s2: Scan for Disk Labels

disk0s2: Scan for Disk Labels

Logical Volume Group 71DFF05B-D4C1-466A-B406-08775ADEF408 spans 2 devices

disk0s2+disk1s2: Scan for Metadata Volume

Logical Volume Group has a 62 MB Metadata Volume with no redundancy

Start scanning metadata for a valid checkpoint

Load and verify Segment Headers

Load and verify Checkpoint Payload

Load and verify Transaction Segment

Incorporate 0 newer non-checkpoint transactions

Load and verify Virtual Address Table

Load and verify Segment Usage Table

Load and verify Metadata Superblock

Load and verify Logical Volumes B-Trees

Logical Volume Group contains 1 Logical Volume

Load and verify FDC9DBCE-29DD-4F54-AEB5-56891A50DFBD

Load and verify 5CD0DA04-089D-4DA3-A30D-61F40B21D0F7

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Live Virtual Addresses

Newest transaction commit checkpoint is valid

Load and verify Segment Cleaning

The volume 71DFF05B-D4C1-466A-B406-08775ADEF408 appears to be OK

Storage system check exit code is 0

The partition map appears to be OK

Finished partition map repair on disk0

-bash-3.2#


Btw, I need to solve this without losing any data.

Mar 2, 2018 6:33 AM

Reply Helpful

Mar 2, 2018 8:55 AM in response to EtayCohen In response to EtayCohen

When you booted in Internet Recovery, the disks were re-numbered. Your 1TB is now a different disk number. Run diskutil list and find out the disk number for the 1TB then modify the following commands to use the appropriate value of 'N'.


diskutil unmountDisk diskN

gpt add -i 4 -b 1683348104 -s 270177031 -t windows /dev/diskN

gpt -vv -r show /dev/diskN

diskutil repairDisk diskN

Mar 2, 2018 8:55 AM

Reply Helpful

Mar 2, 2018 1:17 PM in response to Loner T In response to Loner T

I accidentally forgot to copy the output, but :

diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB
disk0s1

2: Apple_CoreStorage Macintosh HD 861.0 GB
disk0s2

3: Apple_Boot Recovery HD 139.0 GB
disk0s3


/dev/disk1 (internal):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme 28.0 GB disk1

1: EFI EFI 314.6 MB
disk1s1

2: Apple_CoreStorage Macintosh HD 27.6 GB disk1s2

3: Apple_Boot Boot OS X 134.2 MB
disk1s3


/dev/disk2 (internal, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD +887.6 GB
disk2

Logical Volume on disk1s2, disk0s2

5CD0DA04-089D-4DA3-A30D-61F40B21D0F7

Unencrypted Fusion Drive


Mar 2, 2018 1:17 PM

Reply Helpful

Mar 2, 2018 2:18 PM in response to EtayCohen In response to EtayCohen

EtayCohen wrote:


I accidentally forgot to copy the output, but :

diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB
disk0s1

2: Apple_CoreStorage Macintosh HD 861.0 GB
disk0s2

3: Apple_Boot Recovery HD 139.0 GB
disk0s3


Is this after you tried to remove the partition using BC Assistant Remove/Restore?

Mar 2, 2018 2:18 PM

Reply Helpful

Mar 3, 2018 1:03 PM in response to EtayCohen In response to EtayCohen

Unfortunately, now there is a painful exercise to get the disk space now. Can you create a Time Machine backup? For a Fusion drive, if BCA cannot do it correctly, the underlying disks have to be initialized and reconfigured in Fusion configuration, before you can restore and get your disk space back.

Mar 3, 2018 1:03 PM

Reply Helpful
User profile for user: EtayCohen

Question: Lost space after removing Bootcamp using bootcamp assistance