Skip to content

Instantly share code, notes, and snippets.

@alienth

alienth/gist:72e52f8dc4177c383b12

Last active August 29, 2015 14:21
Download ZIP

Revisions

  1. alienth revised this gist May 27, 2015. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -2,7 +2,7 @@ The reason your diskstation may stop sleeping after this update is due to the 'w

    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 from running. 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.
    **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.

  2. alienth revised this gist May 26, 2015. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -6,7 +6,7 @@ An issue which this update fixed is related to this service, so I suspect it was

    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 20 minutes on your diskstation:
    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`

  3. alienth revised this gist May 26, 2015. 1 changed file with 8 additions and 2 deletions.
    10 changes: 8 additions & 2 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,7 +1,13 @@
    The reason your diskstation may stop sleeping after this update is due to the 'winbindd' service continually touching a file which is hosted on disk. The continual touching of the file results in the disks being unable to sleep.
    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 from running. 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.
    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 20 minutes on your diskstation:

    `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)
  4. alienth revised this gist May 26, 2015. 1 changed file with 3 additions and 1 deletion.
    4 changes: 3 additions & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -2,4 +2,6 @@ The reason your diskstation may stop sleeping after this update is due to the 'w

    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 from running. 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.
    **To get your diskstation sleeping again**, you simply have to stop the winbindd service from running. 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.
  5. alienth revised this gist May 26, 2015. No changes.
  6. alienth created this gist May 26, 2015.
    5 changes: 5 additions & 0 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,5 @@
    The reason your diskstation may stop sleeping after this update is due to the 'winbindd' service continually touching a file 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 from running. 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.