lewcass

No. It's hardly an ideal workaround. I've been a happy UNRAID user for around 15 years and was the person who first came up with the idea to include network monitoring in the original sleep script, but it's really not the answer for malfunctioning disk monitoring. Especially since the current Dynamix S3 Sleep runs the time lag countdown before the network monitoring check. That could be changed, but isn't a solution to the root issue with the disk monitoring. While I've been a big fan of UNRAID and the community and developers that support all the useful features that have been added, this is where the support model fails. i.e., when a useful plugin developer is no longer present to maintain their work. Since this disk monitoring issue came up, I've struggled to deal with it, and only recently found the time to check here, to confirm I was the not the only one affected. What I've had to do in the meantime is manually disable and later re-enable the Sleep settings from the Dynamix GUI. This isn't really any better than permanently disabling the script and using the Dynamix GUI to manually put the server to sleep when not using it.

This week I updated to 6.10.3 and Windows 11 Pro 64 also updated to KB5016629 (OS Build 22000.856) and KB5015732 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 11. Now I no longer have write access to public shares on UnRAID. Before either update this was never an issue. This is a big problem for me. How do I get write access back to public shares?

Wow! Still an issue 10 months later! You're welcome. Glad it resolved for you.

😀😉 He didn't help by misstating the first console command he sent to check the NIC status as the same as the one that addresses the issue. Fortunately he actually did know what he was doing. 🙂 Wouldn't be anywhere other than frustrated without his efforts.

OK. This works for me so far with onboard NIC. 😎 (Based on the OP's experiment in this thread. He's asked MSI for help a couple months back, but apparently to no avail so far.) Fortunately we can easily add the required code to our go script. Add following to /config/go . # Enable WOL if needed (i.e. for MSI X470 Gaming Plus). ethtool -s eth0 wol g

Been Googling off and on for two days. 😅 Think I just found a work-around. Testing now.

Yes. Latest BIOS version 7B79vAF. Released less than a month ago. I always update the BIOS when assembling a new build. You're correct in that there had been similar issues with WOL not working with various hardware 5-10 years ago. That's actually why I originally got the Intel NIC EXPI9301CTBLK which enabled WOL with earlier boards but unfortunately does not so far with this X470. Thought we were past this issue by now.

I haven't been able to get WOL to work with an older Intel NIC on the X470 either. Don't know what the Intel chip is offhand, but it worked with AMD X370 and A85X boards. Are there actual reports of WOL working under LInux with Intel i210-T1 NICs on X470 boards?

By now have you, Marc_G2, or anyone else actually tested WOL with an Intel I210-T1 (I210-AT chipset) NIC on the MSI X470 Gaming Plus? I'm in the middle rebuilding my server with this board and just realized that the WOL issue with the onboard NIC exists. Really don't want to drop another $45-$80 on another NIC if it won't solve the problem.

Ditto. On 6.6.2 with 2.2.0j.

I found an issue with the new UNRAID 6.6.0 Dynamix Black Theme. White text on the Server Layout plugin Data screen does not display properly against the screen areas with white or light backgrounds on this theme.

I typically use this plugin to backup key data to hard disks for offsite storage. It works very well for the most part, but the challenge comes in recognizing whether adequate space remains on the backup disks as the data on the server grows. So I've been tying to figure out how to use the plugin's AVAIL variable in my scripts to both log and notify the webgui as to the amount of space available when the disk is mounted and how much remains after the backup is completed. My scripting skills/knowledge are pretty minimal and so far I haven't been successful. Advice would be very much appreciated!

Since no one else has been reporting the issue, could (likely) be completely unrelated to the update. (See logical fallacy: post hoc ergo propter hoc) When I have had similar issues with S3 sleep not recovering properly it has been related to overclocking, specifically the bus-clock. If you aren't overclocking then it also might be hardware related; e.g., power supply no longer delivering adequate standby power, or failing RAM or motherboard. You might want to do some hardware testing. Edit: To clarify, the S3 sleep overclocking related issues I was referring to were with PCs other than my UnRAID servers. I wouldn't overclock a server with data on it I wanted to preserve. Also, more to the point, what I would do first is completely remove unRAID from the equation by booting with another linux distro on a separate flash drive and testing sleep from there. If problem still exists, certainly points to hardware or BIOS settings.

DUH! I'd completely forgotten about that with the passage of time since I first set up the plugin after UnRAID 6.0 came out. Unfortunately the setting location isn't particularly obvious or intuitive. The good news is that it looks like that is solving my issue! So thanks! My theory about the non-array drives was wrong. Even with them removed, after a wake-up the plugin was still continuing to treat the cache disk as active. It was only working correctly before the first S3 sleep was initiated. Setting the plugin to ignore the cache disk seems to be solving the issue. Hope you are successful getting your issue resolved.

Previous version is not compatible with unRaid 6.4.x If you enable the debug log, you may be able to find out why the current version is not working for you. I have mine set to log to Flash. You can view the log in the logs directory of you flash drive. \\TOWER\flash\logs\s3_sleep.log I don't see any setting to ignore cache drive. If it is possible I would like to know how.