How to Fix FUSE errors on Mac OSX High Sierra

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 High Sierra's increased security protocols.

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. 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 High Sierra 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.

Finally, if the FUSE errors persist, please following these steps to troubleshoot and collect the traces and email traces along with full-screen screenshots of the errors to support@gladinet.com to open a support ticket.

Steps: (please save the output of each steps and send to support)

0. see who is the user
whoami

1.  get os x version

sw_vers

2. get os x kernel version

uname -a

3. get a list of file system types

lsvfs

4.get a list of mounted file systems

df -a


5. check if osxfuse is loaded

 kextstat | grep osxfuse

6. get the current user's id and group id

id

7. if in command 5, you see output such as com.gladinet.osxfuse.filesystems.osxgluefs (3.8.0), please issue this command:

sudo sysctl vfs.generic.osxcore.tunables.admin_group

8. If in the command 5, you see output for com.gladinet.osxfuse.filesystem.osxgluefs, do the following command

sudo kextunload -b com.gladinet.osxfuse.filesystems.osxgluefs

In step 8, after step 8 does it solve the problem?

7a: If in command 5, if you don't see any output , please issue this command

sudo kextload /Library/Filesystems/osxcore.fs/Contents/Extensions/10.13/osxcore.kext

if you are in step 7a, and the command runs fine without problem, go to step 8 to unload it, and after that, does it solve the problem?


9. Now open the Application-> Utilities->Console app, and go to the Action menu, enable "Include Info Message" and "include Debug Messages",

while the console app is still open, 
Now let's run the cloud drive from terminal and the trace is log to the clouddrive_log.txt file, could you send us the trace file
/Applications/Gladinet Cloud Mac Client.app/Contents/MacOS>./Gladinet\ Cloud\ Mac\ Client > ~/clouddrive_log.txt 2>&1

10. You will see traces in the Console application as well (system log), please first filter to "osxfuse" and you will see a bunch of traces, and keep a note on the time stamp, such as 10:03, now change the filter from osxfuse to "10:03" or whatever the timestamp is so we will get all the traces related to the second/minute when the drive is mounting. please send us the console trace as well.