You might check the /Volumes directory and see if there are any duplicate names or leftover directories due to mistakes.
(I know svn created a duplicate once that left me wondering where my files went)
Could you elaborate on this, please?
Where do I find this?
/Volumes is the directory on your system that contains all the mounted volumes.
Do you know how to use Terminal and the shell? If not, you will probably need to get someone more experienced to help you clean up your system.
Probably a permission issue. Run the Apple Utility disk to fix permissions. If that does not work look at the non-boot drive and check "ignore ownership".. Open the Finder Get Info Window and it is entry at bottom.
Ignore Ownership worked. Thank you!
I saw this suggestion on another Discussion thread but wondered if that could be the problem since the non-boot scratch disks used on other computers here do not have this property chosen.
"Permissions", "Ignore Ownership", and "apply to enclosed items" remain a mystery to me.
As for Terminal, I've had my hand held a couple of times while I went there and it was not a comforting experience.
Our work setup depends on complete access by everybody to everything (Read&Write Privileges apply to everyone here). We occasionally swap drives between computers which may cause problems, but why should it and how am I to know. The computer that prompted this discussion had its main hard drive replaced a couple of months ago which may have contributed to the problem.
Is there a down-side to ignoring ownership on everything and having "read-write" privileges apply to everyone (aside from lax security)?
Not sure about the "ignore ownership" issue. I will give you what I know about the Windows system and figure the same holds for Mac although the steps will be different. You can find a "how to on the web".
If files are created with one computer and put on a hard drive the drive has an ownership "tag". Now if you switch the drive to another computer permission issuses can arise as now the old ownership tag is not the same as the new ownership tag.
The solution is to go into the drive permissions and add the new ownership "tag" and that will give you read and write permissions.
Hope this helps.
I'm having the exact same problems since upgrading to PS CS6. I've changed my scratch disk from the default boot drive to another internal drive. I've reset the 'ignore ownership' option by checking the box and that fixes the errror message that you are getting. But for me the OS is not remembering or saving taht setting. Subsquently each time I reboot I have to go into the Finder and do a 'Get Info' on that drive and check the box again. So I donb't know if this is a bug in OS 10.8.2 or what the problem is.
Since I'm still using 10.6.8, I can't say much about your problem.
Does this happen to all of your drives, internal or external?
Does re-initializing the drive change matters?
I've only done it on internal drives and it happens to any internal drive (three other drives). I've not tried re-initalizing the drive.
1 person found this helpful
I just figured this out, and it's pretty simple--it is permissions.
Select the drive, get info (command-i). A window will open. At the bottom open the "Sharing and Pemissions" tab. You'll find the "Priviledge" set to read only to some of the users. Unlock by clicking on the lock icon and set them to read and write.
Possibly a noob suggestion but it may not be permissions in some cases. It may be that you've upgraded Photoshop and have old version(s) of it on your computer. In this case, deleting the old versions and/or any Library Preferences relating to Photoshop (on Mac, anyway) could fix it.
This seems to have worked with Photoshop CC, after having the problem with both CC and CS6.
1 person found this helpful
In my case it took a fair amount of time to track down but I have a conflict happening. In my photography business I have a business app (SuccessWare) for book keeping and managing my business and the developers for this software require users to use a hardware dongle to use the software. The driver for that dongle is the culprit that is causing my issues. When I remove it my problems will stop reinstall it and the problem returns. I'm now running Mavericks and the problem still exists and the company that develops the dangle driver will not acknowledge that there is a problem.