philliphartmanjr

Good to hear having c state on could also cause the same problems

Usually on a bad motherboard you can visually look at it and see it's bad. Blown capacitor or the like. Are you sure your network setting are correct? I have had a similar experience to what you are having because the network settings were not correct. I don't just mean the unraid network settings either I also mean the settings on your router and Docker containers. If you try troubleshooting this route I would recommend not letting your Dockers run until you know the rest is working properly then check test and launch your Dockers containers individually

Ah OK. Unless there is something that is needed with .rar files with unraid (which is possible) The only possible problems that I can think of would be bad drive, bad ram, or an issue with the cpu. You are definitely getting logic errors. You have tested your ram and drive and it has check out as far as we can tell. I think we can rule out the motherboard being the issue because unregistered unbuggered ram should be talking straight to the cpu. Unfortunately since ryzens support or ecc memory is a silent support it makes checking if the ecc is working properly. Honestly the only thing I can think of would you be to try regular ram dimm and see if the problem still persists. If yes then it probably is either your drive and the error was not picked up, happens sometimes or the logic in the cpu handling ecc is not working correctly. If the problem goes away then the issue was somewhere in the ecc chain or a bad ram stick that was not detected.

I would either unplug the bad drives or disable them then reboot unraid and see if it is stable then

Sounds like somehow your interface got switched in network settings. This is managed in unraid in settings network then scroll down past eth0 and eth1 you should see interface rules there you can switch which ethernet interfaced is assigned where. Eth0 has to be assigned and functional because that is the one unraid uses for it's self.

I went through your logs have you tried disabling your cache drives to see if your system is normal? whichever one is sdc1 keeps trying to move a file or something and is just sending nonstop errors. particularly with a .rar file for avengers end game. could be a bad file or if that is your ssd it could have a bad cell. and I don't know if this is necessary but do you have nerd pack plug in installed? It has rar and unrar I am not sure if unraid would need that installed to read a rar file it is not something I have ever tried.

Repeating the cpu is a newer thing mostly on CPUs where the pins are on the motherboard. I didn't look at your diagnostics I will do that before I post again. I will say I have had problems with unraid doing similar to me and it ended up being because of it no liking small errors or some minor setting not quite right. Especially network settings have froze my system. I ran a cheep 3rd party pcie card in my old system and it worked great until I upgraded. I don't know if yours is pcie or not maybe try another lane or if you have another PC throw it in there and see if you have any issues with the card. I assuming it's not a raid card, but if it is you will want any parity on the card turned off.

Ok let me clear up my intention for the link. It was not to show you how to how to use memtest to check your ecc I posted the link because it shows how supported ecc systems have a logging functions in BIOS for report errors and it mentions how OS has a logging function windows and Linux. My hope was for you to find one of those to see if it will help you finding a bad stick of ram. Otherwise I would pull the sticks out of your system and put them back in relaunch unraid and see if you problem goes away. I do know with ecc memory it will cause sporadic problems due the t he nature of its self correcting ability. The larger quantity of ram that you have the harder it is to find a bad stick. ECC sticks normally in my experience don't fail very often but if you can either find a bad one or verify they are working it will make it easier to move to another step. Hopefully your BIOS has a logging function.

Sounds like my concerns are not valid. Memtest normally won't find a bad ecc ram because it self corrects. I would take out half of your ram run the system see if the problem is fixed. If not put in the other half and see if that does. I have found by subtracting and adding ram in halves makes the process much faster than 1 at a time. https://www.memtest86.com/ecc.htm This link is Memtest on ecc memory if you want to check it out

I was under the assumption that if you had more than 1 cache drive they needed to be the same type and size. Anyway you probably want to contact your motherboard manufacture to make sure it supports ECC ram. Registered or not most AMD boards do not support ECC memory unless you have ddr5. I found this out the hard way.

Anytime I am glad you got it resolved

I would really encourage reseating the CPU before testing to see if it might be bad because no matter what the test results will be reseating the CPU would be the next step then running the tests again. prime 95 and passmark are the 2 that I use for CPU testing and keep track of its temp during the test. As far as the usb goes I would recommend a different one down the road you can get usb 2.0 flash drives on amazon that are not too expensive. After you check the CPU and if all looks good trying a different USB would be my next step. I have seen older posts where users had issues with USB 3.0 I am not sure if it was fixed or not. Keep in mind that your flash drive needs to be 32g or less I believe unless that has changed and if you find one with slc storage that is more reliable. Also Unraid does not boot from the flash drive. How it works is the contents from the flash drive are offloaded into RAM then the os boots from there. Nothing else happens on the usb unless you make a change in settings add a docker or the like, then the changes happen on the usb and that is it. On the other flash drives that did not work did you reformat them before trying to put unraid on it? If not that may fix that issue.

access point setting should be the same thing as bridge mode could be an issue with different venders not working well together or different types of supported wifi standards or both. Could also be a setting in the Tp link to let it know there is another device being used as an access point. If it was setup as an access point then double Nat was not likely the issue. I have not used either of those brands for a while but i know with asus models they work well together because the main router acts a a controller for the rest. If you are looking at new options unifi is really good as well.

4 passes is probably enough and if it is staying powered on probably not the power supply. i would check the cpu next although in your case you may need another hdd or sdd and boot into windows to do so. could be a motherboard or cpu problem. or since you have just built it check your temps and make sure they are good and reseat the cpu. Even if you are positive you did it right I have found taking the cpu out and reseating it fixes issues like that.

I really doubt you will get 10g speeds with your test. you are going to be limited in this case by either your speed of your nvme or the motherboards capability to transfer the data from the nvme.

what you have may work if you access your belkin device you can look to see if it can be placed in bridge mode. what bridge mode does is it turns off the devices ability to create a network and instead will receive network information from your main device. that is if you want to try and get that setup working. other wise you can do the switch it will work as well. If you did want to have wireless access I would recommend a good wireless repeater. Yes another device working as an access point is better I personally would stay with tp link if you purchased a new one for an access point. Mixing different brands can often lead to some weirdness.

I was looking at your network set up and it looks like you have 2 Ethernet ports one on your motherboard and the other is a USB device and they are bonded. if this is the case you need to make sure that your switch supports the bonding mode you have selected. You could disable bonding and see if this fixes your issue.

It could be a smb problem it may also just be a issue with your set up. I am a little confused on your setup. Are you using 2 modem, router, gateway, wifi combo devices? If so are you sure the one you are using as an access point is compatible? If it is is the access point in bridge mode? if everything was working fine before and your issue is only from the access point iI would personally start there.

I would say my personal preference is to assign a static ip to unraid get it working then if you want you can assign the static ip in pfsense later if you want. Static ip in pfsense is just another layer of complexity. Plus if unraid has a static ip that you know you can always access it if you have to just assign your pc in that same ip range and you are good.

I was reading through this thread, and I am not trying to be mean but i don't think you will be able to pull off straight out switching out your routers in one swoop. I have a pfsense appliance in my home and tried to switch out like mentioned here and it didn't work. my focus in IT is networking with certifications and I can say pfsense is different from any other gateway that I have used and was a much larger learning curve than I expected. I would recommend setting your existing router with at least the main ip address range that you plan on using that way you can configure pfsense and if it does not work no big deal you can just switch back. You mentioned your concern is Plex. Running it locally wont be a problem but getting it set up to run via wan my take you a bit to figure out. If you are buying a pfsense device (that is what i did) depending on which one some of your ports may be on the same physical controller which means you will be stuck creating vlans which will add to the complexity. I do not mean for this to turn you off of the idea I think pfsense is great but i think it will be more involved than you realize. Lastly you really need to put some thought on what you will want to put on your iot network. For example will Plex be iot? If not then what about the devices that will be viewing them? if they are on different ip ranges then plex will go out via wan then back in and that will have an impact on your streaming ability and quality.

Looking through you logs it appears there is an issue with one of your plugins. level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header" I would check them and make sure they are all up to date nerdpack was one of them it is not compatible with your unraid version. your cache I saw you mentioned that you can schedule the mover to run. Your log also showed you do not have Unassigned Devices Plus. there is also a few dockers out of date I would fix these issues first and then reboot

Try going to settings and turning off the docker service and then start it back up again. if that does not work reboot the server, usually one of those will fix the issue.

I have a bit of an update, I have done quite a few things and where I am at now is I am now using pihole and that has fixed some problems since I do not have a local dns. my 2 inic's are still bonded on the 10.0.0.24 and the pcie nic when put on 10.0.1.24 is isolated from the network for some reason. It can not ping out nor can I ping to it. I have white listed both server IP's on piehole and unifi. my 10.0.1.0\24 works fine for other devices. When I ping to 10.0.1.24 from my workstation I get host unreachable from 10.0.0.1. I am not sure if this is normal for unifi but both gateways work 10.0.0.1/10.0.1.1. and I can ping other devices on the 10.0.1.0/24. I aso know that the nic is good I changed 10.0.1.24 to 10.0.0.25 and it works fine. The strangest part is I can access and log into unraid from both 10.0.0.24 and 10.0.1.24 even though I can not ping it. I thought is was a gateway mistyped but everything looks fine. As I finished typing this I noticed on my unifi controller that the ip for the pcie nick is changing on its own from 10.0.1.24 to 10.0.0.24 so a configurtion issue on unraid somewhere? I have included the lasest diagnostics file talonhawk-diagnostics-20220927-1601.zip

It is tuff to say without knowing more about your set up. My guess would be a configuration error somewhere. I would double check your VM setup and make sure you have your cpu assigned correctly and that you have the correct pairs selected for the threads. You may also need to check to make sure nothing else is trying to use the gpu once you pass it through to a vm nothing else can use it.

My guess would be that you need to take off your igpu off of hardware transcoding. An igpu most likely wont be able to transcode a 4k video down to 1080 very fast. Your best bet is to leave the transcoding up to your cpu and it will probably be fine as long as it is only doing 1 or 2.