I’ve noticed that for awhle now that Disk Utility has been flaky on my iMac: iMac, 2015, Oct, 27” 5K display, Fusion HDD, OS 10.14.5
OTOH, it runs just fine on my MB Pro: MacBook Pro Retina, 2013, OS 10.14.5
I ran DU > First Aid last night and the iMac froze completely: no cursor movement, no response to keyboard commands.
Restarted, tried DU again, everything froze again.
Restarted, zapped the pram, unplugged the iMac for 30", tried again, froze again.
Restarted, logged into a test account, DU froze everything again.
Restarted in Safe Boot, DU froze everything again.
Restarted in Recovery Mode, ran DU DFA on the Base System and all was OK. Ran DU DFA on the Macintosh HD, and all was fine but I noted that there were 48 snapshots.
BTW, in all cases noted above, only peripheral attached was the keyboard.
QUESTION: What determines the number of snapshots? Is 48 a “normal” amount? I booted the MB Pro in Recovery Mode, but in DU, the MacintoshHD was greyed out: probably because it is encrypted?
A little searching around revealed that this is not an isolated problem I am experiencing; apprently other folks are having problems with DU in both High Sierra and Mojave but no one is offering any solutions.
Is it time/would it hurt to reinstall the OS via Disk Recovery?
I was trying to repair permissions today on my Mac so I ran the Disk Utility's First Aid on my drive and it said that there was an Invalid Index Key and that my disk was corrupt and I needed to run the first aid in Recovery mode.
So I opened in recovery mode and ran the first aid and it tried to fix the B-Tree of the catalog file, however there wasn't enough disk space to do this.
Then it tried to restore the disk to it's original state on mount but it couldn't do this either, I'm guessing because of lack of disk space.
(I had about 13GB of free space at this time)
Sorry I didn't get any screenshots or anything but that is basically what happened.
Now the disk is greyed out in disk utility and I can't reinstall mac os x because I would need to erase all of the data on the drive and I don't want to lose the files I have on it.
So what I thought I could try is delete my BOOTCAMP partition, which is about 100GB, and then merge the free space into the problem partition so that I can run fsck -fy in single user mode to try to repair the volume which now will have enough space to complete the operation.
However the option to delete the BOOTCAMP partition is disabled in Disk Utility. So I did some research and found another post on AskDifferent that explained how to delete a partition from terminal (in recovery mode) by first unmounting the physical disk using diskutil unmountDisk /dev/disk0 and then deleting the partition using gpt remove.
Now I tried to unmount the disk using that command and even with the force wildcard but it said:
Forced unmount of disk0 failed: at least one volume could not be unmounted
Unmount was dissented by PID 0
The volume with PID 0 from the list provided by diskutil list is called GUID_partition_scheme.
This is as far as I got through searching for solutions online. I need help deleting the BOOTCAMP partition and merging with the greyed out Mac HD partition so that I can run fsck to hopefully restore my mac os to working order. At the moment I can't boot into the OS and can only boot into recovery mode or single user mode. Hopefully I will atleast be able to retrieve files from the HD if all else fails.
Hi! my 2017 macbook seemed to have a problem with my disk after trying to wipe my personal information & installing a new installation of MacOS. I’ve used Disk first aid but it’s been stuck on “unlocking disk” for about 12 hours now. it’s embarrassing how bad i am at stuff like this. can i turn it off without screwing anything up?
(i used to be able to use the macbook just fine, it would just tell me “can’t unlock disk 1” but besides that i didn’t really run into a problem when using the macbook)
edit, Solved: fixed by running First aid from disk utility from recovery
====
Running macOS 10.14 stable.
Disk Utility's output: Running First Aid on “APPLE SSD” (disk1s1)
NOTE: First Aid will temporarily lock the startup volume.
Verifying file system.
Volume could not be unmounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking the container superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking volume.
Checking the APFS volume superblock.
The volume APPLE SSD was formatted by hfs_convert (748.1.46) and last modified by apfs_kext (945.200.129).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the extent ref tree.
Checking the fsroot tree.
error: btn: invalid btn_btree.bt_key_count (expected 12151094, actual 12151370)
fsroot tree is invalid. The volume /dev/rdisk1s1 could not be verified completely.
I don't recall reading anything about why it might not be safe but I just wanted to make sure that it was okay. Thanks
When I run First Aid for the first time, it shows that there are no problems, but when I do it for the second time, it says "First Aid found corruption that needs to be repaired. To repair the startup volume, run First Aid from Recovery. Click Done to continue."
I run it from Recovery, boot back up, again the same: first time on First Aid no problems, second time it shows error.
What could it be?
Running MacBook Pro 15 2018 i7 2.6.
I'm not completely sure, but it could be due to OnyX. I installed it a few days ago and ran an Automation on default settings a few days ago. It has been working fine since, but today, suddenly, this happened. I'm on 10.12.2.
Edit: Spotlight and Notification Center not working either.
I'm trying to erase my Time Machine partition to start anew, as it cannot currently be used for backups for some reason. I can still see the files, but it appears to be read only.
When trying First Aid in Disk Utility, it comes up with the following:
Repairing file system.
Volume was successfully unmounted.
Performing fsck_hfs -fy -x /dev/rdisk2s2
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Incorrect block count for file permStore
(It should be 17 instead of 0)
Keys out of order
Missing thread record (id = 10755774)
Rebuilding catalog B-tree.
The volume Time Machine could not be repaired.
File system check exit code is 8.
Restoring the original state found as mounted.
Problem -69842 occurred while restoring the original mount state.
File system verify or repair failed.
Operation failed…
This Time Machine is part of two partitions on a single drive. The other partition contains files I need to keep, so formatting the complete drive is not an option.
Is there anything I can do? Thanks!
Basically the title.
I'm trying to install Windows on my laptop through a USB drive and I can't get the hard drive to partition and it's extremely frustrating. I've let it sit overnight, run disk repair, first aid, all of that. I've googled about it and checked Apple forums and can't figure it out. Any suggestions?
I have a 2010 Macbook Pro (I know I know, it's a dinosaur), running Sierra. Lately it's been running really sluggishly, as in getting the rainbow wheel when opening any application or folder or tapping on the file bar. I followed some basic clutter removal, and it didn't help. Did some searching and some Apple support recommended running disk utility. I booted it up in recovery mode, and this is the message I got. "Orphaned file inode (id=34788858). Look for missing items in lost+found directory. The volume Macintosh HD could not be repaired." What does this even mean? Any searches come up with extremely technical answers that go straight over my head. I have a Genius Bar appointment tomorrow, but usually they just do the same steps I've already done.
Any help is greatly appreciated!
Hi all,
I'm trying to fix a kernel panic on my 2012 Macbook Pro (macOS Sierra). I'm trying to run First Aid on my partition but it fails and the partition grays out again. If I try to mount the partition again no prompt for my password appears (edit: the partition is encrypted). I have to restart the computer to mount the partition again, but the same issue occurs.
Here's the Keychain First Aid window.
Any help or advice appreciated.
When I run the First Aid on my HD I get an error message saying "The volume /dev/rdisk1s1 could not be verified completely." What does this mean and what are the implications? Below the full operation details:
Running First Aid on “Henkka” (disk1s1)
NOTE: First Aid will temporarily lock the startup volume.
Verifying file system.
Volume could not be unmounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking the container superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking volume.
Checking the APFS volume superblock.
The volume Henkka was formatted by hfs_convert (748.21.6) and last modified by apfs_kext (945.230.6).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 13.
error: btn: invalid btn_btree.bt_key_count (expected 3946437, actual 3946490)
Snapshot is invalid.
The volume /dev/rdisk1s1 could not be verified completely.
File system check exit code is 0.
Restoring the original state found as mounted.
Operation successful.
