AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Could not unmount disk4/2/2023 ![]() I'm pretty sure once the file format is set to Journaled that the "sudo chmod o+rw /volumes/Volume_name" will work, but since it only takes a few more seconds for me to set volume permission through macOS I'm just doing it that way. But if I login with a public lab account (which is what is normally logged into my computers) it gives me the error message about being unable to mount.Īm sort of out of ideas at this point, so I'm just going computer by computer, logging in as Admin and erasing the partition. Not only can you encounter this in the Finder, but it can also prevent running First Aid in Disk Utility, which may report that it couldn’t because it was unable to unmount the volume you. If I login to a computer with an Admin account and then have JSS run the policy, it works. Among the rough edges in macOS is that infuriating message you may see when you try to eject or unmount a volume: it failed because the volume is in use. Even though I run the command as sudo, it seems like it runs as the user currently logged in (I tried using the GUI and Disk Utility while logged in as a non-Admin and it did the exact same thing as the script). So I'm ultimately doing this because the file format of a lot of our computers' partitions is Mac OS Extended and I need it to be set to Mac OS Extended (Journaled).ĭid some troubleshooting, it looks like unless the eraseVolume command completes and mounts the drive it doesn't set the file format to Mac OS Extended (Journaled) but instead leaves it as Mac OS Extended (after rebooting when the drive mounts that's what it shows). Use the Activity Meter (Apple Utility) to see what is runnig. You cannot unmount as long as a process is running, that may may be unvisible for you. If for some reason you can't unmount a filesystem before you turn off the. I get why the 2nd command fails (since it didn't mount it can't change permissions), but does anyone know why the first command would repeatedly fail? I've tried flushing the policy so it would try again in case it was just a fluke, but it continually fails at the same spot (re-mounting). You cannot unmount a disk if the OS is running on it. 4.2.5 Disk Buffering, Caching, and Filesystems Linux, like other Unix. Initialized /dev/rdisk0s4 as a 9 GB case-insensitive HFS Plus volume with a 8192k journalĬhmod: /volumes/Volume_name: No such file or directory However, when I create a script and try to run it through JSS, I get this error: #!/bin/sh ![]() If I run these commands separately on terminal on a computer, it works perfectly. Sudo diskutil eraseVolume JHFS+ Volume_name /dev/disk0s4 Everywhere it really is you get that blunders message, let us know what exhibit screen you're in (Partition, Erase, different), WRITE DOWN the precise words shown and record decrease back. ![]() #erase and reformat Volume_name partition Mac How To Unmount Disk Could Not Unmount Disk If not 'Mac OS prolonged (journaled)' format it wisely. I have a simple script that erases a volume and them sets the permissions so that anyone can access the drive: #!/bin/sh ![]()
0 Comments
Read More
Leave a Reply. |