How to Fix FUSE errors on Mac OSX High Sierra and Mojave.

If your cloud drive does not mount properly on Mac OSX and gives you an error similar to the following image, the most likely reason is the Mac OS increased security protocols that were introduced with High Sierra (10.13). This article also applies to Mojave (10.14).

First, make sure the Mac Client is the highest version that is available for your CentreStack. Mac Client support for the High Sierra OS (OSX 10.13.3) was added back in November of 2017 (with Mac Client version 8.11.39942). If your version is lower than the one released in November, then the solution is to simply update the Mac Client.

The proper way to get the Mac Client that is designed for your CentreStack is to sign in on the web portal, then access the downloads page from the user menu on the top-right of the screen.

If you are getting the error right after the installation of the Mac Client, the FUSE error may go away after a reboot of the computer. Simply reboot the Mac and try to open the Cloud Drive again.

If rebooting doesn't solve the issue, then you should check the System Preferences->Security & Privacy on your Mac. Under the Privacy tab, make sure that anything labeled with the words "Cloud Drive", "Gladinet", and/or "FUSE" are allowed to run without restrictions. FUSE (Filesystem in Userspace) is an open-source software interface that extends the file handling capabilities of the Mac OS, with support for NTFS and many other file systems. The CentreStack Mac Client relies on FUSE to mount the cloud drive among other things.

Some users have also reported FUSE errors while using a Mac through a remote session. This happens because remote session software emulates mouse-clicks/keyboard interactions, and the Mac OS blocks such emulated user-interactions. You need to make sure that the word "Allow" appears next to any items relating to emulation software gestures and remote sessions in the System Preferences->Security & Privacy on your Mac. The names of these entries will vary depending on the software that you are using to do your remote sessions.

Finally, if the FUSE errors persist, please follow the steps below to troubleshoot and collect debugging information. Email us the information along with full-screen screenshots of any errors to ticket@gladinet.com to open a support ticket.

Open the Applications/Utilities/Terminal application and type the following commands:

whoami
(this will let you see the username of the logged in user)

sw_vers
(this will show you the operating system's name, version, and build number)

uname -a
(this will show you the operating system's kernel version)

lsvfs
(this will show you a table of supported file system types)

df -a
(this will show you a table of mounted file systems) 

id
(this will show you the IDs of the local users and groups, as well as ports used by various services)

kextstat | grep osxfuse
(this will show you if OSX Fuse is loaded)

sudo kextload /Library/Filesystems/osxcore.fs/Contents/Extensions/10.13/osxcore.kext
(optional - if after issuing the kextstat command you don't see any output, run the sudo kextload command above)

sudo kextunload -b com.gladinet.osxfuse.filesystems.osxgluefs
(optional - if the kextload command runs without issues, run the kextunload command above)

sudo sysctl vfs.generic.osxcore.tunables.admin_group
(optional - if after issuing the kextstat command you see an output that contains "com.gladinet.osxfuse.filesystems.osxgluefs (3.8.0)", run the sudo sysctl command above)

sudo kextunload -b com.gladinet.osxfuse.filesystems.osxgluefs
(optional - if after issuing the kextstat command you see an output that contains "com.gladinet.osxfuse.filesystem.osxgluefs", run the sudo kextunload command above)

After this set of commands, the problem should be fixed. If, howerver, OSX Fuse is still not working, please do the following.

On the Terminal window where you ran the commands above, hit Command+a and then Command+c on your keyboard. Open a Simpletext document and hit Command+v. Save the document as terminal.txt to your desktop.

Now open the Application/Utilities/Console. From the Console's Action menu, enable "Include Info Messages" and "include Debug Messages".

With the Console app still open, invoke the cloud drive from the Terminal. The following Terminal command will start the cloud drive and output debugging trace information to a text file:

/Applications/Gladinet Cloud Mac Client.app/Contents/MacOS>./Gladinet\ Cloud\ Mac\ Client > ~/drivelog.txt 2>&1

Debugging information will also appear in the Console/system.log. Please apply a filter for "osxfuse" on the top-right portion of the Console app. Once you can see the hour and minute when the first entry occurs, change the filter to a timestamp (example: "10:03"). The final, filtered system.log will contain the system activity for the minute when the OSX Fuse mounting occurred. Copy the text into a Simpletext document and save it to your desktop as systemlog.txt.

Send an email to ticket@gladinet.com with a descriptive subject/body and the following attachments that resulted from the steps above:

1-terminal.txt
2-drivelog.txt
3-systemlog.txt