Skip to content

Instantly share code, notes, and snippets.

@alienth
Last active August 29, 2015 14:21
Show Gist options
  • Save alienth/72e52f8dc4177c383b12 to your computer and use it in GitHub Desktop.
Save alienth/72e52f8dc4177c383b12 to your computer and use it in GitHub Desktop.
DSM 5.2-5565 Update 1 issue: no disk sleeping or hibernation

The reason your diskstation may stop sleeping after this update is due to the 'winbindd' service continually touching a file (/usr/syno/etc/private/winbind_domain_list) which is hosted on disk. The continual touching of the file results in the disks being unable to sleep.

An issue which this update fixed is related to this service, so I suspect it was unintentionally introduced to fix a separate issue (specifically regarding RW access of Guest users).

To get your diskstation sleeping again, you simply have to stop the winbindd service. You can do this via the simple command "stop winbindd" via command line. Note that disabling that service will likely reintroduce the Guest RW issue which was fixed in this update.

Note that this service will automatically restart when your diskstation reboots. The permanent fix will need to come from Synology.

As a side note, you can use the following command line to hunt for any files modified within the last 30 minutes on your diskstation. This is what I used to find the above issue:

find / -path /dev -prune -o -path /proc -prune -o -path /run -prune -o -path /tmp -prune -o -mmin -30 -print

(The 'prune' flags will exclude paths which aren't hosted off of disk, such as /proc and /run)

@DeanTaplin
Copy link

You also need to run that stop command logged on as the root user

@schnatterer
Copy link

Hi guys,
thanks that worked for me in Update 1.

I Just installed 5.2-5565 Update 2 that announces Fixed an issue where system cannot enter hibernation. Let's see if they did as promised 😄

@Missingdatabit
Copy link

Still after the latest update my synology doesn't hibernate. I have just contacted them today to ask for an explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment