Putting my server to sleep / hibernate or shut down to 'wake it up' automatically [SOLVED]

  • I have my OMV 5 installed in debian buster and I would like a way to put it into hibernation or sleep in one hour and wake up at another hour automatically on a daily basis but I have not found how to do it.


    Can you recommend a pluging or a way or instructions to do it please?

    :thumbup:

    OMV Server

    MotherBoard: DP43TF Intel
    Processor: Intel Pentium Dual E2200 @ 2x 2.2GHz
    Ram: 2gb
    OS: Debian 10 buster
    Kernel: x86_64 Linux 4.19.0-14-amd64
    OMV: 5.x Usul
    Docker: 5.x~debian-buster
    Portainer: 2.1.1
    Containers: Plex / Tranmission
    (disk 1 - hdd 80gb)
    partition sda1 / = 10gb
    partition sda2 extended
    partition sda5 swap = 4gb
    partition sda6 home = 14gb
    partition sda3 Movies (mounted in OVM) = 47gb

    (disk 2 md127 - 2tb)
    1 raid 5 (1tb hdd x 3)

    (disk 3 - ssd 250gb)
    partition for work = 250gb

  • I want him to turn off daily at 1am and wake up daily at 7am


    rtcwake -m off -t $(date -d "everyday 7:00" +%s)


    is fine?

    OMV Server

    MotherBoard: DP43TF Intel
    Processor: Intel Pentium Dual E2200 @ 2x 2.2GHz
    Ram: 2gb
    OS: Debian 10 buster
    Kernel: x86_64 Linux 4.19.0-14-amd64
    OMV: 5.x Usul
    Docker: 5.x~debian-buster
    Portainer: 2.1.1
    Containers: Plex / Tranmission
    (disk 1 - hdd 80gb)
    partition sda1 / = 10gb
    partition sda2 extended
    partition sda5 swap = 4gb
    partition sda6 home = 14gb
    partition sda3 Movies (mounted in OVM) = 47gb

    (disk 2 md127 - 2tb)
    1 raid 5 (1tb hdd x 3)

    (disk 3 - ssd 250gb)
    partition for work = 250gb
  • is this will be good for everyday?

    OMV Server

    MotherBoard: DP43TF Intel
    Processor: Intel Pentium Dual E2200 @ 2x 2.2GHz
    Ram: 2gb
    OS: Debian 10 buster
    Kernel: x86_64 Linux 4.19.0-14-amd64
    OMV: 5.x Usul
    Docker: 5.x~debian-buster
    Portainer: 2.1.1
    Containers: Plex / Tranmission
    (disk 1 - hdd 80gb)
    partition sda1 / = 10gb
    partition sda2 extended
    partition sda5 swap = 4gb
    partition sda6 home = 14gb
    partition sda3 Movies (mounted in OVM) = 47gb

    (disk 2 md127 - 2tb)
    1 raid 5 (1tb hdd x 3)

    (disk 3 - ssd 250gb)
    partition for work = 250gb
  • i was using the WOL plugin and it worked but in just for 2 or three days stop working to startup the machine just shutdown it... hope this keep working on good 😄

    OMV Server

    MotherBoard: DP43TF Intel
    Processor: Intel Pentium Dual E2200 @ 2x 2.2GHz
    Ram: 2gb
    OS: Debian 10 buster
    Kernel: x86_64 Linux 4.19.0-14-amd64
    OMV: 5.x Usul
    Docker: 5.x~debian-buster
    Portainer: 2.1.1
    Containers: Plex / Tranmission
    (disk 1 - hdd 80gb)
    partition sda1 / = 10gb
    partition sda2 extended
    partition sda5 swap = 4gb
    partition sda6 home = 14gb
    partition sda3 Movies (mounted in OVM) = 47gb

    (disk 2 md127 - 2tb)
    1 raid 5 (1tb hdd x 3)

    (disk 3 - ssd 250gb)
    partition for work = 250gb
  • I have done several tests and, when the time has come yes the machine shut up or turns off but never turn on again: this is what always happens to me with the rtcwakeup o wol plugin

    code example I've been using


    what iam doin wrong?

    OMV Server

    MotherBoard: DP43TF Intel
    Processor: Intel Pentium Dual E2200 @ 2x 2.2GHz
    Ram: 2gb
    OS: Debian 10 buster
    Kernel: x86_64 Linux 4.19.0-14-amd64
    OMV: 5.x Usul
    Docker: 5.x~debian-buster
    Portainer: 2.1.1
    Containers: Plex / Tranmission
    (disk 1 - hdd 80gb)
    partition sda1 / = 10gb
    partition sda2 extended
    partition sda5 swap = 4gb
    partition sda6 home = 14gb
    partition sda3 Movies (mounted in OVM) = 47gb

    (disk 2 md127 - 2tb)
    1 raid 5 (1tb hdd x 3)

    (disk 3 - ssd 250gb)
    partition for work = 250gb

    Edited once, last by roycordero ().

  • Ready! Everything is fine, it was a problem of setting the hours, it works perfect!

    this thread should be closed

    Thank you

    OMV Server

    MotherBoard: DP43TF Intel
    Processor: Intel Pentium Dual E2200 @ 2x 2.2GHz
    Ram: 2gb
    OS: Debian 10 buster
    Kernel: x86_64 Linux 4.19.0-14-amd64
    OMV: 5.x Usul
    Docker: 5.x~debian-buster
    Portainer: 2.1.1
    Containers: Plex / Tranmission
    (disk 1 - hdd 80gb)
    partition sda1 / = 10gb
    partition sda2 extended
    partition sda5 swap = 4gb
    partition sda6 home = 14gb
    partition sda3 Movies (mounted in OVM) = 47gb

    (disk 2 md127 - 2tb)
    1 raid 5 (1tb hdd x 3)

    (disk 3 - ssd 250gb)
    partition for work = 250gb
  • roycordero

    Changed the title of the thread from “Putting my server to sleep / hibernate or shut down to 'wake it up' automatically [HELP]” to “Putting my server to sleep / hibernate or shut down to 'wake it up' automatically [SOLVED]”.
  • macom

    Added the Label resolved
  • For me, not working.

    I have WOL installed.


    Raspberry Pi 4 (4Gb) - 5.6.5-2 (Usul) -- ARMv7 Processor rev 3 (v7l) -- Linux 5.10.17-v7l+

  • It's a RPI, as you can see in my signature.

    I don't know what is a real time clock (hardware) and how to achive that.

    Maybe not for my level of knowledge but that's okay.

    Raspberry Pi 4 (4Gb) - 5.6.5-2 (Usul) -- ARMv7 Processor rev 3 (v7l) -- Linux 5.10.17-v7l+

  • I don't know what is a real time clock (hardware) and how to achive that.

    :) It´s a daughter board for the RPI, which keeps the time when power is off.


    See here: Adding a Real Time Clock to Raspberry Pi

    OMV 3.0.100 (Gray style)

    ASRock Rack C2550D4I C0-stepping - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1) - Fractal Design Node 304 -

    3x WD80EMAZ Snapraid / MergerFS-pool via eSATA - 4-Bay ICYCube MB561U3S-4S with fan-mod

  • It seems a little complicated.

    I will study the topic calmly and patiently and try to achieve the goal.

    Thank you very much for this tip.

    Raspberry Pi 4 (4Gb) - 5.6.5-2 (Usul) -- ARMv7 Processor rev 3 (v7l) -- Linux 5.10.17-v7l+

  • Think about the power consumption of an RPi. It is very low. Probably the investment for a RTC module does not pay off. Keep the RPi running 24/7 and enjoy the instant availability of the NAS.

    You can achieve most power saving by spinning downs the drives, when not needed.

  • Thank you for the advice 'macom'.

    I have been using OMV for a few years in a basic with no problems, but very useful way for me.

    Despite my limitations in linux i am a little curious and i will study the topic.

    Thanks a lot.

    Raspberry Pi 4 (4Gb) - 5.6.5-2 (Usul) -- ARMv7 Processor rev 3 (v7l) -- Linux 5.10.17-v7l+

  • :) It´s a daughter board for the RPI, which keeps the time when power is off.


    See here: Adding a Real Time Clock to Raspberry Pi

    Currently I have my rpi 4 running 24/7 and I think the energy consumption is too low to leave it like that, however it is good to know that there is the option of adding a hardware with a battery like that ...

    On the other hand


    You can achieve most power saving by spinning downs the drives, when not needed.

    This yes I am interested in how to do it for my server because I think it would increase the life of my hard drives by lowering their spinnings at the same time as lowering consumption at times of the day that it is not used...

    how could i do that?

    OMV Server

    MotherBoard: DP43TF Intel
    Processor: Intel Pentium Dual E2200 @ 2x 2.2GHz
    Ram: 2gb
    OS: Debian 10 buster
    Kernel: x86_64 Linux 4.19.0-14-amd64
    OMV: 5.x Usul
    Docker: 5.x~debian-buster
    Portainer: 2.1.1
    Containers: Plex / Tranmission
    (disk 1 - hdd 80gb)
    partition sda1 / = 10gb
    partition sda2 extended
    partition sda5 swap = 4gb
    partition sda6 home = 14gb
    partition sda3 Movies (mounted in OVM) = 47gb

    (disk 2 md127 - 2tb)
    1 raid 5 (1tb hdd x 3)

    (disk 3 - ssd 250gb)
    partition for work = 250gb
  • There is some controversy whether or not spinning down a hdd increases or decreases the lifetime. For sure it should not be done too often. I would adjust the timing so, that you have not more than 2-4 spin ups per day. But this is really a gut feeling. I have no proof for this. Others prefer to never spin their drives down.


    How to do it?

    As you have an RPi you have the drives in some enclosure and connect them to the RPi by USB. In this enclosure you have a controller that is managing the drive. One possibility is, that this controller is able to do a spin down after some time the drive have not be accessed. You need to check the documentation for that.


    Test this option first.


    If that is not working you can try another option in OMV to configure a program that is called hdparm. That might or might not work with your drives (due to the controller):


    Go to the GUI of OMV and then

    Storage >> Disks >> select a disk >> press "Edit" >> a new windows opens

    Select the values like in the picture and press "Save" and then "Apply"


    For the power management do not use smaller values. You might safe some more power, but will increase the stress on your drive.


  • Currently rpi 4 I use it only as a cups server nothing else,

    my omv server is a:

    intel dual core 2.8ghz

    2 ram

    (disco 1 - 80 gb)

    particion / = 10gb

    particion extendidad

    particion swap = 4gb

    particion home = 14gb

    particion Movies (mounted in OVM) = 47gb

    (disco 2 - 2tb)

    1 raid 5 (3 discos 1 tb cada uno)

    (disco 3 - ssd 250gb)

    paticion work


    and change the configuration as you say to do tests and see the performance

    OMV Server

    MotherBoard: DP43TF Intel
    Processor: Intel Pentium Dual E2200 @ 2x 2.2GHz
    Ram: 2gb
    OS: Debian 10 buster
    Kernel: x86_64 Linux 4.19.0-14-amd64
    OMV: 5.x Usul
    Docker: 5.x~debian-buster
    Portainer: 2.1.1
    Containers: Plex / Tranmission
    (disk 1 - hdd 80gb)
    partition sda1 / = 10gb
    partition sda2 extended
    partition sda5 swap = 4gb
    partition sda6 home = 14gb
    partition sda3 Movies (mounted in OVM) = 47gb

    (disk 2 md127 - 2tb)
    1 raid 5 (1tb hdd x 3)

    (disk 3 - ssd 250gb)
    partition for work = 250gb

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!