coppit
-
Posts
498 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by coppit
-
-
1 hour ago, ljm42 said:
I think it would be worth trying this plugin with out-of-tree drivers
It was fun decoding the .plg file to manually download and install the files with my laptop. (CA doesn't work without internet.) Based on the output of "modinfo r8125", it looks like the driver installed okay after I rebooted. I don't see any "network is unreachable" errors in the syslog, but that could be chance. Pinging the gateway still fails.
-
After rebooting into normal mode, now sshd is failing to stay up. But then later in the log ntpd comes up fine. What the heck? System diagnostics attached.
Based on the "Network is unreachable" errors, this thread suggested that I disable C states, but that didn't help.
I manually ran "/etc/rc.d/rc.sshd start" after the server was up to get sshd running again. Thank god for the GUI console feature.
I feel like my server is falling apart before my eyes...
-
2 hours ago, ljm42 said:
Disable all containers (starting with any VPN containers) and see if it makes a difference
I stopped the docker service entirely. Oddly, my Windows VM that I was using lost connectivity to the unpaid host at that point. Weird. I hopped on my laptop and disabled the VM service as well. Then I rebooted into safe mode and started the array.
The server still can't ping the gateway or 8.8.8.8. Safe mode diagnostics attached. This is with wg0, docker, and KVM all disabled.
-
2 hours ago, ljm42 said:
Your go script is pretty scary at first glance
but I don't see anything that is obviously problematic.
There's probably a lot of flotsam and jetsam in there dating back to the 5.x days.
2 hours ago, ljm42 said:I do see that wg0 is starting, can you stop it and see if it makes a difference?
Disabled the tunnel and its autostart, and rebooted. No change.
Oops. I forgot to try the other things. I'll reply in a few minutes with those results as well.
-
16 hours ago, ljm42 said:
Disable Jumbo Frames.
You have FCP installed, so it should have warned you and provided a link to:
https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1167702
Thanks for the assistance. I see that it's defaulting to 1500. Did you see something where the MTU was different? I got no warning from FCP.
I stopped VMs and Docker, and manually set it to 1500. Then I re-enabled VMs and Docker, and rebooted for good measure. Still no luck.
-
Could someone please post a screenshot of their Docker settings page? Mine doesn't have the "Docker custom network type" referred to in the release notes.
-
I'm having trouble enabling amd_pstates with my 1950X Threadripper, on an ASRock X399 Taichi motherboard. I have the latest BIOS.
I added "amd_pstate=passive" as a kernel boot option. When I run "cpufreq-info", I see that it's still using "acpi-cpufreq" as the driver.
In dmesg I see "amd_pstate: the _CPC object is not present in SBIOS or ACPI disabled". Given that I see tons of ACPI messages, I'm guessing that ACPI is not disabled.
P.S. I don't know if it's related, but I'm also seeing this:
[Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) ACPI: \_PR_.C000: Found 2 idle states -
In case it helps anyone... I ran
sudo fs_usage -w | grep Volumes.Backupsto see what was accessing my backups volume, besides my backup software. (I'm using Carbon Copy Cloner instead of Time Machine.)
It turns out that Finder was updating every time the directory was being written, because I had a window open to the directory. After closing that window, speeds shot up.
Hopefully that helps someone...
but I don't see anything that is obviously problematic.
[6.12.4] Server can't ping gateway or access internet
in Stable Releases
Posted
I spent some time with SpaceInvaderOne this morning on this. We assigned the server a different IP and everything started working again. Then for fun we assigned the old IP to an IPad, and it exhibited the same behavior. So it's definitely related to my TP-Link XE75 router, and not the server. Ed's only recommendation there was to factory reset the router and set it up again.
So this can be closed as not a bug.
Separately, I also had an issue where the VMs couldn't be reached, but could reach out. (That said, intermittently, I also had issues with the VMs being able to reach the server.) We switched to bridge networking and that issue cleared up as well. I guess I was too eager to follow the release notes. There might be some issue with not using bridge networking, but at this point I don't think I want to delve into it.