Hi people.
I'm unable to reclaim free space after uninstalling Bootcamp (done through Boot Camp Assistant).
I've already search this and other forums with related problems, but none could solve mine.
Here are some screenshots from Disk Utility and results from diskutil:
What can I do to fix this?
Thanks!
I'm unable to reclaim free space after uninstalling Bootcamp (done through Boot Camp Assistant).
I've already search this and other forums with related problems, but none could solve mine.
Here are some screenshots from Disk Utility and results from diskutil:
Code:
$ 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_APFS Container disk2 771.3 GB disk0s2
(free space) 228.7 GB -
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *28.0 GB disk1
1: EFI EFI 314.6 MB disk1s1
2: Apple_APFS Container disk2 27.7 GB disk1s2
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +799.0 GB disk2
Physical Stores disk1s2, disk0s2
1: APFS Volume Macintosh HD - Data 365.7 GB disk2s1
2: APFS Volume Preboot 1.8 GB disk2s2
3: APFS Volume Recovery 1.1 GB disk2s3
4: APFS Volume VM 4.3 GB disk2s4
5: APFS Volume Macintosh HD 8.9 GB disk2s5
6: APFS Snapshot com.apple.os.update-... 8.9 GB disk2s5s1
$ diskutil info disk0
Device Identifier: disk0
Device Node: /dev/disk0
Whole: Yes
Part of Whole: disk0
Device / Media Name: APPLE HDD ST1000DM003
Volume Name: Not applicable (no file system)
Mounted: Not applicable (no file system)
File System: None
Content (IOContent): GUID_partition_scheme
OS Can Be Installed: No
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Disk Size: 1.0 TB (1000204886016 Bytes) (exactly 1953525168 512-Byte-Units)
Device Block Size: 512 Bytes
Media OS Use Only: No
Media Read-Only: No
Volume Read-Only: Not applicable (no file system)
Device Location: Internal
Removable Media: Fixed
Solid State: No
Virtual: No
Hardware AES Support: No
$ diskutil info disk1
Device Identifier: disk1
Device Node: /dev/disk1
Whole: Yes
Part of Whole: disk1
Device / Media Name: APPLE SSD SM0032L
Volume Name: Not applicable (no file system)
Mounted: Not applicable (no file system)
File System: None
Content (IOContent): GUID_partition_scheme
OS Can Be Installed: No
Media Type: Generic
Protocol: PCI-Express
SMART Status: Verified
Disk Size: 28.0 GB (28000002048 Bytes) (exactly 54687504 512-Byte-Units)
Device Block Size: 4096 Bytes
Media OS Use Only: No
Media Read-Only: No
Volume Read-Only: Not applicable (no file system)
Device Location: Internal
Removable Media: Fixed
Solid State: Yes
Virtual: No
Hardware AES Support: No
$ diskutil info disk2
Device Identifier: disk2
Device Node: /dev/disk2
Whole: Yes
Part of Whole: disk2
Device / Media Name: APPLE SSD SM0032L
Volume Name: Not applicable (no file system)
Mounted: Not applicable (no file system)
File System: None
Content (IOContent): EF57347C-0000-11AA-AA11-00306543ECAC
OS Can Be Installed: No
Media Type: Generic
Protocol: PCI-Express
SMART Status: Verified
Disk / Partition UUID: A267C17A-5F6E-42B8-8B18-0F212E883B18
Disk Size: 4.6 EB (4611686789742047232 Bytes) (exactly 9007200761214936 512-Byte-Units)
Device Block Size: 4096 Bytes
Media OS Use Only: No
Media Read-Only: No
Volume Read-Only: Not applicable (no file system)
Device Location: Internal
Removable Media: Fixed
Solid State: Yes
Virtual: Yes
Hardware AES Support: No
This disk is an APFS Container. APFS Information:
APFS Physical Store: disk1s2
APFS Physical Store: disk0s2
Fusion Drive: Yes
$ diskutil apfs resizecontainer disk0s2 0
Started APFS operation
Aligning grow delta to 228 680 470 528 bytes and targeting a new container size of 999 995 129 856 bytes
Determined the maximum size for the APFS Container to be 999 994 101 760 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /dev/disk1s2
Checking the container superblock
Checking the fusion superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the Fusion data structures
Checking the encryption key structures
Checking volume /dev/rdisk2s1
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the document ID tree
Checking the fsroot tree
warning: inode (id 12938549223): dir-stats key xf does not exist, despite internal_flags (0x8412)
error: doc-id tree: record exists for doc-id 66941, file-id 12938156163 but no inode references this doc-id
error: doc-id tree: record exists for doc-id 66979, file-id 1192909 but no inode references this doc-id
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk2s1 was found to be corrupt and needs to be repaired
Checking volume /dev/rdisk2s2
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk2s2 appears to be OK
Checking volume /dev/rdisk2s3
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk2s3 appears to be OK
Checking volume /dev/rdisk2s4
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk2s4 appears to be OK
Checking volume /dev/rdisk2s5
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 1 (com.apple.os.update-DCFA9E2D4E4407822BB513A874B2A2922E2DD50403877F878FA8D11CC3D57596)
Checking the fsroot tree
Checking the file extent tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk2s5 appears to be OK
Checking volume /dev/rdisk2s6
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk2s6 appears to be OK
Verifying allocated space
warning: MT mapping (0x400000067872b -> 0x4463a8, 1, C) is not completely referenced
warning: MT mapping (0x400000068769a -> 0x3f4c58, 512, C) is not completely referenced
warning: MT mapping (0x40000006af835 -> 0x445664, 1, C) is not completely referenced
warning: MT mapping (0x40000039e04a7 -> 0xf8da9, 1, C) is not completely referenced
warning: MT mapping (0x4000003ad54a1 -> 0x1a047f, 1, C) is not completely referenced
Performing deferred repairs
error: doc-id tree record exists for doc-id 66941, but no inode references this doc-id
Skipped 2/2 repairs of this type in total
The container /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Growing APFS Physical Store disk0s2 from 771 314 659 328 to 999 995 129 856 bytes
Modifying partition map
Growing APFS data structures
APFS Container Resize error code is 49174
A problem occurred; undoing all changes
Modifying partition map
Error: -69606: A problem occurred while resizing APFS Container structuresWhat can I do to fix this?
Thanks!
