eagle470
-
Posts
423 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by eagle470
-
-
2 hours ago, jonathanm said:
If you are on the NEXT branch, you are expected to install updates as you can, and participate with diagnostics if you find an issue. If you don't want to be bugged until the a stable release, you need to be running the stable branch.
I know there are valid reasons to not stay on 6.7.2, but it's not reasonable to expect to treat the NEXT branch as stable.
Its the holiday week and I have a snow storm coming...I'd rather not be troubleshooting while my users are bored and pissed at me...
-
Simple request, I'd like a check box on the NEXT branch where I can ask for the system to not notify me until there is a stable 6.8 release.
Additionally, an automatic polling request for updates would be nice.
-
It seemed to vary, once they came up almost right away, other times they never did after waiting 3 or 4 minutes.
-
I have the same issue with the array not starting properly, pulled diags and reverted to rc3
-
So I disabled WSD and the lone core pegging issue went away. I don't really use it, though I had turned on discovery on my machine for something else the other day. I disabled it on both the UnRAID box and my surface and I'm back to a normal utilization level.
-
All of my containers are back up right now, here are the diags attached as well as TOP WITH the containers running.
-
Here ya go! I shut all my containers off (no VM's) to reduce noise as much as possible.
-
21 hours ago, bonienl said:
How do you know it is WG?
Its my best guess, this wasn't happening before the upgrade and I don't recall it happening until after installing WG.
-
Wire Guard seems to be pegging a specfic core (changes after service or system restart) rather than load balancing across cores. Is this to be expected?
-
In 6.7.2 when powering on the system, I have the array set to auto start. It always took less than 30 seconds for the array to auto start, I had to wait for more than a minute after upgrading to 6.8-rc1 for everything to come online. It's not a HUGE issue per say, but I thought the change was worth noting. Let me know what trouble shooting steps you'd like to see.
-
Just installed 6.8-rc1. Holy cow was the load tiem for the array slower than normal (diags attached.)
Wireguard is super slick and was very easy to setup, however, I'm not sure it's routing properly as I cannot get to local assets within my primary subnet, such as pihole and my unraid box. I'm using the "Remote Access to LAN" setting.
Will trouble shoot throughout the day as I get time.
unraid1-diagnostics-20191013-1644.zip
-
1 hour ago, trurl said:
The preferred way to edit would be to go to Settings - Network Settings, but I suggested deleting to get to default as a way to reset before editing.
The second NIC was not available for editing and I've always hated the "start from scratch" default answer. I've seen no negative reprocussions from my manual edits after rebooting.
-
2 hours ago, trurl said:
Delete config/network.cfg from your flash and reboot to get default network settings.
I just edited the config file to remove eth1 and it's config. That should solve it after the reboot.
-
On 4/13/2019 at 1:50 PM, bonienl said:
Your diagnostics tell otherwise.
# Generated settings: IFNAME[0]="eth0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="10.10.1.233" NETMASK[0]="255.255.255.0" GATEWAY[0]="10.10.1.1" DNS_SERVER1="10.10.1.1" DNS_SERVER2="8.8.4.4" DNS_SERVER3="8.8.8.8" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" IFNAME[1]="eth1" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="10.10.1.234" NETMASK[1]="255.255.255.0" GATEWAY[1]="10.10.1.1" SYSNICS="2"OK, so at one point I had a tyan motherboard with two NIC's on it. I've moved to a different hardware set (AMD) and no longer have this. I can find instructions for removing this ghost NIC in Cent, but they don't seem to apply to unRAID. Please advise. Thank you
-
First, I only have one NIC, second, I’m not sure how I would have done what you’re saying or how I would undo it...
-
On my system, no DNS servers could be contacted. I tried: OpenDNS, Google DNS, Comodo, Cloudflare. None of it worked. I attached diagnostics and images of the issue.
-
Oh, well, of course I did.
-
I see nothing that was suggested at this point.
-
I've also discovered the CA plugin is no longer working properly due to DNS. Neither was speedtest.net.
I've rolled back to 6.6.7 at this point.
-
I'm getting some DNS errors that don't make sense. Uploaded logs. System claims to not find DNS, DNS is google and I'm not blocking it. Not sure what the deal is.
-
I wonder if the time out changes happened in Unraid or are being screwed up due to old plugins or something.
-
8 minutes ago, mrbilky said:
google but I didn't change it from rc5 to rc6 so it works on rc5 was I supposed to change it due to the upgrade? Funny thing to my other server an R710 is working fine with rc6 but the DNS is the routers DNS
Sounds like a time out issue, maybe? Were DNS time out settings changed anywhere?
-
an ability to download and upload the patches in an offline capacity would be fantastic.
-
I would possibly pay for this feature as well. In fact, it's something I requested a while back!
Unraid OS version 6.8.0-rc7 available
-
-
-
-
-
in Prereleases
Posted
I don't want to patch this week as I expect I will need my system online full time starting Wednesday and I've found 6.8-rc6 to be stable enough for me. I just don't want the notification now that my system has found an update available.
Patching means a certain level of risk, while I'm understanding and generally prepared for that, I don't want to deal with a 1 year old and no Sesame Street and we can't leave the house...Also all my other users would be frustrated too.....