jmt380

I DM'd you my diagnostics. Looking into this further on my end. The error log seems to indicate an issue at line 16 of the CustomMerge.php script. Line's 15 and 16 of that script are: $smartALL = '/boot/config/smart-all.cfg'; if (file_exists($smartALL)) $var = array_merge($var, parse_ini_file($smartALL)); My flashdrive does contain the file smart-all.cfg. It looks like the reason that file exists on my flashdrive is because I had enabled notifications for attribute 188 under Global Smart Settings...I'm not really sure why I did that, or if possibly that was the default way back when I originally installed Unraid. Regardless, it is my understanding that attribute 188 is now NOT enabled by default in Unraid. I unchecked the box for attribute 188, and now my /boot/config/smart-all.cfg is blank. I am guessing this has likely solved my issue. I will perform a manual parity check over the next day or two and report back.

Good Evening, I am observing the following entries in my syslog every 7 minutes when a parity check is in progress: crond[1196]: exit status 255 from user root /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null Whenever this message appears in the syslog, the phplog records the following message: [03-Apr-2024 16:36:27 America/New_York] PHP Fatal error: Uncaught TypeError: array_merge(): Argument #1 must be of type array, null given in /usr/local/emhttp/plugins/dynamix/include/CustomMerge.php:16 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/include/CustomMerge.php(16): array_merge(NULL, Array) #1 /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php(333): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix/include/CustomMerge.php on line 16 I am currently running version 6.12.9 of Unraid and version 2024.02.15 of the Parity Check Tuning plugin. I did upgrade Unraid from v6.11.5 to v6.12.9 very recently. I do not capture and retain my syslogs, so I don't know if this was an issue before, or if this is something new. I perform a parity check every 2 months, and can't remember if I saw these errors last time or not. Do you have any insight as to why I might be seeing these messages in the syslog? Thank you for your time.