Can't create disk image with Disk Utility

Question

I just upgraded to OS X Mountain Lion and i can no longer create disk images with Disk Utility in order to store encrypted data.The operation fails and ends with the post :Failed to create disk image, error:hdiutil: create failed - Resource busyI use three Macs with Mountain Lion, and this problem occurs only on one of the three.I check the disk, repair permissions and did a reset of the PRAM. I even did a reinstall of Mountain Lion, without success.But curiously, using a new user account, I was able to create a first disk image. But no one after.

Linc Davis · Answer

Launch the Console application in any of the following ways:☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens. ☞ Open LaunchPad. Click Utilities, then Console in the page that opens.Make sure the title of the Console window is All Messages. If it isn&#x27;t, select All Messages from the SYSTEM LOG QUERIES menu on the left.Click the Clear Display icon in the toolbar. Try the action that you&#x27;re having trouble with again. Post any messages that appear in the Console window – the text, please, not a screenshot.When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.DO NOT INDISCRIMINATELY DUMP THOUSANDS OF LINES FROM THE LOG INTO A MESSAGE. If you do that, I will not respond.Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

klmorin · Answer

2012-09-06 06:10:44,740          Finder[220]          ISGetIconFamilyFromStorage: seed mismatch for 2d12001c, actual seed is c798418c          1   OSServices                          0x00007fff8fc29d20 _ZL26ISGetIconFamilyFromStoragejPP17CIconStorageArrayPj + 140          2   OSServices                          0x00007fff8fc5815b _ISIsStorageOnTheVolume + 23          3   OSServices                          0x00007fff8fc8268a _ISIsAnyOfImageStoragesOnTheVolume + 47          4   LaunchServices                      0x00007fff8d1c01f3 _ZN13CIconRefEntry23DataChangedAfterUnmountEs + 13          5   LaunchServices                      0x00007fff8d1bf388 _ZN13CIconRefArray13UnmountVolumeEs + 82          6   LaunchServices                      0x00007fff8d1c01dc _ZL21MountNotificationHookP15VolumeNoticeBlk + 39          7   CarbonCore                          0x00007fff8fdb68d3 _Z29_FSVolumeNotificationCallbacksPK10__CFStringPKvPv + 282          8   CarbonCore                          0x00007fff8fd82e5e _FSVolumeObserverCallback + 165          9   CoreFoundation                      0x00007fff95314b50 __CFMachPortPerform + 288          10  CoreFoundation                      0x00007fff95314a19 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41          11  CoreFoundation                      0x00007fff95314759 __CFRunLoopDoSource1 + 153          12  CoreFoundation                      0x00007fff953478bf __CFRunLoopRun + 1775          13  CoreFoundation                      0x00007fff95346dd2 CFRunLoopRunSpecific + 290          14  HIToolbox                           0x00007fff914bd774 RunCurrentEventLoopInMode + 209          15  HIToolbox                           0x00007fff914bd512 ReceiveNextEventCommon + 356          16  HIToolbox                           0x00007fff914bd3a3 BlockUntilNextEventMatchingListInMode + 62          17  AppKit                              0x00007fff9663ffa3 _DPSNextEvent + 685          18  AppKit                              0x00007fff9663f862 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128          19  AppKit                              0x00007fff96636c03 -[NSApplication run] + 517          20  AppKit                              0x00007fff965db656 NSApplicationMain + 869          21  Finder                              0x0000000105bb60c6 Finder + 24774          22  libdyld.dylib                       0x00007fff8bd2a7e1 start + 0          23  ???                                 0x0000000000000001 0x0 + 12012-09-06 06:10:44,000          kernel[0]          hfs: Initializing the journal (joffset 0x3000 sz 0x80000)...

Linc Davis · Answer

Are you using Disk Utility or "Espionage?"Tao Effect Forums • View topic - Failed to create disk image - Resource busyThe latter is a third-party system modification. If you have problems with it, either get rid of it (recommended) or get help from the developer.

klmorin · Answer

Indeed, I first identified this issue when testing Espionage.Subsequently I found that the problem was the same with Disk Utility.And strangely, this problem I encountered on one of my three Macs is also found now on a second.

Linc Davis · Answer

Is "Espionage" installed on all these machines?

klmorin · Answer

It was, but i uninstalled.

Linc Davis · Answer

Please read this whole message before doing anything.This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:Be sure your Mac is shut down.Press the power button.Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).*Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, you can’t boot in safe mode.Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.Test while in safe mode. Same problem(s)?After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

klmorin · Answer

I&#x27;ve done my homework, your approach was right.Everything worked normally in safe mode, but back in normal mode the problem was still present.Could be deduced, as you suggested, that the problem was caused by a third-party application that load automatically at startup or login.And, by elimination, I came to discover the culprit: module DrivePulse of Drive Genius.Everything works fine now, a big thank you.

Dana Nau · Answer

Thanks! I ran into the exact same problem today, and disabling DrivePulse has fixed it.