- MAC VOLUME COULD NOT BE UNMOUNTED USING LIVE MODE MAC OS X
- MAC VOLUME COULD NOT BE UNMOUNTED USING LIVE MODE PRO
- MAC VOLUME COULD NOT BE UNMOUNTED USING LIVE MODE FREE
Of course not on the same machine, but I've been keeping settings from machine to machine, and old stuff gets to accumulate.), but I don't think it will find (and delete/fix) hidden snapshots.Īlso, I'm a fan of Onyx, which usually fixes almost everything and always recovers a lot of disk space, but, this time, even Onyx gets stumped.
MAC VOLUME COULD NOT BE UNMOUNTED USING LIVE MODE MAC OS X
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. Click Run to check and repair for disk errors. Select the disk or volume you want to repair in the left sidebar, and then click First Aid at the top. Choose View and choose Show All Devices at the upper left of this app. Go to Launchpad, find Other, and then launch Disk Utility. 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). To do First Aid again, follow these steps. 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. Type diskutil list in the Terminal window. To unmount a disk in Terminal: Open Terminal in Applications > Utilities or choose Terminal from Utilities in Recovery Mode. You can use it from the Normal Mode if you want to unmount any external drive.
MAC VOLUME COULD NOT BE UNMOUNTED USING LIVE MODE PRO
Sadly, it didn't work for me (running 10.13.2 Beta (17C79a) on a MacBook Pro (Retina, 15-inch, Mid 2014)). Open Terminal from the Recovery Mode if you need to unmount the drive you are currently booted from. 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.
MAC VOLUME COULD NOT BE UNMOUNTED USING LIVE MODE FREE
Checking the space manager free queue trees. 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. Performing fsckapfs -n -l -x /dev/rdisk1s1 Checking the container superblock. TM, however, seems to be working fine regardless. You can use it when your Mac volume gives the unmountable. Disk Utility is capable of repairing specific drive issues. Secondly, it is likely to cause damage to the data, making it impossible to recover it. Firstly, it is often seen to fail to repair errors at times. 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. However, using First Aid is not a favorable method. So before I go down that road, I'm here to ask if I'm missing something obvious like an apfs_kext version or something.This seems to be related to/caused by local Time Machine snapshots. Most of my googling is telling me, "reformat your drive." Well, I'd rather not. Restoring the original state found as mounted. The volume /dev/rdisk1s1 could not be verified completely. The volume Hackint0sh HD was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (945.250.134).Įrror: directory valence check: directory (oid 0x130053): nchildren (1) does not match drec count (0)Įrror: directory valence check: directory (oid 0x130063): nchildren (2) does not match drec count (0)Įrror: invalid dstream.size (134218472), is greater than dstream.alloced_size (4096)Įrror: xf : INO_EXT_TYPE_DSTREAM : invalid dstreamĮrror: inode_val: object (oid 0x300a3ca8a): invalid xfields Performing fsck_apfs -n -l -x /dev/rdisk1s1Ĭhecking the space manager free queue trees. NOTE: First Aid will temporarily lock the startup volume. Running First Aid on “Hackint0sh HD” (disk1s1) Building a CustoMac Hackintosh: Buyer's Guide