Shutdown and wake up timer

  • Hi at all guys!
    I was thinking about setting a timer for the shutdown and wakeup of my OMV. Is this possible?
    Also, I don't get why, but even if both my motherboard and OMV have WoL enabled, I can't wake it up :(
    Can someone help me with both the things?

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • 1) Use the autoshutdown plug-in for scheduled shutdown, I'm not sure how it works with a scheduled wakeup (but WOL would fit for that)


    2) WOL: enabled in the BIOS as well?

    OMV 5.x | Banana PI (M1) | Seafile Server
    OMV 4.x | ShuttlePC SH55J2

  • 1) scheduled is still better for me, but yeah, wol is still good
    2) yes

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • Use 'Cron Jobs' to schedule or you can use 'crontab' too, ( /etc/crontab).
    Ensure 'WOL' is enabled in the OMV network settings of your interface.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • Is enabled on both motherboard and OMV :(
    you mean "Scheduled jobs"?

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • Yes.
    Some motherboard support hibernation (S4), & sleep (S3), while others are not.
    Try it out on your system, and see which method is best for you.


    Here's an example of my sleep/wake up schedule in /ect/crontab:


    Code
    # Monday-Thursday: sleep @ 10:40PM, wake up @ 4PM.
    40 22 * * 1-4 root /usr/sbin/rtcwake -m disk -s 62400

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • Thanks for this tip.

    OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware


    OMV-Server-SW: Debian Buster with Proxmox kernel (always up-to-date), OMV v5 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Docker with PlexMediaServer, TVHeadend, any many more


    BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2

  • Yes.
    Some motherboard support hibernation (S4), & sleep (S3), while others are not.
    Try it out on your system, and see which method is best for you.


    Here's an example of my sleep/wake up schedule in /ect/crontab:


    Code
    # Monday-Thursday: sleep @ 10:40PM, wake up @ 4PM.
    40 22 * * 1-4 root /usr/sbin/rtcwake -m disk -s 62400

    Thanks! so whats should I write to wake up at 6PM during week, and 8AM during weekend?
    for what I read your lane include the shutdown too right?

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • Time is in seconds.
    It depends what time your system sleep on daily basis.


    If it sleep at 10PM, and wake up at 6PM (20 hrs), then it would be something like:


    Code
    # Monday - Friday: sleep @ 10PM, wake at 6PM.
    00 22 * * 1-5 root /usr/sbin/rtcwake -m disk -s 72000

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • this is my crontab

    Code
    # m h dom mon dow user  command
    17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
    25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
    47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
    52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
    #

    I made the scheduled jobs into the web interface:
    daily->root ->/usr/sbin/rtcwake -m disk -s 72000
    is this correct?

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • If you use the schedule jobs in the OMV interface, then you don't need to use crontab.
    Use only one scheduler, otherwise, the schedules may conflict.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • I use crontab b/c you can do day range while the 'scheduled jobs' can only set per day per cron job.
    My previous example is from crontab.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • Hi guys, I tried to create a wake up timer for certain day of the week, but I'm having this error:
    My Delibird NAS, [23.11.16 00:00]
    Cron - Sveglia alle 18 on the Wed, 23 Nov 2016 00:00:30 +0100 (CET)



    rtcwake: wakeup from "disk" using /dev/rtc0 at Wed Nov 23 17:00:02 2016



    My Delibird NAS, [23.11.16 00:00]
    Cron <root@Delibird> /var/lib/openmediavault/cron.d/userdefined-8a52783a-a8bb-4f47-adf7-c0f78decb593 | mail -E -s "Cron - Sveglia alle 18" -a "From: Cron Daemon <root>" root >/dev/null 2>&1 on the Wed, 23 Nov 2016 00:00:30 +0100 (CET)



    rtcwake: write error


    I put an attachement with how I set up the wake up for Sunday. I copied it from the general one, only changing the seconds

  • I think your 'daily' schedule is conflict with your 'Sunday ' schedule.
    If you use daily, then don't enable the other ones.
    Or set Monday - Saturday, and a separate schedule for Sunday.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • understood :) in that case I'll keep the general one for now

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • Dear all, I'm not an expert. As I know the Intel processors and AMD as well, both can write some hide bios parameters from Windows OS.
    Step 1. To can have a working WOL, is neccesary to install first an windows, doesn't meter witch version. Try to configure the BIOS & Windows network settings. Internet is full of information.
    Step 2. Check the network, PING your PC & be careful about the router settings. If exist any router between your PC and PC on witch will be OMV installed please set it careful ( don't use NAT). Read on internet about routers configuration
    Step 3. Download an WOL magic packet program & with your OMV-PC (now with Windows OS) online scan the network. See if you find your OMV-PC. Shutdown the OMV-PC & send WOL magic packets.
    If works go to next step, if not go back.
    Step 4. Install a clean Open Media Vault on your PC, better with fix IP address. Be very careful how is configured the name of your workgroup. If chose for standard (HOME), should change any PC in your network to have the same WORKGROUP NAME.
    Step 5. Ping the OMV-PC to be sure that the network is fine. Here is included the router
    Step 6. Activate WOL on OMV-PC web gui interface/Network. Do an WOL with the same program used before.


    P.S. Durring OMV installation please check error messages, in special about network configuration. If you can't see any issue, WOL should work fine. If yes, should take in consideration to replace the network card & reinstall OMV.
    If is OK enjoy, if not go back.


    Intel G3220, MSI H81M-E33, onboard RTL 8111 network card. OMV 4.1.4 - Kernel 4.14

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!