starred/synology_hibernation_fixer

Fork 0

mirror of https://github.com/AlexFromChaos/synology_hibernation_fixer.git synced 2026-04-26 03:06:02 +03:00

[GH-ISSUE #5] No effect after applying fixer script/HDDs not hibernating #11

New issue

Open

opened 2026-03-07 19:31:29 +03:00 by kerem · 3 comments

kerem commented

2026-03-07 19:31:29 +03:00

Owner

Originally created by @baqsoft on GitHub (Dec 9, 2023).
Original GitHub issue: https://github.com/AlexFromChaos/synology_hibernation_fixer/issues/5

First of all I would like to thank you for creating this script and sharing it here.
I'm sure it has helped a lot of people to making their hardware quieter and less power consuming :)

However, I encountered a major problem with it - applying it has no effect on the connected HDDs.
I'm using DSM 7.2-64570 Update 1 and two 500GB HDDs combined into single SHR plus single SSD as another volume.
I have no Virtual Machine Manager, I have Container Manager but all docker-mounted volumes are located on the SSD.
What I've tried so far:

Applied the Script with all default answers
Several reboots
Moved all data out of the volume (migrated shared folders)
Excluded it completely from SHR (deactivated)
Disabled Active Insight

I noticed (by sound and diode activtiy) that drives are constantly accessed. In the Resource Monitor I can see that there's constant write (several kB/s) but no reads.

Then I enabled "system hibernation debugging mode" with "unable to hibernate" option.
In these logs I can find a repeating pattern:
8 sectors write to md0, followed by the write to sda (SSD), sdb (first HDD), sdc (second HDD).

[18133.792200] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sda1 (8 sectors)
[18133.792234] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sdc1 (8 sectors)
[18133.792250] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sdb1 (8 sectors)
[18133.821345] ppid:2(kthreadd), pid:6322(jbd2/md0-8), WRITE block 4477864 on md0 (8 sectors)
[18133.821712] ppid:2(kthreadd), pid:6322(jbd2/md0-8), WRITE block 4477872 on md0 (8 sectors)
[18134.053064] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sda1 (8 sectors)
[18134.053083] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sdc1 (8 sectors)
[18134.053093] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sdb1 (8 sectors)

As far as I understand, the md0 is a RAID1 which DSM automatically creates by attaching every newly connected drive to it.
I'm not sure if to allow HDDs to hibernate they should not be attached to md0, or maybe the system should avoid writes to the md0 to allow the hardware to hibernate?

Is there something I missed that prevents the NAS from hibernating the drives properly?

Originally created by @baqsoft on GitHub (Dec 9, 2023). Original GitHub issue: https://github.com/AlexFromChaos/synology_hibernation_fixer/issues/5 First of all I would like to thank you for creating this script and sharing it here. I'm sure it has helped a lot of people to making their hardware quieter and less power consuming :) However, I encountered a major problem with it - applying it has no effect on the connected HDDs. I'm using `DSM 7.2-64570 Update 1` and two 500GB HDDs combined into single SHR plus single SSD as another volume. I have no Virtual Machine Manager, I have Container Manager but all docker-mounted volumes are located on the SSD. What I've tried so far: - Applied the Script with all default answers - Several reboots - Moved all data out of the volume (migrated shared folders) - Excluded it completely from SHR (deactivated) - Disabled Active Insight I noticed (by sound and diode activtiy) that drives are constantly accessed. In the Resource Monitor I can see that there's constant write (several kB/s) but no reads. Then I enabled "system hibernation debugging mode" with "unable to hibernate" option. In these logs I can find a repeating pattern: 8 sectors write to md0, followed by the write to sda (SSD), sdb (first HDD), sdc (second HDD). ```[18133.792123] ppid:2(kthreadd), pid:6322(jbd2/md0-8), WRITE block 4477856 on md0 (8 sectors) [18133.792200] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sda1 (8 sectors) [18133.792234] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sdc1 (8 sectors) [18133.792250] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sdb1 (8 sectors) [18133.821345] ppid:2(kthreadd), pid:6322(jbd2/md0-8), WRITE block 4477864 on md0 (8 sectors) [18133.821712] ppid:2(kthreadd), pid:6322(jbd2/md0-8), WRITE block 4477872 on md0 (8 sectors) [18134.053064] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sda1 (8 sectors) [18134.053083] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sdc1 (8 sectors) [18134.053093] ppid:2(kthreadd), pid:5679(md0_raid1), WRITE block 16777088 on sdb1 (8 sectors) ``` As far as I understand, the md0 is a RAID1 which DSM automatically creates by attaching every newly connected drive to it. I'm not sure if to allow HDDs to hibernate they should not be attached to md0, or maybe the system should avoid writes to the md0 to allow the hardware to hibernate? Is there something I missed that prevents the NAS from hibernating the drives properly?

kerem commented

2026-03-13 22:54:43 +03:00

Author

Owner

@marcomauri78 commented on GitHub (Dec 25, 2023):

Can Someone confirm that it works on Version: 7.2.1-69057 Update 2 or 3

I've Just installed 2 nvme drives and moved docker on them but hibern never happened. If i switch off the container It works (with some random wake up everybday) thanks

@marcomauri78 commented on GitHub (Dec 25, 2023): Can Someone confirm that it works on Version: 7.2.1-69057 Update 2 or 3 I've Just installed 2 nvme drives and moved docker on them but hibern never happened. If i switch off the container It works (with some random wake up everybday) thanks

kerem commented

2026-03-13 22:54:48 +03:00

Author

Owner

@marcomauri78 commented on GitHub (Jan 20, 2024):

hi @AlexFromChaos
i tried the script with 7.2.1-69057 update 3 and home assistant running on docker (on NVME ssd) but the HDD don't hibernate. Any idea on how ti solve the issiue ? Thanks

@marcomauri78 commented on GitHub (Jan 20, 2024): hi @AlexFromChaos i tried the script with 7.2.1-69057 update 3 and home assistant running on docker (on NVME ssd) but the HDD don't hibernate. Any idea on how ti solve the issiue ? Thanks

kerem commented

2026-03-13 22:54:53 +03:00

Author

Owner

@TheRealMaN commented on GitHub (Mar 25, 2024):

On my system the disk sleeps and never wakes up on its own only after I set a sleep time manually via terminal command with root user:
hdparm -S 60 /dev/sd{X}
I've tested different time values and came to the conclusion that disk only can sleep when time is no more than 5 minutes. If its greater than 5 minutes - the disk would never enter hibernation state.
You can also force it to hibernate immediately using command:
hdparm -y /dev/sd{X}

@TheRealMaN commented on GitHub (Mar 25, 2024): On my system the disk sleeps and never wakes up on its own only after I set a sleep time manually via terminal command with root user: `hdparm -S 60 /dev/sd{X}` I've tested different time values and came to the conclusion that disk only can sleep when time is no more than 5 minutes. If its greater than 5 minutes - the disk would never enter hibernation state. You can also force it to hibernate immediately using command: `hdparm -y /dev/sd{X}`

No labels

enhancement

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/synology_hibernation_fixer#11

No description provided.

Rows
Columns