Schwiing

I installed devel. On the smart tab I don't see any drives...so I'm assuming I need to run smart tests on all drives via the plugin to get that data. Will report back once my parity check completes.

Thanks for this overhaul! Despite disabling all of the LED options, all of the trays blink red regardless.

I installed the new plugin on unraid 7. Despite the tape drive showing up in system tools, ltfs -o device_list doesn't show my tape drive. Any ideas?

Thanks! Much appreciated!

Apologies, I meant when I click "Action Centre" on the left menu, it says "No matching applications found" and then brings me back to the CA store. If i click "Apps" again, or refresh, it'll happen again and again. I uploaded a screen cap to help illustrate it. 2024-08-30_21-13-01.mp4

I Keep getting the "Action Centre Enabled" banner every time i go to the CA store - usually when i click it i have out of date plugins/containers....but when I click it now it just takes me back to the store, and the banner appears now every time i click apps.

Bigger Array? Would be nice to have more than 30 drives (if that means 3 parity drives, that's reasonable)

unRAID is considered as a product for prosumers/hobbyists/etc. What features would need to be added or changed, in your opinion, to turn unRAID into an enterprise product?

I created a new ZFS pool with 4 disks (2 groups of 2 devices) - a 2 vdev mirror. All went very well...added data and moved some stuff over from my XFS pools. I then put my docker containers on it and migrated the appdata over...all was working. I stopped the array to make another change..and it couldn't unmount my ZFS pool. I tried to do a lazy unmount, then I got: (the pool name is thunder) over and over. Had to perform an unclean shutdown afterwards. Anything I did wrong?

How was the fit with the SST-FS305-12G in the L4500U? Did you need to use the rails or did they fit well without them?

The only issue I have is that I usually update all of my plugins before updating unRAID (based on advice from update assistant). In this case I'm hoping that by the time 6.12 stable comes out, there won't be an issue with leaving this plugin as-is until after the update

Updated the plugin, ran the command but still no joy on the driver download. Updated the plugin, ran the command and still failed to update the driver.

I am too. Thanks for the quick replies and let me know if you want me to test anything else out for troubleshooting.

Looks correct to me: 0 0 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null 0 7 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null 17 * * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null

The check started on 4/1. The update was on 3-30. What am I missing?

I'm confused. Wasn't the syntax error issue resolved with the 3-30 update? Or what syntax error are you referring to?

This was the original check that started at midnight on April 1st (Today). The pause time was scheduled for 0700 and when I checked at 0715, the check wasn't paused, then I started to troubleshoot.

On the latest v3-30 plugin and this morning's parity check did not pause. Furthermore, if I try to set a different time for the pause while the parity check is running, 95% of the time the changes don't stick when hitting "apply". (i.e. changing the pause and resume times). I can toggle the scheduled check to yes or no, but the times usually don't change. I also tried reinstalling the plugin but the same behavior was exhibited. I'm on unraid 6.9.1. EDIT: Changing increment frequency to custom and changing the pause/resume times with crontab format work, but I can't enable sending notifications for pause or resume of increments. Strange. I guess we'll see if it pauses at half past the hour, but it didnt at the top of the hour previously. EDIT 2: No joy. 30 7 * * * pause time had no affect and the parity check continues. Nothing in the log. EDIT 3: Changed the log level to testing (derp. Should have done that to begin with when I discovered it didn't work). Looks like the plugin thinks I kicked off a manual parity check, when it's actually a scheduled one: Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: ----------- PAUSE begin ------ Apr 1 07:37:01 ADRASTEA Parity Check Tuning: DEBUG: Pause request Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: /boot/config/forcesync marker file present Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: progress marker file present Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: manual marker file present Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: disks marker file present Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: ... appears to be manual parity check Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: ...configured action for MANUAL Correcting Parity Check: 0 Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: ----------- PAUSE end ------ EDIT 4: Set "Use Increments for manual parity check" to "Yes" (for testing. Would prefer this to be off regularly) and it paused at the next scheduled time ( I set it to 40 7 * * * ). So, it pauses, but I guess it thought my scheduled check was manual somehow. That seems to be the conclusion of my report.

Cool, no worries, and thanks for the explanation. As long as it pauses and resumes properly for scheduled runs on stable, I'm happy

I'd be willing to try it if it were compatible with stable. Is there an incompatibility issue?

Yep, same here. That has been my temporary workaround for now, despite not wanting that behavior long-term.

At least in my instance, the parity history looks like it finished the parity check, but also has an aborted message (when it paused). Strange.

I got the same notification. Strange.

This time it worked. Strange. Attached the log + parity tuning files. Parity.zip

I can only get my parity check to pause if i set "Use Increments for Unscheduled Parity Check:" to yes. Despite it being a scheduled event, I'm not sure why it won't pause unless setting this option to yes. I'm on Stable unraid with the latest plugin version.