Schwiing

Members
  • Content Count

    47
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Schwiing

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am too. Thanks for the quick replies and let me know if you want me to test anything else out for troubleshooting.
  2. 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
  3. The check started on 4/1. The update was on 3-30. What am I missing?
  4. I'm confused. Wasn't the syntax error issue resolved with the 3-30 update? Or what syntax error are you referring to?
  5. 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.
  6. 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 notifica
  7. Cool, no worries, and thanks for the explanation. As long as it pauses and resumes properly for scheduled runs on stable, I'm happy
  8. I'd be willing to try it if it were compatible with stable. Is there an incompatibility issue?
  9. Yep, same here. That has been my temporary workaround for now, despite not wanting that behavior long-term.
  10. 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.
  11. I got the same notification. Strange.
  12. This time it worked. Strange. Attached the log + parity tuning files. Parity.zip
  13. 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.
  14. Right, which is very weird. Is there anywhere in my logs I can check if the memory is incompatible or anything else? I have 64GB of ram with no VMs and a handful of dockers that use ~11GB of RAM total. I can't figure out what the issue is.
  15. This is from my syslog last week. I forgot I accidentally turned it off this week, hence the lack of logs for the latest crash: https://paste.ubuntu.com/p/tfNzSNDRGb/