Can't start my NAS with MagicPacket or WOL from Fritzbox

    • OMV 2.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Can't start my NAS with MagicPacket or WOL from Fritzbox

      I hope you can help me, I have read here many threads about autoshutdown and WOL but I didn't found the solution.

      My NAS doesn't respond to MagicPaket from my PC or WOL from my fritzbox.
      I have this issue after I had installed update pakets from OMV 1.19. So I have think I can solve this issue if I update my OMV to 2.1.17.

      but it was doesn't so. There no action from my NAS when my PC send an magicpaket

      Here My autoshutdown log
      Display Spoiler

      Oct 27 12:24:11 :INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
      Oct 27 12:24:11 :INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
      Oct 27 12:24:11 :INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
      Oct 27 12:24:11 :INFO: ' X Version: 0.9.9.10'
      Oct 27 12:24:11 :INFO: ' Initialize logging to local6'
      Oct 27 12:24:11 :INFO: ' /etc/autoshutdown.conf loaded'
      Oct 27 12:24:11 :INFO: ' ------------------------------------------------------'
      Oct 27 12:24:11 :INFO: ' Checking config'
      Oct 27 12:24:11 :INFO: ' LOADPROCNAMES is set to: 'smbd,nfsd,transmission-daemon,mt-daapd,forked-daapd' (default)'
      Oct 27 12:24:11 :INFO: ' TEMPPROCNAMES is set to: in.'tftpd' (default)'
      Oct 27 12:24:11 :INFO: ' If you want more processes monitored, please have a look at the expert-settings'
      Oct 27 12:24:11 :INFO: ' SHUTDOWNCOMMAND is set to 'pm-suspend''
      Oct 27 12:24:11 :INFO: ' Your Kernel supports the following modes from pm-utils:'
      Oct 27 12:24:11 :INFO: ' Kernel supports SUSPEND (SUSPEND to RAM)'
      Oct 27 12:24:11 :INFO: ' Kernel supports HIBERNATE (SUSPEND to DISK)'
      Oct 27 12:24:11 :INFO: ' Kernel supports HYBRID-SUSPEND (to DISK & to RAM)'
      Oct 27 12:24:11 :WARN: ' LOADAVERAGECHECK is set to false'
      Oct 27 12:24:11 :WARN: ' Ignoring LOADAVERAGE'
      Oct 27 12:24:11 :INFO: ' ------------------------------------------------------'
      Oct 27 12:24:11 :INFO: ' Reading NICs ,IPs, ...'
      Oct 27 12:24:11 :INFO: ' NIC 'bond0' not found, skipping 'bond0''
      Oct 27 12:24:11 :INFO: ' NIC 'eth0' found: try to get IP'
      Oct 27 12:24:11 :INFO: ' _check_networkconfig(): Run: #1: IP-Adress found'
      Oct 27 12:24:11 :INFO: ' 'eth0' has IP: 192.168.178.60'
      Oct 27 12:24:11 :INFO: ' NIC 'eth1' not found, skipping 'eth1''
      Oct 27 12:24:11 :INFO: ' /tmp/autoshutdown created'
      Oct 27 12:24:11 :INFO: '---------------- script started ----------------------'
      Oct 27 12:24:11 :INFO: ' 2 test cycles until shutdown is issued.'
      Oct 27 12:24:11 :DEBUG: ' _check_ul_dl_rate(): /tmp/autoshutdown/txrx created successfully'
      Oct 27 12:24:11 :DEBUG: ' _check_hddio(): /tmp/autoshutdown/hddio created successfully'
      Oct 27 12:24:11 :INFO: ' Waiting 5 min until the first check


      The NAS response to WOL over Keyboard.

      The Backport kernel is upgraded to 3.16

      Interface information
      Display Spoiler
      Interface information eth0:
      ===========================
      Settings for eth0:
      Supported ports: [ TP MII ]
      Supported link modes: 10baseT/Half 10baseT/Full
      100baseT/Half 100baseT/Full
      1000baseT/Half 1000baseT/Full
      Supported pause frame use: No
      Supports auto-negotiation: Yes
      Advertised link modes: 10baseT/Half 10baseT/Full
      100baseT/Half 100baseT/Full
      1000baseT/Full
      Advertised pause frame use: Symmetric Receive-only
      Advertised auto-negotiation: Yes
      Link partner advertised link modes: 10baseT/Half 10baseT/Full
      100baseT/Half 100baseT/Full
      Link partner advertised pause frame use: Symmetric Receive-only
      Link partner advertised auto-negotiation: Yes
      Speed: 100Mb/s
      Duplex: Full
      Port: MII
      PHYAD: 0
      Transceiver: internal
      Auto-negotiation: on
      Supports Wake-on: pumbg
      Wake-on: g
      Current message level: 0x00000033 (51)
      drv probe ifdown ifup
      Link detected: yes
      --------------------------------------------------------------------------------
      Driver information eth0:
      ========================
      driver: r8169
      version: 2.3LK-NAPI
      firmware-version: rtl8168g-2_0.0.1 02/06/13
      bus-info: 0000:02:00.0
      supports-statistics: yes
      supports-test: no
      supports-eeprom-access: no
      supports-register-dump: yes
      supports-priv-flags: no
    • How do you send the WOL package by your fritzbox?
      This only works if you press the button inside the webIF and/or if you have enabled to send a wol package if you surf your Dyndns adress
      OMV stoneburner | HP Microserver | 256GB Samsung 830 SSD for system | 4x 2TB in a RAID5
      OMV erasmus| Odroid XU4 | 5TB Data drive | 500GB Backup drive
    • I send the packet normely by the tool "MagicPacket" Version 1.5.0.0 from my PC or Laptop im my LAN
      in this tool I bind the MAC adress from my NAS
      Usually I don't use the WOL function from my fritzbox.And yes it is the button inside the webIF.
      This I have do only for testing, because my NAS don't response to the MAgicPacket tool since the update.
      Here are my network config.


      In my Bios is wol enable.

      The post was edited 1 time, last by vandog ().

    • omg ;(
      1. I have type pm-suspend
      2. after 2min I send the magic packet but nothing happens. X(
      3. I went in my Bios from the NAS.
      - the ACPI Config are ok
      -on by PCIE-Device
      -on by USB-Keybord
      then I check my Start-Device
      it was first NAS-Storage , secondly Network <- this I have change to first Network and then storage.
      4. then restart NAS
      5. type pm-suspend
      6. send the magic packet
      and "tataa" my NAS wake up. 8o :thumbsup:
      Thanks for your help guys
    • vandog wrote:

      then I check my Start-Device
      it was first NAS-Storage , secondly Network <- this I have change to first Network and then storage.
      Erm.. this has nothing to do with WOL. However - it works. So... Well done :D
      OMV stoneburner | HP Microserver | 256GB Samsung 830 SSD for system | 4x 2TB in a RAID5
      OMV erasmus| Odroid XU4 | 5TB Data drive | 500GB Backup drive