If you can wake up your NAS manually, but doesn't work via rcS, then something goes wrong. You can check spelling, permissions and path - sorry, I can't help you much more. It's really difficult to say what's wrong, because we don't see your files.

Normally if it's in /usr/local/etc/rcS, it has to work after reboot.

Yes, I was afraid of that. Well, will keep on checking. rcS is in correct spot though.

@Christian_Ku

Perhaps it is possible to capture the output of the command.
This could tell you what's wrong.

Try adding ' > /usr/local/etc/output.txt 2>&1', to the line containing the ether-wake command.
This will store the output(and errors) of the command into output.txt

After the POHD is started, you can look in the file. Perhaps there's some kind of error message in the file, that explains why it doesn't work

Hope it helps

kaay

Well, it appears to be much simpeler. Yesterday for some strange reason the POHD stalled and I had to get the power off the machine to be able to start it again. When I did restart it this way it did start the NAS via WOL. Have not tested it thoroughly yet to see if it will start the server also from suspended mode. Will keep you posted, otherwise I will use the above mentioned method by Kaay. Thanks!

Allright, now I'm at a loss, it works when I do a complete shutdown (with power off) and start-up. It does NOT work when I just put it on stand-by and then turn it on. As if it already has ran the rcS file and skips that.

Will try the option mentioned by Kaay.

Hello everyone,

I have 2 PlayonHD Mini. One is connected to wired LAN and the other via WiFi. Now I have the problem that the WOL function to run at the Wired Box perfect. In the pits, unfortunately, not WLAN.

Chance does anyone have a tip for me how I can get with wifi go?

Is it somehow possible to create a file that can be called with the PlayonHD waking up the server with it?

Or does the command for the Magic packet for WLAN in another script to be integrated?

Greetings
Pilepalle

Try to put some delay like sleep 30 just before ether_wake.

It could be that the WLAN is not initialized when the WOL signal is being sent.

The sleep (suggested in previous post) should fix that problem

Hope this helps

Hi,

I have entered the sleep 30th
The NAS drive but not online.

Pilepalle

Now the new GUI 2.0 has arrived, I have to redo the work. Because I encountered some problems, here is what i did

- Login to the POHD using putyy(telnet). Make sure you connect to ssl not ssh
- Make sure you log in as user root
- Goto /usr/local/etc (thats were I had some free space) with the command:
- Download busybox 2 (note the different location)using the command: (remember to remove the _ between w and get)
- Make sure it's executable with the command:
- Add the ether-wake command to, I think some kind of startup script, /usr/local/etc/rcS, using the following command:
- Check if the command is stored in the rcS file, using the command cat /usr/local/etc/rcS. You should something like this:
- Shutdown POHD
- Shutdown your server, WOL should be active
- Start POHD, and the server should be activated with the magic packet sent. it's magic

Hope this helps others with this problem