Startup not working issue in Control Panel Power Schedule

Peter Suh · July 12, 2022

Below is the result of collecting the operation status for TCRP users.

DS3617xs (Operation OK)
DS3615xs (Operation OK)
DS3622xs+ (Operation OK)
DVA3221 (Operation OK)
DVA1622 (Operation OK)
DS918+ (Operation Not OK)
DS920+ (Operation Not OK)
DS1621+ (Operation Not OK)
DS2422+ (Operation Not OK)
DS1520+ (Operation Not OK)

GeminiLake (DS920+, DS1520+, etc.), known as a DTC-only model
and V1000 (DS1621+, DS2422+, etc.), this function does not work, and DS918+ also does not work.

Monitoring equipment DVA3221, DVA1622 (based on DTC) is OK.

Jun Mode and Jot Mode seem to be a common phenomenon without any distinction.

ACPI ext is related to the power button and has nothing to do with this power schedule reservation.

Is there any way to solve this problem?

koval · November 29, 2022

Hello,

I have the same issue with the startup on my DS918+ (Asrock j3455b-itx).

I want to try an extension, but I need some clarification.

1. What extension should I use?

RTC-cmos, powersched, or both?

2. How can I configure startup ? From Synology GUI or I still need to use this shell commands:

$ sudo sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm"
$ sudo sh -c "echo `date '+%s' -d '+ 5 minutes'` > /sys/class/rtc/rtc0/wakealarm"

3. I use the latest version of TCRP. Is it enough to add extension and build it?

./rploader.sh ext ds918p-7.1.1-42962 add 
https://raw.githubusercontent.com/pocopico/rp-ext/main/rtc-cmos/rpext-index.json
./rploader.sh ext ds918p-7.1.1-42962 add 
https://raw.githubusercontent.com/pocopico/rp-ext/main/powersched/rpext-index.json
./rploader.sh build ds918p-7.1.1-42962

I really appreciate any help you can provide.

Edited November 29, 2022 by koval

Peter Suh · November 30, 2022

14 hours ago, koval said:
Hello,

I have the same issue with the startup on my DS918+ (Asrock j3455b-itx).

I want to try an extension, but I need some clarification.

1. What extension should I use?

RTC-cmos, powersched, or both?

2. How can I configure startup ? From Synology GUI or I still need to use this shell commands:
$ sudo sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm"
$ sudo sh -c "echo `date '+%s' -d '+ 5 minutes'` > /sys/class/rtc/rtc0/wakealarm"
3. I use the latest version of TCRP. Is it enough to add extension and build it?
./rploader.sh ext ds918p-7.1.1-42962 add 
https://raw.githubusercontent.com/pocopico/rp-ext/main/rtc-cmos/rpext-index.json
./rploader.sh ext ds918p-7.1.1-42962 add 
https://raw.githubusercontent.com/pocopico/rp-ext/main/powersched/rpext-index.json
./rploader.sh build ds918p-7.1.1-42962 
I really appreciate any help you can provide.

Go to M SHELL for TCRP FRIEND on Github below
try to build
Bundled for models that require power-related modules.
You just need to build after selecting the model.

https://github.com/PeterSuh-Q3/tinycore-redpill#readme

sten12341 · December 31, 2022

Hi this extension is working for me in Proxmox and on an old laptop

[DS918+]
./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS918+
./rploader.sh identifyusb now
./rploader.sh satamap now
(Proxmox: WinSCP SATA to 4 and 00)
./rploader.sh ext ds918p-7.1.1-42962 add https://github.com/pocopico/redpill-load/raw/develop/redpill-acpid/rpext-index.json
./rploader.sh ext ds918p-7.1.1-42962 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json
./rploader.sh ext ds918p-7.1.1-42962 add https://raw.githubusercontent.com/pocopico/rp-ext/main/powersched/rpext-index.json
./rploader.sh build ds918p-7.1.1-42962
./rploader.sh clean now
sudo poweroff

Peter Suh · January 23, 2023

@pocopico

It was confirmed that power start reservation does not work even in DS923+ (r1000).

Temporarily tried to operate with v1000 used by DS1621+,

It seems to work fine.

There is no rtc-cmos.ko file for r1000,

Will it matter like this?

https://github.com/pocopico/rp-ext/tree/main/powersched/releases

pocopico · January 23, 2023

46 minutes ago, Peter Suh said:

@pocopico

It was confirmed that power start reservation does not work even in DS923+ (r1000).

Temporarily tried to operate with v1000 used by DS1621+,

It seems to work fine.

There is no rtc-cmos.ko file for r1000,

Will it matter like this?

https://github.com/pocopico/rp-ext/tree/main/powersched/releases

No, its better to always use compiled modules with the platform specific toolkit. I've added the missing release.

Peter Suh · January 23, 2023

1 hour ago, pocopico said:

No, its better to always use compiled modules with the platform specific toolkit. I've added the missing release.

@pocopico

A strange phenomenon has been identified.

Of course, r1000, which was expected to work well, does not work.

I replaced the newly added rtc-cmos.ko for r1000 with rtc-cmos.ko for v1000 and reserved the start time and waited, but there was no response from DS923+.

Installation of rtc-cmos.ko seems to have failed.

Running "check-rtc-cmos.sh" for powersched->on_boot
Loading module rtc-cmos -> Module rtc-cmos is not loaded
Ran "check-rtc-cmos.sh" for powersched->on_boot - exit=0

admin2@NAS4:/etc/systemd/system$ ll
total 64
drwxr-xr-x 13 root root 4096 Jan 22 15:50 .
drwxr-xr-x 4 root root 4096 Jan 22 16:13 ..
drwxr-xr-x 2 root root 4096 Jan 23 23:58 multi-user.target.wants
drwxr-xr-x 2 root root 4096 Jul 13 2022 network-online.target.wants
-rw-r--r-- 1 root root 141 Jan 22 15:56 nvme-cache.service
drwxr-xr-x 2 root root 4096 Jul 13 2022 pkg-AudioStation-StartDaemon.target.wants
drwxr-xr-x 2 root root 4096 Dec 7 19:20 pkgctl-apache2.2.service.wants
drwxr-xr-x 2 root root 4096 Dec 7 19:20 pkgctl-apache2.4.service.wants
drwxr-xr-x 2 root root 4096 Jul 13 2022 pkg-SynologyPhotos-StartDaemon.target.wants
-rw-r--r-- 1 root root 146 Jan 23 23:58 powersched.service
-rw-r--r-- 1 root root 136 Jan 23 23:58 powersched.timer
drwxr-xr-x 2 root root 4096 Jul 13 2022 syno-bootup-done.target.wants
drwxr-xr-x 2 root root 4096 Aug 29 20:18 syno-high-priority-packages.target.wants
drwxr-xr-x 2 root root 4096 Dec 15 00:19 syno-low-priority-packages.target.wants
drwxr-xr-x 2 root root 4096 Jul 13 2022 syno-volume.target.wants
drwxr-xr-x 2 root root 4096 Jan 23 23:58 timers.target.wants
admin2@NAS4:/etc/systemd/system$ cd multi-user.target.wants
admin2@NAS4:/etc/systemd/system/multi-user.target.wants$ ll
total 16


drwxr-xr-x 2 root root 4096 Jan 23 23:58 .
drwxr-xr-x 13 root root 4096 Jan 22 15:50 ..
lrwxrwxrwx 1 root root 47 Sep 26 22:54 accountdb-cache.service -> /usr/lib/systemd/system/accountdb-cache.service
lrwxrwxrwx 1 root root 37 Jul 14 2022 atalk.service -> /usr/lib/systemd/system/atalk.service
lrwxrwxrwx 1 root root 37 Jul 13 2022 avahi.service -> /usr/lib/systemd/system/avahi.service
lrwxrwxrwx 1 root root 39 Jul 14 2022 bonjour.service -> /usr/lib/systemd/system/bonjour.service
lrwxrwxrwx 1 root root 36 Jul 13 2022 ntpd.service -> /usr/lib/systemd/system/ntpd.service
lrwxrwxrwx 1 root root 38 Jan 22 15:56 nvme-cache.service -> /etc/systemd/system/nvme-cache.service
lrwxrwxrwx 1 root root 61 Jan 2 20:19 pkg-synosamba-env-setup.service -> /usr/local/lib/systemd/system/pkg-synosamba-env-setup.service
lrwxrwxrwx 1 root root 56 Jan 2 20:19 pkg-synosamba-nmbd.service -> /usr/local/lib/systemd/system/pkg-synosamba-nmbd.service
lrwxrwxrwx 1 root root 56 Jan 2 20:19 pkg-synosamba-smbd.service -> /usr/local/lib/systemd/system/pkg-synosamba-smbd.service
lrwxrwxrwx 1 root root 70 Jan 2 20:19 pkg-synosamba-wstransfer-genconf.service -> /usr/local/lib/systemd/system/pkg-synosamba-wstransfer-genconf.service
lrwxrwxrwx 1 root root 38 Jan 23 23:58 powersched.service -> /etc/systemd/system/powersched.service
lrwxrwxrwx 1 root root 36 Jul 13 2022 ssdp.service -> /usr/lib/systemd/system/ssdp.service
lrwxrwxrwx 1 root root 36 Jul 13 2022 sshd.service -> /usr/lib/systemd/system/sshd.service
lrwxrwxrwx 1 root root 42 Dec 13 23:48 synorelayd.service -> /usr/lib/systemd/system/synorelayd.service
lrwxrwxrwx 1 root root 41 Jul 13 2022 synotifyd.service -> /usr/lib/systemd/system/synotifyd.service


admin2@NAS4:/etc/systemd/system/multi-user.target.wants$ ll /lib/modules/rtc*.ko
ls: cannot access '/lib/modules/rtc*.ko': No such file or directory

HERQUIN · May 29, 2023

Hello everyone, in latest version of DSM 7.2, turning on with power schedule don´t work, at least with my version of DS920+, build it with tinycore-redpill v0.9.4.3-2 m shell, any ideas?, thanks in advance.

Edited May 29, 2023 by HERQUIN

Peter Suh · May 30, 2023

20 hours ago, HERQUIN said:

Hello everyone, in latest version of DSM 7.2, turning on with power schedule don´t work, at least with my version of DS920+, build it with tinycore-redpill v0.9.4.3-2 m shell, any ideas?, thanks in advance.

Addon modified and redeployed.
According to the check command, it is confirmed that the module is normally loaded.

for file in `ls /etc/systemd/system/*.service | awk -F / '{print $NF}'`; do systemctl status ${file}; done

● cpufreq-userspace-scaler.service - ACPI cpufreq userspace scaler
   Loaded: loaded (/etc/systemd/system/cpufreq-userspace-scaler.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2023-05-30 21:36:41 KST; 1min 46s ago
 Main PID: 9725 (scaler.sh)
   CGroup: /system.slice/cpufreq-userspace-scaler.service
           ├─ 9725 /bin/bash /usr/sbin/scaler.sh
           └─25061 sleep 0.5
● cpuinfo.service - Adds correct CPU Info, from FOXBI
   Loaded: loaded (/etc/systemd/system/cpuinfo.service; enabled; vendor preset: disabled)
   Active: active (exited) since Tue 2023-05-30 21:37:00 KST; 1min 27s ago
 Main PID: 13153 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/cpuinfo.service
● nvme-cache.service - NVMe cache enabler schedule
   Loaded: loaded (/etc/systemd/system/nvme-cache.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Tue 2023-05-30 21:36:41 KST; 1min 46s ago
 Main PID: 9661 (code=exited, status=0/SUCCESS)
● powersched.service - Configure RTC to DSM power schedule
   Loaded: loaded (/etc/systemd/system/powersched.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Tue 2023-05-30 21:38:01 KST; 26s ago
  Process: 23540 ExecStart=/usr/sbin/powersched (code=exited, status=0/SUCCESS)
 Main PID: 23540 (code=exited, status=0/SUCCESS)
● smb3-multi.service - smb3 multi channel enabler schedule
   Loaded: loaded (/etc/systemd/system/smb3-multi.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
● pkg-synorelayd.service - synorelay daemon
   Loaded: loaded (/usr/local/lib/systemd/system/pkg-synorelayd.service; enabled; vendor preset: disabled)
   Active: inactive (dead)

Please do the reservation test yourself.
The loader needs to be rebuilt.

Edited May 30, 2023 by Peter Suh

HERQUIN · May 30, 2023

7 hours ago, Peter Suh said:

Addon modified and redeployed.
According to the check command, it is confirmed that the module is normally loaded.

for file in `ls /etc/systemd/system/*.service | awk -F / '{print $NF}'`; do systemctl status ${file}; done

● cpufreq-userspace-scaler.service - ACPI cpufreq userspace scaler
   Loaded: loaded (/etc/systemd/system/cpufreq-userspace-scaler.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2023-05-30 21:36:41 KST; 1min 46s ago
 Main PID: 9725 (scaler.sh)
   CGroup: /system.slice/cpufreq-userspace-scaler.service
           ├─ 9725 /bin/bash /usr/sbin/scaler.sh
           └─25061 sleep 0.5
● cpuinfo.service - Adds correct CPU Info, from FOXBI
   Loaded: loaded (/etc/systemd/system/cpuinfo.service; enabled; vendor preset: disabled)
   Active: active (exited) since Tue 2023-05-30 21:37:00 KST; 1min 27s ago
 Main PID: 13153 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/cpuinfo.service
● nvme-cache.service - NVMe cache enabler schedule
   Loaded: loaded (/etc/systemd/system/nvme-cache.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Tue 2023-05-30 21:36:41 KST; 1min 46s ago
 Main PID: 9661 (code=exited, status=0/SUCCESS)
● powersched.service - Configure RTC to DSM power schedule
   Loaded: loaded (/etc/systemd/system/powersched.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Tue 2023-05-30 21:38:01 KST; 26s ago
  Process: 23540 ExecStart=/usr/sbin/powersched (code=exited, status=0/SUCCESS)
 Main PID: 23540 (code=exited, status=0/SUCCESS)
● smb3-multi.service - smb3 multi channel enabler schedule
   Loaded: loaded (/etc/systemd/system/smb3-multi.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
● pkg-synorelayd.service - synorelay daemon
   Loaded: loaded (/usr/local/lib/systemd/system/pkg-synorelayd.service; enabled; vendor preset: disabled)
   Active: inactive (dead)

Please do the reservation test yourself.
The loader needs to be rebuilt.

@Peter Suh thank you, it works now, accesing to tiny core gets the update, rebuild and done.

Hackaro1 · July 10, 2023

Hello @Peter Suh

same problem as @HERQUIN, with latest version of DSM 7.2U1, turning on with power schedule doesn´t work, at least with my version of DS920+, build it with TCRP v0.9.4.3-2 m_shell, but the service is correctly loaded:

admin@NAS:~$ sudo -i
Password: 
root@NAS:~# systemctl status powersched.service
● powersched.service - Configure RTC to DSM power schedule
   Loaded: loaded (/etc/systemd/system/powersched.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Mon 2023-07-10 16:59:00 CEST; 10s ago
  Process: 3968 ExecStart=/usr/sbin/powersched (code=exited, status=0/SUCCESS)
 Main PID: 3968 (code=exited, status=0/SUCCESS)

Jul 10 16:59:00 NAS systemd[1]: Starting Configure RTC to DSM power sched.....
Jul 10 16:59:00 NAS systemd[1]: Started Configure RTC to DSM power schedule.
Hint: Some lines were ellipsized, use -l to show in full.
root@NAS:~# logout
admin@NAS:~$ logout

with the same USB stick I've made a test system (with just a test HDD and no cache) on the same hardware (see my signature) and the power schedule was correctly working. Then I've attached my whole bunch of raid disk and correctly migrated to DSM 7.2U1 from an ARPL previous version. Now the power schedule is not correctly functioning. Any hints?

Peter Suh · July 11, 2023

10 hours ago, Hackaro1 said:
Hello @Peter Suh

same problem as @HERQUIN, with latest version of DSM 7.2U1, turning on with power schedule doesn´t work, at least with my version of DS920+, build it with TCRP v0.9.4.3-2 m_shell, but the service is correctly loaded:
admin@NAS:~$ sudo -i
Password: 
root@NAS:~# systemctl status powersched.service
● powersched.service - Configure RTC to DSM power schedule
   Loaded: loaded (/etc/systemd/system/powersched.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Mon 2023-07-10 16:59:00 CEST; 10s ago
  Process: 3968 ExecStart=/usr/sbin/powersched (code=exited, status=0/SUCCESS)
 Main PID: 3968 (code=exited, status=0/SUCCESS)

Jul 10 16:59:00 NAS systemd[1]: Starting Configure RTC to DSM power sched.....
Jul 10 16:59:00 NAS systemd[1]: Started Configure RTC to DSM power schedule.
Hint: Some lines were ellipsized, use -l to show in full.
root@NAS:~# logout
admin@NAS:~$ logout
with the same USB stick I've made a test system (with just a test HDD and no cache) on the same hardware (see my signature) and the power schedule was correctly working. Then I've attached my whole bunch of raid disk and correctly migrated to DSM 7.2U1 from an ARPL previous version. Now the power schedule is not correctly functioning. Any hints?

Like the phenomenon of DS923 (r1000) that I discussed with pocopico on January 24, 2023,

I doubt whether the rtc-cmos module for Gemini Lake has failed to load.

Now I can't communicate with Github due to a firewall problem in my office, so I can't test the DS920+.
If you want a quick solution, please send me the results of the log with the command below.

Below is how you can receive the results of the log.

First, press the j key within 7 seconds during kernel booting of TCRP FRIEND to enter junior mode.
Connect to the 7681 TTYD port as already instructed in this console screen.

cat /var/log/*rc* | grep rtc-cmos

Expect log of installation failure of rtc-cmos module like below.

Running "check-rtc-cmos.sh" for powersched->on_boot
Loading module rtc-cmos -> Module rtc-cmos is not loaded
Ran "check-rtc-cmos.sh" for powersched->on_boot - exit=0

Although it is a VM, it has been confirmed that there is no problem with module loading.

BusyBox v1.30.1 () built-in shell (ash)

SynologyNAS> cat /var/log/*rc* | grep rtc-cmos
rtc-cmos.ko
Running "check-rtc-cmos.sh" for powersched->on_boot
Ran "check-rtc-cmos.sh" for powersched->on_boot - exit=0

There is one more thing I want to check.
Has Schedule Power On worked normally with the DS3622xs+ model in your PC?

This model operates by itself without the help of rtc-cmos.

If the DS3622xs+ doesn't work, the DS920+ won't either.
Schedule Power On depends a lot on the characteristics of the MOBO.

Edited July 11, 2023 by Peter Suh

Hackaro1 · July 11, 2023

11 hours ago, Peter Suh said:

There is one more thing I want to check.
Has Schedule Power On worked normally with the DS3622xs+ model in your PC?

This model operates by itself without the help of rtc-cmos.

If the DS3622xs+ doesn't work, the DS920+ won't either.
Schedule Power On depends a lot on the characteristics of the MOBO.

SOLVED !!!! Thanks anyway!!! It has been sufficient to delete all the previous schedules and reset it in DSM and recreate the schedule and everything is working as expected.

Never tried with DS3622xs+ model on my hardware. I have real 920+ MAC addresses (from a broken unit) and having the QC is very convenient for me. So if I need a file and I'm out of home I can request it easily. Plus I don't know whether DS3622xs+ has DT model as 920+ has or not. So I've never given a try to DS3622xs+ model but maybe there are some other advantages.

One more thing: during the setup process I've manually added my S/N and my 3 NIC's MACs; these last ones have been added in this order:

i-210 (on the mobo, this should be OOB)
i-219 (on the mobo)
Realtek 8125 (PCI card)

I didn't know if the system is able to catch them all automatically and - above all - in which order, that's the reason why I proceeded with manual insertions.

Anyway after building the loader and restarting the system the ethernet cable was connected to the i-210 but the loader failed to show the gotten IP. I'm writing "show" because the SynologyAssistant app was able to show me the system with the correctly acquired IP. Same story if I put the ETH cable onto i-219... if I remember correctly. Isn't it weird?

Peter Suh · July 11, 2023

53 minutes ago, Hackaro1 said:

SOLVED !!!! Thanks anyway!!! It has been sufficient to delete all the previous schedules and reset it in DSM and recreate the schedule and everything is working as expected.

Never tried with DS3622xs+ model on my hardware. I have real 920+ MAC addresses (from a broken unit) and having the QC is very convenient for me. So if I need a file and I'm out of home I can request it easily. Plus I don't know whether DS3622xs+ has DT model as 920+ has or not. So I've never given a try to DS3622xs+ model but maybe there are some other advantages.

One more thing: during the setup process I've manually added my S/N and my 3 NIC's MACs; these last ones have been added in this order:

i-210 (on the mobo, this should be OOB)

i-219 (on the mobo)

Realtek 8125 (PCI card)

I didn't know if the system is able to catch them all automatically and - above all - in which order, that's the reason why I proceeded with manual insertions.

Anyway after building the loader and restarting the system the ethernet cable was connected to the i-210 but the loader failed to show the gotten IP. I'm writing "show" because the SynologyAssistant app was able to show me the system with the correctly acquired IP. Same story if I put the ETH cable onto i-219... if I remember correctly. Isn't it weird?

This strange phenomenon can be guessed because the order of loading and recognizing eth0, eth1, eth2, eth3, etc.

is different between Tinycore Linux and GNU/Linux used by FRIEND.
So it is very difficult to specify the order of Ethernet ports.

Sometimes they fit in the order you expect, sometimes they don't.
In my case, if the order expected by Tinycore and GNU operate differently
It also switches the mac address of eth0 and the mac address of eth1 to each other.
Sometimes this method works just fine.

Hackaro1 · July 12, 2023

18 hours ago, Peter Suh said:

This strange phenomenon can be guessed because the order of loading and recognizing eth0, eth1, eth2, eth3, etc.

is different between Tinycore Linux and GNU/Linux used by FRIEND.
So it is very difficult to specify the order of Ethernet ports.

Sometimes they fit in the order you expect, sometimes they don't.
In my case, if the order expected by Tinycore and GNU operate differently
It also switches the mac address of eth0 and the mac address of eth1 to each other.
Sometimes this method works just fine.

Thanks! To be honest I made a mistake: I put the Realtek as eth3 and now the WOL command of DSM doesn't work for it because DS920 supports only two NICs ... uhm ... is there a way to have WOL even on the third NIC? ...

Startup not working issue in Control Panel Power Schedule

Question

Link to comment

Share on other sites

64 answers to this question

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation