Mac Os X Unable To Unmount Volume For Repair
DU First Aid on internal user folder drive: Unable to unmount volume for repair Discussion in ' OS X El Capitan (10.11) ' started by pullman, Dec 29, 2015. Most Liked Posts. 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. 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.
Regarding reverse enginnering, it is a fellony if it causes financial or moral damage to the copyright owners of the software involved AFAIK. You will find different threads in this forum related to ways and tools allowing to use newer versions of OSX in still nicely working old mac computers which unfortunately are not able to do it natively because of wrong decisions Apple took in the past and made them in this way obsolete. Apple is no exception to the rule that everyone can make errors. There are much more enginnering changes involved in those tools than there might be in simply using the DU of Yosemite or of Mavericks in El Capitan. Since all those developers do their work for free and without any intention to infringe the copyrights of Apple (or any other company) in order to make money on behalf of the original software creators through their work, they can safely publish their results in this forum and they actually do it! Not everything not intended by Apple (or any other computer company) is in its nature illegal, must be strictly avoided by the computer users and should be punished by the law. What many people ( including Apple's decision makers) lack is the simple and basic common sense, which seems to be much less 'common' than the word implies.
Any OS X boot drive is needed to complete the task. But, the important point to remember is that the installer or the recovery drive must reside in the drive, separate from the primary boot disk with the installed OS on it. The following steps can do the fixing: • • The USB boot drive is attached to the Mac, and the system is rebooted • The OPTION key is held during the booting and then the attached boot drive is selected • Disk Utility is accessed through the Boot menu.
You can download the macOS® Sierra® installer by using the link below: macOS® Sierra® 10.12.5: You can also use App Store directly for downloading it. The “Install macOS® Sierra.app” will be saved to the following path once downloaded: /Applications/ Creating bootable USB Disk for macOS®: Plug in a USB flash drive (8Gb or larger) and launch disk utility to format the flash drive. To create a bootable USB drive for macOS®, everything must be exactly as shown in the picture below. Once you successfully formatted the flash drive, open Terminal from /Applications/Utilities: Copy and paste the following command into terminal without the “”: For macOS® Sierra®: “sudo /Applications/Install macOS Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install macOS Sierra.app —nointeraction” Press return/enter to run the command. You’ll be asked to give your password and once you type your password press return/enter and the process will start. Depending on the speed of the USB drive you are using it will take about 5 to 30 minutes to complete the process.
(3) Fixing With the Recovery Partition The above error may also be triggered due to first Aid or while formatting a non-boot partition. In this case, a resolution of the problem occurs with the Recovery Partition, which comes with all the newer versions of the Mac OS X.
I know as you do that the command line still has possibilities taken away from the present DU but users were not asked if they wanted to give them up in DU and just leave them in the command line. After all every software is made to assist and bring results to their users and not for its own sake or for simple enjoyment of the programmers. In other threads you will find countless users who regretted the crippled present DU and found that the 'stupid' one was the Apple developping team who took the decision to cripple it.
However, this is not applicable for the modification of the boot disk with the help of partitions or formatting. Then the resolution lies in the previous method.
Purchased new HD and it initially recognized disk when formatting. Error came up, can’t unmount disk.
Click to expand.Hmm, I had the same problem. Try the following. Backup as much as possible. Both Windows and Mac. Boot Mac, I assume you already downloaded macOS Sierra, so, go to mac partition and delete the macOS Sierra Install files. They're probably there, so just delete them.
I let it run overnight for a 60GB drive. DW will let you set up a logical disk on the desktop to inspect the recovered files before toasting the bad drive. You should see the entire folder structure, except the possibility of a few corrupted files. If you don't like the way it looks, abort and try again. Of course you need a drive as large as the files you want to recover, since it ddoesn't do any compression.
Now I tried again a few times and the programmes took forever to start up but now disk utility opens after about 30 mins and can see the drive, but it's lost it's name and I can't even repair or repair disk permisssions. Drive Genius can see it but not repair and same for Disk Warrior, the 'rebuild' tool is greyed out.
Thank you very much for the suggestion. I did run that after I posted last night. Unfortunately I am now at work so I don't have access to the info. I remember there were a few 'crashes' listed at the end. Some of them involved the driver for my rather old Wacom Pen and Touch tablet. I am using the latest driver (5.3.6.6 I think), which supposedly works with El Cap but perhaps it isn't fully compatible. There were also other crashes listed but I don't remember them now unfortunately.
Could not unmount disk. In some rare situations, your computer might not respond for several seconds. If you cannot determine which files are open on the disk that you want to verify or repair, restart your computer and then mount the disk again, or start up from your Mac OS X Install DVD or CD to repair. You may notice some 'Incorrect size for file temp number' alerts when you attempt to verify or repair a volume using Disk Utility or with the '-l' option. You can safely ignore these alerts for any 'temp number' files. For example, you might see something like this: Verifying volume 'Macintosh HD' Checking Extents Overflow file. Checking Catalog file.
Does anyone have an idea of what other causes there could be for these errors? I'd be very grateful for any assistance as this is my main machine. Thanks kindly in advance, Philip. Thank you very much for the suggestion. I did run that after I posted last night. Unfortunately I am now at work so I don't have access to the info.
I have rebooted a few times, and spent days running everything from TechTool Pro on it and it won't go. $ diskutil list disk2 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *4.0 TB disk2 1: EFI EFI 314.6 MB disk2s1 2: Apple_HFS Everest 4.0 TB disk2s2 $ diskutil repairVolume /dev/disk2s2 Started file system repair on disk2s2 Everest Updating boot support partitions for the volume as required Error: -69673: Unable to unmount volume for repair $ diskutil eraseDisk JHFS+ Everest /dev/disk2 Started erase on disk2 Unmounting disk Error: -69888: Couldn't unmount disk Any thoughts on how to get it to unmount and reformatted? Is there a way in Terminal to do this instead? When a disk is first connected, macOS helpfully tries to run fsck on the volume.
Summary The user often experiences a problem, while handling some of the Macs, when they are not allowed to repair permissions or directory in Disk Utility. They are unable to erase or partition the drive. Even the Network deployment tools like Apple’s Netinstall service or the DeployStudio fails, on account of this error.
Use your external media to boot your computer after Restore is completed successfully. Note: Create Bootable DMG option is available for boot volume only. Do not stop the image creation process in the middle. It may corrupt your hard disk. I use MacBook Pro Mid 2012, 750GB HDD.
It could have been due to that, although MSR partition is also known to cause problems in some situations. The partition structure was as follow: - ESP = EFI Partition - MSR = Microsoft Reserved (culprit, too?) - Win10 = Windows drive - Sierra = New partition created for Sierra - Macintosh HD = El Capitan drive (already installed and working) - RecoveryHD = El Capitan recovery drive. Solution: Use the 'Restore BaseSystem.dmg' method. It's the vanilla way and it doesn't divide into two parts.
When I went to eject the SSD after resetting the boot drive to the MacBook internal SSD(I rebooted after doing this) I got message saying the drive could not be ejected because some applications may be using it. I am assuming that as soon as I plug this SSD in some background process starts up and starts using it for some reason but have no idea what it is. I am using a 500GB Samsung T5 by the way. Hoping someone can help out with a suggestion as I expected this to go much smoother like my MacBook Pro upgrade went lol. I have the same problem.
I hope someone finds a solution soon. I finally managed to update to High Siera. After trying many different methods to unmount the internal drive, this is what finally worked - *Make sure you have a Time Machine Backup before doing this!
Recently i bought it from my friend. It had OS X Mountain Lion installed.
I have two internal drives in my 27' iMac (10.8.5). An SSD system disk and a 1TB SATA drive. The HDD has been acting up recently, very slow performance, bad behavior etc.
All windows started opening themselves and I had to shut down my MacBook by the power button. Mar 14, 2012 Lately, my MacBook Pro (mid 2010) started to slow down even with over 60% disk space is empty and max RAM is installed.
I have two internal drives in my 27' iMac (10.8.5). An SSD system disk and a 1TB SATA drive. The HDD has been acting up recently, very slow performance, bad behavior etc. Tech Tool Pro and Disk Utility don't seem to be able to fix the drive, so I decided to wipe the data by a reformat and writing zeros to the entire drive. Everytime I try and format, it tells me that the drive cannot be unmounted.
Type “diskutil list” and press return/enter You’ll see list of all the Internal and the external hard drives Type “diskutil mount /dev/diskXsX” and press return/enter First X is the number of the disk and the second X is the number of the partition In this case the command will be: e.g. Diskutil mount /dev/disk2s1 Now you can see the EFI partition of disk6 is mounted on the desktop, if you can’t see the partition on the desktop you can find it in finder window’s “Sidebar” under “Devices” BIOS Settings: Now it’s time to configure the BIOS before installing macOS®. First of all, it’s better to “Load Optimized Defaults” settings on the BIOS so we could start from scratch without having any misconfigurations.
It's a recovery tool, not a backup. I don't know if youi can use the logical partition on the same drive. I'd see if DW has any info on this, but not take the chance it it doesn't.
Also perform a permissions repair if required. • Attempt again to perform whichever task caused your ‘Couldn’t Unmount Disk’ error. (For example to Erase/Partition the disk). 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). Download snailsvn free. At the unix prompt enter: diskutil list Press RETURN.
Otherwise, we follow the steps: • The Mac is rebooted, with the OPTION key being held down and the Recovery Partition is chosen • The Disk Utility is chosen from the Boot Menu • Verification and repairing the disk is done with the “First Aid.” or • “ Erase” is used for the disk formatting This will not work with the disk that is throwing the error is the same as the primary boot partition. The solution lies only in using a separate USB drive for fixing the error. Resolving Unmounting External USB Drive on Mac. To resize the Mac startup disk, you need to create bootable DVD.
Now I believe that I have made as far as possible my case clear and see no sense to argue any longer with you. That was it as far as I am concerned. I do not agree with your opinion KALLT that is it 'stupid' to use the previous DU in El Capitan and I am not alone in deploring the way it was crippled. I know as you do that the command line still has possibilities taken away from the present DU but users were not asked if they wanted to give them up in DU and just leave them in the command line. After all every software is made to assist and bring results to their users and not for its own sake or for simple enjoyment of the programmers.
Mac Os X Unable To Unmount Volume For Repair
I can see the HD but cannot repair it. When I connect using target mode with my mac book pro, the hard drive does not appear on my host (macbook pro) computer. I have reloaded OS X (Leopard) onto a firewire external drive and can boot my imac that way but I can not find my original internal Macintosh HD.
Cannot Unmount Disk
• If you see any 'Incorrect size for file temp' alerts, you can safely ignore them. Disk Utility may stop responding without displaying an error message, or stall your computer for several seconds, when trying to verify or repair some non-startup volumes that can't be unmounted. If you try to verify a volume that is not your startup disk but for some reason Disk Utility can't unmount the volume (for example, the disk may have open files), the verification will appear to start but then stop without displaying any alert message. If you look in the Console (/Applications/Utilities/), you will see an entry like this: Verifying volume “Storage” The disk “Storage” could not be unmounted Could not unmount disk for verification, attempting live verify If you try to repair a disk that cannot be unmounted, the repair will appear to start, but then stop as Disk Utility displays this message: 'Repairing disk failed with error. Could not unmount disk.' If you look in the Console (/Applications/Utilities/), you will see an entry like this: Verify and Repair disk 'Storage.'
I then went into OSX Recovery, started repairing Macintosh HD, but the error message saying 'Disk Utility can't repair Macintosh HD' came up and now I don't now what to do. Is there any way I can back up my files in this situation? Is there any way I can repair the disk without having to erase all data and reinstalling OSX? Or do I really need to bring it to a Apple Store for repair? Info: MacBook Pro, OS X Mavericks (10.9.4) Aug 22, 2014 Is it possible to reformat a single partition of a disk w/o reformatting the entire disk?Or must one reformat the entire disk? In DU, If I click on the volume/partition in question, I do NOT get the tab “Partition.” If I click on the disk, not just the volume/partition in question, then I do get the tab “Partition.” Also, does using DU to secure erase a volume by overwriting with 0s, cause a format issue? Some details on my other post:Create a bootable clone using Disk Utility Info: iMac, OS X Mavericks (10.9.4), 4 GB RAM, Win XP Pro-Boot Camp Apr 11, 2010 I am considering purchasing diskwarrior but want to make sure it can help my situation before I purchase it. My imac will not boot from the internal hard drive (Intel processor) When I use disk utility to try and repair the disk, I get error messages and it won't repair.
I really can’t afford to pay someone $300 when I’m this close!
Kurt Jefferson wants El Capitan to let his drives go! Sometimes the drive won’t unmount no matter what, and I get the dreaded “The disk wasn’t ejected because one or more programs may be using it” or “The volume cannot be ejected because it’s currently in use” messages. He’s had this happen routinely with a Mac mini using flash drives and external hard disk drives (HDDs).
It took about 5 minutes on my computer to create the bootable disk on a USB 3.0 flash drive. How to mount the EFI partition using command line: Launch the terminal application again if you closed it previously.
Error: The underlying task reported failure on exit 1 HFS volume checked Volume needs repair If this happens, use in single user mode, or start up your computer from a different volume before verifying or repairing. Advanced: This issue can happen because the on-disk size for truncated open-unlinked files doesn't get updated before you start a live verification. The presence of these files doesn't cause an issue because their in-memory size is correct. These files are deleted as soon as they are closed. If your computer does not shut down normally, they will be deleted during the next startup.
If you have not made a backup STOP HERE! And create one. I will not be held responsible for any data loss or any damage you might cause to your computer in the process of installing macOS® on your computer.
It gets slow when using hungry programs such as Photoshop CS5. I used the disk utility first aid and fixed all permissions that were shown with errors. When scanning the disk, I received the message that my disk is corrupt and I need to fix by restarting with command+R keys pressed until the apple symbol is displayed.
Tried every single thing above. Looks like it starts erasing, but then quits and says at least one volume could not be unmounted. Tried to force unmount to no avail. Any idea what else I can do?
It's a 500GB drive and only has 3GB spare on it, it has loads and loasds of stuff on there, work, music, films, all my preferences, passwords and of course all my software - I do have a backup of some stuff, my photos luckily enough - but I still need to get it fixed. Now what can I do? Is there anything in terminal I can do? Any other ideas anyone? I'm desperate for help.I have downloaded Data Rescue II and it has been gathering device information for an hour, I'm hoping it will carry on and later on I can start recovering.
I had the same problem, I fixed mine by creating the installation USB different way. The problem I believe was due to the createinstallmedia tool. If the USB is in fact created with that tool, the installer divides the installation process into two. First, it copies the installation files to the HDD partition (that part creates problem), and then it reboots from that partition to install the files and eventually create the Recovery partition. The problem is that it for some reasons tries to unmount the partition it has booted from, which is obviously not possible; hence, it fails. The root problem probably has much to do with the partitions structure. In my case, I used MiniTools Partition Manager to migrate my Windows installation from my HDD to the new SSD drive.