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.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Unraid Crash

quinnmjcj
in General Support

Featured Replies

This is a crash that seems to be related to the problem I was having with non-crashing dumps in another thread.

I basically have 6.1.9, and created a new docker img (42 GB) and then added my dockers 1 by 1.

binhex-delugevpn, binhex-nzbget, cadvisor, CrashPlan - I added them about 60 minutes apart.

 

When I added binhex-sonarr - this crash occurred soon after.

 

 

Mar 23 10:46:18 QNas kernel: docker0: port 2(veth5974221) entered forwarding state

Mar 23 10:46:18 QNas kernel: docker0: port 2(veth5974221) entered forwarding state

Mar 23 10:46:18 QNas avahi-daemon[5625]: Withdrawing workstation service for vetha745ece.

Mar 23 10:46:18 QNas kernel: eth0: renamed from vetha745ece

Mar 23 10:46:33 QNas kernel: docker0: port 2(veth5974221) entered forwarding state

Mar 23 11:18:00 QNas kernel: BUG: unable to handle kernel NULL pointer dereference at          (null)

Mar 23 11:18:00 QNas kernel: IP: [<ffffffff812c727d>] end_bio_extent_readpage+0x83/0x441

Mar 23 11:18:00 QNas kernel: PGD 13433d067 PUD 10f167067 PMD 0

Mar 23 11:18:00 QNas kernel: Oops: 0000 [#1] PREEMPT SMP

Mar 23 11:18:00 QNas kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_amd kvm vhost_net vhost macvtap macvlan tun ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod pl2303 k10temp usbserial mvsas fam15h_power libsas scsi_transport_sas i2c_piix4 ahci libahci e1000e ptp pps_core acpi_cpufreq

Mar 23 11:18:00 QNas kernel: CPU: 0 PID: 31702 Comm: kworker/u8:0 Not tainted 4.1.18-unRAID #1

Mar 23 11:18:00 QNas kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A88XM-D3H, BIOS F8 04/09/2015

Mar 23 11:18:00 QNas kernel: Workqueue: btrfs-endio btrfs_endio_helper

Mar 23 11:18:00 QNas kernel: task: ffff8800117f6480 ti: ffff8800071a0000 task.ti: ffff8800071a0000

Mar 23 11:18:00 QNas kernel: RIP: 0010:[<ffffffff812c727d>]  [<ffffffff812c727d>] end_bio_extent_readpage+0x83/0x441

Mar 23 11:18:00 QNas kernel: RSP: 0018:ffff8800071a3c98  EFLAGS: 00010246

Mar 23 11:18:00 QNas kernel: RAX: 0000000000000000 RBX: ffffea0004186dc0 RCX: ffff8801eaa65980

Mar 23 11:18:00 QNas kernel: RDX: 0000000000000000 RSI: ffffea0004986d80 RDI: ffff8800071a3c48

Mar 23 11:18:00 QNas kernel: RBP: ffff8800071a3d48 R08: ffff88033efb51e8 R09: 0000000000000000

Mar 23 11:18:00 QNas kernel: R10: 700eb406668c64f0 R11: ffff8801261b6ff0 R12: ffff88015408ea68

Mar 23 11:18:00 QNas kernel: R13: 0000000000098000 R14: ffff8800668c64f0 R15: 0000000000000001

Mar 23 11:18:00 QNas kernel: FS:  00002b47c1c6c700(0000) GS:ffff88033ec00000(0000) knlGS:0000000000000000

Mar 23 11:18:00 QNas kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Mar 23 11:18:00 QNas kernel: CR2: 0000000000000000 CR3: 0000000134220000 CR4: 00000000000406f0

Mar 23 11:18:00 QNas kernel: Stack:

Mar 23 11:18:00 QNas kernel: ffff8800071a0000 ffff880100241988 ffff8800117f64e8 0000000000001000

Mar 23 11:18:00 QNas kernel: ffff88015408ea00 0000000000000098 ffff880000000001 0000000002b12fff

Mar 23 11:18:00 QNas kernel: 0000000000000fff ffff8801eaa65980 0000000000098000 ffff8800668c6368

Mar 23 11:18:00 QNas kernel: Call Trace:

Mar 23 11:18:00 QNas kernel: [<ffffffff81332e07>] bio_endio+0x61/0x68

Mar 23 11:18:00 QNas kernel: [<ffffffff81332e1b>] bio_endio_nodec+0xd/0xf

Mar 23 11:18:00 QNas kernel: [<ffffffff812a5213>] end_workqueue_fn+0x3a/0x3f

Mar 23 11:18:00 QNas kernel: [<ffffffff812d47a4>] normal_work_helper+0xbc/0x171

Mar 23 11:18:00 QNas kernel: [<ffffffff812d499c>] btrfs_endio_helper+0xd/0xf

Mar 23 11:18:00 QNas kernel: [<ffffffff81057d6a>] process_one_work+0x1a1/0x2b7

Mar 23 11:18:00 QNas kernel: [<ffffffff8105865b>] worker_thread+0x273/0x367

Mar 23 11:18:00 QNas kernel: [<ffffffff810583e8>] ? cancel_delayed_work_sync+0x10/0x10

Mar 23 11:18:00 QNas kernel: [<ffffffff8105c74a>] kthread+0xd6/0xde

Mar 23 11:18:00 QNas kernel: [<ffffffff8105c674>] ? kthread_create_on_node+0x172/0x172

Mar 23 11:18:00 QNas kernel: [<ffffffff815f7f12>] ret_from_fork+0x42/0x70

Mar 23 11:18:00 QNas kernel: [<ffffffff8105c674>] ? kthread_create_on_node+0x172/0x172

Mar 23 11:18:00 QNas kernel: Code: 31 ed 48 89 45 98 41 0f b7 44 24 70 39 85 78 ff ff ff 0f 8d d3 02 00 00 48 8b 4d 98 48 8b 19 48 81 79 08 00 10 00 00 48 8b 43 08 <4c> 8b 30 49 8d 86 78 fe ff ff 48 89 45 a8 74 35 8b 51 0c 8b 49

Mar 23 11:18:00 QNas kernel: RIP  [<ffffffff812c727d>] end_bio_extent_readpage+0x83/0x441

Mar 23 11:18:00 QNas kernel: RSP <ffff8800071a3c98>

Mar 23 11:18:00 QNas kernel: CR2: 0000000000000000

Mar 23 11:18:00 QNas kernel: ---[ end trace 9cf370d297d5291d ]---

Mar 23 11:18:00 QNas kernel: ------------[ cut here ]------------

Mar 23 11:18:00 QNas kernel: WARNING: CPU: 0 PID: 31702 at kernel/smp.c:292 smp_call_function_single+0x81/0xef()

Mar 23 11:18:00 QNas kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_amd kvm vhost_net vhost macvtap macvlan tun ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod pl2303 k10temp usbserial mvsas fam15h_power libsas scsi_transport_sas i2c_piix4 ahci libahci e1000e ptp pps_core acpi_cpufreq

Mar 23 11:18:00 QNas kernel: CPU: 0 PID: 31702 Comm: kworker/u8:0 Tainted: G      D        4.1.18-unRAID #1

Mar 23 11:18:00 QNas kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A88XM-D3H, BIOS F8 04/09/2015

Mar 23 11:18:00 QNas kernel: 0000000000000009 ffff8800071a3898 ffffffff815f2403 ffffffff8182e140

Mar 23 11:18:00 QNas kernel: 0000000000000096 0000000000000124 0000000000000000 ffff8800071a38d8

Mar 23 11:18:00 QNas kernel: ffffffff8104778b ffff88033ec15ec0 ffffffff81092cb1 ffff8800117f6480

Mar 23 11:18:00 QNas kernel: Call Trace:

Mar 23 11:18:00 QNas kernel: [<ffffffff815f2403>] dump_stack+0x65/0x85

Mar 23 11:18:00 QNas kernel: [<ffffffff8104778b>] warn_slowpath_common+0x97/0xb1

Mar 23 11:18:00 QNas kernel: [<ffffffff81092cb1>] ? smp_call_function_single+0x81/0xef

Mar 23 11:18:00 QNas kernel: [<ffffffff810a74c9>] ? perf_event_refresh+0x39/0x39

Mar 23 11:18:00 QNas kernel: [<ffffffff81047839>] warn_slowpath_null+0x15/0x17

Mar 23 11:18:00 QNas kernel: [<ffffffff81092cb1>] smp_call_function_single+0x81/0xef

Mar 23 11:18:00 QNas kernel: [<ffffffff810a5fb1>] task_function_call+0x44/0x4e

Mar 23 11:18:00 QNas kernel: [<ffffffff810ab3c3>] ? __perf_event_task_sched_out+0x35b/0x35b

Mar 23 11:18:00 QNas kernel: [<ffffffff810a75df>] perf_cgroup_exit+0x19/0x1b

Mar 23 11:18:00 QNas kernel: [<ffffffff8109ce0e>] cgroup_exit+0xa9/0xc8

Mar 23 11:18:00 QNas kernel: [<ffffffff810497bc>] do_exit+0x3e0/0x8db

Mar 23 11:18:00 QNas kernel: [<ffffffff81078a10>] ? kmsg_dump+0xa7/0xb0

Mar 23 11:18:00 QNas kernel: [<ffffffff8100e053>] oops_end+0xb5/0xba

Mar 23 11:18:00 QNas kernel: [<ffffffff815edb5f>] no_context+0x2d4/0x335

Mar 23 11:18:00 QNas kernel: [<ffffffff812c4237>] ? free_extent_state.part.27+0x34/0x38

Mar 23 11:18:00 QNas kernel: [<ffffffff815edc3c>] __bad_area_nosemaphore+0x7c/0x1d4

Mar 23 11:18:00 QNas kernel: [<ffffffff81043995>] ? crc32c_pcl_intel_update+0x70/0x9d

Mar 23 11:18:00 QNas kernel: [<ffffffff815edda2>] bad_area_nosemaphore+0xe/0x10

Mar 23 11:18:00 QNas kernel: [<ffffffff8103e228>] __do_page_fault+0xc0/0x309

Mar 23 11:18:00 QNas kernel: [<ffffffff8103e4b4>] do_page_fault+0x22/0x2a

Mar 23 11:18:00 QNas kernel: [<ffffffff815f9538>] page_fault+0x28/0x30

Mar 23 11:18:00 QNas kernel: [<ffffffff812c727d>] ? end_bio_extent_readpage+0x83/0x441

Mar 23 11:18:00 QNas kernel: [<ffffffff812c74de>] ? end_bio_extent_readpage+0x2e4/0x441

Mar 23 11:18:00 QNas kernel: [<ffffffff81332e07>] bio_endio+0x61/0x68

Mar 23 11:18:00 QNas kernel: [<ffffffff81332e1b>] bio_endio_nodec+0xd/0xf

Mar 23 11:18:00 QNas kernel: [<ffffffff812a5213>] end_workqueue_fn+0x3a/0x3f

Mar 23 11:18:00 QNas kernel: [<ffffffff812d47a4>] normal_work_helper+0xbc/0x171

Mar 23 11:18:00 QNas kernel: [<ffffffff812d499c>] btrfs_endio_helper+0xd/0xf

Mar 23 11:18:00 QNas kernel: [<ffffffff81057d6a>] process_one_work+0x1a1/0x2b7

Mar 23 11:18:00 QNas kernel: [<ffffffff8105865b>] worker_thread+0x273/0x367

Mar 23 11:18:00 QNas kernel: [<ffffffff810583e8>] ? cancel_delayed_work_sync+0x10/0x10

Mar 23 11:18:00 QNas kernel: [<ffffffff8105c74a>] kthread+0xd6/0xde

Mar 23 11:18:00 QNas kernel: [<ffffffff8105c674>] ? kthread_create_on_node+0x172/0x172

Mar 23 11:18:00 QNas kernel: [<ffffffff815f7f12>] ret_from_fork+0x42/0x70

Mar 23 11:18:00 QNas kernel: [<ffffffff8105c674>] ? kthread_create_on_node+0x172/0x172

Mar 23 11:18:00 QNas kernel: ---[ end trace 9cf370d297d5291e ]---

Mar 23 11:18:00 QNas kernel: BUG: unable to handle kernel paging request at ffffffffffffffd8

Mar 23 11:18:00 QNas kernel: IP: [<ffffffff8105cb8d>] kthread_data+0xc/0x11

qnas-diagnostics-20160323-1127.zip

  • Quote
    • Author

    Seems to be related to an interaction between binhex-sonarr and binhex-delugevpn dockers.  If I don't install delugevpn, things seem ok (well, sample size of 1 hour so far, but sonarr and nzbget are acting quite nicely together so far).

  • Quote
    • 3 months later...
    • Author

    Just to kind of close this thread out - I reformatted my cache drive as XFS and have had no trouble whatsoever.

    Once I update to 6.2 (soon), I'll try btrfs again and see how it plays.

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    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.