Mainfrezzer
-
Posts
368 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Mainfrezzer
-
-
I would suggest you use either the IP directly or another nameserver. the .local domains are iffy and according to your logs, you have another mdns service running somewhere
-
Something in your setup is borked. If you would have taken the time to check the IP Adress, you would have noticed the reason for your issue. That IP was used for malicious actions and has a virgin media info on it. It doesnt lead to githubusercontent. Most likely your dns got fiddled with.
Also, the ips belong to amazon, which is odd, considering Github ips have a proper lookup on themselves with "GitHub, Inc." -
Ich bin ja eher verwundert dass der Server nicht crash'd. Würde definitiv abraten macvlan laufen zu lassen.
https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces
Ich hab ja jetzt keine Ahnung welche Brücken/Netzwerktopologie da benutzt werden für die Container aber ich bin neugierig ob's funktioniert mit der 172.17.0.1 IP(ggf. zu X.X.X.1)?
Edit: Nach Begutachtung des Videos wie siehts mit localhost aus? Wenn der container unter hostmode laufen sollte. -
I would say create the peer before you do the manual change. I actually have no clue if adding a peer will change the file like a save does, because, im sure as hell aint giving anyone remote access to my server(and home) apart from myself
-
1 hour ago, karower said:
Mmh, as mentioned above, I used exactly this version.
3 hours ago, karower said:May 6 20:17:52 Server docker: Error: RAM-Disk Mod found incompatible files: 60ad47ed6cadcd544f92bd012d30a4f2 /etc/rc.d/rc.docker 99915e9e302b0df53cb3739951f4e33f /usr/local/emhttp/plugins/dynamix/scripts/monitorshows "99915e9e302b0df53cb3739951f4e33f" which is absolutely not whats in 6.12.10 by default.
You did something in the meantime with the file.
Edit, im a doofus, too many similar posts
but yeah. the file gets modified. Good luck^^
Edit 2: was having a look but i have no clue what rc.docker version that could be from. But yeah basically the whole 6.12.x release had the same monitor file. Theres something seriously changing your files before the go file gets a hand on both of them. Have a look at your scripts and check whats messing with those 2 -
Dont switch to macvlan, that will just crash your server.
Macvtap works differently and is enabled by disabling the bridge in the network settings.
Its up to you if you want to switch. Both works absolutely fine and the guide from the original post still is correct in setting things up with ipvlan.
Setup the first, "Emergency tunnel" which always works when the array is offline (That you can do completely over the vpn manager interface)
then setup a second one "Normal tunnel" which only works when the array is running. (Apart from the initial setup, never save changes in the vpn manager in there, only manually with the file manager plugin, since it removes the shim- from the interface) -
58 minutes ago, Ravinala said:
Hi y all I am facing the same issue, but i can't access my router, nor internet i can just access my home server.
And i can't seem to find a patch after editing the conf files they get overwritten
Thanks for your help!Which Unraid version are you runing? And what "protocol" are you using, IPVlan or Macvtap?
The whole Shebang is not needed anymore with 6.12.10 and the macvtap interface, since it sets the vhost0 correctly and it just work out of the box.
I havent tested ipvlan since, well, my router cant handle it. But since ipvlan still uses the old method (having 2 tunnel just in case), you have to do it manually. Dont use the VPN Manager to make changes, because they alway overwrite the file. Stop the tunnel, navigate to the flashdrive, edit the file with the "Dynamix File Manager", save it, switch back to the vpn manager and just start the tunnel without saving anything. -
Gehen die Anfragen vorher durch die Fritzbox oder wird das PiHole via DHCP an die Teilnehmer verteilt? Die Fritzbox funkt da nämlich zwischen
-
7 minutes ago, long-term-form1240 said:
I incorrectly modified WebUI port to 79 which seems to other default service. And then I could not use WebUI, even when I use GUI mode. How can I change it back in command line or any other way? Thank you for your help.
most likely not the reason for the problem. The problem is that port 79 is by default "banned" on firefox, chrome etc. You could remove the restriction of the browser by diging in their configs but youre probably way faster with modifying the ident.cfg. as mentioned above
-
1
-
-
Of course its gonna have a different "name"/identifier if you use it though usb controller beforehand. Not all usb-sata controller are transparent and the WD-Element build in control boards are clearly changing the drive identification.
you could check "parity is already valid" and then run a parity check afterwards. If it passes it passes, worst case, you have to fix parity. Because im sure you dont wanna put the drive back into the usb enclosure.
The take away from this incident is, you can "stresstest" aka preclear, a drive while its in the enclosure to see if its a dud, but if you wanna integrate it, you should shuck it and attach it via sata directly to avoid such hassles in the future -
Im sure a simple shutdown timer in the go file alongside a timer socket with the "power on on power loss" in the bios will work more reliably than S3 sleep and subsequent recovery.
-
1
-
-
Im confused. The setting is "hide dot files" and no is the default.
-
-
2 hours ago, Johann said:
I like macvlan because it assigns a different MAC address. Is this still the recommended way to use macvlan, by disabling bridging? I have the same behavior in the RX drops as you showed in the videos.
Yes, currently the only way for docker container.
2 hours ago, Johann said:Adding onto the previous question, I see that you are saying macvtap on (is this bridging off?), and macvlan on, doesn't have this issue?
Indeed, but, I currently have the ipvlan bridge enabled because macvlan bridge would cause crashes.
Given that im stuck with a fritzbox too, i picked up the lxc pluging again for any application that needs to be run on a seperate ip.
Overall you *could* just ignore the drops. The only reason i noticed them is that i got a lot of complaints about disconnects from other people after upgrading from 6.11.5 and it took me a while until i figured the issue out. So if you didnt notice anything apart from the number itself, youre good. -
-
12 minutes ago, questionbot said:
binhex qbittorrent vpn docker
wget and curl are not avaliable.
are you sure about that?
-
The drops are caused by the macvtap interface.
I can recreate them on different machines at will. Big issue that you cannot disable the macvtap if you dont need it. The versions where just eth0 is present work without an issue.
https://forums.unraid.net/bug-reports/stable-releases/6126-macvtap-causes-consistent-package-loss-r2836/If you wanna contribute to it^^
Edit: For the funsies, here is the result from my main pc, as before, completely different hardware, completely different cables.
Heres a comparison with an older Unraid version
-
https://forums.unraid.net/bug-reports/stable-releases/6126-macvtap-causes-consistent-package-loss-r2836/
If its not causing any issues like disconnects, you can ignore it for now, if you do, your only solution would be to run a ipvlan bridge -
Run
reiserfsck --check /dev/sdd
and let us know what it says
Otherwise without fiddling around, what i personally would do is to copy all files from the cache to the array or any other space you would have for that and reformat the whole cache drive to xfs, and then move the files back on it. (Especially considering the 2025 deadline but you would have to take care of your array drives at some point too since theyre reiser too)
The drive seems fine, although it does list having 2 UDMA_CRC errors but that could have happend at any point. -
Well, your cache is read only.
(how did you even get reiserfs on your cache drive to work) -
No you cannot do that since the array is inherently not a exclusive share. Only works for pool devices. You might wanna look into disk shares
-
1
-
-
"Header custom text color" should be the one
"Header custom background color" does affect it aswell -
31 minutes ago, sasbro97 said:
I know I have "Preserve user defined networks" activated but thank you.
impossible. your diagnostics clearly show "DOCKER_USER_NETWORKS="remove""
if you had it enabled it would say "DOCKER_USER_NETWORKS="preserve""
Edit:
Your VMs complain about a missing interface aswell -
Glad to see that it wasnt that much money.
but yeah. the file gets modified. Good luck^^
critical temperature reached unrad is shutting down
in General Support
Posted · Edited by Mainfrezzer
"sensors -u" should show your the devices listed under thermal_zone0
Edit:
Although, it seems like this might be the culprit
That seems oddly low of a critical temp, for anything really. You could try to start with "thermal.nocrt=1" to disable the automatic shutdown feature and re-do what you did when it originally triggered while having an eye on the sensor to see which one hit critical.