[Help] Getting WOL to Work on F6-424 Max

[brob2684]

Hi,

I am having trouble getting WOL working as the NIC seems to lose power during the shutdown process.

The details are as follows:

• I have a Terramaster F6-424 Max running TOS7.

• WOL is enabled in the Terramaster UI and the boot settings of the BIOS

• If the machine is shutdown using

  Code: Select all

  halt -f -p

  the NIC remains powered on and WOL works

• If the machine is shutdown from the UI or scheduled shutdown, the NIC loses power and WOL does not work

I'd appreciate some tips as to what additional settings or changes I need to make to get WOL working as it's probably not optimal in the long run to continually skip the proper shutdown procedure.

[OrionXie]

WOL works normally within the local area network.

1. If the TNAS PC cannot recognize the wake-up button, please delete the history, enable Wake-on-Network, and then try accessing the TNAS PC again.

2. Do not use a network drive connected to the network for Wake-on-Network functionality.

3. Check if Wake-on-Network is enabled in the BIOS boot menu.

[brob2684]

Hi,

Thanks for the reply.

Are you able to explain to me how to carry out #1? I'm not sure what you mean by "please delete the history"?

[TMjack]

To clear the access history in the TNAS PC client, please open the client first, select a TNAS device under "Access History Locations," then click the "More" button in the upper right corner, and choose "Delete."

Please note that TOS only supports Wake-on-LAN functionality through the LAN1 interface; the LAN2 interface does not support this feature. Currently, TOS7 software indeed has a bug related to Wake-on-LAN, and our team is actively working on a fix. Additionally, may I ask if you encountered the same Wake-on-LAN issue when using TOS6 previously?

[brob2684]

Hi,

Thanks for the instructions. I'll clear the history later this week - unfortunately have a couple of big days at work.

I can confirm I am aware of the LAN1 limitation and that is the port I have been trying

Unfortunately I have only recently looked into using WOL, so I cannot advise as to the behaviour on TOS6.

[TMjack]

It has been confirmed that TOS7 software does have a known bug related to the Wake-on-LAN feature. Currently, we have completed the fix for this bug internally, and the fix will be incorporated into a future version of TOS7. Please stay tuned for updates on the release of the new TOS7 version to ensure you receive the update in a timely manner.

[brob2684]

Thanks for keeping me updated.

I can confirm that I have completed the steps above and there has been no change in behaviour.

I'll look forward to the fix being released.

[Gremlin]

Additionally, may I ask if you encountered the same Wake-on-LAN issue when using TOS6 previously?

As far as I can recall, WOL via the TNAS -mobile and TNAS-PC apps has always been a bit flaky. Even when enabled in bios and in GUI, it rarely seems to be "available" in the app GUI - unless the device is already running! ie 'History' == 'greyed out'; 'Active' == 'available' but not needed. However, not something I use as I have 3rd party WO utilities - and they present their own problems on occasion. Since my working machines are always-on and ususlly accessible (except in snow, ice, hail, rain when I don't want to walk down the garden) I don't really mind.

However, I would take this opportunity to ask:
Why can't WOL be made available on all network interfaces?
I remember in the past using Link Aggregation could be especially problematic when my utility would be looking for a registered MAC address but the Link was using a diferent (ie LAN2) MAC.

[TMjack]

Due to hardware architecture differences in some NAS models, their LAN2/3/4 interfaces utilize USB network chips connected to the backend of the HUB chip, which prevents Wake-on-LAN (WOL) functionality from being supported. To ensure consistent user understanding, it is officially stated that only the LAN1 interface supports WOL functionality.

Special Note: All LAN interfaces on the F6-424 Max model support WOL functionality.

[Den07y]

Hello,
I am still using Tos 6, and till the begining i have exactely the same problem: the wol just cannot work:
I mean it works "time to time" => means everything looks configured correctly: i can start from external network (smartphone) or internal (smartphone on wifi or computer directly onto the same network).
But very often when i stop the F6-424 Max, the network leds on the rear panel turned off immediately with the nas.
All the wol (from internal or external network), cannot works of course.
If i disconnect/connect the plug (without starting the nas), the led light on again with the network and then of course i can wake the nas again from outside or at home.
Well i already sent informations to the support but i wasted already too much time on that, for me the function is just not working (and yes i already checked my bios items but the question is why asking this kind of question when the network go off just time to time? ...
Well look like something is just not stable but when i see some ridiculous bugs i just stopped wasting my time on that nas.

exemple of "funny" bug on Tos6: when i tryied to define a period of validity , trying to send a sharing link for friends, the calendar proposed me the start date (the CURRENT date) : it was something like 03/04/2026 when we were the 04 of March . As the days/month are inverted in french format (i am French), i of course trusted the selection . I spend hours on that with just a message "like "dont work" without any smart message specifying the origin of the problem (period disabled for example).
Then i thought about this inversion... i really though: no that is not possible that they not even test that... but yes, that was the reason...
it was just proposing the 3rd of April as the current date when we were the 4th of March... (it is an example of course maybe i did this test in February)
I cannot believe it is the 6th version of Tos and this kind of bug are still there????
Well i was quite happy to then, being able to share my holidays videos with my friends but... They were not able to connect to the nas using the link...
It was too slow...
And indeed with my smartphone i was able to connect (time to time but waiting few minutes!) before seeing any folder, but then it was too slow and very unstable when i have a fiber line and huge system.

I just stopped thinking using this Nas for this kind of things, and i am hopping a lot that Tos7 will solve the problems but when i see this kind of discussion... and all the incredible bugs in the list of release notes...

And beeing able to send a shared link to friends or being able to wake on lan my nas is not a small functionality when we have a nas right?
Do you really think it is serious?
It would have been funny if i would have not spend so much money and time on that nas.
I am still looking on that subject time to time, who knows...
Denis