Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

mf808

Members
  • Joined

  • Last visited

  1. Has anyone got the intel uhd 630 passthrough to work with a macinabox so that It outputs to the motherboard hdmi port?
  2. I have noticed that transfer from the array to my desktop over a 10G network is now only running at 40MB/s or lower. Previously this was running smoothly at over 100MB/s. Also on the dashboard shows high usage of all cores. Ther are no other activities on this drive or the server. Clean reboot. Any ideas? nasmuc-diagnostics-20201021-2012.zip
  3. I had my unraid server crash on me. Web Front End is not anymore responsive. SSH Login with root does not work. Docker Containers are working. Running 6.9 Beta 22 From my syslog server I was able to pull this information. I assume the server was running for about 20 days. <1>Aug 6 15:43:14 NASMUC kernel: BUG: unable to handle page fault for address: 000000015d3ea242 <1>Aug 6 15:43:14 NASMUC kernel: #PF: supervisor write access in kernel mode <1>Aug 6 15:43:14 NASMUC kernel: #PF: error_code(0x0002) - not-present page <6>Aug 6 15:43:14 NASMUC kernel: PGD 8000000103655067 P4D 8000000103655067 PUD 0 <4>Aug 6 15:43:14 NASMUC kernel: Oops: 0002 [#1] SMP PTI <4>Aug 6 15:43:14 NASMUC kernel: CPU: 3 PID: 21330 Comm: curl Tainted: G W 5.7.2-Unraid #1 <4>Aug 6 15:43:14 NASMUC kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 M/Z390 M-CF, BIOS F6c 12/18/2019 <4>Aug 6 15:43:14 NASMUC kernel: RIP: 0010:rwsem_down_write_slowpath+0xc2/0x3c4 <4>Aug 6 15:43:14 NASMUC kernel: Code: 48 89 44 24 10 49 8b 47 18 48 8d 4c 24 40 48 39 44 24 10 49 89 4f 20 49 8d 4f 18 48 89 4c 24 40 48 8d 4c 24 40 48 89 54 24 48 <48> 89 0a 0f 94 c3 48 39 44 24 10 75 1c eb 71 be 01 00 00 00 4c 89 <4>Aug 6 15:43:14 NASMUC kernel: RSP: 0000:ffffc90001f77d10 EFLAGS: 00010087 <4>Aug 6 15:43:14 NASMUC kernel: RAX: ffff888fc9609780 RBX: 0000000000000000 RCX: ffffc90001f77d50 <4>Aug 6 15:43:14 NASMUC kernel: RDX: 000000015d3ea242 RSI: ffffc90001f77cfc RDI: ffff8882e75ccbf4 <4>Aug 6 15:43:14 NASMUC kernel: RBP: ffffc90001f77db8 R08: 0000000000000001 R09: 0000000000023d00 <4>Aug 6 15:43:14 NASMUC kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff888f7ea97000 <4>Aug 6 15:43:14 NASMUC kernel: R13: ffff8882e75ccbf4 R14: 0000000000000002 R15: ffff8882e75ccbe0 <4>Aug 6 15:43:14 NASMUC kernel: FS: 0000000000000000(0000) GS:ffff88907e4c0000(0000) knlGS:0000000000000000 <4>Aug 6 15:43:14 NASMUC kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>Aug 6 15:43:14 NASMUC kernel: CR2: 000000015d3ea242 CR3: 0000000450920003 CR4: 00000000003606e0 <4>Aug 6 15:43:14 NASMUC kernel: Call Trace: <4>Aug 6 15:43:14 NASMUC kernel: ? atime_needs_update+0x6d/0xcc <4>Aug 6 15:43:14 NASMUC kernel: ? vma_set_page_prot+0x46/0x6c <4>Aug 6 15:43:14 NASMUC kernel: down_write+0x43/0x6d <4>Aug 6 15:43:14 NASMUC kernel: __anon_vma_prepare+0x7d/0x110 <4>Aug 6 15:43:14 NASMUC kernel: __handle_mm_fault+0xb8e/0xcf5 <4>Aug 6 15:43:14 NASMUC kernel: handle_mm_fault+0x117/0x165 <4>Aug 6 15:43:14 NASMUC kernel: do_page_fault+0x2a2/0x3ad <4>Aug 6 15:43:14 NASMUC kernel: page_fault+0x34/0x40 <4>Aug 6 15:43:14 NASMUC kernel: RIP: 0033:0x1487931d28f1 <4>Aug 6 15:43:14 NASMUC kernel: Code: 20 66 0f 7f 41 30 48 83 c1 40 48 39 ca 75 e4 f3 c3 66 48 0f 7e c1 80 fa 08 73 0f 80 fa 04 73 13 80 fa 01 77 15 72 02 88 0f c3 <48> 89 4c 17 f8 48 89 0f c3 89 4c 17 fc 89 0f c3 66 89 4c 17 fe 66 <4>Aug 6 15:43:14 NASMUC kernel: RSP: 002b:00007ffc748c0128 EFLAGS: 00010246 <4>Aug 6 15:43:14 NASMUC kernel: RAX: 000014879297c1c8 RBX: 00007ffc748c01c0 RCX: 0000000000000000 <4>Aug 6 15:43:14 NASMUC kernel: RDX: 0000000000000008 RSI: 0000000000000000 RDI: 000014879297c1c8 <4>Aug 6 15:43:14 NASMUC kernel: RBP: 00007ffc748c03f0 R08: 000014879297c1c8 R09: 0000000000024000 <4>Aug 6 15:43:14 NASMUC kernel: R10: 0000000000000003 R11: 000014879297c1d0 R12: 000014879297d000 <4>Aug 6 15:43:14 NASMUC kernel: R13: 00007ffc748c04d8 R14: 0000000000000004 R15: 0000000000000002 <4>Aug 6 15:43:14 NASMUC kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables xt_nat vhost_net tun vhost vhost_iotlb tap veth macvlan xt_MASQUERADE iptable_filter iptable_nat nf_n$ <4>Aug 6 15:43:14 NASMUC kernel: CR2: 000000015d3ea242 <4>Aug 6 15:43:14 NASMUC kernel: ---[ end trace 5944a143c284ad2b ]--- <4>Aug 6 15:43:14 NASMUC kernel: RIP: 0010:rwsem_down_write_slowpath+0xc2/0x3c4 <4>Aug 6 15:43:14 NASMUC kernel: Code: 48 89 44 24 10 49 8b 47 18 48 8d 4c 24 40 48 39 44 24 10 49 89 4f 20 49 8d 4f 18 48 89 4c 24 40 48 8d 4c 24 40 48 89 54 24 48 <48> 89 0a 0f 94 c3 48 39 44 24 10 75 1c eb 71 be 01 00 00 00 4c 89 <4>Aug 6 15:43:14 NASMUC kernel: RSP: 0000:ffffc90001f77d10 EFLAGS: 00010087 <4>Aug 6 15:43:14 NASMUC kernel: RAX: ffff888fc9609780 RBX: 0000000000000000 RCX: ffffc90001f77d50 <4>Aug 6 15:43:14 NASMUC kernel: RDX: 000000015d3ea242 RSI: ffffc90001f77cfc RDI: ffff8882e75ccbf4 <4>Aug 6 15:43:14 NASMUC kernel: RBP: ffffc90001f77db8 R08: 0000000000000001 R09: 0000000000023d00 <4>Aug 6 15:43:14 NASMUC kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff888f7ea97000 <4>Aug 6 15:43:14 NASMUC kernel: R13: ffff8882e75ccbf4 R14: 0000000000000002 R15: ffff8882e75ccbe0 <4>Aug 6 15:43:14 NASMUC kernel: FS: 0000000000000000(0000) GS:ffff88907e4c0000(0000) knlGS:0000000000000000 <4>Aug 6 15:43:14 NASMUC kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>Aug 6 15:43:14 NASMUC kernel: CR2: 000000015d3ea242 CR3: 0000000450920003 CR4: 00000000003606e0 <4>Aug 6 15:43:24 NASMUC kernel: stack segment: 0000 [#2] SMP PTI <4>Aug 6 15:43:24 NASMUC kernel: CPU: 3 PID: 580 Comm: docker_load Tainted: G D W 5.7.2-Unraid #1 <4>Aug 6 15:43:24 NASMUC kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 M/Z390 M-CF, BIOS F6c 12/18/2019 <4>Aug 6 15:43:24 NASMUC kernel: RIP: 0010:kmem_cache_alloc+0x5d/0xd2 <4>Aug 6 15:43:24 NASMUC kernel: Code: 8b 28 48 85 ed 75 16 4c 89 f1 83 ca ff 44 89 ee 4c 89 e7 e8 8e ff ff ff 48 89 c5 eb 2a 41 8b 44 24 20 48 8d 4a 01 49 8b 3c 24 <48> 8b 5c 05 00 48 89 e8 65 48 0f c7 0f 0f 94 c0 84 c0 74 b0 41 8b <4>Aug 6 15:43:24 NASMUC kernel: RSP: 0018:ffffc9000198fcd0 EFLAGS: 00010202 <4>Aug 6 15:43:24 NASMUC kernel: RAX: 0000000000000050 RBX: ffff8890730bd6c0 RCX: 0000000001a986ba <4>Aug 6 15:43:24 NASMUC kernel: RDX: 0000000001a986b9 RSI: 0000000000000cc0 RDI: 0000000000027610 <4>Aug 6 15:43:24 NASMUC kernel: RBP: 3e9decfe03000107 R08: ffff88907e4e7610 R09: 0000000000000000 <4>Aug 6 15:43:24 NASMUC kernel: R10: ffff888453e7ac60 R11: ffffc9000198fce8 R12: ffff889078007a40 <4>Aug 6 15:43:24 NASMUC kernel: R13: 0000000000000cc0 R14: ffffffff81112f41 R15: ffff888978d1a9c0 <4>Aug 6 15:43:24 NASMUC kernel: FS: 000014a72697e740(0000) GS:ffff88907e4c0000(0000) knlGS:0000000000000000 <4>Aug 6 15:43:24 NASMUC kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>Aug 6 15:43:24 NASMUC kernel: CR2: 00007ffc3a36dfb8 CR3: 00000010741c2006 CR4: 00000000003606e0 <4>Aug 6 15:43:24 NASMUC kernel: Call Trace: <4>Aug 6 15:43:24 NASMUC kernel: anon_vma_alloc+0x11/0x2c <4>Aug 6 15:43:24 NASMUC kernel: anon_vma_fork+0x4b/0x10f <4>Aug 6 15:43:24 NASMUC kernel: dup_mm+0x233/0x48a <4>Aug 6 15:43:24 NASMUC kernel: copy_process+0xb0b/0x157b <4>Aug 6 15:43:24 NASMUC kernel: ? _cond_resched+0x1b/0x1e <4>Aug 6 15:43:24 NASMUC kernel: _do_fork+0x7c/0x1e3 <4>Aug 6 15:43:24 NASMUC kernel: ? __clear_close_on_exec.isra.0+0xd/0x19 <4>Aug 6 15:43:24 NASMUC kernel: __do_sys_clone+0x76/0x90 <4>Aug 6 15:43:24 NASMUC kernel: do_syscall_64+0x7a/0x87 <4>Aug 6 15:43:24 NASMUC kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 <4>Aug 6 15:43:24 NASMUC kernel: RIP: 0033:0x14a726a5d95b <4>Aug 6 15:43:24 NASMUC kernel: Code: ed 0f 85 f8 00 00 00 64 4c 8b 0c 25 10 00 00 00 45 31 c0 4d 8d 91 d0 02 00 00 31 d2 31 f6 bf 11 00 20 01 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 41 89 c5 85 c0 0f 85 9e 00 00 <4>Aug 6 15:43:24 NASMUC kernel: RSP: 002b:00007ffc3a36f130 EFLAGS: 00000246 ORIG_RAX: 0000000000000038 <4>Aug 6 15:43:24 NASMUC kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 000014a726a5d95b <4>Aug 6 15:43:24 NASMUC kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011 <4>Aug 6 15:43:24 NASMUC kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 000014a72697e740 <4>Aug 6 15:43:24 NASMUC kernel: R10: 000014a72697ea10 R11: 0000000000000246 R12: 0000000000000000 <4>Aug 6 15:43:24 NASMUC kernel: R13: 00007ffc3a36f1f0 R14: 0000000000000001 R15: 00000000004dbbf8 <4>Aug 6 15:43:24 NASMUC kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables xt_nat vhost_net tun vhost vhost_iotlb tap veth macvlan xt_MASQUERADE iptable_filter iptable_nat nf_n$ <4>Aug 6 15:43:24 NASMUC kernel: ---[ end trace 5944a143c284ad2c ]--- <4>Aug 6 15:43:24 NASMUC kernel: RIP: 0010:rwsem_down_write_slowpath+0xc2/0x3c4 <4>Aug 6 15:43:24 NASMUC kernel: Code: 48 89 44 24 10 49 8b 47 18 48 8d 4c 24 40 48 39 44 24 10 49 89 4f 20 49 8d 4f 18 48 89 4c 24 40 48 8d 4c 24 40 48 89 54 24 48 <48> 89 0a 0f 94 c3 48 39 44 24 10 75 1c eb 71 be 01 00 00 00 4c 89 <4>Aug 6 15:43:24 NASMUC kernel: RSP: 0000:ffffc90001f77d10 EFLAGS: 00010087 <4>Aug 6 15:43:24 NASMUC kernel: RAX: ffff888fc9609780 RBX: 0000000000000000 RCX: ffffc90001f77d50 <4>Aug 6 15:43:24 NASMUC kernel: RDX: 000000015d3ea242 RSI: ffffc90001f77cfc RDI: ffff8882e75ccbf4 <4>Aug 6 15:43:24 NASMUC kernel: RBP: ffffc90001f77db8 R08: 0000000000000001 R09: 0000000000023d00 <4>Aug 6 15:43:24 NASMUC kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff888f7ea97000 <4>Aug 6 15:43:24 NASMUC kernel: R13: ffff8882e75ccbf4 R14: 0000000000000002 R15: ffff8882e75ccbe0 <4>Aug 6 15:43:24 NASMUC kernel: FS: 000014a72697e740(0000) GS:ffff88907e4c0000(0000) knlGS:0000000000000000 <4>Aug 6 15:43:24 NASMUC kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>Aug 6 15:43:24 NASMUC kernel: CR2: 00007ffc3a36dfb8 CR3: 00000010741c2006 CR4: 00000000003606e0 <4>Aug 6 15:43:26 NASMUC kernel: stack segment: 0000 [#3] SMP PTI <4>Aug 6 15:43:26 NASMUC kernel: CPU: 3 PID: 4420 Comm: diskload Tainted: G D W 5.7.2-Unraid #1 <4>Aug 6 15:43:26 NASMUC kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 M/Z390 M-CF, BIOS F6c 12/18/2019 <4>Aug 6 15:43:26 NASMUC kernel: RIP: 0010:kmem_cache_alloc+0x5d/0xd2 <4>Aug 6 15:43:26 NASMUC kernel: Code: 8b 28 48 85 ed 75 16 4c 89 f1 83 ca ff 44 89 ee 4c 89 e7 e8 8e ff ff ff 48 89 c5 eb 2a 41 8b 44 24 20 48 8d 4a 01 49 8b 3c 24 <48> 8b 5c 05 00 48 89 e8 65 48 0f c7 0f 0f 94 c0 84 c0 74 b0 41 8b <4>Aug 6 15:43:26 NASMUC kernel: RSP: 0018:ffffc9000065bcd0 EFLAGS: 00010202 <4>Aug 6 15:43:26 NASMUC kernel: RAX: 0000000000000050 RBX: ffff889073dd40c0 RCX: 0000000001a986ba <4>Aug 6 15:43:26 NASMUC kernel: RDX: 0000000001a986b9 RSI: 0000000000000cc0 RDI: 0000000000027610 <4>Aug 6 15:43:26 NASMUC kernel: RBP: 3e9decfe03000107 R08: ffff88907e4e7610 R09: 0000000000000000 <4>Aug 6 15:43:26 NASMUC kernel: R10: ffff889074fcebe0 R11: ffff889072255940 R12: ffff889078007a40 <4>Aug 6 15:43:26 NASMUC kernel: R13: 0000000000000cc0 R14: ffffffff81112f41 R15: ffff888978d1ad80 <4>Aug 6 15:43:26 NASMUC kernel: FS: 0000153a5bdd5740(0000) GS:ffff88907e4c0000(0000) knlGS:0000000000000000 <4>Aug 6 15:43:26 NASMUC kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>Aug 6 15:43:26 NASMUC kernel: CR2: 00007ffed015ffc8 CR3: 0000001072f08004 CR4: 00000000003606e0 <4>Aug 6 15:43:26 NASMUC kernel: Call Trace: <4>Aug 6 15:43:26 NASMUC kernel: anon_vma_alloc+0x11/0x2c <4>Aug 6 15:43:26 NASMUC kernel: anon_vma_fork+0x4b/0x10f <4>Aug 6 15:43:26 NASMUC kernel: dup_mm+0x233/0x48a <4>Aug 6 15:43:26 NASMUC kernel: copy_process+0xb0b/0x157b <4>Aug 6 15:43:26 NASMUC kernel: ? _cond_resched+0x1b/0x1e <4>Aug 6 15:43:26 NASMUC kernel: _do_fork+0x7c/0x1e3 <4>Aug 6 15:43:26 NASMUC kernel: ? __clear_close_on_exec.isra.0+0xd/0x19 <4>Aug 6 15:43:26 NASMUC kernel: __do_sys_clone+0x76/0x90 <4>Aug 6 15:43:26 NASMUC kernel: do_syscall_64+0x7a/0x87 <4>Aug 6 15:43:26 NASMUC kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 <4>Aug 6 15:43:26 NASMUC kernel: RIP: 0033:0x153a5beb495b <4>Aug 6 15:43:26 NASMUC kernel: Code: ed 0f 85 f8 00 00 00 64 4c 8b 0c 25 10 00 00 00 45 31 c0 4d 8d 91 d0 02 00 00 31 d2 31 f6 bf 11 00 20 01 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 41 89 c5 85 c0 0f 85 9e 00 00 <4>Aug 6 15:43:26 NASMUC kernel: RSP: 002b:00007ffed01610e0 EFLAGS: 00000246 ORIG_RAX: 0000000000000038 <4>Aug 6 15:43:26 NASMUC kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 0000153a5beb495b <4>Aug 6 15:43:26 NASMUC kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011 <4>Aug 6 15:43:26 NASMUC kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000153a5bdd5740 <4>Aug 6 15:43:26 NASMUC kernel: R10: 0000153a5bdd5a10 R11: 0000000000000246 R12: 0000000000000000 <4>Aug 6 15:43:26 NASMUC kernel: R13: 00007ffed01611a0 R14: 0000000000000000 R15: 00000000004dbbf8 <4>Aug 6 15:43:26 NASMUC kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables xt_nat vhost_net tun vhost vhost_iotlb tap veth macvlan xt_MASQUERADE iptable_filter iptable_nat nf_n$ <4>Aug 6 15:43:26 NASMUC kernel: ---[ end trace 5944a143c284ad2d ]--- <4>Aug 6 15:43:26 NASMUC kernel: RIP: 0010:rwsem_down_write_slowpath+0xc2/0x3c4 <4>Aug 6 15:43:26 NASMUC kernel: Code: 48 89 44 24 10 49 8b 47 18 48 8d 4c 24 40 48 39 44 24 10 49 89 4f 20 49 8d 4f 18 48 89 4c 24 40 48 8d 4c 24 40 48 89 54 24 48 <48> 89 0a 0f 94 c3 48 39 44 24 10 75 1c eb 71 be 01 00 00 00 4c 89 <4>Aug 6 15:43:26 NASMUC kernel: RSP: 0000:ffffc90001f77d10 EFLAGS: 00010087 <4>Aug 6 15:43:26 NASMUC kernel: RAX: ffff888fc9609780 RBX: 0000000000000000 RCX: ffffc90001f77d50 <4>Aug 6 15:43:26 NASMUC kernel: RDX: 000000015d3ea242 RSI: ffffc90001f77cfc RDI: ffff8882e75ccbf4 <4>Aug 6 15:43:26 NASMUC kernel: RBP: ffffc90001f77db8 R08: 0000000000000001 R09: 0000000000023d00 <4>Aug 6 15:43:26 NASMUC kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff888f7ea97000 <4>Aug 6 15:43:26 NASMUC kernel: R13: ffff8882e75ccbf4 R14: 0000000000000002 R15: ffff8882e75ccbe0 <4>Aug 6 15:43:26 NASMUC kernel: FS: 0000153a5bdd5740(0000) GS:ffff88907e4c0000(0000) knlGS:0000000000000000 <4>Aug 6 15:43:26 NASMUC kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>Aug 6 15:43:26 NASMUC kernel: CR2: 00007ffed015ffc8 CR3: 0000001072f08004 CR4: 00000000003606e0 <4>Aug 6 15:44:01 NASMUC kernel: stack segment: 0000 [#4] SMP PTI <4>Aug 6 15:44:01 NASMUC kernel: CPU: 3 PID: 1945 Comm: crond Tainted: G D W 5.7.2-Unraid #1 <4>Aug 6 15:44:01 NASMUC kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 M/Z390 M-CF, BIOS F6c 12/18/2019 <4>Aug 6 15:44:01 NASMUC kernel: RIP: 0010:kmem_cache_alloc+0x5d/0xd2 <4>Aug 6 15:44:01 NASMUC kernel: Code: 8b 28 48 85 ed 75 16 4c 89 f1 83 ca ff 44 89 ee 4c 89 e7 e8 8e ff ff ff 48 89 c5 eb 2a 41 8b 44 24 20 48 8d 4a 01 49 8b 3c 24 <48> 8b 5c 05 00 48 89 e8 65 48 0f c7 0f 0f 94 c0 84 c0 74 b0 41 8b <4>Aug 6 15:44:01 NASMUC kernel: RSP: 0018:ffffc900004c7cd0 EFLAGS: 00010202 <4>Aug 6 15:44:01 NASMUC kernel: RAX: 0000000000000050 RBX: ffff889073dada80 RCX: 0000000001a986ba <4>Aug 6 15:44:01 NASMUC kernel: RDX: 0000000001a986b9 RSI: 0000000000000cc0 RDI: 0000000000027610 <4>Aug 6 15:44:01 NASMUC kernel: RBP: 3e9decfe03000107 R08: ffff88907e4e7610 R09: 0000000000000000 <4>Aug 6 15:44:01 NASMUC kernel: R10: ffff889077afbd60 R11: ffff889072255500 R12: ffff889078007a40 <4>Aug 6 15:44:01 NASMUC kernel: R13: 0000000000000cc0 R14: ffffffff81112f41 R15: ffff8881005cb840 <4>Aug 6 15:44:01 NASMUC kernel: FS: 00001497fc511540(0000) GS:ffff88907e4c0000(0000) knlGS:0000000000000000 nasmuc-diagnostics-20200808-0011.zip
  4. Thanks. I got it fixed. Issue was the binhex nzbget as $APPDIR configured for the main directory. This should only point to /data, which is the folder that get mounted during container creation. Theoretically this should be set as a standard in the binhex-nzbget image.
  5. I need some help here. Ive switched from the linuxserver version of nzbget to binhex. Now Sonarr can't find the downloaded files. It seems as if the mapping for /data in the container does not work. The download is within the container at /usr/local/bin/nzbget/downloads/completed. And after completion it is clear that Sonarr cant find the file thats within the container. Can somebody tell me what I am doing wrong?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.