After upgrading to 10.13, my 500GB SSD is nearly full. With 10.12 i always had ~200GB free. Looking at AboutThisMac->Storage->Manage, i see "System" using up nearly 300GB. However, looking at my SSD in finder, i cannot see any folders that would sum up to this size.
Does anyone notice this as well and is there a workaround?
radar://32782835
What's the workaround until Apple fixes this? Anyone succesffully revert back?
viettanium,
Go here: https://bugreport.apple.com
https://bugreport.apple.com/web/?problemID=32840169
Please open a problem ID, the more that we open the more likely Apple will investigate and resolve. What's odd is that Apple hasnt acknowleged the issue or marked my ticket as "duplicate". Usually they're quick to do those things.
I was unable to install DP2 and Xcode, so I reformated my SSD to HFS+.
Same problem. Now cannot upgrade to beta 2 to becasue there is not enogh space. Also getting incessant low space notifications from various applications which is very annoying. Need a fix for this ASAP please!
Same problem, I removed 50GB of win10 parallel desktop, but only get 8 GB back
Me too. Worse yet, booting to the recovery mode and using Disk Utility reported an error #8, but was unable to fix it!
I installed a fresh Sierra on my SD card.
Even though its Disk Utility still can't fix the filesystem, it is letting me access the APFS file system on the Apple SSD,
which should let me rescue some files.
Here's what Sierra's "diskutil list" booting off of /dev/disk3 has to say for itself:
Jasons-MacBook-Pro:~ moo$ 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 999.7 GB disk0s2
3: Apple_KernelCoreDump 655.4 MB disk0s3
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme +999.7 GB disk1
/dev/disk1s1 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Volume MBP-1TB-SSD +991.2 GB disk1s1
/dev/disk1s2 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Volume Preboot +18.2 MB disk1s2
/dev/disk1s3 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Volume Recovery +507.9 MB disk1s3
/dev/disk1s4 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Volume VM +1.1 GB disk1s4
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *63.9 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_CoreStorage Untitled 1 63.0 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS SD Card 64Gb +62.6 GB disk3
Logical Volume on disk2s2
7BB1C619-BDDD-433F-9D69-84B72524F577
UnencryptedFWIW I was able to get build 17A291j installed by using another Mac to download the installer and then copy to an External USB Drive and then run the installer from there.But, yeah.. The issues remain. I filed a radar, 32856449, and have been documenting everything I'm doing. I even took a video of me moving a Parallels VM to an External Drive to free up that space so I could install it. They're telling me that the info I'm giving them is helping.. I'd suggest everyone here file a Radar, too. Might be a good thing for them to have info about all of the different types of hardware we're using.
I used Carbon Copy Clone to copy my existing drive to a HPS+ FS drive and I was able to boot off of it. Everything came over but some apps didnt like it wanting me to re-enter my stored passwords. They're likely tied to the drive. I was hoping Beta 2 would fix this but everytihng I've tried so far has been unsucessful. I'm thinking of getting a thunderbolt SSD exnteral drive, boot off of that for awhile. (I'll encrypt it so that it's secure.)
Yesterday I decided to finally reinstall or restore the system.
Turned out to be a pretty horrendous experince, but at least it can help someone who'll decide to do the same
Some parts of it might only be applicable to older hardware, in my case a 2012 Macbook Retina.
What I found out
1) Recovery partition contains High Sierra (good)
2) Internet Recovery started when this partition is not present starts Lion installation (that will depend on what your HW shipped with)
3) Internet Recovery when invoked manually starts Sierra Installation
4) Time Machine backups made on 10.13 don't work with Sierra Time Machine (they do, mostly, but not for restoring the whole system)
5) Deleting your OS APFS Volume will not reclaim any significiant disk space!!!
6) Choosing "Restore from Time Machine" will thus not free anything and will run out of space shortly after starting restore!
What does it all mean?
Well, the only way to reclaim this lost disk space is to recreate the APFS Container, even deleting the whole volume doesn't free anything. Take a look how it looked after deleting disk2s1, AKA my root volume:
APFS Container (1 found)
|
+-- Container disk2 FD4007F5-FE7F-4DE9-B21A-941F76189504
====================================================
APFS Container Reference: disk2
Capacity Ceiling (Size): 479238864896 B (479.2 GB)
Capacity In Use By Volumes: 465694814208 B (465.7 GB) (97.2% used)
Capacity Available: 13544050688 B (13.5 GB) (2.8% free)
|
+-< Physical Store disk0s2 00000064-76DA-0000-5C45-000096220000
| -----------------------------------------------------------
| APFS Physical Store Disk: disk0s2
| Size: 479238864896 B (479.2 GB)
|
+-> Volume disk2s2 27355FD9-0817-4AF5-8D42-81115A5CC7C1
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s2 (Preboot)
| Name: Preboot
| Mount Point: Not Mounted
| Capacity Consumed: 30117888 B (30.1 MB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s3 0CA2FD60-F37B-4D46-A91A-CCAFA36C10EB
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s3 (Recovery)
| Name: Recovery
| Mount Point: Not Mounted
| Capacity Consumed: 2581450752 B (2.6 GB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s4 518E1584-3568-43DB-9673-43003ED70192
---------------------------------------------------
APFS Volume Disk (Role): disk2s4 (VM)
Name: VM
Mount Point: Not Mounted
Capacity Consumed: 1073766400 B (1.1 GB)
Capacity Reserve: None
Capacity Quota: None
Encrypted: NoAnd yes, fsck was still pretty happy with this situation. Nothing wrong here, move along...
Also, after deleting this Volume, even though Recovery Volume was still present, Macbook would no longer boot Recovery anymore. That means you're stuck with Sierra (hopefully) which will not restore your High Sierra installation, thus you either need to revert to a Sierra backup (that's what I did) or somehow boot the installer (from USB stick?) and delete and recreate the whole Container.
But even if you solve this, for some reason contents of the other Volumes simply can't be dumped and restored - you'll get a permission denied. I'm sure this could be solved but I haven't had a chance to try.
Apple really needs to provide a working fsck_apfs to fix this in the first place. It's pretty sad that the one we have can't really be used from Recovery anyway and even this wasn't fixed in the second Beta. Even for a development machine, having no way to even restore system from this state makes it absolutely unacceptable to install IMO. Tools such as fsck simply can't be left for "later" just because it's not meant to be public yet...
If only Apple went with ZFS instead of reinventing the wheel...
You can't repair APFS disks with DU (as I have found after much work. I had a 128GB MBA with this loss of space problem. Here's how I fixed it.
1. Created a USB bootable 10.13 installer (Google for how-tos) for Beta 2
2. Used Carbon Copy Cloner to back up my files
3. Booted from the USB stick
4. Reformatted the MBA hard disk as HFS+
5. Installed Beta 2 and chose APFS during installtion (trying to format as APFS through Disk Utility DOES NOT WORK - do it in the isntall (if you do it at all))
6. Restored from my CCC backup
I went from 1.3GB to 66GB free and so far (fingers crossed) Beta 2 seems to behave properly
I was able to create a USB installed for b1, but from what I’m seeing, the createinstallmedia option isn’t included in b2. I just had to reformat my entire drive (losing my BootCamp partition, too. Thanks WinClone!) and reinstall b1 from the USB installer. Would have loved to just do a straight up clean install with a b2 installer. But I can just format the drive again after a few more betas of this are released.
What's the right fsck command to repair APFS?
probably
fsck_apfs -y /dev/disk0s1
use
diskutil list
to find your drive.
I found that the TIme Machine error indicating that my APFS startup volume could no longer be backed up was easily corrected by selecting the Time Machine menu item while holding down the option key, and selecting the Verify Backups drop-down option displayed in place of the standard Back Up Now item.
This was the first and only step necessary in my response to the error dialog: "Time Machine could not complete the backup to "AirPort Time Capsule 2TB. Unable to complete backup. An error occurred while creating the backup folder. Latest successful backup: June 20, 2017." A date, I would note, upon which I installed the second release of macOS High Sierra 10.13.