getting a resource busy error

[Kale-Thungs]

:beetle: Description

Describe clearly and concisely what is not working.

When trying to create disk image mist is failing and reporting a resource busy error

:clipboard: Steps to Reproduce

1. Open Mist.app
2. Click on ...
3. Wait for ...
4. Observe error

Mist Log 2024-07-05_20-30-46.log

an error has occurred invalid termination status 1 hdiutil create failed - resource busy

:white_check_mark: Expected Behaviour

Describe what should be happening (ie. the happy path).

Hopefully it would make a disk image and I could move onto making another disk image of another os

:computer: Environment

• Mist version (App menu ⇨ About Mist): VERSION
• macOS Version (sw_vers): VERSION BUILD
• Hardware (system_profiler SPHardwareDataType):
  • Model Identifier: MODEL_IDENTIFIER
  • Chip : CHIP

Version 0.10 (0.10) mac os: 12.7.5 (21H1222) iMac (Retina 5K, 27-inch, Late 2015) 3.2 GHz Quad-Core Intel Core i5 Model Name: iMac Model Identifier: iMac17,1 Processor Name: Quad-Core Intel Core i5 Processor Speed: 3.2 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 6 MB Memory: 16 GB System Firmware Version: 529.120.1.0.0 OS Loader Version: 540.120.3~37 SMC Version (system): 2.33f12

:camera: Screenshots

If applicable, add screenshots to help explain the bug.

not available

:information_source: Additional context

• Is this also a bug in mist-cli? :white_check_mark: / :x:
  • Provide links to GitHub Issues
• Links to 3rd-party tools / references / documentation

[ninxsoft]

@Kale-Thungs does the issue occur after a fresh restart of macOS? Sometimes Disk Utility or hdiutil can get confused, and the simple solution is just to unmount and try again. Restarting macOS is probably the simplest method to guarantee no disks are still mounted.

[Kale-Thungs]

@ninxsoft I have rebooted a number of times and now it seems to just happen over and over again. I’ve done the process on different Mac’s of different macOS versions and types of Mac products, but It still occurs if you use Mist more then like 4 or 5 times after the first install it seems.