Manni01

Thanks for your work, sounds great but how do we download/install your forked version? When I follow your link on GitHub, the readme says not to download the Zip, but the links to the s3sleep plugin (like all the others) returns a 404 error.

Thnaks for this. Sleep used to work absolutely fine until recent changes in the OS (it did take a while to get it to work initially, but it had been trouble-free for years). The servers are not accessible from the outside, they are only used locally, so security isn't that much of an issue. That being said, I still had issues with 6.11.5, so I re-upgraded to 6.12.6 and I think I might have found a way to make sleep work again by disabling docker, which I think was creating random MAC addresses when using sleep, so couldn't be powered back up reliably. Unfortunately powering off isn't an option as my MOBOs don't wake up from powered off, they only power up from sleep, it's a limitation of the MOBO/BIOS. Thanks for the advice!

s3 sleep seems to be working again as it used to, so that's great. One downside to the downgrade to 6.11.5, common problems reports an issue with an update needed for the docker patch, but when I click on the update button it sends me to the app tab and I'm told that I can't install the community apps plugin as it needs 6.12.0 minimum. Apart from the lack of easy access/install of apps, and incompatible apps with 6.11.5, is there any downside to this or can I ignore this docker update and community app error? I don't really need any new app and as I won't update the OS, I guess that I won't need updates either as long as my hardware remains the same. Thanks

I have downgraded my two UnRAID servers from 6.12.x to 6.11.5 and after initial tests the downgrade seems to have resolved my issues with sleep S3 (both servers now go to sleep when expected and wake up on WOL without issue). Fingers crossed, it will keep working that way. Unfortunately, as the plugin is unsupported and there is no alternative, this is the only only solution at the moment. [EDIT: main downside at this stage: the community applications plugin doesn't install anymore as it requires 6.12.0 at a minimum. I'm sure it's the case of many other plugins.

Downgraded both servers to 6.11.5, went without a glitch this time, and I did exactly the same thing (copied the bz*files to the flash drive). No idea what went wrong, but thanks for sticking with me and helping me to get back in action. Much appreciated! Now I just have to test the sleep s3 plugin on both servers, hoping that it will work as well as it used too.

I found the issue. I had to select the flash drive in the HDD BBS list in order to make it a non-UEFI boot option in the boot option. I have copied the full backup back to the flash disc and I've booted into the system fine. Phew! No idea why the boot config changed in the first place, as I had made sure to shutdown the server before taking the flash out and to use the same USB port on the motherboard, but at least I'm back and up and running. Will save a backup from unRaid and I'll try to downgrade again... Fingers crossed, I'll keep you posted, thanks again for your help.

Thanks, so I recreated a boot drive using USB Creator without checking the UEFI box, and there is still no boot. I checked with a Win11 install USB drive, and it boots fine, so there is no issue with that. No idea what's wrong. This server was working fine before I tried to copy the 6.11.5 files to the flash drive. Never had a booting issue before, and I had used the USB creator to create the boot disk initially. I'm stumped.

Thanks I'll try to boot after re-creating the drive without copying anything. Do I need to abort that first boot without my config, or is it safe if the boot completes?

I re-created the drive using the USB creator, copied the content of my backup folder that wasn't on the newly created flash (I have many other folders such as extras, logs, packages and files such as hardware and syslinux.cfg- etc). I got a security message on boot, probably because EFI was enabled (the folder was called EFI, not EFI- as on the original flash drive and in the backup). So I renamed it as EFI-, as per the instructions, and I got the same behavior as last time (no boot to flash, direct to BIOS as I make the USB flash drive the only boot option). My question is what happens if I only copy the config folder after following the manual procedure (or the USB creator as I did)? What about the plugins, VMs, screen, etc. Will they be automatically downloaded if they are missing? I also have a couple of .rec files but I suspect these are not needed. I'm just concerned about booting with just the config folder copied and then something going wrong because of the missing files/folders.

Thanks, but as you've confirmed that the partition scheme is correct (single FAT32 partition, UNRAID label) I'm not sure how it would help given that the make_bootable.bat doesn't help. Is there a downside to using the USB Flash creator, and do I have to use it on the same drive, or can I use it on another flash drive to keep the original untouched? I think there is a license issue if I use a different drive. One last question, is the config folder the only folder to copy from the backup? What if there are other folders/files on the original flash drive/backup folder? Thanks again for your help, much appreciated.

Thanks, so how do I recreate the flash drive?

Also how many partitions is the flashdrive supposed to have? I can see only one using diskpart.

I had just tried, it doesn't help. As I had copied all the content with 6.12.6 from the flash drive to a folder, can I reformat the flash drive (as bootable) and copy the content back to it from the folder, without causing issues as I think the license is linked to that specific drive?

I've never experienced copying files making a drive not bootable either. I've resolved the BIOS access, fast boot was enabled and made it tricky to get access. I disabled fast boot, checked that the flash drive was the bootable device, so it's definitely detected and selected as the only bootable device, but it doesn't boot. How can I make it bootable?

Thank you very much for your quick reply. I downloaded the 6.11.5 zip from the link provided, followed the intructions to replace all the bz* files on the flash drive with those from the 6.11.5 ZIP, unfortunately when I put the flash drive back into the server, it's not recognised as a bootable drive, and for some reason I can't even get to the BIOS anymore. I had copied the content of the flash drive before changing anything, but I got the same result after restoring the original bz* files from before the downgrade. In case it matters, I accessed the drive from a win11 x64 pro laptop (Dell XPS 17 9720). I didn't do anything to the drive and it had no errors. Suggestions? The only other backup from the drive (made from UnRAID) dates back to July 2022, unless more recent versions were saved automatically to the cloud. The array has changed since, as I added a few drives, but nothing else that's significant as far as I can remember.

Hi there, Like many other users, I have many issues with the Dynamix S3 Sleep plugin since I upgraded UnRAID to 6.12.x. As the plugin isn't supported anymore (no replies from the devs in the Dynamix thread in months, no new version of the plugin since March 2023, I'd like to downgrade my two UnRAID servers to the last working version, which is 6.11.x. I don't see any other option as there doesn't seem to be a supported alternative to this plugin and the sleep feature is a key feature for me. Please could you advise on the following: 1) Where can I source 6.11.x versions of UnRAID (I can only revert to a previous 6.12.x version that doesn't work). 2) One server is on the latest 6.12.6, the other on 6.12.3, please could you let me know of the steps I should be taking to make sure that I don't lose anything during the downgrade process, specifically going from 6.12 to 6.11. 3) I have never downgraded UnRAID, so any tips you could offer in order to do this safely would be welcome as well as links to any resource describing the downgrade process. 4) I will most likely be stuck with that UnRAID version forever, is there a way to disable the UnRAID upgrade notice? Many thanks!

On top of this sleep issue, one of my UnRAID servers stopped waking up from sleep with WOL and I have no idea why. It works if I put it to sleep manually with the GUI, but it doesn't if the sleep plugin does it. Identical MB to the other server, identical sleep settings, but WOL doesn't work anymore for that server. Neither server supports WOL from shutdown, but they both support it from sleep. Of course I checked the MAC Address, it's correct. Very weird.

Does anyone know if the Dynamix plugins (especially sleep) are still under active development? Not expecting or demanding anything, but it's a bit weird not to get a reply or bug aknowledgement from the dev when quite a few users report the same issues. I have network activity on medium to detect even lower traffic than high, detection of all the disks (including those in the array as array activity is definitely not detected) and user activity on local, but there are still many sleeps happening that shouldn't be. This wasn't the case before. Using power off isn't an option if your MB doesn't support WOL from power off (which is the case for my two UnRAID servers with an Asus MB). Not sure what the CPU bug is when using sleep vs power off? Excluding hours limits the likelyhood of an unwanted sleep, but it keeps the system up for hours unnecessary, so it's a (costly) workaround, not a fix. I hope this will get fixed, either at OS level or at plugin level, I love the dynamix plugins and since I've set them up a few years ago (I use most of them) I barely had any issues. It would be a shame if development had halted.

Sorry for the late reply, I was away. No it's basically broken, it causes the array to go to sleep even before the disk delay kicks in. I had to exclude some hours to make sure it wouldn't sleep the array during the day, while still putting it to sleep at 1am in case I forgot. Please could you provide some info on your Mobo? Any chance to hear from the devs? Is this a known issue and are you working on this? Sleep used to work fine on both of my servers until some recent update, it would be great if that functionality could be brought back. Thanks!

Hi there, Just to report an issue with the S3 sleep plugin. I've been using it for a long time with no problems (thanks for all the great work by the way!), but since a recent update (not sure if it's an unraid update, a plugin update or both) the server goes to sleep during array parity checks, which obviously isn't desirable. It doesn't if I disable sleep of course, which is what I currently have to do to allow the parity check to complete. This happens on my two servers, both with an Asus P8P67 Pro mobo. Unraid is latest stable 6.12.3, plugin is latest 2023.23.23. The plugin is set to sleep after 30 minutes of disk inactivity (it's set to ignore the cache). My Please let me know if you need more details to reproduce and/or fix.

Hi there, I've used this plugin without any issues for a long time, but recently (I assume after an OS or plugin update) it started going to sleep during a parity check. It happens on both my servers, so I have to disable sleep before running a parity check. Is this behaviour to be expected now? Otherwise, sleep works as expected and only goes to sleep with there is no array activity for the specified amount of time. For some reason, it looks like parity check is not considered to be array activity.

Hello, First of all, many thanks for all the excellent work on the Dynamix plugins, I'm using many of these plugins on my two Unraid servers and I'm extrememely pleased with them. I post here because I have a weird issue with the S3 plugin. WOL works fine on one of my servers (Asus P8Z77-V LX), though I had to enable the Realtek adapter and the Realtek BIOS to get WOL to work. On the other (Asus P8P67 Pro), WOL works fine if I manually ask the sytem to go to S3 standby, but for some reason WOL doesn't work (I can't wake the system up when I send the same magic packet to the same MAC address using the same software) if the system goes on stanbye according to the settings in the S3 plugin. The S3 settings are the same on both servers (after 15 min of array inactivity and medium ethernet activity). The "g" parameter is selected and enabled when you check with ethtools eth0. Here is what is reported with the server that works: 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: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on master-slave cfg: preferred slave master-slave status: master Port: Twisted Pair PHYAD: 0 Transceiver: external MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Link detected: yes And here is what's reported for the server that doesn't work: Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on Port: Twisted Pair PHYAD: 1 Transceiver: internal MDI-X: on (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes Can you spot anything that could explain why WOL works when the server is put in stanby manually, but not when the plugin sends it to sleep? I've tried everything in the BIOS of that server: enabling/disabling EPU, enabling/disabling the Intel Ethernet adapter ROM, resetting to defaults and only enabling the wake up with PCI (needed to enabled WOL on the Intel ethernet), I can't find settings that also works when the system goes to sleep by itself and not manually. Many thanks for any help.