Jump to content
SatSunMon

Disk Utility First Aid in recovery failed to restore volume to original state

1 post in this topic

Recommended Posts

Posted (edited)

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: 
 

Quote

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.

Edited by SatSunMon

Share this post


Link to post
Share on other sites
Advertisement

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By BugsB
      This is my mod of dimosgmx's Yosemite (10.10) Disk Utility app with the El Capitan (10.11) diskmanagementd:
       
      https://www.insanelymac.com/forum/files/file/621-disk-utility-v13-for-macos-sierrazip
       
      Please read his statements over there FIRST !!
       
      This built (607) is dimosgmx's built 606 ever-so-slightly edited* by me (BugsB) for usage in High Sierra beyond 10.13.3. It thus works in 10.12 - 10.13.6 (not yet tested in Mojave because I don't have it installed). Therefore I bumped CFBundleVersion to 607 and BuildVersion to 19 to differentiate it from dimosgmx's 606/ 18 which was only compatible up to 10.13.3.
       
      You can use it side-by-side with the default Disk Utility.
       
      NOT WORKING (at least not in High Sierra): functions which would invoke a Finder style window, like clicks onto "New Image", "Convert", "Resize Image", "Image", "File/ New/.." etc.
       
      In case of issues with the default (original/ stock/ vanilla) Disk Utility: run killall diskmanagementd, also supplied in this package.
       
      If you have the SIMBL plug-in AFLOAT installed and have not included AppleScript Utility in mySIMBL's blacklist**, you MUST blacklist Disk Utility 13 (607) (see screenshot "AFLOAT users mySIMBL application blacklist")!
       
      Virustotal result: 0 / 57
       
      Enjoy & Greetings
      BugsB
      2019-01-05
      ---
      * Disk Utility 13 (607).app/Contents/MacOS/loader.sh:
      Added two instances of:
      sudo killall diskmanagementd
       
      ** in mySIMBL: System Info/ SIMBL application blacklist (because Afloat is NOT fully compatible with Apple Scripts (parts of Disk Utility 13 (60x))
       
      PS: let me know if it also works in Mojave. Include your EXACT version (10.14.0/ .1/ .2 /.3 BETA etc.)
       
       
       
       
       
    • By jackluke
      Premise: the following explanation is only to exploit the little APFS Recovery (less than 600 MB) embedded inside the APFS File System, so avoiding an external USB Installer, you can't reinstall macOS from here but use just the Utilities (Terminal, DiskUtility) in case of emergency, however as known from a Recovery Terminal can do a lot of things, especially troubleshooting an unbootable macOS.
       
      To those who have installed Mojave on APFS file system with a GUID/GPT Scheme (I suppose it will work even on MBR scheme), I have managed to "fix" the "APFS Recovery Volume" to make it bootable from any computer (capable of HighSierra and Mojave) with USB input devices (trackpad, keyboard, USB mouse and so on) responsive, working wifi and everything else, just follow next steps, totally safe and harmless for any Mojave installation, after booting normally from your Mojave APFS Volume, launch Terminal and type:

      diskutil apfs list
      {locate your "APFS Recovery Volume" on diskXs3 [for an internal "APFS Container" is typically mounted on disk1s3]}
      On APFS scheme the "APFS Recovery Volume" is tipically on the 3rd (hidden) partition.

      diskutil mount diskXs3
      open /Volumes/Recovery

      landing on Finder, double click on the "random-numbers-letters" folder (it's the gpt UUID folder where Recovery stores itself), once inside rename these files:

      prelinkedkernel into prelinkedkernelbackup
      immutablekernel into immutablekernelbackup
      PlatformSupport.plist into PlatformSupportbackup

      Don't close this opened Finder window yet, once you renamed those 3 files, now you have to open a new Finder window, then from this new Finder window go into your Mojave path: /System/Library/PrelinkedKernels/

      while inside this path copy the file prelinkedkernel into the previous Finder window exactly where you renamed those 3 files
       
      lastly rename this fresh copied file from prelinkedkernel to immutablekernel

      Now you have a working APFS Recovery Volume.
       
       
      Note for those who use Clover bootloader in the config.plist you have to don't "Hide" the APFS Preboot and Recovery hidden partition, otherwise you can't use the APFS Recovery.
       
       
       
    • By Denicio
      QuickESP is a minimalistic and discreet ESP/EFI Mounter application. It's simple! Click to mount, and re-click to unmount.
       

       
      The Preferences pane enables you to configure the following:

      Enable Advanced View. Shows additional information about all discovered ESP volumes. This is helpful when you have multiple SSD/HDD installed on your system. Also you will be able to distinguish between drives with identical names.
      Open ESP folder on Finder. After mounting an ESP volume, its respective folder will open on Finder. This is a convenient time-saver.
      Autostart. Automatically launch the application on login. Make sure you have copied QuickESP.app into your /Applications folder.


       
      Credits: Dennis Koluris (a.k.a Denicio), Rick Patrick for the HDRV icon.
    • By Oschły
      Hi! I want to resize my system's partitions, but I have a problem. Many small partitions like EFI, Windows MSR and Recovery and macOS Recovery are between that partitions on screenshot. Can I use easeus Partition Master to shrink Windows 10 partition, move this free space next to macOS partition by gparted and resize macOS partition by DU? My hackintosh is encrypted by FileVault 2.
       
      My specs:
      Motherboard: Gigabyte P85-D3
      GPU: GTX 750 Ti
      CPU: i5-4670
      RAM: 8 GB DDR3 1666 MHz
      Ethernet: Realtek rtl8111
      Sound card: ALC887
      Disks: GoodRam Iridium Pro 240GB and HDD 1TB 5400 RPM
      OS: macOS Sierra 10.12.6 and Windows 10 Creators Update.
       
      Thanks for help!

    • By swordsx48
      Hi, I first started Hackintosh with a Yosemite installation. This was the second partition on an MBR drive with the first partition as NTFS w/o Windows. It worked fine despite what I've heard but it ran out of space so I cloned that partition to another drive. This was eventually pointless because it created a 160gb partition on a 500gb drive and I came to learn HFS cannot be resized if the table is MBR. Now, this clone, which I used for a long period of time, still boots fine. However, no bootloader recognizes the initial OSX partition. They both used to come up and work just fine however.
       
      Nowadays, I'm running macOS Sierra with a Clover EFI installation which doesn't recognize the first partition, nor does the chameleon from the second clone.
       
      I've tried installing Chameleon and Clover to that partition and booting from it, but no go.
       
      Thanks in advance.
×