Unraid server acting weird lately reddit / selfhosted ---------------------------------------------------------------------- trainwreck_summer · 2023-11-07 15:27 I am running unraid on i5 11th Gen, gigabyte mobo with 32 gigs of ram. Been getting weird situations where the server is physically up but I am unable to reach unraid as if it was frozen or something. I've had a usb corrupt on me a couple months back which I replaced with a new one. Today morning I saw the following displayed on my screen. **screenshot attached** To me it is looking like a processor issue but I'm no expert. Please help!!! ---------------------------------------------------------------------- thekrautboy · 2023-11-07 15:41 And how is that about selfhosting? Ask /r/unRAID ---------------------------------------------------------------------- trainwreck_summer · 2023-11-07 15:52 I'm not sure that it is unraid issue. ---------------------------------------------------------------------- thekrautboy · 2023-11-07 15:57 Maybe its a issue with your processor, your RAM or whatever. How does that make it a selfhosting issue? Tons of subs exist for hardware techsupport. ---------------------------------------------------------------------- kitanokikori · 2023-11-07 16:13 Kernel throwing Illegal Instruction, likely either bad RAM or an overheating / faulty CPU ---------------------------------------------------------------------- Far-Lack-3217 · 2023-11-07 17:21 I see macvlan errors. I would change your docker network settings to ipvlan, to see if that resolves the issue. It did for me, but my firewall prefers mac addressed systems for port forwarding, so I had to fall back to macvlan. ---------------------------------------------------------------------- EndlessHiway · 2023-11-07 17:22 Smack it. ---------------------------------------------------------------------- skc5 · 2023-11-07 18:11 FYI I don’t think r/selfhosted has a “no tech support” rule and Unraid is indeed self-hosted. ---------------------------------------------------------------------- thekrautboy · 2023-11-07 18:26 Cute. ---------------------------------------------------------------------- Dalearnhardtseatbelt · 2023-11-07 18:56 Are you using 6.12.4 ---------------------------------------------------------------------- kitanokikori · 2023-11-07 18:57 Uhhh where? ---------------------------------------------------------------------- Far-Lack-3217 · 2023-11-07 19:03 Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)). ---------------------------------------------------------------------- Unlanded · 2023-11-07 19:18 Is it always the same CPU core? Mine would crash every few days with ZFS the apparent culprit, but it was always the same core. I disabled that core and no more crash. Now just waiting to have a second CPU to see if the failure is in the processor or motherboard. Just food for thought. ---------------------------------------------------------------------- kitanokikori · 2023-11-07 19:21 Call stacks mean something fam, you can't just see every single kernel panic and tell people "yeah, definitely macvlan" ---------------------------------------------------------------------- skc5 · 2023-11-07 19:22 It’s probably a good idea to at least be aware of the sub rules if you’re gonna attempt to play Moderator. Have a day. ---------------------------------------------------------------------- thekrautboy · 2023-11-07 19:38 Same goes for you :) ---------------------------------------------------------------------- Far-Lack-3217 · 2023-11-07 20:06 I see macvlan in the kernel dump. Your suggestion is to replace the entire system. Sit down, kid. ---------------------------------------------------------------------- kitanokikori · 2023-11-07 20:27 Where? You see it in the loaded modules list. That means nothing. ---------------------------------------------------------------------- Far-Lack-3217 · 2023-11-07 20:39 I gave a suggestion for the user to try ASAP, yours was to go replace every part in the system. Not helpful, and neither is this BS argument of yours. ---------------------------------------------------------------------- kitanokikori · 2023-11-07 20:41 So that's a "No" then. Got it. ---------------------------------------------------------------------- Far-Lack-3217 · 2023-11-07 20:42 As someone who blah, blah, blahs… just drop your resume and shut the F* UP. ---------------------------------------------------------------------- evilryry · 2023-11-07 22:03 His suggestion was to check thermals and run memtest, not replace parts. This is almost certainly corruption. The error could be caused by many things (including macvlan), but bad components or overheating is the most sensible guess with the given information. Testing is easy and would rule out the most likely cause. ---------------------------------------------------------------------- Far-Lack-3217 · 2023-11-07 22:54 Never commented on that users suggested fix, till my suggestion was attacked. It could be many things, and I submitted a suggestion. You can defend kittykory all you want, I don’t care. Just submitting a suggestion. Move on. ---------------------------------------------------------------------- speculatrix · 2023-11-07 23:38 I would have suggested this too. Bad ram can cause a bunch of odd problems including data corruption. ---------------------------------------------------------------------- 100GHz · 2023-11-07 23:54 Wild guess by looking at the stack trace: you are running out of memory. Can you check how much you have periodically before the next crash ? :) ---------------------------------------------------------------------- dddd0 · 2023-11-08 06:49 Least deranged redditor