cybersteel8

I have 5 errors in my most recent scheduled (uncorrecting) parity check. I also do scheduled btrfs scrubs and determined the disk and file at fault. I would like to use what's on the parity disk to replace the data that's on the affected disk. A correcting parity check would update parity with the errored data, which I do not want. I trust my parity for these bits so I'd like to use them to repair the disk's data. Does Unraid have a way to do this?

I'm getting the API failure too. Does it have to do with the self-signed certificate that was regenerated? I've mapped the TCP and UDP port on the container, both 7777

I just noticed that the Shinobi app is no longer here. Has support stopped for the template? Should I remove it and migrate to a supported one?

This link does not work, so maybe this endpoint is offline. I would like to reinstate the request for nethogs to be added to Nerdtools as it would be an extremely valuable tool. Never mind, this plugin is unmaintained, so I have no expectation of these feature requests to be fulfilled. Ah well.

Hey @ich777 There is some lowlevel updates to how docker containers for Counter Strike Global Offensive are built, and I have found some information from Valve about this. It may be relevant for your CSGO image, as well as maybe some other Valve game images. https://www.reddit.com/r/GlobalOffensive/comments/10szs27/additional_details_for_linux_community_server/ https://gitlab.steamos.cloud/steamrt/sniper/platform/-/tree/steamrt/sniper I am still able to run my dedicated server using your image (had to update sourcemod though) but I wonder if there's compatibility concerns for the future.

I am having this problem as well, after Steam successfully using the LANCache it eventually comes up with "Forgetting cache type LANCache on host due to chunk timeout" and refuses to use the cache for the rest of the download. I hope we can get some help with this!

Ah, so a btrfs scrub actually documents the names of the files that are corrupt? That's incredibly useful to know, thanks!

Thanks. Due to the following test, I have now run a correcting parity check, and it corrected the 5 errors. I have done this and the results seem successful. After the correcting check, I ran a non-correcting check immediately without rebooting at all. There were no errors detected in the non-correcting check. Would the diagnostics still be useful, considering the second parity check resulted in no errors? I am unsure if it is safe to assume that my hardware is fault-free, but I suppose if I keep getting parity errors, diagnostics would become more useful. I think this is something I will keep an eye on, but not worry about. I'd like your opinion on this. -- It seems the answer to my original question is that, when a non-correcting parity check results in errors, no action is taken by Unraid. A second parity check will show the same errors. The action that ought to be taken by the user is to run a btrfs scrub on all of the array drives to determine if there are any problems with the data on the drive. If the btrfs scrubs result in no errors, then the errors are on the parity drive, so a correcting parity check is appropriate. Another non-correcting parity check after correcting parity is appropriate, to ensure that parity is indeed in a valid state. "If there are errors as a result of the scrub, then that drive should be rebuilt from parity, as the parity mismatch is from the data not the parity" - This is my assumption. I would appreciate a comment on this to know if my assumption is correct.

My last good parity check was a month ago, and unfortunately I have rebooted since then, as I upgraded from 6.9.2 to 6.10.1 and that requires a reboot. It was not unclean.

I still don't know how to determine which files are affected. I don't even know which drive I would want to rebuild, if I took this approach. How do I know which files are affected? Thanks. I have done this on all my array drives, and no errors were found on any of them. Does this mean the error was on the parity drive and not on my data drives? Do I know this with confidence?

I am using btrfs - how do I find out if the errors are in data or parity? I understand that a correcting parity check will update parity, but what if the errors are in the data, not the parity? How would I fix the data using the parity information?

My monthly parity check completed with 5 errors. This is in my syslog: kernel: md: recovery thread: P incorrect, sector=1962934168 kernel: md: recovery thread: P incorrect, sector=1962934176 kernel: md: recovery thread: P incorrect, sector=1962934184 kernel: md: recovery thread: P incorrect, sector=1962934192 kernel: md: recovery thread: P incorrect, sector=1962934200 [...] kernel: md: sync done. time=82684sec kernel: md: recovery thread: exit status: 0 There is no other messages in my syslog related to the parity check. I don't actually know what happens now. Unraid says there were 5 errors, but all my disks are still active, nothing's simulated or whatever. What action did Unraid take once these errors appeared? As it was non-correcting, did nothing happen? It just reports them and that's it? Which files are these in particular - is there a way to know? Do I need to know? I don't know what action I take once errors appear in the non-correcting parity check.

I successfully updated from 6.9.2 to 6.10.1 I was initially concerned when looking at the Main tab, seeing all my drives mounting one by one with 0TB, but after the Array finished starting up, everything is fine. So don't be worried if you notice this! I really like the new dashboard graphs, and the btrfs schedule-able features. Very exciting!

Hi all, I am new to using the Dynamix Auto Fan Control plugin, and I would like to ask - can this plugin control multiple PWM controllers at once? I have my fans plugged into different pins on my motherboard, so they are independently controllable. Can the plugin modify the fan speed of all of these fans, or only one controller?