Bob_C

As I only run a full parity check once a quarter, I am not sure when this issue may have arisen since the last check I did. I do not have the Parity Check Tuning plugin so expect the check to take about 12 hours on a 40TB system (5 x 8TB disks incl parity). No Smart errors on any disks. It's housed in an unheated cool area and whilst parity runs, no disk temp goes bout 46C with most of the time the disks operate about 40C. I set the job running and it ran for about 2.5 hours with no issues at which time I logged off the UI to go to bed. Looking at the previous log, it appears the system may have just shutdown even though the S3 sleep plugin is set to monitor for parity check. Have attached my diagnostics file if that helps to figure out what is going on! Thanks nas-diagnostics-20240401-1044.zip

On the 9th January I manually copied a number of directories from my W11 desktop PC to a 'mydata' share on Unraid - about 47GB. These folders show up in the Unraid WEB GUI as well as via SSH (WinSCP) when on the PC. But if I use Explorer on W11 these later directories do not show up. I have rerun permissions and made sure the copied directories have the same permissions as those directories that I can see in Explorer but no joy. The share was a private share but I have since change it to a public share and I still get the same issue. I tried clearing the Net cache on the PC but that didn't help. As far as I know I have not changed anything on my PC or unraid. I also upgraded to 6.12.6 to see if that resolved it. But no. The images below (redacted) show all the files on the GUI, WINSCP and my Explorer (from where I copied the directories originally), but you'll see that when I open //192.168.1.102/mydata/downloads directory over the network, there are a bunch of 'C' directories missing. The only one my PC can see on the share is the cFosSpeed.1 directory. And yet on the GUI (as an example) the 'CTR' directories are there (with others as well). I cannot get my PC to see the directories I copied to the Unraid Server late on the 9th Jan (and any subsequent directories). I am stumped. Any ideas how to resolve this irksome feature? nas-diagnostics-20240113-2251.zip

It is a pity then that on installing this plugin and using the same settings as the old CA plugin, that the new plugin's retention policy then deleted a load of my older backups that I would have kept separate if I had known that non-compatible directories would be deleted.. Why not just have a prompt to keep old backups before the install date?

I would very much like to install this plugin for Jellyfin: https://github.com/ilarramendi/BetterCovers but I am struggling to figure out how to install the docker for this as it's not in the Unraid Apps repository. Any help or pointers would be appreciated! Thank you!

Is there any of the dev team looking at fixing the S3 Sleep problem where if the default SSH port is changed from 22, the plugin does not recognise a remote connection on another port and will shut Unraid down whilst still connected? Thanks.

Except it is no longer valid from the link. https://unraid.net/forum/index.php?topic=36543.0

After a reboot, problem returns.

Is there no interest in getting this issue resolved to allow S3 to 'see' when there is an external connection on a port other than 22? EDIT: I edited the s3_sleep script in /usr/local/emhttp/plugins/dynamix.s3.sleep/scripts Line 314. Change (22|23) to add the port I want to monitor. i.e. (22|23|XXXXX) Works as expected now. EDIT #2: Looks like that file gets replaced with the original on reboot. How do I make this change permanent?

UPDATE: Since upgrading to 6.11.5 the issue has resolved. PC goes to sleep as it used to. So some bug fix has alos cured the S3 issue. YAY!

Can anyone else confirm this issue? Reverting the port back to 22 does result in S3 not shutting down when I am loggd in via WinSCP. I changed 22 to a 5 digit port number and S3 does not appear to check this port.

^

Since the upgrade to 6.11.1 I am experiencing the exact same issue. Was there a solution to this?

Although I have asked the question in the Dynamix thread, I tried this command line to sleep Unraid. echo -n mem > /sys/power/state After a short while this message appears. write error: Device or resource busy Does this point to an issue other then the S3 plugin?

^

Dynamix S3 Plugin - Activity Monitor not working for ports other than 22 I recently changed the unraid default SSH port from 22 to a higher port for security reasons. Since doing that, if I am logged in to unraid via SSH, the S3 plugin does not find any active connection and executes a shutdown. Changing default port back to 22 and it works again.