Still unable to work on the disk? Still getting those pesky disk errors? Bit more drastic, but you can attempt to force a volume or the entire physical disk to unmount: FOR A VOLUME: 1) Using the Terminal application again, booting from OS X Recovery or an external bootable drive. Nov 18, 2017 Open the USB drive (the name 'USB' will become 'OS X Base System', that's why you need to smartly unmount the other one using Disk Utility to avoid confusion.) Inside the USB drive, go to 'System' then 'Installation' remove the file named 'Packages'. That's actually an allias (or a shortcut if you want). Go to OS X Install ESD drive. There are a couple of ways to get around the problem, so you can check and repair your Mac’s normal startup drive. The methods include starting up from your OS X Recovery HD volume, or another drive that contains OS X. (Please note: If you're checking a Fusion drive, you must start up with OS X 10.8.5 or later. Failing that, logging out of your OS X account and back in should clear the state, allowing you to unmount it. And if that doesn’t work, a full restart should help. Unmount the disk. Unmount the disk called /dev/disk2: $ diskutil unmountDisk /dev/disk2 Sample outputs: Unmount of all volumes on disk2 was successful 3. Create the disk image with dd. Finally create the disk image of the entire disk /dev/disk2: $ sudo dd if=/dev/disk2 of=backup.my.sdcard-18-oct-2015.img.dd bs=512 OR.
Hello -
I've successfully installed the High Sierra GM candidate on my MacBook Pro.
I've spent the past few hours trying to get it to install onto my Mac Mini (Late 2014). Currently running Sierra.
When I run the installer, it reboots, starts to install, then says 'Unable to unmount volume for repair'.
If I boot into Recovery, then run disk utility, I get a similar error. If I bring up a terminal, then 'diskutil unmount' the drive, it says 'Volume Macintosh HD on diskX failed to unmount: dissented by PID=0 (kernel)'. This is from the Recovery partition, so I'm not actively booted from 'Macintosh HD'.
I ran 'diskutil unmount force' on the partition, then I was able to run Disk Utility's 'First Aid'. Everything seemed OK. I still couldn't install High Sierra (same error).
I then created a High Sierra installer on an SD card, and booted from it (held Option while booting). Again, when installing macOS, I get the 'Unable to unmount the volume for repair' error.
If (while booted from the SD card) I bring up a terminal and 'diskutil unmount force', the installer doesn't show 'Macintosh HD' as an option (expected).
If I run 'diskutil mount readOnly ..', then run the installer, it sees the disk - but fails (because it's readonly). When it's mounted readonly, 'diskutil unmount' (without force) works fine.
If I run 'diskutil mount ..', then immediately try 'diskutil unmount' (without 'force'), it fails with the same 'dissented by PID=0 (kernel)' error.
Why is the kernel mounting 'Macintosh HD' (even when I'm booted from external media) and keeping it 'locked'? Is there any way to fix this?
I've also tried 'csrutil disable' to disable the System Integrety protection stuff. No difference.
Any ideas/suggestions?
Thanks!
- Paul B.
I have found myself recently experiencing a couple of Macs which would not allow me to repair the directory or permissions in Disk Utility, or erase/partition the drive with an error such as: ‘Disc erase failed couldn’t unmount disc’ or ‘Disk Erase failed with the error: Couldn’t unmount disk.’
Even trying to use Network Deployment tools such as Apple’s Netinstall service or DeployStudio have also failed to deploy due to these errors.
Normally, any ‘Couldn’t Unmount Disk’ error is attributed to circumstances where the boot drive is being modified or is being used by an application or process. So the first thing to do is to startup the Mac from another bootable drive such as an external drive or OS X Recovery. You can then run Disk Utility from there.
An external drive or a network drive is preferred if it is the internal hard drive you have an issue with, since the OS X Recovery is a partition on the same physical drive which may not be able to successfully unmount or modify your internal disk.
To create your own bootable disk, refer to our blog ‘Creating a Mavericks bootable install disk’.
I would strongly recommend at this stage attempting to back up any data that is required before proceeding with the following steps. Some of the following steps are destructive and will lose ALL data on your drive.
Mac Os X Unable To Unmount Volume For Repair Shop
Still not playing ball?
You can try booting from OS X Recovery (by holding ‘CMD’ + ‘R’ keys at startup) or an external drive and use the command line to attempt to unmount or erase the disk:
1) Once booted from OS X Recovery, select Terminal from the Utilities pull down menu. (Or if you are booting to your own bootable drive with a full system, open Disk Utility from /Applications/Utilities).
At the unix prompt enter:
Press RETURN. From the listing, look in the Identifier column for your disk identifier. It will look like ‘diskx’ where ‘x’ is an integer starting at 0. You should also see the name of the disk such as ‘Macintosh HD’. In my example below, the disk name is ‘Server’. Note down the disk identifier. For a single drive system this will probably be ‘disk0’ :
2) Now enter the following where ‘x’ is your disk identifier:
3) Press RETURN. Enter your admin password if prompted. This should unmount all volumes of the physical drive:
4) Attempt again to perform whichever task caused your ‘Couldn’t Unmount Disk’ error. (For example to Erase/Partition the disk).
Still unable to work on the disk? Still getting those pesky disk errors?
Bit more drastic, but you can attempt to force a volume or the entire physical disk to unmount:
Mac Os X Unable To Unmount Volume For Repair 69673
FOR A VOLUME:
1) Using the Terminal application again, booting from OS X Recovery or an external bootable drive,
Enter the following where ‘x’ is your disk identifier and ‘y’ is your volume identifier, (remember to use the ‘diskutil list’ command if you need to find out your disk and volume identifiers):
2) Press RETURN. Enter your admin password if prompted. This should force unmount the volume:
3) Attempt again to perform whichever task caused your ‘Couldn’t Unmount Disk’ error. (For example to Erase/Partition the disk).
FOR AN ENTIRE PHYSICAL DISK:
1) Using the Terminal application again, booting from OS X Recovery or an external bootable drive.
Enter the following where ‘x’ is your disk identifier. (Remember to use the ‘diskutil list’ command if you need to find out your disk identifiers):
2) Press RETURN. Enter your admin password if prompted. This should force unmount the entire physical disk and all its related volumes:
3) Attempt again to perform whichever task caused your ‘Couldn’t Unmount Disk’ error. (For example to Erase/Partition the disk).
OK, we’ve tried to be nice, but is the disk STILL not letting you work with it?
Be sure you backup your files to an external drive or second internal drive, the following procedure will remove everything from the hard drive!
We are now going to force erase the physical disk, creating a single Mac OS Extended (Journaled) volume. This should then allow you to partition and work with the physical disk again.
1) Using the Terminal application again, booting from OS X Recovery or an external bootable drive.
Enter the following where ‘MacintoshHD’ is the name of the newly created Mac formatted partition, and where ‘x’ is your disk identifier, (remember to use the ‘diskutil list’ command if you need to find out your disk identifiers):
2) Press RETURN. Enter your admin password if prompted. This should force erase the entire physical disk and all its related volumes, then create a single Mac OS Extended (Journaled) volume:
3) Hopefully you can now perform your desired erase, partition, installation or deployment on this drive.
![]()
NOTE: Use of the ‘sudo’ command may not be necessary for some of these actions, however, as long as you know the administrator account’s password, starting any unix command with ‘sudo’ will force the command to be run as the unix root user, so you shouldn’t have any permission issues executing the command.
Disclaimer:
While the author has taken care to provide our readers with accurate information, please use your discretion before acting upon information based on the blog post. Amsys will not compensate you in any way whatsoever if you ever happen to suffer a loss/inconvenience/damage because of/while making use of information in this blog.
This feature has been tested using OS X v10.9.2 which was the latest Mac OS release at the time of writing.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |