tnorman

It was intentional. It's set to -1. Only reason was because I was trying to trick it into running longer since it was cutting off while the drives were still temperature wise just fine. The negative value didn't seem to help much though. Think I'll reset it back to 2 which I think was the default.

I'm using Unraid version 6.9.1 2021-03-08 with the Parity Check Timing version 2021.05.14 I turned on the logging. I then started a parity check. It ran for a few minutes and then it was paused by the plugin. About 20 minutes passed by and it did not restart. I ended up cancelling the parity check and turning off logging. The end file is what I've attached. I

Issues with the temperature pausing/restart. It's pausing when disks are still in normal temp range. I started using this plugin because I had a case that I had neglected and needed to finish a parity check before cleaning it out. I don't have AC in the room the computer normally runs, so I figured this would also help with those upcoming hot summer days/nights. Run it at night to do parity checks and pause in case there is a heat issue. Anyway, I replaced a drive and I'm trying to a do a rebuild on the drive. But it keeps pausing the rebuild even though temps are no where near the warning state. (I have a warning temp on all drives of 113 Fahrenheit or 45 Celsius.) It was also doing the same when it was running the parity check. It would pause when temps were still well below, though now it seems even more sensitive when running the rebuild. The plugin is set to pause at -1 (so 114 Fahrenheit or 46 Celsius) and restart at 8 degrees below the warning temp. (105 Fahrenheit or 37 Celsius). Assuming I have those numbers accurate in what I understand from this forum and the help info, then it's pausing when the disks are well below those temps. I had my system set to Fahrenheit. I changed it to Celsius to see if that would affect the problem since I saw a few posts back that you suggested it incase the default wasn't set. But it doesn't seem to matter. (Though with Celsius and now doing a rebuild, it seems almost more touchy than it was when it was set to Farenheit during the parity check.) The latest pause pushed out this notification: Parity Check Tuning: 2021-06-01 13:35 [TOWER] Pause Following drives overheated: parity(31C) disk1(31C) disk2(32C) disk3(28C) disk4(29C) disk5(31C) disk6(31C) disk7(26C) disk8(31C) Parity Sync/Data Rebuild (2.0%% completed)" I cleaned out the case and removed the dead fan that was the primary culprit of the heat issue I was having. I'm not sure why it's stopping as you can see none of the drives are overheating. I would think it would just tell which drive was overheating and not push out info for all 9 drives, but it's saying all 9. If I can help provide anything else, please let me know. I've actually disabled the temp pause feature for the time being so the rebuild can continue, and it's been running with the temperature of the drives staying pretty consistently well below 32 Celsius. But I've got more changes to the system coming. (Replacing another fan, replacing another drive, maybe adding a second parity drive, assuming I can find a way to power an extra drive... honestly I'm running out of room in my current case, so I'm not sure yet... but I know I need some more space coming up. But I'm rambling now... lol. ) Thanks for the plugin, and I appreciate your continued work on it.

K. I didn't check the change log. Thank you for the info. So just got told by the Fix Common Problems plugin that newransomware.bait.plg is deprecated. "This plugin has been deprecate and should no longer be used due to the following reason(s): While this plugin should still be functional, it is no recommended to continue to use it."

So just got told by the Fix Common Problems plugin that newransomware.bait.plg is deprecated. "This plugin has been deprecate and should no longer be used due to the following reason(s): While this plugin should still be functional, it is no recommended to continue to use it."

BTW the attack history shows this: (i've removed part of the ip address which actually corresponds to my main computer. And I changed the username to tempuser. Not sure why it is reporting this user but it is the only one I regularly use for transfering via Samba.) Time Of Attack:Sat, 07 Jul 2018 06:01:32 -0600Attacked File: /mnt/user/BackupbyCABackup_usb/.SquidBanking-DO_NOT_DELETE.xlsxSamba version 4.6.12PID Username Group Machine Protocol Version Encryption Signing----------------------------------------------------------------------------------------------------------------------------------------2997 tempuser users 192.168.*.*(ipv4:192.*.*:56861) SMB3_11 - partial(AES-128-CMAC)Service pid Machine Connected at Encryption Signing---------------------------------------------------------------------------------------------IPC$ 2997 192.168.*.* Fri Jul 6 17:13:32 2018 MDT - -No locked files

Got hit with what I think was a false positive this morning at about 06:01:32. I think a bait file suddenly disappeared while unraid was running Community Applications appData Backup. It reported a possible attack on /mnt/user/BackupbyCABackup_usb/.SquidBanking-DO_NOT_DELETE.xlsx When I look at the log, I noticed Community Applications appData Backup started running at about 0600 at this was in the log. The only line in the system log around that time referencing that folder is this: Jul 7 06:01:31 Tower CA Backup/Restore: Using command: /usr/bin/rsync -avXHq --delete --log-file="/var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log" /boot/ "/mnt/user/BackupbyCABackup_usb/" > /dev/null 2>&1 I'm not 100% familiar what it being done on this line, but after looking up the options for rsync it appears the destination folder has any extraneous files removed by the --delete option. So I assume what happened is the backup was removing the bait files in the folder when it backed up to that share, causing a report of ransomware. Odd that this action hasn't happened before though the backup is set to run at 0600 on the 7th day of every month... so the program is expected to run. I just never had a ransomware attack notice before. Wondering if one of the programs was recently changed and caused the new notice with a change in something I'm adding the folder to the exclude from placing a bait file in the folders. Thought that was already set, but I guess I didn't. Am I correct in what looks to be the cause of this notice?

Thank you. I was getting the same error for the Krusader docker. I was staring at the information for the past 2 days trying to figure out what it wanted me to change. Changed /mnt/disks/ to RW Slave (it was RW prior) and the error went away. Sometimes things are as intuitive as some people think they are and we just need a slap on the back of th head. Tim