October 2, 20187 yr Community Expert During parity check call trace happened, also loads of NIC errors in log. The windows VM became unresponsive and the CPU pegged at 100%. After Parity check restarted VM and system is fine no issues. Check time increased by nearly 2 hrs. DateDurationSpeedStatusErrors 2018-10-01, 22:22:1922 hr, 22 min, 18 sec99.4 MB/sOK0 2018-09-01, 20:31:4520 hr, 31 min, 44 sec108.3 MB/sOK0 2018-07-01, 20:14:2020 hr, 14 min, 19 sec109.8 MB/sOK0 running 6.6.1 any thoughts on issue? No issues normally with system just during parity check. unraid-diagnostics-20181001-2226.zip
October 2, 20187 yr Community Expert Intel NIC error is quite common, but it usually recovers OK, your's looks like it didn't, reboot and see it it happens again on the next check.
October 2, 20187 yr Author Community Expert Hi it did recover after check had completed, but also noticed was doing both of them at different points
October 4, 20187 yr Author Community Expert Has anyone else seen performance issues during parity check?
October 4, 20187 yr Community Expert Some users get an unresponsive server during parity checks usually together with NMI events in the log, for those lowering the Unraid tunables usually helps.
October 4, 20187 yr Author Community Expert Thanks Johnnie.Black, seen these values from one of your previous posts: Tunable (md_num_stripes): 4096 Tunable (md_sync_window): 2048 Tunable (md_sync_thresh): 2000 Would these ok values to try?
October 4, 20187 yr Community Expert 14 minutes ago, SimonF said: Would these ok values to try? Depends on your current values, those values are usually good for parity check speed, if your are using lower ones then you need to lower them even more, try 5 or 10% at a time until you notice an improvement.
October 4, 20187 yr Author Community Expert Ok thanks, where the defaults, will try lower, 1280 384 192
Archived
This topic is now archived and is closed to further replies.