daTroll

Yeah, that could be it.. I'm running 6.12.0-rc2. The files you asked for are attached (the server hasn't been rebooted yet after the last parity check). parity.check.tuning.progress.save parity-checks.log untroll-diagnostics-20230418-1115.zip

Using version 2023.04.08 for the first time, the Action in my History page has only a hyphen ("-") for the most recent run which was completed at noon today. It was running in 4 increments according to the same page. Normally, I would expect the Action to show "Scheduled Non-Correcting Parity-Check" like it did in March.

I just installed 6.12.0-rc2. The 2Hz "disco flashing" of my HDD activity LEDs, while the drives are shown as inactive in the UI Dashboard, is still the same as before. The fans are still running when the entire HDD array is spun-down.

Tiny cosmetic request: the next time you update this plugin, can you please remove the "v" prefix in the version designation? Most of my other plugins use the same YYYY.MM.DD format but without any "v" prefix. Occasionally I like to sort the list of plugins in the WebUI based on version, to quickly identify the oldest/newest. Cheers, T

Tiny cosmetic request: the next time you update this plugin, can you please remove the "v" prefix in the version designation? Most of my other plugins use the same YYYY.MM.DD format but without any "v" prefix. Occasionally I like to sort the list of plugins in the WebUI based on version, to quickly identify the oldest/newest. Cheers, T

On my side, the status says “Running” in green. On your suggestion, because the Sleep plugin is no longer working also in my system, I changed the first setting to Disabled. This changed the status to “Stopped” in orange, and like you I seem to recall this is what it said in the past (before the most recent update) as well. I changed the setting back to Sleep, but going to sleep it does not. 🤷‍♂️ I’m sure I haven’t touched any configuration since it was working, except for installing a few updates including the latest Sleep plugin.

I encountered the same problem in September. It isn’t possible to back out 6.11 if you’re using an SSD.

The new version of the plugin is showing the correction/noncorrection mode and the support link is working!

I ran a new test for 26 minutes, cancelled, then waited 20 minutes. The history is still not showing whether I had enabled corrections or not, it now just says "Manual Parity-Check". Secondly, installing a plugin that does a whole lot more than I want is increasing the complexity of my setup and therefore also the risk for undesirable side effects later. I only want the history display to be a little more informative. I don't have any need for incremental parity-checks etc. Thirdly, the plugin provides a link to a support thread that is invalid: https://unraid.net/forums/topic/78394-parity-check-tuning Cheers, T

I expected something like that. After installing the plugin, I tried running manual parity checks, once with and the other without the corrective checkbox ticked. As this takes nearly two days on my system, I then cancelled the processing. Both tests say only "Parity-Check" in the Action column, just like before I had this plugin in my system. It will however be helpful to see future scheduled runs with a different Action, and then any manual run could be implicitly assumed to be corrective. Not perfect but it goes half the mile.

Thanks for the suggestion! I've installed this plugin and I see two additional columns in the history: Elapsed Time and Increments. Where can I see the indicator for corrective or non-corrective parity-check?

Please? In addition to Action, Date, Size, Duration, Speed, Status and Errors, I think it could be nice to see whether a parity-check was run as corrective or non-corrective. Cheers, T

I noticed that @SpaceInvaderOne recommends to remove all fruity entries in the SMB config in a recent YouTube video about UnRAID & TM. I recently added a new disk to my array, and tried to move my TM backups to this. It worked for two of my Macs, but for one it failed. I then tried the recommendation to remove the fruity entries, but still no joy. I had to rebuild the backup from scratch. This worked however subsequent incremental backups got the error "Failed to attach using DiskImages2"... Then I reconfigured the SMB with the following: (Some of the lines were there before as well.) I don't know which line fixed it but incremental backups are running fine now. Hopefully this helps someone, and perhaps @SpaceInvaderOne could do a follow-up video.

Issue solved! This is not a request for support, only intended to help someone who is perhaps facing the same issue I was. My server has an internal slot for an M.2 PCIe nvme SSD that I use as a cache for the appdata, domains and system shares. The server is on standby during nights using the Sleep plugin. After a wake-on-LAN ping from my iPad in the morning, the cache drive failed to mount. I saw log entries saying I/O error on dev/loop2, and mc displayed the device name in red with a question mark under /mnt. A reboot always solved it, until the next WOL. Other posts here made me double-check that my docker apps were correctly configured with all folders in place, then I suspected a hardware issue. My SSD is less than a year old, but it appears that some controller chips don't support sleep/wake modes. I replaced the SSD with a different make & model, and now the issue is fixed! The SSD that didn't work is a GAMMIX S50 Lite 512G-CS. The replacement is an Innovation IT SSD M.2 256GB. Cheers, T

I've applied your patch but I don't see any new configuration setting for the S3 Sleep plugin. Did I do something wrong, or it's normal?