Synology DS1511+ fan error: how to disable warning

My old Synology DS1511+ has a failed fan. It gave warnings in the form of beeps and in the logs, which it is supposed to do.

To be honest, I found someone who already had done what I wanted, so I just modified it slightly to work for DS1511+.

What we are going to do:

  1. Enable SSH and connect to our Synology box.
  2. Locate any files named “fan” something.
  3. Use the Editor VI to create a Shell Script to disable the “check_fan” function after each reboot.
    Info: basic VI commands and Vi commands on Synology wiki. We are only going to use the [ESC] key, and the command “:wq!” to exit and save from vi.

Steps to make this Work:

  1. First turn on SSH in Control Panel |Terminal

  2. Connect to your Synology box using a program like Putty where username is “root” and password is the same you use for “admin“.
  3. Locate the file we need to modify in order to disable the fan check.
    Note: if you cant find the file, navigate to sys dir first using cd /sys/

    find -name "*fan*"
    Results in:
  4. Create a Shell script by navigating to the location containing the scripts. Creating a new script file and modify the permissions for the file (do this with sudo):
    cd /usr/syno/etc.defaults/rc.sysv/
    echo 0 > /sys/module/pineview_synobios/parameters/check_fan
    :x [Enter]
    chmod +x
  5. That’s it. Reboot your NAS and now you don’t have to modify the file after each reboot.

Synology Cloud Station and the pesky TailCharacterConflict error

At my (previous) company we’re using Synology Cloud Station with 20 users and lots of files. One user was complaining that the folder names were renamed with this nice addition:

Company Name B.V._PC_Name_UserName_Jan-27-145750-2015_TailCharacterConflict

Everything I tried didn’t help: renaming the folder, deleting it from the server, resyncing, everything. Google wasn’t a big help either. The folder kept being renamed with this very irritating TailCharacterConflict.

Until I saw the pattern.

You CAN’T let you folder name end with a trailing PERIOD. In this case, the folder name was Company Name B.V.

Changing the folder name to Company Name BV (with the periods) solved the problem. Insane, but true!