This morning I woke up to an alert that my server saying that 11 out of 11 of my drives had errors. I quick rand a diag and turned it off, until I could work on it later tonight. Looking through the longs I'm not sure if this is part of the VT-D kernel bug but i did have it turned on. Any help would be great.

 

tidehunter-diagnostics-20220613-0749.zip

6 hours ago, fatalfurry said:

Looking through the longs I'm not sure if this is part of the VT-D kernel bug but i did have it turned on.

It does look like the exact same issue, which is strange since so far it's only been found on mostly HP and similar servers from the same era, your hardware is completely different, suggest either disabling VT-d or updating to v6.10.3-rc1 which I'm confident fixes this issue, since you have array auto start disabled you can safely boot the server and update, then reboot, start the array and post new diags (same if you just prefer disabling vt-d for now).

P.S. unrelated but I also saw macvlan call traces, those can end up crashing the server.

 

Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.

https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/

See also here:

https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

JorgeB,

 

Thanks for looking into this. After upgrading and disabling things are looking better. I was able to recreate my array and have had no errors with 10.3.

8 hours ago, fatalfurry said:

After upgrading and disabling things

You can leave vt-d enabled with 10.3, release has been out for many days and no more issues about that reported.