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.