![mac at least one volume could not be unmounted mac at least one volume could not be unmounted](https://i.stack.imgur.com/PMnrw.png)
New access icons would be created on new plug events (although there would need to be some UI to detect the contents of unsensed optical drives: perhaps just a generic link in Places). devices where the user *intentionally* doesn't want to see it. It could also apply to sensed USB/MMC/etc. This could apply to network connection or unsensed optical media links where the user no longer has a need for immediate access (although there may be leftover links in Places to allow easy restoration of removed access icons). If access is unavailable to a resource when the user attempts to use it, the user could be presented with some dialog that could help resolve it (Please insert the disc "foo" (OK retries, Cancel stops the access attempt)) or (Please check your network connect tio resource "bar" (same options)).Īt that point, it perhaps becomes interesting to have a means to remove access icons for mitigated access, which should be amenable to discoverable text (e.g. This works less well for optical drives without hardware sense, and doesn't work at all for network resources, but should cover other cases (USB, firewire, MMC, etc.). The next trick is determining when to present the user with a means to start navigating to known paths, which might involve the creation of an access icon on hardware detection, left present until hardware detection of removal. An example of such mitigation would be ltspfs (although that also involves network mounting), although this doesn't currently have any means of notifying the user during the short periods it is unsafe to remove the device and carries some performance penalties. Perhaps rather than having an explicit unmount/eject feature, the UI should inform the user during the times that it is unsafe to remove the device, and allow/encourage unsupervised removal at all other times. The trick with just removing media without warning the system is the data write cache, such that users randomly pulling a USB drive without unmounting may well have not fully flushed all the writes (the "Not safe to remove" bit). Simply dropping the "unmount" functionality in favour of an "eject" function is an overly simplistic solution. While all of these represent less common use cases, I believe it ought be possible to construct an interface that permits the user to unmount volumes with the default tools used to display those volumes, yet still provide discoverability to users who simply want to remove the removable media. "unmounting" an encrypted loopback file when allowing someone else to use your maching)ĭ) Wishing to disconnect from some network store with foreknowledge that it will become unavailable (e.g.
![mac at least one volume could not be unmounted mac at least one volume could not be unmounted](https://www.igeeksblog.com/wp-content/uploads/2021/03/click-on-data-in-under-internal-in-disk-utility-on-mac.jpg)
setting up an encrypted partition on a USB key)Ĭ) Wishing to temporarily make some information inaccessible to the system until remounted (e.g.
MAC AT LEAST ONE VOLUME COULD NOT BE UNMOUNTED ISO
writing the newest Ubuntu ISO to a rewritable disk that may have contained previous data).ī) Wishing to perform various manipulations on media that cannot be done with a live mount (e.g.
![mac at least one volume could not be unmounted mac at least one volume could not be unmounted](https://2.bp.blogspot.com/-cn5-vkgQAcw/Tc13F33j5wI/AAAAAAAABUU/OBl6pSZVfgI/s400/khayree.jpeg)
Some examples might include:Ī) Wishing to overwrite rewritable media from some image (e.g. While I'm not that concerned about wording, I do feel there is a use case for unmounting without removing.