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). 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). 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 #erase and reformat Volume_name partition 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
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |