Mr_Jay84

Yes mate I did exactly that and also add the folders to the container by adding additional paths. Unsure if that's a necessary stage though but it worked for me.

Got it working now, thanks awfully mate!

Does the script need to be executable? I placed it in the folder yet no add-ons downloaded.

I'm also struggling with this. Any ideas on how to inject the scripts into the container?

Hello Guys About two years ago I was using ARM in a VM to backup DVDs to ISO files which worked wonderfully, until I deleted the VM by accident that is lol. I'm using ARM (2.6.67) in a docker now in yet MakeMKV will only now rip to MKV, surely I can set this to rip to ISO as before? Additionally, I installed MakeMKV standalone in docker on the same machine which can rip straight to ISO. I'm obviously missing something here??

They are located in /boot/config/plugins/user.scripts/ (user scripts plugin)

I have an error stating my pre and post scripts are not executable even though they are. Chmod them again, still same error.

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.

I've tried three different lan cards in various slots over the last few months. This happens using onboard NICs and PCI NICs

And again this morning..... ar 11 07:05:25 Ultron kernel: docker0: port 25(veth02cb09c) entered disabled state Mar 11 07:05:25 Ultron kernel: docker0: port 25(veth02cb09c) entered disabled state Mar 11 07:05:25 Ultron kernel: device veth02cb09c left promiscuous mode Mar 11 07:05:25 Ultron kernel: docker0: port 25(veth02cb09c) entered disabled state Mar 11 07:05:39 Ultron kernel: ------------[ cut here ]------------ Mar 11 07:05:39 Ultron kernel: NETDEV WATCHDOG: eth1 (igb): transmit queue 0 timed out Mar 11 07:05:39 Ultron kernel: WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:477 dev_watchdog+0x10c/0x166 Mar 11 07:05:39 Ultron kernel: Modules linked in: xt_mark xt_comment ipvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap nvidia_modeset(PO) nvidia_uvm(PO) veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod uinput nvidia(PO) ipmi_devintf nct6775 hwmon_vid corefreqk(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables igb i2c_algo_bit mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif drm_vram_helper drm_ttm_helper ttm kvm drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel drm mpt3sas aesni_intel crypto_simd cryptd rapl intel_cstate backlight i2c_i801 agpgart i2c_smbus ahci syscopyarea raid_class sysfillrect sysimgblt intel_uncore fb_sys_fops corsair_psu i2c_core scsi_transport_sas libahci acpi_ipmi Mar 11 07:05:39 Ultron kernel: ipmi_si wmi button [last unloaded: i2c_algo_bit] Mar 11 07:05:39 Ultron kernel: CPU: 8 PID: 0 Comm: swapper/8 Tainted: P S O 5.14.15-Unraid #1 Mar 11 07:05:39 Ultron kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./EP2C612 WS, BIOS P2.70 11/15/2019 Mar 11 07:05:39 Ultron kernel: RIP: 0010:dev_watchdog+0x10c/0x166 Mar 11 07:05:39 Ultron kernel: Code: bd af 00 00 75 36 48 89 ef c6 05 4c bd af 00 01 e8 7f f6 fb ff 44 89 e1 48 89 ee 48 c7 c7 3e ac f2 81 48 89 c2 e8 c0 4f 11 00 <0f> 0b eb 0e 41 ff c4 48 05 40 01 00 00 e9 65 ff ff ff 48 8b 83 90 Mar 11 07:05:39 Ultron kernel: RSP: 0018:ffffc900065e8ec8 EFLAGS: 00010282 Mar 11 07:05:39 Ultron kernel: RAX: 0000000000000000 RBX: ffff88810c114438 RCX: 0000000000000027 Mar 11 07:05:39 Ultron kernel: RDX: 0000000000000003 RSI: ffffc900065e8d50 RDI: ffff88905fa18570 Mar 11 07:05:39 Ultron kernel: RBP: ffff88810c114000 R08: ffff88a09ff0b460 R09: ffffffff826232c8 Mar 11 07:05:39 Ultron kernel: R10: 0000000000000001 R11: ffff88a09ff6b947 R12: 0000000000000000 Mar 11 07:05:39 Ultron kernel: R13: 0000000103532600 R14: ffffc900065e8f10 R15: ffffffff816952ae Mar 11 07:05:39 Ultron kernel: FS: 0000000000000000(0000) GS:ffff88905fa00000(0000) knlGS:0000000000000000 Mar 11 07:05:39 Ultron kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 11 07:05:39 Ultron kernel: CR2: 00007ffea1d3fff8 CR3: 0000001d2c74a002 CR4: 00000000001726e0 Mar 11 07:05:39 Ultron kernel: Call Trace: Mar 11 07:05:39 Ultron kernel: <IRQ> Mar 11 07:05:39 Ultron kernel: ? netif_tx_lock+0x83/0x83 Mar 11 07:05:39 Ultron kernel: call_timer_fn+0x59/0xde Mar 11 07:05:39 Ultron kernel: __run_timers+0x140/0x17e Mar 11 07:05:39 Ultron kernel: ? enqueue_hrtimer+0x62/0x69 Mar 11 07:05:39 Ultron kernel: ? recalibrate_cpu_khz+0x1/0x1 Mar 11 07:05:39 Ultron kernel: run_timer_softirq+0x19/0x2d Mar 11 07:05:39 Ultron kernel: __do_softirq+0xef/0x218 Mar 11 07:05:39 Ultron kernel: __irq_exit_rcu+0x52/0x8d Mar 11 07:05:39 Ultron kernel: sysvec_apic_timer_interrupt+0x66/0x7d Mar 11 07:05:39 Ultron kernel: </IRQ> Mar 11 07:05:39 Ultron kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Mar 11 07:05:39 Ultron kernel: RIP: 0010:arch_local_irq_enable+0x7/0x8 Mar 11 07:05:39 Ultron kernel: Code: a2 60 1b 00 85 db 48 89 e8 79 03 48 63 c3 5b 5d 41 5c c3 9c 58 0f 1f 44 00 00 c3 fa 66 0f 1f 44 00 00 c3 fb 66 0f 1f 44 00 00 <c3> 0f 1f 44 00 00 55 49 89 d3 48 81 c7 b0 00 00 00 48 83 c6 70 53 Mar 11 07:05:39 Ultron kernel: RSP: 0018:ffffc9000634fea0 EFLAGS: 00000246 Mar 11 07:05:39 Ultron kernel: RAX: ffff88905fa2a980 RBX: 0000000000000002 RCX: 000000000000001f Mar 11 07:05:39 Ultron kernel: RDX: 0000000000000008 RSI: 0000000000000008 RDI: 0000000000000000 Mar 11 07:05:39 Ultron kernel: RBP: ffffe8efff43f100 R08: 00000000ffffffff R09: 071c71c71c71c71c Mar 11 07:05:39 Ultron kernel: R10: 0000000000000020 R11: 000000000000023d R12: ffffffff82110ba0 Mar 11 07:05:39 Ultron kernel: R13: 0000000000000002 R14: 000033018915a577 R15: 0000000000000000 Mar 11 07:05:39 Ultron kernel: cpuidle_enter_state+0x117/0x1db Mar 11 07:05:39 Ultron kernel: cpuidle_enter+0x2a/0x36 Mar 11 07:05:39 Ultron kernel: do_idle+0x1b7/0x225 Mar 11 07:05:39 Ultron kernel: cpu_startup_entry+0x1d/0x1f Mar 11 07:05:39 Ultron kernel: secondary_startup_64_no_verify+0xb0/0xbb Mar 11 07:05:39 Ultron kernel: ---[ end trace 558bc4d050503d86 ]--- Mar 11 07:05:39 Ultron kernel: igb 0000:09:00.0 eth1: Reset adapter Mar 11 07:05:41 Ultron kernel: igb 0000:09:00.0 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Mar 11 10:41:11 Ultron kernel: microcode: microcode updated early to revision 0x46, date = 2021-01-27 Mar 11 10:41:11 Ultron kernel: Linux version 5.14.15-Unraid (root@Develop) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP Thu Oct 28 09:56:33 PDT 2021 Mar 11 10:41:11 Ultron kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot nomodeset pcie_aspm=off pci=noaer isolcpus=22-23,46-47 Mar 11 10:41:11 Ultron kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 11 10:41:11 Ultron kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 11 10:41:11 Ultron kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'

I've had some success of late by turning off the bonding on eth0,eth1 and assigning everything to a dedicated NIC. I installed TubeArchivist this morning and assigned its own IP, A few hours later...complete lock up again. Mar 10 11:10:27 Ultron kernel: eth0: renamed from veth50eda3d Mar 10 11:10:27 Ultron kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth39e9426: link becomes ready Mar 10 11:10:27 Ultron kernel: docker0: port 8(veth39e9426) entered blocking state Mar 10 11:10:27 Ultron kernel: docker0: port 8(veth39e9426) entered forwarding state Mar 10 11:10:46 Ultron kernel: ------------[ cut here ]------------ Mar 10 11:10:46 Ultron kernel: NETDEV WATCHDOG: eth1 (igb): transmit queue 0 timed out Mar 10 11:10:46 Ultron kernel: WARNING: CPU: 0 PID: 13 at net/sched/sch_generic.c:477 dev_watchdog+0x10c/0x166 Mar 10 11:10:46 Ultron kernel: Modules linked in: ipvlan vhost_net vhost vhost_iotlb tap kvm_intel kvm xt_mark xt_comment xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle tun nvidia_modeset(PO) nvidia_uvm(PO) veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod uinput nvidia(PO) ipmi_devintf nct6775 hwmon_vid corefreqk(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables igb i2c_algo_bit x86_pkg_temp_thermal intel_powerclamp coretemp mxm_wmi ipmi_ssif drm_vram_helper drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd cryptd rapl drm intel_cstate mpt3sas intel_uncore backlight agpgart i2c_i801 ahci syscopyarea i2c_smbus sysfillrect sysimgblt raid_class corsair_psu fb_sys_fops i2c_core scsi_transport_sas libahci acpi_ipmi Mar 10 11:10:46 Ultron kernel: ipmi_si wmi button [last unloaded: kvm] Mar 10 11:10:46 Ultron kernel: CPU: 0 PID: 13 Comm: migration/0 Tainted: P S O 5.14.15-Unraid #1 Mar 10 11:10:46 Ultron kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./EP2C612 WS, BIOS P2.70 11/15/2019 Mar 10 11:10:46 Ultron kernel: Stopper: multi_cpu_stop+0x0/0xca <- migrate_swap+0xed/0x10c Mar 10 11:10:46 Ultron kernel: RIP: 0010:dev_watchdog+0x10c/0x166 Mar 10 11:10:46 Ultron kernel: Code: bd af 00 00 75 36 48 89 ef c6 05 4c bd af 00 01 e8 7f f6 fb ff 44 89 e1 48 89 ee 48 c7 c7 3e ac f2 81 48 89 c2 e8 c0 4f 11 00 <0f> 0b eb 0e 41 ff c4 48 05 40 01 00 00 e9 65 ff ff ff 48 8b 83 90 Mar 10 11:10:46 Ultron kernel: RSP: 0000:ffffc90000003ec8 EFLAGS: 00010282 Mar 10 11:10:46 Ultron kernel: RAX: 0000000000000000 RBX: ffff888107cbc438 RCX: 0000000000000027 Mar 10 11:10:46 Ultron kernel: RDX: 0000000000000003 RSI: ffffc90000003d50 RDI: ffff88905f818570 Mar 10 11:10:46 Ultron kernel: RBP: ffff888107cbc000 R08: ffff88a09ff6a2a8 R09: ffffffff826232c8 Mar 10 11:10:46 Ultron kernel: R10: 0000000000000000 R11: ffff88a09ff994a7 R12: 0000000000000000 Mar 10 11:10:46 Ultron kernel: R13: 000000010dbdee00 R14: ffffc90000003f10 R15: ffffffff816952ae Mar 10 11:10:46 Ultron kernel: FS: 0000000000000000(0000) GS:ffff88905f800000(0000) knlGS:0000000000000000 Mar 10 11:10:46 Ultron kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 10 11:10:46 Ultron kernel: CR2: 000000c000215000 CR3: 0000001d125b8002 CR4: 00000000001726f0 Mar 10 11:10:46 Ultron kernel: Call Trace: Mar 10 15:11:31 Ultron nerdpack: Cleaning up packages... Mar 10 15:11:31 Ultron rsyslogd: action 'action-3-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2102.0 try https://www.rsyslog.com/e/2359 ] Mar 10 15:11:31 Ultron root: ultron.log ultron-diagnostics-20220310-1554.zip