Mr_Jay84

Excellent thanks 👍

Okay great cheers. I now have this error though.

The root of the usb drive?

Where is the .conf located? I can't seem to find it?

Seems like it was down to the dockers being set to use IPVLAN, switching to MACVLAN cured the issues. I've also just discovered Giganet uses CGNAT rendering it useless for my needs due to unable route traffic to my server. I'll contact them tomorrow to see if they can provide a status otherwise it's cancellation time.

What version of Unraid are you guys running?

Will do mate. I'm away for a week. I'll be right on it when I get back. I'll be ditching the connection if unraid won't play nice. No use to me if the sodding server won't work

Yeah this is FTTH too. They did provide an Eero router which I haven't tried Unraid on as yet. There's a few things left to try out. Eeros way to basic for my needs It's really weird how every other device has no issues whatsoever apart from Unraid. Even if it was an MTU issue, why only unraid?

Who's your ISP? I'm using Giganet on Cityfibre.

Did you find a solution to this? I had fibre installed the other week using a PPPOE connection. Exact same issues as you yet all other network devices have no issues at all. I'm using OPNsense and tried both physical and virtual machines. It just doesn't like this PPPOE WAN connection!

I replaced all of mine with Seagate 18Tb drives. All the Reds became backup drives. I never solved the issue, drives just kep throughing up errors ermvery so often.

The issue has not returned since the RC4 upgrade even with PiHole and other known offending containers re-enabled. This is excellent!

Upgraded to RC3 a few weeks back, still the same crashing however as soon as RC4 came out I tried that. It's been up for almost 9 days with no issues so far. This is a record for me, tomorrow i'll turn on piHole again as that's a sure way of causing the previous crashes. Fingers crossed!

Another lockup today not sure if it's related though. Mar 16 15:06:55 Ultron kernel: veth437980e: renamed from eth0 Mar 16 15:06:55 Ultron kernel: docker0: port 26(veth244df90) entered disabled state Mar 16 15:06:55 Ultron kernel: docker0: port 26(veth244df90) entered disabled state Mar 16 15:06:55 Ultron kernel: device veth244df90 left promiscuous mode Mar 16 15:06:55 Ultron kernel: docker0: port 26(veth244df90) entered disabled state Mar 16 15:07:55 Ultron kernel: docker0: port 26(veth90a6157) entered blocking state Mar 16 15:07:55 Ultron kernel: docker0: port 26(veth90a6157) entered disabled state Mar 16 15:07:55 Ultron kernel: device veth90a6157 entered promiscuous mode Mar 16 15:07:55 Ultron kernel: eth0: renamed from vethc67d2ac Mar 16 15:07:55 Ultron kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth90a6157: link becomes ready Mar 16 15:07:55 Ultron kernel: docker0: port 26(veth90a6157) entered blocking state Mar 16 15:07:55 Ultron kernel: docker0: port 26(veth90a6157) entered forwarding state Mar 16 15:07:57 Ultron kernel: docker0: port 26(veth90a6157) entered disabled state Mar 16 15:07:57 Ultron kernel: vethc67d2ac: renamed from eth0 Mar 16 15:07:57 Ultron kernel: docker0: port 26(veth90a6157) entered disabled state Mar 16 15:07:57 Ultron kernel: device veth90a6157 left promiscuous mode Mar 16 15:07:57 Ultron kernel: docker0: port 26(veth90a6157) entered disabled state Mar 16 18:48:14 Ultron kernel: br-caf2c2672c89: port 1(vethdf85790) entered disabled state Mar 16 18:48:14 Ultron kernel: veth6c760c6: renamed from eth0 Mar 16 18:48:15 Ultron kernel: br-caf2c2672c89: port 1(vethdf85790) entered disabled state Mar 16 18:48:15 Ultron kernel: device vethdf85790 left promiscuous mode Mar 16 18:48:15 Ultron kernel: br-caf2c2672c89: port 1(vethdf85790) entered disabled state Mar 16 18:48:15 Ultron kernel: br-caf2c2672c89: port 1(veth400e60b) entered blocking state Mar 16 18:48:15 Ultron kernel: br-caf2c2672c89: port 1(veth400e60b) entered disabled state Mar 16 18:48:15 Ultron kernel: device veth400e60b entered promiscuous mode Mar 16 18:48:15 Ultron kernel: br-caf2c2672c89: port 1(veth400e60b) entered blocking state Mar 16 18:48:15 Ultron kernel: br-caf2c2672c89: port 1(veth400e60b) entered forwarding state Mar 16 18:48:15 Ultron kernel: docker0: port 1(vethc04644b) entered blocking state Mar 16 18:48:15 Ultron kernel: docker0: port 1(vethc04644b) entered disabled state Mar 16 18:48:15 Ultron kernel: device vethc04644b entered promiscuous mode Mar 16 18:48:15 Ultron kernel: docker0: port 1(vethc04644b) entered blocking state Mar 16 18:48:15 Ultron kernel: docker0: port 1(vethc04644b) entered forwarding state Mar 16 18:48:15 Ultron kernel: eth0: renamed from veth3e19731 Mar 16 18:48:15 Ultron kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth400e60b: link becomes ready ultron.log

I've had the onboard NICs turned off too. Assigning IPs to containers is a sure way of causing a crash in under 24hrs. I'm not buying anymore hardware. I've already spent a lot of money replacing pretty much everything and trying out various hardware combinations over at least a year. Upgraded to RC3 today.....so fingers crossed. I'll have to look into other solutions as unRaid isn't reliable enough if this doesn't work.