![]() I'm also exploring a bit with DaisyDisk, and finding lots of interesting garbage to delete (note that I've been progressively upgrading Mac OS X since. I wonder if the only way out is going the way of reformatting the SSD disk with HFS+. Time Machine automatic backups are shut down. This time, however, tmutil listLocalSnapshotDates / didn't show anything by contrast, tmutil listLocalSnapshots / gives .-003459 (dataless), but I have no way to delete that (assuming it's even possible to do so). I did tmutil listLocalSnapshotDates / and it did find one local snapshot, which I deleted as per instructions then I tried to run fsck_apfs again (in SU mode), and it failed at the exact spot with the same error message. Sadly, it didn't work for me (running 10.13.2 Beta (17C79a) on a MacBook Pro (Retina, 15-inch, Mid 2014)). Targeting the main partition (/dev/rdisk1s1), it'd say that live repairs weren't supported yet.įinally, I'm getting a similar error to what albugna is getting which I have a feeling is related to this. ![]() Seemingly no matter what I did, it would say the drive as a whole (ie /dev/rdisk1) was mounted with write access even with the drive completely ejected. Even booting the 10.13 installer from a flash drive, for the life of me, I couldn't get fsck_apfs to even attempt to repair anything. As far as I can tell, fsck_apfs (so by extension, Disk Utility and diskutil) isn't able do any repairs right now because it thinks the APFS drive is perpetually mounted. Still, even with the local snapshots deleted (and automatic backups disabled to prevent new snapshots from being created), I get the same the same 'error 8' in SU or Recovery mode. ![]() TM, however, seems to be working fine regardless. Using 'tmutil deleteLocalSnapshots ' to delete all the local snapshots, I no longer get 'Snapshot is invalid.' So Apple has apparently (and so far, poorly) integrated features for TM directly into APFS. This seems to be related to/caused by local Time Machine snapshots.
0 Comments
Leave a Reply. |