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.

Prior to updating to 6.11.1 from 6.10.9 (? not sure if that was it or not, but it was the latest prior to 6.11.1) S3 plugin worked fine and I had no issues with it. Since the update, the NAS does go into sleep mode but immediately re-awakes. I have shutdown, unplugged power and rebooted but the same issue. A cursory look at Syslog seems to show this error after sleep and before re-awake... NAS kernel: Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0): Any idea how to keep my server sleeping? Thanks EDIT: Out of interest I changed S3 to do a Shutdown instead of sleep - it worked fine. Sleep will not work however. Even if pressing sleep off the Main Tab. nas-diagnostics-20221012-1309.zip

A small 'bug' on a page element...... There is an image missing to delete a schedule. "src="/plugins/dynamix.docker.manager/images/remove.png"" Was getting messages in Syslog.

1. It's green. 2. Only scheduled tasks are Move once per day at 13:00PM and a backup at 04:00AM 3. Have already moved all content off disk (Unbalance) and then removed any reference in any share. The drive should be well and truly not used/accessed. And yet I get messages to say it's preventing sleep and timers reset.

Green - active. But I'm sure I have seen it spun down (grey) and the same message issued. Could be wrong so I will double check. Scheduled tasks in the evening only about midnight or early morning. I have already moved everything off the drive and removed from shares etc. It is completely empty. Each and every share is set to exclude the drive. Short of physically removing it, not sure what else I could do to isolate it from the rest of the system. I see that in the syslog that S3 plugin reports both includes and excludes on the disks. Aug 26 16:28:11 NAS s3_sleep: ---------------------------------------------- Aug 26 16:28:11 NAS s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh Aug 26 16:28:11 NAS s3_sleep: excluded disks=sda Aug 26 16:28:11 NAS s3_sleep: ---------------------------------------------- It would be good to move the sdb from included to excluded just for testing! EDIT: If I power all the drives down, the parity and disk 1 spin up almost immediately and then S3 Sleep reports activity on the disk 1. Which is fair enough! With disk 3 spun down (grey on the main sheet) it is not seen with any activity. What I did notice in the Syslog however was that when I do not monitor disk activity, and the disks are 'green' on the sheet, the SYSLOG for S3 Plugin reports: Aug 26 20:34:42 NAS s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh Aug 26 20:34:42 NAS s3_sleep: excluded disks=sda Aug 26 20:34:42 NAS s3_sleep: ---------------------------------------------- Aug 26 20:34:42 NAS s3_sleep: s3_sleep process ID 14830 started, To terminate it, type: s3_sleep -q Aug 26 20:34:42 NAS s3_sleep: All monitored HDDs are spun down so either the system is erroneously reporting all drives are spun down when they are not, or the plugin throws out that message when monitor disk activity is set to No, irrespective of whether the disks are spun down or not. Something is definitely amiss with this disk monitoring. I came across a post from a couple of years ago implying that HDPARM was not reliable in some instances. Perhaps the same might be true of my MB set up - Asrock Z68 Extreme4 Gen3 running an Intel 2500K which has a mix of the Intel SATA ports and Marvel. Dunno, Beginning to grasp at straws now!

Semantics and grammar aside, how does one determine what that 'something' is? Without understanding the cause there is no remedy. Perhaps it's more of a general Unraid question than it is of the plugin itself. All I know is that I have removed as many potential causes that my limited knowledge will allow and then reviewed the SYSLOG when the plugin is in debug mode. I even moved all data off the drive and removed it from shares and any potential docker involvement. And yet still there is a message of activity on SDB. Is there any temporary way to exclude this drive to see if the problem resolves itself or the issue just moves to another disk?

Had done. Made no difference. S3 Sleep thinks there is activity on one specific drive which is not in any share or any docker. I don't have any VMs. Even disabled Cached directories.

Anyone? Seems a bit quiet in here this week! Is everyone on summer hols?!!!

I tried that and no go. That said, toggling the setting (with a Start array inbetween) resulted in TeraCopy not being able to copy as I mentioned above. Am i right to say that changing the Enhanced macOS Interoperability from yes to no will result in the exisiting shares not working?

The option is to 'hide' dot files and it's set to No.

I think the nugget in that article was that many OS's will hide files/folders that begin with '.' . I think in my case the _ is irrelevant because I think my windows backup program attempts to create a folder beginning with a '.', succeeds then it is auto hidden by the Unraid OS and windows cannot find it to then copy the contents of the directory. Hence the windows error message. As a test, I removed the _ from the ._noUser folder name and windows still threw up the same error I described in my OP. So I put it back. But then I thought, what if I manually created the .noUser folder directly in the folder on Unraid using WinSCP. Sure enough the folder was shown as a hidden folder in the Ui. But when I manually copied using Explorer on WIndows to the share, it reported the same error and would not copy. Now here's something really strange........ I did the same copy but using TeraCopy and this time TeraCopy wrote all the files in the windows ._noUser folder to the same hidden directory name on Unraid and then threw up the same error message once it had copied. I know it had copied because I looked at the files via WinSCP. Deffo an issue with dot files/folders from windows to the SMB share.