KimoB

Weird, now it is working! I will keep an eye on it and see if something changes.

I used these on my 12th gen 12600k. It stopped the message from appearing. That said, I still think something weird is going on, as now I don't get any actual activity, everything just sits at 0%. If I try to use the intel top command, everything is at 0% as well. When I use Plex, I can see on the dashboard it is using hardware to transcode.

I too am experiencing the exact same issue. The most recent change I have made is I upgraded to 6.12.8. I wonder if there is some driver related issue on the igpu side of things?

I am in the process of adding additional storage into my array, where i have 5x4TB, 1x8TB and 1 14TB parity. 3 of my 4TB are over 9 years old, and while they are chugging along, it is time for me to retire them to a second unraid box I use as an additional backup source. I was planning on adding another 14TB drive, and moving data off from the old 4TBs to the remaining 4TB and 8TB drives. During my preclear of the 14TB (on my other unraid box), it started throwing out errors, so I RMAed it. The company did not have any 14TB available, so they sent me a 16TB. Since I would need to rebuild my parity anyways when I remove any of the 4TBs, would it be OK to do the following? 1. Stop array 2. Make note of my config and then reset it 3. Make sure my new parity (16tb) disk is set (after I did a preclear of course) 4. Select my existing remaining data drives that I want to keep (but do not include the old 14TB parity drive) 5 Star array. 6. Wait till the parity is rebuilt 7. Go through the process on adding the old 14TB parity drive as a new data drive. Would that work? Can I skip step 7 and just include the 14TB as one of the data drives? Thank you for any advice.

My subsequent parity checks are coming back as clean, so I suspect i rant into the empty space parity issue.

I did, and it is set to NO, so the mystery continues

Just wanted to provide an update. I am running another parity check, and it is not detecting any errors at this point. The speeds after 50% are also much faster than they were last time. So I am guessing it did do a correction last time it ran, which I didn't think it did on the scheduled parity check since I have it set to NO. (or at least I thought I did.)

The parity finished, and what is interesting, is the pop up message indicated 0 errors, and that it only took 9 hours and 46 minutes (which is the usual time when I had a 4tb drive). It certainly took more time than that. Looking under the main section, this is the output: Last check completed on Tue 03 Jan 2023 03:46:14 AM MST (today) Duration: 1 day, 6 hours, 46 minutes, 13 seconds. Average speed: 72.2 MB/s Finding 709671375 errors This is my parity check rebuild history, and adding an updated diag file. Parity-Check2023-01-03, 03:46:14 (Tuesday)8 TB1 day, 6 hr, 46 min, 13 sec72.2 MB/s OK709671375 Data-Rebuild2022-12-27, 17:44:57 (Tuesday)4 TB9 hr, 46 min, 34 sec113.7 MB/s OK0 Parity-Check2022-12-26, 06:42:50 (Monday)4 TB9 hr, 42 min, 49 sec114.4 MB/s OK0 Parity-Check2022-12-23, 05:57:09 (Friday)4 TB9 hr, 43 min, 16 sec114.3 MB/s OK0 Parity-Check2022-12-22, 07:42:50 (Thursday)4 TB9 hr, 43 min, 18 sec114.3 MB/s OK0 Parity-Check2022-12-19, 06:43:09 (Monday)4 TB9 hr, 43 min, 8 sec114.3 MB/s OK0 I can certainly do another parity with write corrections enabled. homeunraid-diagnostics-20230103-0415.zip

I replaced my parity drive a week ago (new 8TB drive) and did the parity swap procedure as one of my 4TB data drives was reporting errors. (my old parity drive was 4TB) The Parity copy, and subsequent parity check went fine, however when my next scheduled parity check started (sunday night), I am seeing the Sync errors corrected continuously counting up at over 400 million so far. My parity check usually takes 14-15 hours (when the parity drive was 4TB), and it is currently 21 hours, and with 8-9 more hours to go. I don't remember seeing any errors this morning (when it was below 50%, and I suspect the errors started right after the 50% mark, which makes me wonder if it is "correcting" the empty parts of my parity drive? I believe the parity check is set to "not" correct errors since it is the automated run. Adding my diagnostic file. homeunraid-diagnostics-20230102-1755.zip

Hi. I tried to click this link, and I get "You do not have permission to view this topic." Is there a new location for this information?

Thank you, I will give that a shot.

I have been doing some forum searching, and I think I can ignore the following trace that pops up, but figured I would get another set of eyes on it. I have a ConnectX-3 10G adapter setup in a LACP Bond. (br0) I initially added a vlan to this adapter for my web service, and was receiving these trace output's in my syslog. After some googling it seemed to be related to docker and vlans (macvlan) so I decided (yesterday 12/22/22) to remove the web service vlan (80) from br0 and utilize a completely separate NIC attached to the vlan in question and setup br2. I updated the Docker to have access to both br0 and br2. I received what appears to be the same trace output this morning. Is this something I should just ignore, or am I doing something wrong with my network configuration. Dec 23 06:19:29 HomeUnraid kernel: ------------[ cut here ]------------ Dec 23 06:19:29 HomeUnraid kernel: WARNING: CPU: 6 PID: 46 at net/netfilter/nf_conntrack_core.c:1208 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack] Dec 23 06:19:29 HomeUnraid kernel: Modules linked in: tcp_diag udp_diag inet_diag nfsv3 nfs xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat nvidia_uvm(PO) iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls mlx4_en mlx4_core r8169 realtek wmi_bmof x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore i915 iosf_mbi nvidia_drm(PO) drm_buddy ttm i2c_i801 nvidia_modeset(PO) i2c_smbus nvidia(PO) drm_display_helper mpt3sas igb drm_kms_helper intel_gtt i2c_algo_bit ahci agpgart input_leds raid_class Dec 23 06:19:29 HomeUnraid kernel: scsi_transport_sas libahci drm joydev led_class i2c_core nvme syscopyarea sysfillrect sysimgblt nvme_core vmd fb_sys_fops thermal fan wmi video backlight tpm_crb tpm_tis tpm_tis_core tpm acpi_tad acpi_pad button unix [last unloaded: mlx4_core] Dec 23 06:19:29 HomeUnraid kernel: CPU: 6 PID: 46 Comm: kworker/6:0 Tainted: P O 5.19.17-Unraid #2 Dec 23 06:19:29 HomeUnraid kernel: Hardware name: ASUS System Product Name/PRIME Z690-P WIFI D4, BIOS 2014 10/14/2022 Dec 23 06:19:29 HomeUnraid kernel: Workqueue: events macvlan_process_broadcast [macvlan] Dec 23 06:19:29 HomeUnraid kernel: RIP: 0010:__nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack] Dec 23 06:19:29 HomeUnraid kernel: Code: c6 48 89 44 24 10 e8 dd e2 ff ff 8b 7c 24 04 89 da 89 c6 89 04 24 e8 56 e6 ff ff 84 c0 75 a2 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 16 de ff ff e8 2c e3 ff ff e9 7e 01 Dec 23 06:19:29 HomeUnraid kernel: RSP: 0018:ffffc900002e4da0 EFLAGS: 00010202 Dec 23 06:19:29 HomeUnraid kernel: RAX: 0000000000000188 RBX: 0000000000000000 RCX: 4325099371cde41b Dec 23 06:19:29 HomeUnraid kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffa035c0b8 Dec 23 06:19:29 HomeUnraid kernel: RBP: ffff8881fb36df00 R08: 018d601a3f724eba R09: b260b62da2d71bc0 Dec 23 06:19:29 HomeUnraid kernel: R10: 8de059305b16d16b R11: e1f54a9f1120e8df R12: ffffffff82909480 Dec 23 06:19:29 HomeUnraid kernel: R13: 0000000000011ef1 R14: ffff8881b8170700 R15: 0000000000000000 Dec 23 06:19:29 HomeUnraid kernel: FS: 0000000000000000(0000) GS:ffff88903f980000(0000) knlGS:0000000000000000 Dec 23 06:19:29 HomeUnraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 23 06:19:29 HomeUnraid kernel: CR2: 000014e087d3f240 CR3: 000000000420a006 CR4: 0000000000770ee0 Dec 23 06:19:29 HomeUnraid kernel: PKRU: 55555554 Dec 23 06:19:29 HomeUnraid kernel: Call Trace: Dec 23 06:19:29 HomeUnraid kernel: <IRQ> Dec 23 06:19:29 HomeUnraid kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Dec 23 06:19:29 HomeUnraid kernel: nf_hook_slow+0x3a/0x96 Dec 23 06:19:29 HomeUnraid kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Dec 23 06:19:29 HomeUnraid kernel: NF_HOOK.constprop.0+0x79/0xd9 Dec 23 06:19:29 HomeUnraid kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Dec 23 06:19:29 HomeUnraid kernel: __netif_receive_skb_one_core+0x77/0x9c Dec 23 06:19:29 HomeUnraid kernel: process_backlog+0x8c/0x116 Dec 23 06:19:29 HomeUnraid kernel: __napi_poll.constprop.0+0x28/0x124 Dec 23 06:19:29 HomeUnraid kernel: net_rx_action+0x159/0x24f Dec 23 06:19:29 HomeUnraid kernel: __do_softirq+0x126/0x288 Dec 23 06:19:29 HomeUnraid kernel: do_softirq+0x7f/0xab Dec 23 06:19:29 HomeUnraid kernel: </IRQ> Dec 23 06:19:29 HomeUnraid kernel: <TASK> Dec 23 06:19:29 HomeUnraid kernel: __local_bh_enable_ip+0x4c/0x6b Dec 23 06:19:29 HomeUnraid kernel: netif_rx+0x52/0x5a Dec 23 06:19:29 HomeUnraid kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Dec 23 06:19:29 HomeUnraid kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Dec 23 06:19:29 HomeUnraid kernel: process_one_work+0x1a8/0x295 Dec 23 06:19:29 HomeUnraid kernel: worker_thread+0x18b/0x244 Dec 23 06:19:29 HomeUnraid kernel: ? rescuer_thread+0x281/0x281 Dec 23 06:19:29 HomeUnraid kernel: kthread+0xe4/0xef Dec 23 06:19:29 HomeUnraid kernel: ? kthread_complete_and_exit+0x1b/0x1b Dec 23 06:19:29 HomeUnraid kernel: ret_from_fork+0x1f/0x30 Dec 23 06:19:29 HomeUnraid kernel: </TASK> Dec 23 06:19:29 HomeUnraid kernel: ---[ end trace 0000000000000000 ]--- homeunraid-diagnostics-20221223-0626.zip

Thank you for posting this. I also have an Asus z690 board (Prime version DDR4) and am having a very similar issue. I am not sure if it is exactly the same as yours (explanation below) but sometimes when I power on my system, I get the Asus logo for a second or so, and then black screen. I power off / on and sometimes it works fine. I am concerned it is the HBA I just added (9207-8i from theartofserver), and that is when the random boot issue seems to have started. Not sure it is related, or just coincidental. When Unraid does boot, everything looks great. The HBA is working, all disks are seen, etc. I definitely have to get this resolved though, as I want to be confident it will boot up whenever I reboot.

I know this is really late, but there appears to be an issue with the ASM1166 and the Z690 motherboard. There are a few forum posts / reviews that outline a fix. Basically there is a firmware that can be applied to make the asm1166 work with z690 chipset.

Makes sense, let me enable that. I was able to narrow it down to the system hanging at 1:10am MT. (I have pihole running as a docker, and have a nice big gap in my graph.)