mctavish01

nothing is showing on the gui as far as errors Also speeds are going back down to down to 1MBs during parity checks. it goes in bursts and is not constant. although for whatever reason as I opened obs to record it for you it's now maintaining 1gbs for at least 4 mins...

@trurl unraid-diagnostics-20260309-1805.zip could you take a quick look at the attached diag? I assumed my sata card was the issue so I had ordered an LSI 9305 but it is a couple weeks ago and I wanted to try my best to not have something die on me so I just primed another sata card assuming I could at least run a parity check again without errors but with the new card it is also bum slow. can I assume that there may be another issue at play? ram? power? other disks? Let me know what you see. Currently I am not specifically noticing performance issues other than parity is basically not a thing speed wise.

@JorgeB https://www.amazon.ca/MZHOU-Profile-Bracket-Support-Devices/dp/B09K3NFK5H/ref=sr_1_32?crid=39ILKOLEL4715&refinements=p_85%3A5690392011&rnid=5690384011&rps=1&sprefix=asmedia%2B%2Caps%2C164&sr=8-32&th=1 Does this card / brand have any recommendations? Amazon reviews are somewhat typical as its totally fine or it insulted my mother and killed my dog. Specs wise does this fit the bill for unraid?

Looks like a sata cable swap has improved the speeds back to normal. I greatly appreciate the help!

unraid-diagnostics-20260301-1702.zipunraid-safemode-diagnostics-20260301-1733.zip Hey, this is a new issue for me. leaning towards a hardware issue but unsure where to start. I woke up this morning to my server being powered down for an unknown reason. it started a parity check when I booted it up which I was fine with due to not knowing the cause of the shutdown. came back a few hours later and noticed it hadn't even moved a percent. Did a restart, no difference. Updated, safe/maintenance mode, no difference. Dashboard is not showing any specific errors. Any insight would be greatly appreciated.

Hey everyone, managed to google something from 10 years ago. Looks like deleting the config file and restarting the docket fixed it. disregard original issue

Good day everyone, Just noticed this morning I can't access Webui for the docker. Just get a "this site can't be reached", I did auto-update all my dockets a couple of days ago and nothing else since then. (everything was working before the updates) when I check docker logs it just has a repeating "/config/config.xml:1.1: Document is empty" My simple logic says that's likely an issue. How did this likely happen and how can I roll this back?

Good day everyone, got a odd one here. Literally no public torrent will work, magnet links will be stuck on "downloading meta data" downloaded torrent files will go straight to "stalled" Private torrents are totally fine. (I did update just now to see if fixed, it did not) Public flies and magnet links work totally fine just with qbit on my desktop computer. I have made no changes to my networking setup or qbit, just stopped working overnight. Any ideas?

Hey thanks so much for the helping hand ijuarez, I felt I knew how to do something but got scared after I messed up one docker. In short I also have a bunch of ubiquti stuff which I admittedly don't know as much as I want to for networking stuff. Got a hold of a friend who works on that area in IT and just walked me through assigning my server my old address as it's static IP and it all just works now. So all is not good aside from me needed to fix the thing I broke

friendly bump

looks like they are all bridge. Can I just change them all host? I also found where it looks like i can set a static ip for my server but docker/vm needs to be disabled, would that delete my current dockers and would need to reset up?

Forgive me, bit of a noob. no idea why anything changed. there was a bad storm so I shut everything down, the networking stuff is on a UPS so that was fine. when I turned it on, everything went from XXX.XXX.0.34 to XXX.XXX.0.35 and this has lead to dockers not talking to each other.

So seems all my IP address change for server and dockers, now nothing is talking to each other. How can this be corrected without removing dockers and settings and how can this be prevented in the future? The main dockers I need fixed are Jacket,Sonarr and qbit. I already broke qbit by trying something I found on google to change ip manually and it just removed it and all my settings already =\ Please let me know any more info that is needed and the future help. thanks

Thank you so much, this was very clear and fixed my issue =]

I guess I will add to this as myself and a friend have same issues. When writing to array from off server (like unloading gopro footage) our cpu is absolutely pinned causing issues with all dockers and the like, essentially rendering dockers useless while transfer is active. Anything useful we can provide to help resolve the issue?