rnance

So I did this and it worked for a brief period (several minutes) and then stopped. Same issue. I am now getting a slightly different issue. At first CA was not getting through to the internet. FCP was not giving a failure to access github warning, and unraid connect was not throwing an error. After following This post about manually setting DNS if CA does not load, I was able to get CA working again. However, now docker will not update. All of my apps have "unavailable" listed for the version number and when I click check for updates it shows the blue "checking" symbol for a bit and then just stops. Attached are new logs. Thanks nancenas-diagnostics-20230811-1354.zip

Ok, I set eth1 to no bridging and eth2 back to none for ip assignment. The “two NICs on one network” warning has disappeared, however the system still is not able to access the internet. doing this also removed an entry from the routing table. Attached photos and an updated set of diagnostics nancenas-diagnostics-20230808-1449.zip

Unfortunately this didn’t work. I’ve included my updated diagnostics. I am now also getting a two NICs on one network warning from FCP. Still getting no internet access to docker containers or to unraid. I’ve also included a photo of the routing table. All of these were automatically configured. Eth2 is the docker configured interface. Br0/eth0 is the onboard nic. Both are connected to my network switch. nancenas-diagnostics-20230808-1401.zip

I guess the simpler way to ask this is : 1. Does doecker need bridged access to eth0/br0 in order to get internet if there is internet available on another interface that it has access to.

Ok I'll give that a shot. Would this be an explanation for the inability to write to the cache?

Hi, I recently changed my docker networking configuration to macvlan so that I could see all of the containers with individual IPs on my router. In order to avoid the issues mentioned in many of the forums, I decided to follow the official unraid guide for setting a separate interface that is docker dedicated. This seemed to work for a day and then it crashed. So after looking around, I found that I still have the macvlan calls in my syslog (relevant info attached). After browsing the forum I came across this post which seemed to suggest that if I turn off the bridging in the dedicated docker interface it would fix the issue. I dd this and now none of the containers are able to access the internet. Community apps, docker updates are both showing errors. Fix common problems says it cannot reach github. Is there a way to keep bridging off but allow docker to access the internet.? Is this just a waste of time and turning off bridging will not solve the crashing issue? Thanks! nancenas-diagnostics-20230802-1322.zip MacVLAN before disabling bridging.txt

Hi, I have been experiencing unexplained shutdowns with increasing frequcncy recently. Right now, I get about ~2 days of time before I have to do a hard reset. I thought this was an issue with my macvlan setup (will be setting up a separate post about that) and I have been trying to troubleshoot, however its difficult because once it freezes I cant pull diagnostics. (even via local) However yesterday, common problems alerted me that docker could not write to cache. This has happened once before but a restart fixed the issue. It also said that it could not write to cache (separate of docker) which is new. When I looked at thy syslog, I see many of the errors show below. Does this mean one of my cache drives is failing (a 6 month old Samsung 980Pro M.2 SSD)? I have also included a copy of my diagnostics that I just pulled. It seems odd to me that the drive would fail so soon. Also, it is part of a pool of two (two 1 TB drives) and on my dashboard it shows up as a 1 TB pool. I am assuming that this means the drives are configured in RAID 1 (or the bttrFS equivalent) and as such if I lose one of those drives I will not lose any data. Am I correct in this assumption? I tried to backup the important items on the cache drive, however my download speed was in the kb/s range for some reason. For the whole system, not just the cache drive. Any help would be appreciated. BttrFS.txt nancenas-diagnostics-20230802-1322.zip

Hi, I just updated to V3 and am experiencing a weird error. After running a backup, one of my docker containers was deleted (nextcloud) It was working just fine before the backup. Additionally the appdata is still there for the container, however the container itself is not there. Attached are the log from the most recent backup (which completed with errors) as well as screenshots of the configuration. Why am I getting errors, and how do I get nextcloud back without reinstalling and having to go through all the configuration steps again. Additionally the backup is HUGE. ~50GB backup.log

Hi, I have had my unraid server for about 2 years now. I have WD Red Drives, and a Hitachi drive as my parity drive. About 6 months ago, my server notified my that one of the drives had failed. I bought a new drive and sent the old one back to WD for repair. However I did not get very far. About 5 minutes into the rebuild process, the system indicated that the new drive had also failed(Red X). This process has happened 4 times now. I have either bought new or replaced with refurbished drives sent from WD and the data rebuild fails. Today, I went out and purchased a BRAND NEW 2TB WD RED Drive and installed it with the same problem. What is going on? This has to be an unraid problem because 4 drives bought over 6 months from different sources cannot all be faulty. Attached is everything that is in my diagnostics folder. Hopefully this is enough. nancenas-diagnostics-20171231-1954.zip

I am having the same EXACT issue