Jump to content
XPEnology Community

HDD fail to hibernate after upgrade from 6.2.2 to 6.2.3


e-ghost

Recommended Posts

Hi,

 

I am new to this.  May I know how do I know if I have extra.lzma?  Can anyone guide me on how to edit /etc.defaults/syslog-ng/patterndb.d/scemd.conf?  What are the command to edit it and how do I save it?  Also how can I backup a copy of scemd.conf?  Thank you,

Edited by hostet
Link to comment
Share on other sites

On 10/15/2020 at 12:12 PM, vasiliy_gr said:

Simple and dirty fix based on written above. Modified /etc.defaults/syslog-ng/patterndb.d/scemd.conf:

 



filter f_scemd { program(scemd);  };
filter f_scemd_sev { level(err..emerg) };
# destination d_scemd { file("/var/log/scemd.log"); };
destination d_scemd { file("/dev/null"); };
log { source(src); filter(f_scemd); filter(f_scemd_sev); destination(d_scemd); };

 

Edit file and reboot. Result - HDD hybernation works fine now...

 

My config: DS3617xs, DSM 6.2.3-25426-U2, extra.lzma v0.11.2_test.

 

Hi, I cannot get my HDD hibernated. May I confirm with you that the only change to the system is to amend the 3rd line of that file? (as you commented the orginal 3rd line with # then added a new line to point the logs to /dev/null?)

 

My config: DS3615xs, DSM 6.2.3-25426-U2 & U3, extra.lzma v0.11_test.

 

I have amended that line and reboot. U see the /var/log/scemd.log is keep on growing. The HDDs are not willing to sleep at all. Keep spinning.... :-(

Thank you in advance!

Edited by e-ghost
Link to comment
Share on other sites

10 minutes ago, e-ghost said:

 

Hi, I cannot get my HDD hibernated. May I confirm with you that the only change to the system is to amend the 3rd line of that file? (as you commented the orginal 3rd line with # then added a new line to point the logs to /dev/null?)

 

My config: DS3615xs, DSM 6.2.3-25426-U2 & U3, extra.lzma v0.11_test.

 

I have amended that line and reboot. U see the /var/log/scemd.log is keep on growing. The HDDs are not willing to sleep at all. Keep spinning.... :-(

Thank you in advance!

 

Yes - you only need to redirect your scemd messages to /dev/null. If your log file keeps growing after that - you missed something... As it should not.

Link to comment
Share on other sites

21 hours ago, vasiliy_gr said:

 

Yes - you only need to redirect your scemd messages to /dev/null. If your log file keeps growing after that - you missed something... As it should not.

 

Can you help to take a look what I did wrong? I already fully copied your file to replace my /etc.defaults/syslog-ng/patterndb.d/scemd.conf. After rebooted, the /etc/syslog-ng/patterndb.d/scemd.conf is the same as it. However, I see the /var/log/scemd.log is still keep on growing 8-lines per minute:
 

2020-12-27T02:10:49+08:00 fevernas03 scemd: SYSTEM:     Last message 'polling_fan_speed_rp' repeated 1 times, suppressed by syslog-ng on fevernas03
2020-12-27T02:10:49+08:00 fevernas03 scemd: polling_sys_thermal.c:35 ioctl device failed
2020-12-27T02:10:49+08:00 fevernas03 scemd: polling_sys_thermal.c:35 ioctl device failed
2020-12-27T02:10:49+08:00 fevernas03 scemd: SYSTEM:     Last message 'polling_sys_thermal.' repeated 1 times, suppressed by syslog-ng on fevernas03
2020-12-27T02:10:49+08:00 fevernas03 scemd: polling_sys_voltage.c:35 ioctl device failed
2020-12-27T02:10:49+08:00 fevernas03 scemd: polling_sys_voltage.c:35 ioctl device failed
2020-12-27T02:10:49+08:00 fevernas03 scemd: SYSTEM:     Last message 'polling_sys_voltage.' repeated 1 times, suppressed by syslog-ng on fevernas03
2020-12-27T02:10:49+08:00 fevernas03 scemd: polling_fan_speed_rpm.c:35 ioctl device failed
2020-12-27T02:10:49+08:00 fevernas03 scemd: polling_fan_speed_rpm.c:35 ioctl device failed

 

Is there any other factor that I can re-check? Thanks a lot!

 

Link to comment
Share on other sites

4 hours ago, e-ghost said:

Is there any other factor that I can re-check? Thanks a lot!

 

Check access rights and ownership:

root@XPEnologyX:~# ls -l /etc.defaults/syslog-ng/patterndb.d/scemd.conf
-rw-r--r-- 1 root root 260 Oct 15 04:22 /etc.defaults/syslog-ng/patterndb.d/scemd.conf

 

Recheck again the contents:

root@XPEnologyX:~# cat /etc.defaults/syslog-ng/patterndb.d/scemd.conf
filter f_scemd { program(scemd);  };
filter f_scemd_sev { level(err..emerg) };
# destination d_scemd { file("/var/log/scemd.log"); };
destination d_scemd { file("/dev/null"); };
log { source(src); filter(f_scemd); filter(f_scemd_sev); destination(d_scemd); };

 

Link to comment
Share on other sites

9 hours ago, vasiliy_gr said:

 

Check access rights and ownership:


root@XPEnologyX:~# ls -l /etc.defaults/syslog-ng/patterndb.d/scemd.conf
-rw-r--r-- 1 root root 260 Oct 15 04:22 /etc.defaults/syslog-ng/patterndb.d/scemd.conf

 

Recheck again the contents:


root@XPEnologyX:~# cat /etc.defaults/syslog-ng/patterndb.d/scemd.conf
filter f_scemd { program(scemd);  };
filter f_scemd_sev { level(err..emerg) };
# destination d_scemd { file("/var/log/scemd.log"); };
destination d_scemd { file("/dev/null"); };
log { source(src); filter(f_scemd); filter(f_scemd_sev); destination(d_scemd); };

 

Thanks a lot! I got these:

 

bash-4.3# ls -l /etc.defaults/syslog-ng/patterndb.d/scemd.conf
-rw-r--r-- 1 root root 261 Dec 27 01:46 /etc.defaults/syslog-ng/patterndb.d/scemd.conf

 

bash-4.3# cat /etc.defaults/syslog-ng/patterndb.d/scemd.conf
filter f_scemd { program(scemd);  };
filter f_scemd_sev { level(err..emerg) };
# destination d_scemd { file("/var/log/scemd.log"); };
destination d_scemd { file("/dev/null"); };
log { source(src); filter(f_scemd); filter(f_scemd_sev); destination(d_scemd); };

 

bash-4.3# ls -l /etc/syslog-ng/patterndb.d/scemd.conf
-rw-r--r-- 1 system log 261 Dec 27 16:33 /etc/syslog-ng/patterndb.d/scemd.conf

Seems the file content and permission are the same as your, but it just unable to point the logs to null device. Really strange.... Not sure where did the system pick up the scemd log settings from....
 

Link to comment
Share on other sites

11 minutes ago, e-ghost said:

Seems the file content and permission are the same as your, but it just unable to point the logs to null device. Really strange.... Not sure where did the system pick up the scemd log settings from....

My scemd.log:

root@XPEnologyX:~# cat /var/log/scemd.log | tail -10
2020-10-15T03:54:36+03:00 XPEnologyX scemd: polling_fan_speed_rpm.c:35 ioctl device failed
2020-10-15T03:55:36+03:00 XPEnologyX scemd: polling_sys_thermal.c:35 ioctl device failed
2020-10-15T03:55:36+03:00 XPEnologyX scemd: polling_sys_voltage.c:35 ioctl device failed
2020-10-15T03:55:36+03:00 XPEnologyX scemd: polling_fan_speed_rpm.c:35 ioctl device failed
2020-10-15T03:55:40+03:00 XPEnologyX scemd: manage_services.c:464 hw polling thread exit
2020-10-15T03:55:41+03:00 XPEnologyX scemd: manage_services.c:464 scemd connector thread exit
2020-10-15T03:55:43+03:00 XPEnologyX scemd: manage_services.c:464 led ctrl thread exit
2020-10-15T03:55:43+03:00 XPEnologyX scemd: manage_services.c:464 disk led ctrl thread exit
2020-10-15T03:55:43+03:00 XPEnologyX scemd: event_handler.c:318 event handler claimed
2020-10-15T03:55:43+03:00 XPEnologyX scemd: scemd.c:327 ************************SCEMD End**************************

I have no idea what is the problem with your setup...

Link to comment
Share on other sites

1 hour ago, vasiliy_gr said:

My scemd.log:


root@XPEnologyX:~# cat /var/log/scemd.log | tail -10
2020-10-15T03:54:36+03:00 XPEnologyX scemd: polling_fan_speed_rpm.c:35 ioctl device failed
2020-10-15T03:55:36+03:00 XPEnologyX scemd: polling_sys_thermal.c:35 ioctl device failed
2020-10-15T03:55:36+03:00 XPEnologyX scemd: polling_sys_voltage.c:35 ioctl device failed
2020-10-15T03:55:36+03:00 XPEnologyX scemd: polling_fan_speed_rpm.c:35 ioctl device failed
2020-10-15T03:55:40+03:00 XPEnologyX scemd: manage_services.c:464 hw polling thread exit
2020-10-15T03:55:41+03:00 XPEnologyX scemd: manage_services.c:464 scemd connector thread exit
2020-10-15T03:55:43+03:00 XPEnologyX scemd: manage_services.c:464 led ctrl thread exit
2020-10-15T03:55:43+03:00 XPEnologyX scemd: manage_services.c:464 disk led ctrl thread exit
2020-10-15T03:55:43+03:00 XPEnologyX scemd: event_handler.c:318 event handler claimed
2020-10-15T03:55:43+03:00 XPEnologyX scemd: scemd.c:327 ************************SCEMD End**************************

I have no idea what is the problem with your setup...

sorry I found out the problem and resolved! I copied /etc.defaults/syslog-ng/patterndb.d/scemd.conf as /etc.defaults/syslog-ng/patterndb.d/scemd.conf_orig as a backup. The system also loaded both scemd.conf and scemd.conf_orig also. After I removed scemd.conf_orig then it works! 

 

Sorry for stupid question but you still keep on helping! ^_^

Link to comment
Share on other sites

  • 6 months later...

interesting topic, i never could make drives sleep, and it's frustrating from day one.

never saw "ioctl device failed" errors, so my scemd is quiet.

perhaps apparmor.log is the busy one, constantly dropping dmidecode messages

dmidecode: AppArmor: /sys/firmware/dmi/tables/smbios_entry_point denied by profile /usr/sbin/dmidecode

 

it's hard to test since hdparm -Y /dev/sdX will spin down volume, but it will wake up immediately:

ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: waking up from sleep
ata5: hard resetting link
ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata5.00: retrying FLUSH 0xea Emask 0x0

i wonder which nasty daemon is doing this? Dovecot stats? Marvell driver? Any of tons of DSM services? I don't know. In Proxmox, it'd be pvestatd, for example.

Link to comment
Share on other sites

  • 10 months later...
  • 1 month later...
On 5/18/2022 at 2:15 AM, synologyturkey said:

Hello, same problem persists for DSM 7. Has a solution been found?

 

Hi all, also for me. anyone tried the solutions above with recents DSM 7.1.0 updates? if so, is it working or is there a different way to do?

Thank you

Link to comment
Share on other sites

On 5/18/2022 at 2:15 AM, synologyturkey said:

Hello, same problem persists for DSM 7. Has a solution been found?

 

On 6/24/2022 at 8:42 AM, Stefano said:

Hi all, also for me. anyone tried the solutions above with recents DSM 7.1.0 updates? if so, is it working or is there a different way to do?

 

please ope a new thread as your problem is not with dsm 6.2.3 as the topic indicates, you may link to that old thread as reference but keep in mind that your's is a new problem wit a different dsm version and might not be related to the old problem

Link to comment
Share on other sites

23 hours ago, IG-88 said:

 

 

please ope a new thread as your problem is not with dsm 6.2.3 as the topic indicates, you may link to that old thread as reference but keep in mind that your's is a new problem wit a different dsm version and might not be related to the old problem

Hi IG-88. Apologise, I'll open a new thread.

Thank you

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...