December 7, 20187 yr Community Expert Any suggestions on call trace and network interface up and downs whilst doing parity check. My Win10 VM also became unresponsive with 100% on one of the CPUs. Machine is ok all the time, issues only appear during check. unraid-diagnostics-20181207-1957.zip
December 8, 20187 yr Community Expert The Intel NIC related call trace is quite common: Dec 7 09:18:34 unraid kernel: NETDEV WATCHDOG: eth0 (igb): transmit queue 1 timed out But all the subsequent NIC resets are not so normal, reboot and see if it happens again during the next parity check, or before. Also you have read/write errors on one of your pool devices: Dec 4 08:13:59 unraid kernel: BTRFS info (device sdi1): bdev /dev/sdj1 errs: wr 40846, rd 4546, flush 115, corrupt 0, gen 0 See here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582 P.S: There were some parity sync errors, were those expected?
December 8, 20187 yr Author Community Expert Thanks I will review your feedback I have just updated BIOS so see if that helps also. Sync errors may have been due to power outage, I am running another check.
December 8, 20187 yr $150 UPS has saved me endless aggravation and headaches. It's easily worth putting off purchasing extra drives for it. I always highly recommend one.
Archived
This topic is now archived and is closed to further replies.