Mac OS X: Disk Image mount point changes in a non-obvious way

November 25th at 12:00am

I use owncloud to keep greater control over where my 'cloud' data resides. Everything has been working extremely well, so it came as a surprise this morning to find that the owncloud client was giving me this error:

CSync failed to load the state db

References

 

Troubleshooting

After doing some googling I came to the seemingly obvious conclusion that even though the Disk Image where I keep the OwnCloud data is mounted, the ownCloud client is unable to access the data. Looking on the Desktop I could see the image mounted and could access all the data on the image manually. I dug a little deeper using the CLI find out that the Disk Image had been mounted with a " 1" suffix appended to the end of it (which is pretty weird). Looks like there was an empty folder with the proper name of the Disk Image in the /Volumes directory which was NOT being used as the proper moutn point. Sequentially, what I did looks like this:

  • After a reboot, I can access the disk image data but ownCloud cannot
  • Remounting the disk image and restarting ownCloud client does not solve the problem
  • Opened Terminal.app and examined the /Volumes directory
    • Strangely enough there is both a "/DiskImage" as well as a "/DiskImage 1" directory
    • Looks like the disk image data is available in the " 1" directory (No indication of this in the Finder UI)

 

Solution

To get things working correctly I had to:

  • Stop ownCloud client
  • Unmount the disk image
  • Open /Volumes in the Terminal
  • rm -rf /Volumes/DiskImageName
  • Remount the Disk Image
  • Restart the ownCloud client

 

This was kind of weird, I'm not entirely sure why the Disk Image mounted to a different path.