• Crashes since updating to v6.11.x for qBittorrent and Deluge users


    JorgeB
    • Closed

    EDIT: issue was traced to libtorrent 2.x, it's not an Unraid problem, more info in this post:

     

    https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/?do=findComment&comment=21671

     

     

    Original Post:

     

    I'm creating this to better track an issue that some users have been reporting where Unraid started crashing after updating to v6.11.x (it happens with both 6.11.0 and 6.11.1), there's a very similar call traced logged for all cases, e.g:

     

    Oct 12 04:18:27 zaBOX kernel: BUG: kernel NULL pointer dereference, address: 00000000000000b6
    Oct 12 04:18:27 zaBOX kernel: #PF: supervisor read access in kernel mode
    Oct 12 04:18:27 zaBOX kernel: #PF: error_code(0x0000) - not-present page
    Oct 12 04:18:27 zaBOX kernel: PGD 0 P4D 0
    Oct 12 04:18:27 zaBOX kernel: Oops: 0000 [#1] PREEMPT SMP PTI
    Oct 12 04:18:27 zaBOX kernel: CPU: 4 PID: 28596 Comm: Disk Tainted: P     U  W  O      5.19.14-Unraid #1
    Oct 12 04:18:27 zaBOX kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 AORUS PRO WIFI/Z390 AORUS PRO WIFI-CF, BIOS F12 11/05/2021
    Oct 12 04:18:27 zaBOX kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
    Oct 12 04:18:27 zaBOX kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
    Oct 12 04:18:27 zaBOX kernel: RSP: 0000:ffffc900070dbcc0 EFLAGS: 00010246
    Oct 12 04:18:27 zaBOX kernel: RAX: 0000000000000082 RBX: 0000000000000082 RCX: 0000000000000082
    Oct 12 04:18:27 zaBOX kernel: RDX: 0000000000000001 RSI: ffff888757426fe8 RDI: 0000000000000082
    Oct 12 04:18:27 zaBOX kernel: RBP: 0000000000000000 R08: 0000000000000028 R09: ffffc900070dbcd0
    Oct 12 04:18:27 zaBOX kernel: R10: ffffc900070dbcd0 R11: ffffc900070dbd48 R12: 0000000000000000
    Oct 12 04:18:27 zaBOX kernel: R13: ffff88824f95d138 R14: 000000000007292c R15: ffff88824f95d140
    Oct 12 04:18:27 zaBOX kernel: FS:  000014ed38204b38(0000) GS:ffff8888a0500000(0000) knlGS:0000000000000000
    Oct 12 04:18:27 zaBOX kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 12 04:18:27 zaBOX kernel: CR2: 00000000000000b6 CR3: 0000000209854005 CR4: 00000000003706e0
    Oct 12 04:18:27 zaBOX kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Oct 12 04:18:27 zaBOX kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Oct 12 04:18:27 zaBOX kernel: Call Trace:
    Oct 12 04:18:27 zaBOX kernel: <TASK>
    Oct 12 04:18:27 zaBOX kernel: __filemap_get_folio+0x98/0x1ff
    Oct 12 04:18:27 zaBOX kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a
    Oct 12 04:18:27 zaBOX kernel: filemap_fault+0x6e/0x524
    Oct 12 04:18:27 zaBOX kernel: __do_fault+0x2d/0x6e
    Oct 12 04:18:27 zaBOX kernel: __handle_mm_fault+0x9a5/0xc7d
    Oct 12 04:18:27 zaBOX kernel: handle_mm_fault+0x113/0x1d7
    Oct 12 04:18:27 zaBOX kernel: do_user_addr_fault+0x36a/0x514
    Oct 12 04:18:27 zaBOX kernel: exc_page_fault+0xfc/0x11e
    Oct 12 04:18:27 zaBOX kernel: asm_exc_page_fault+0x22/0x30
    Oct 12 04:18:27 zaBOX kernel: RIP: 0033:0x14ed3a0ae7b5
    Oct 12 04:18:27 zaBOX kernel: Code: 8b 48 08 48 8b 32 48 8b 00 48 39 f0 73 09 48 8d 14 08 48 39 d6 eb 0c 48 39 c6 73 0b 48 8d 14 0e 48 39 d0 73 02 0f 0b 48 89 c7 <f3> a4 66 48 8d 3d 59 b7 22 00 66 66 48 e8 d9 d8 f6 ff 48 89 28 48
    Oct 12 04:18:27 zaBOX kernel: RSP: 002b:000014ed38203960 EFLAGS: 00010206
    Oct 12 04:18:27 zaBOX kernel: RAX: 000014ed371aa160 RBX: 000014ed38203ad0 RCX: 0000000000004000
    Oct 12 04:18:27 zaBOX kernel: RDX: 000014c036530000 RSI: 000014c03652c000 RDI: 000014ed371aa160
    Oct 12 04:18:27 zaBOX kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 000014ed38203778
    Oct 12 04:18:27 zaBOX kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
    Oct 12 04:18:27 zaBOX kernel: R13: 000014ed38203b40 R14: 000014ed384fe940 R15: 000014ed38203ac0
    Oct 12 04:18:27 zaBOX kernel: </TASK>
    Oct 12 04:18:27 zaBOX kernel: Modules linked in: macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net vhost vhost_iotlb tap tun veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs md_mod kvmgt mdev i915 iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper intel_gtt agpgart hwmon_vid iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls ipv6 nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) x86_pkg_temp_thermal intel_powerclamp drm_kms_helper btusb btrtl i2c_i801 btbcm coretemp gigabyte_wmi wmi_bmof intel_wmi_thunderbolt mxm_wmi kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd
    Oct 12 04:18:27 zaBOX kernel: btintel rapl intel_cstate intel_uncore e1000e i2c_smbus bluetooth drm nvme nvme_core ahci i2c_core libahci ecdh_generic ecc syscopyarea sysfillrect input_leds sysimgblt led_class joydev nzxt_kraken2 intel_pch_thermal fb_sys_fops thermal fan video tpm_crb wmi tpm_tis backlight tpm_tis_core tpm acpi_pad button unix
    Oct 12 04:18:27 zaBOX kernel: CR2: 00000000000000b6
    Oct 12 04:18:27 zaBOX kernel: ---[ end trace 0000000000000000 ]---

     

    Another example with very different hardware:

    Oct 11 21:32:08 Impulse kernel: BUG: kernel NULL pointer dereference, address: 0000000000000056
    Oct 11 21:32:08 Impulse kernel: #PF: supervisor read access in kernel mode
    Oct 11 21:32:08 Impulse kernel: #PF: error_code(0x0000) - not-present page
    Oct 11 21:32:08 Impulse kernel: PGD 0 P4D 0
    Oct 11 21:32:08 Impulse kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
    Oct 11 21:32:08 Impulse kernel: CPU: 1 PID: 5236 Comm: Disk Not tainted 5.19.14-Unraid #1
    Oct 11 21:32:08 Impulse kernel: Hardware name: System manufacturer System Product Name/ROG STRIX B450-F GAMING II, BIOS 4301 03/04/2021
    Oct 11 21:32:08 Impulse kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
    Oct 11 21:32:08 Impulse kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b e9 cc 5f 86 00 <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
    Oct 11 21:32:08 Impulse kernel: RSP: 0000:ffffc900026ffcc0 EFLAGS: 00010246
    Oct 11 21:32:08 Impulse kernel: RAX: 0000000000000022 RBX: 0000000000000022 RCX: 0000000000000022
    Oct 11 21:32:08 Impulse kernel: RDX: 0000000000000001 RSI: ffff88801e450b68 RDI: 0000000000000022
    Oct 11 21:32:08 Impulse kernel: RBP: 0000000000000000 R08: 000000000000000c R09: ffffc900026ffcd0
    Oct 11 21:32:08 Impulse kernel: R10: ffffc900026ffcd0 R11: ffffc900026ffd48 R12: 0000000000000000
    Oct 11 21:32:08 Impulse kernel: R13: ffff888428441cb8 R14: 00000000000028cd R15: ffff888428441cc0
    Oct 11 21:32:08 Impulse kernel: FS:  00001548d34fa6c0(0000) GS:ffff88842e840000(0000) knlGS:0000000000000000
    Oct 11 21:32:08 Impulse kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 11 21:32:08 Impulse kernel: CR2: 0000000000000056 CR3: 00000001a3fe6000 CR4: 00000000003506e0
    Oct 11 21:32:08 Impulse kernel: Call Trace:
    Oct 11 21:32:08 Impulse kernel: <TASK>
    Oct 11 21:32:08 Impulse kernel: __filemap_get_folio+0x98/0x1ff
    Oct 11 21:32:08 Impulse kernel: filemap_fault+0x6e/0x524
    Oct 11 21:32:08 Impulse kernel: __do_fault+0x30/0x6e
    Oct 11 21:32:08 Impulse kernel: __handle_mm_fault+0x9a5/0xc7d
    Oct 11 21:32:08 Impulse kernel: handle_mm_fault+0x113/0x1d7
    Oct 11 21:32:08 Impulse kernel: do_user_addr_fault+0x36a/0x514
    Oct 11 21:32:08 Impulse kernel: exc_page_fault+0xfc/0x11e
    Oct 11 21:32:08 Impulse kernel: asm_exc_page_fault+0x22/0x30
    Oct 11 21:32:08 Impulse kernel: RIP: 0033:0x1548dbc04741
    Oct 11 21:32:08 Impulse kernel: Code: 48 01 d0 eb 1b 0f 1f 40 00 f3 0f 1e fa 48 39 d1 0f 82 73 28 fc ff 0f 1f 00 f3 0f 1e fa 48 89 f8 48 83 fa 20 0f 82 af 00 00 00 <c5> fe 6f 06 48 83 fa 40 0f 87 3e 01 00 00 c5 fe 6f 4c 16 e0 c5 fe
    Oct 11 21:32:08 Impulse kernel: RSP: 002b:00001548d34f9808 EFLAGS: 00010202
    Oct 11 21:32:08 Impulse kernel: RAX: 000015480c010d30 RBX: 000015480c018418 RCX: 00001548d34f9a40
    Oct 11 21:32:08 Impulse kernel: RDX: 0000000000004000 RSI: 000015471f8cd50f RDI: 000015480c010d30
    Oct 11 21:32:08 Impulse kernel: RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
    Oct 11 21:32:08 Impulse kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
    Oct 11 21:32:08 Impulse kernel: R13: 00001548d34f9ac0 R14: 0000000000000003 R15: 0000154814013d10
    Oct 11 21:32:08 Impulse kernel: </TASK>
    Oct 11 21:32:08 Impulse kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_mark xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc ipv6 mlx4_en mlx4_core igb i2c_algo_bit edac_mce_amd edac_core kvm_amd kvm wmi_bmof mxm_wmi asus_wmi_sensors crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel mpt3sas aesni_intel crypto_simd nvme cryptd ahci i2c_piix4 raid_class rapl k10temp i2c_core nvme_core ccp scsi_transport_sas libahci wmi button acpi_cpufreq unix [last unloaded: mlx4_core]
    Oct 11 21:32:08 Impulse kernel: CR2: 0000000000000056
    Oct 11 21:32:08 Impulse kernel: ---[ end trace 0000000000000000 ]---

     

    So they always start with this (end address will change):

     

    Oct 11 05:02:02 Cogsworth kernel: BUG: kernel NULL pointer dereference, address: 0000000000000076

     

    and always have this:

     

    Oct 11 05:02:02 Cogsworth kernel: Call Trace:
    Oct 11 05:02:02 Cogsworth kernel: <TASK>
    Oct 11 05:02:02 Cogsworth kernel: __filemap_get_folio+0x98/0x1ff

     

    The fact that it's happening to various users with very different hardware, both Intel and AMD, makes me think it's not a hardware/firmware issue, so we can try to find if they are running anything in common, these are the plugins I've found in common between the 4 or 5 cases found so far, these are some of the most used plugins so not surprising they are installed in all but it's also easy to rule them out:

     

    ca.backup2.plg - 2022.07.23  (Up to date)
    community.applications.plg - 2022.09.30  (Up to date)
    dynamix.active.streams.plg - 2020.06.17  (Up to date)
    file.activity.plg - 2022.08.19  (Up to date)
    fix.common.problems.plg - 2022.10.09  (Up to date)
    unassigned.devices.plg - 2022.10.03  (Up to date)
    unassigned.devices-plus.plg - 2022.08.19  (Up to date)

     

    So anyone having this issue try temporarily uninstalling/disabling these plugin to see if there's any difference.

    • Like 2
    • Upvote 1



    User Feedback

    Recommended Comments



    As a data point, my near-daily failures have the same versions as above, however my fix common problems plugin is still a bit out of date.  And still having the problem.  It just took a spell where it was being updated (what seemed like) a few times a day, and I was tired of clicking the button every time :)

     

    fix.common.problems.plg - 2022.09.26  (Update available: 2022.10.09)

     

    I'll disable the above plugins, with the exception of the unassigned devices.  If anyone can tell me how to mount my drives seamlessly in Unraid without this plugin, I'll try that too.  Just a linux command-level mount?

     

    Thanks for this follow-up post.

    • Like 1
    Link to comment

    Add me to the list of users affected by this, i was running 6.9.2 without issue for months at a time, i took the plunge on release of 6.11.1 and upgraded on 10th Oct, its now 12th Oct and i have identical symptoms to this post (apart from NO hardware changes for me in years):- https://forums.unraid.net/topic/129456-unraid-kernel-crashing-after-611-upgrade/

     

    Sadly for me, even attempting to generate diagnostics from the cli (web ui not accessible) did not complete, leaving me with no option but to attempt a soft reboot, which hung so hard reset it is. This then allowed me access to the web ui and i have dumped the list of plugins on my system (see below).

     

    hardware spec
    Mobo:- ASUS ROG STRIX X470-F Gaming
    PSU:- Seasonic SSR-750PD2 Prime Ultra 750 W
    CPU:- AMD 3900X
    RAM:- 2 x Corsair CMK32GX4M2A2666C16 (64GB)
    Cache (appdata/vm):- Samsung 970 EVO Plus 1 TB (NVME)
    Cache (downloads):- Samsung 500 GB 860 EVO
    GPU:- Nvidia Quadro P2000 (Plex duties)
    RAID Controllers:- 2 x IBM M1015 (cross flashed to IT mode)

     

    plugins installed

    CA Auto Turbo Write Mode
    Support Thread    Andrew Zawadzki    2022.09.16      up-to-date    

    CA Auto Update Applications
    Support Thread    Andrew Zawadzki    2021.09.24      up-to-date    

    Community ApplicationsSupport Thread
    Andrew Zawadzki    2022.09.30      up-to-date    

    ** Dynamix Auto Fan Control
    Support Thread    Bergware/gfjardim    2022.09.16      up-to-date    

    Dynamix Cache Directories
    Support Thread    Bergware    2020.08.03      up-to-date    

    GPU Statistics
    Support Thread    b3rs3rk    2022.02.22      up-to-date    

    ** Nerd Tools
    Support Thread    dmacias72    2021.08.11      up-to-date    

    Nvidia Driver
    Support Thread    ich777    2022.10.05      up-to-date    

    ** Unassigned Devices
    Support Thread    dlandon    2022.10.03      up-to-date    

    ** Unassigned Devices Plus
    Support Thread    dlandon    2022.08.19      up-to-date 

     

     ** = now removed in hope of better stability.

     

    I guess i will let you know in a few days whether the system is still up or crashed again, if crashed i shall be doing a binary split on the plugins still installed.

    Link to comment

    As you can probably see from my list of plugins i only have the following installed from your list of commonly installed plugins, which does shorten the list quite a lot, although i am only a metric of 1 so far so take it with a large pinch of salt 🙂


    community.applications.plg - 2022.09.30 (Up to date)
    unassigned.devices.plg - 2022.10.03 (Up to date)
    unassigned.devices-plus.plg - 2022.08.19 (Up to date)

     

    I am loathed to uninstall CA for obvious reasons, but i have nuked UD, so we shall see what happens.

    Link to comment
    5 minutes ago, binhex said:

    Sadly for me, even attempting to generate diagnostics from the cli (web ui not accessible) did not complete, leaving me with no option but to attempt a soft reboot, which hung so hard reset it is.

    If it happens again see if you can at least get the syslog to confirm if it's the same issue:

    cp /var/log/syslog /boot/syslog.txt

     

    Link to comment
    3 minutes ago, JorgeB said:

    If it happens again see if you can at least get the syslog to confirm if it's the same issue:

    will do

    Link to comment
    8 hours ago, phbigred said:

    I agree it's probably a plugin interaction.

    I'm not so sure it's a plugin issue, especially considering that most in the list are some of the most used ones, e.g., if CA or UD were the problem I would expect many more cases, not the half a dozen reported (at least so far), I guess it could be an interaction between two different plugins, but have my doubts, still since it's easy to rule them out we should do that first.

    Link to comment

    It happens again this night.
    I'm on Intel system and unraid v. 6.11.1

     

    Oct 13 02:39:24 Pegasus kernel: BUG: kernel NULL pointer dereference, address: 0000000000000116
    Oct 13 02:39:24 Pegasus kernel: #PF: supervisor read access in kernel mode
    Oct 13 02:39:24 Pegasus kernel: #PF: error_code(0x0000) - not-present page
    Oct 13 02:39:24 Pegasus kernel: PGD 0 P4D 0 
    Oct 13 02:39:24 Pegasus kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
    Oct 13 02:39:24 Pegasus kernel: CPU: 11 PID: 29073 Comm: Disk Tainted: P           O      5.19.14-Unraid #1
    Oct 13 02:39:24 Pegasus kernel: Hardware name: ASUS System Product Name/PRIME B560M-K, BIOS 1605 05/13/2022
    Oct 13 02:39:24 Pegasus kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
    Oct 13 02:39:24 Pegasus kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
    Oct 13 02:39:24 Pegasus kernel: RSP: 0000:ffffc900047dfcc0 EFLAGS: 00010246
    Oct 13 02:39:24 Pegasus kernel: RAX: 00000000000000e2 RBX: 00000000000000e2 RCX: 00000000000000e2
    Oct 13 02:39:24 Pegasus kernel: RDX: 0000000000000001 RSI: ffff88819e20cdb0 RDI: 00000000000000e2
    Oct 13 02:39:24 Pegasus kernel: RBP: 0000000000000000 R08: 000000000000003c R09: ffffc900047dfcd0
    Oct 13 02:39:24 Pegasus kernel: R10: ffffc900047dfcd0 R11: ffffc900047dfd48 R12: 0000000000000000
    Oct 13 02:39:24 Pegasus kernel: R13: ffff88812ca1bab8 R14: 000000000001693f R15: ffff88812ca1bac0
    Oct 13 02:39:24 Pegasus kernel: FS:  000014744eb4bb30(0000) GS:ffff88883c2c0000(0000) knlGS:0000000000000000
    Oct 13 02:39:24 Pegasus kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 13 02:39:24 Pegasus kernel: CR2: 0000000000000116 CR3: 00000001a8754004 CR4: 00000000007726e0
    Oct 13 02:39:24 Pegasus kernel: PKRU: 55555554
    Oct 13 02:39:24 Pegasus kernel: Call Trace:
    Oct 13 02:39:24 Pegasus kernel: <TASK>
    Oct 13 02:39:24 Pegasus kernel: __filemap_get_folio+0x98/0x1ff
    Oct 13 02:39:24 Pegasus kernel: filemap_fault+0x6e/0x524
    Oct 13 02:39:24 Pegasus kernel: __do_fault+0x2d/0x6e
    Oct 13 02:39:24 Pegasus kernel: __handle_mm_fault+0x9a5/0xc7d
    Oct 13 02:39:24 Pegasus kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a
    Oct 13 02:39:24 Pegasus kernel: handle_mm_fault+0x113/0x1d7
    Oct 13 02:39:24 Pegasus kernel: do_user_addr_fault+0x36a/0x514
    Oct 13 02:39:24 Pegasus kernel: exc_page_fault+0xfc/0x11e
    Oct 13 02:39:24 Pegasus kernel: asm_exc_page_fault+0x22/0x30
    Oct 13 02:39:24 Pegasus kernel: RIP: 0033:0x14760dfc57b5
    Oct 13 02:39:24 Pegasus kernel: Code: 8b 48 08 48 8b 32 48 8b 00 48 39 f0 73 09 48 8d 14 08 48 39 d6 eb 0c 48 39 c6 73 0b 48 8d 14 0e 48 39 d0 73 02 0f 0b 48 89 c7 <f3> a4 66 48 8d 3d 59 b7 22 00 66 66 48 e8 d9 d8 f6 ff 48 89 28 48
    Oct 13 02:39:24 Pegasus kernel: RSP: 002b:000014744eb4a900 EFLAGS: 00010212
    Oct 13 02:39:24 Pegasus kernel: RAX: 00001473fe1e4ea0 RBX: 000014744eb4aa70 RCX: 0000000000004000
    Oct 13 02:39:24 Pegasus kernel: RDX: 00001459b93431bd RSI: 00001459b933f1bd RDI: 00001473fe1e4ea0
    Oct 13 02:39:24 Pegasus kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 000014744eb4a718
    Oct 13 02:39:24 Pegasus kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
    Oct 13 02:39:24 Pegasus kernel: R13: 000014744eb4aae0 R14: 0000147418fce8a0 R15: 000014744eb4aa60
    Oct 13 02:39:24 Pegasus kernel: </TASK>
    Oct 13 02:39:24 Pegasus kernel: Modules linked in: ccp veth nvidia_uvm(PO) xt_nat xt_CHECKSUM cmac ipt_REJECT nf_reject_ipv4 cifs xt_tcpudp asn1_decoder cifs_arc4 cifs_md4 oid_registry dns_resolver ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod nct6775 nct6775_core hwmon_vid efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls ipv6 e1000e r8169 realtek i915 iosf_mbi drm_buddy i2c_algo_bit nvidia_drm(PO) ttm nvidia_modeset(PO) wmi_bmof x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm nvidia(PO) crct10dif_pclmul drm_display_helper crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel drm_kms_helper crypto_simd cryptd rapl intel_cstate drm intel_uncore i2c_i801 intel_gtt i2c_smbus agpgart ahci i2c_core libahci input_leds joydev
    Oct 13 02:39:24 Pegasus kernel: syscopyarea led_class corsair_psu sysfillrect sysimgblt fb_sys_fops thermal wmi fan tpm_crb tpm_tis video tpm_tis_core backlight tpm acpi_pad acpi_tad button unix [last unloaded: e1000e]
    Oct 13 02:39:24 Pegasus kernel: CR2: 0000000000000116
    Oct 13 02:39:24 Pegasus kernel: ---[ end trace 0000000000000000 ]---
    Oct 13 02:39:24 Pegasus kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
    Oct 13 02:39:24 Pegasus kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
    Oct 13 02:39:24 Pegasus kernel: RSP: 0000:ffffc900047dfcc0 EFLAGS: 00010246
    Oct 13 02:39:24 Pegasus kernel: RAX: 00000000000000e2 RBX: 00000000000000e2 RCX: 00000000000000e2
    Oct 13 02:39:24 Pegasus kernel: RDX: 0000000000000001 RSI: ffff88819e20cdb0 RDI: 00000000000000e2
    Oct 13 02:39:24 Pegasus kernel: RBP: 0000000000000000 R08: 000000000000003c R09: ffffc900047dfcd0
    Oct 13 02:39:24 Pegasus kernel: R10: ffffc900047dfcd0 R11: ffffc900047dfd48 R12: 0000000000000000
    Oct 13 02:39:24 Pegasus kernel: R13: ffff88812ca1bab8 R14: 000000000001693f R15: ffff88812ca1bac0
    Oct 13 02:39:24 Pegasus kernel: FS:  000014744eb4bb30(0000) GS:ffff88883c2c0000(0000) knlGS:0000000000000000
    Oct 13 02:39:24 Pegasus kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 13 02:39:24 Pegasus kernel: CR2: 0000000000000116 CR3: 00000001a8754004 CR4: 00000000007726e0
    Oct 13 02:39:24 Pegasus kernel: PKRU: 55555554


    And again I can't kill qbittorrent. It always qbittorrent. When i try to kill it from gui, its says "Server Error".
    SSH into the server and run "docker restarte qbittorrent"

     

    docker restart qbittorrent
    Error response from daemon: Cannot restart container qbittorrent: tried to kill container, but did not receive an exit event



    Plugins in common:

     

    ca.backup2.plg - 2022.07.23  (Up to date)
    community.applications.plg - 2022.09.30  (Up to date)
    fix.common.problems.plg - 2022.10.09  (Up to date)
    unassigned.devices.plg - 2022.10.12  (Up to date)


    And when I trying to kill qbittorrent I see this all the time:
     

    Oct 13 05:58:09 Pegasus  emhttpd: shcmd (835): umount /mnt/cache
    Oct 13 05:58:09 Pegasus root: umount: /mnt/cache: target is busy.
    Oct 13 05:58:09 Pegasus  emhttpd: shcmd (835): exit status: 32
    Oct 13 05:58:09 Pegasus  emhttpd: Retry unmounting disk share(s)...
    Oct 13 05:58:14 Pegasus  emhttpd: Unmounting disks...
    Oct 13 05:58:14 Pegasus  emhttpd: shcmd (836): umount /mnt/cache
    Oct 13 05:58:14 Pegasus root: umount: /mnt/cache: target is busy.
    Oct 13 05:58:14 Pegasus  emhttpd: shcmd (836): exit status: 32
    Oct 13 05:58:14 Pegasus  emhttpd: Retry unmounting disk share(s)...
    Oct 13 05:58:19 Pegasus  emhttpd: Unmounting disks...
    Oct 13 05:58:19 Pegasus  emhttpd: shcmd (837): umount /mnt/cache


    But all my other containers are working normally.

    I managed to get my syslog before i forced a reboot.

    First thing I did when I login to my unraid was to stop qbittorrent. Then got the "Server Error" message.
    After that login to my unraid with SSH and run command "docker restart qbittorrent" Got that error little bit up here in my post.
    After that i did the soft reboot with command: powerdown -r
    You can probably see all that in my syslog.


     


     

    syslog.txt

    Edited by CiscoCoreX
    Link to comment

    Anyone with this issue using ipvlan? If using macvlan try switching to ipvlan:

     

    (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right))

    • Like 2
    Link to comment
    40 minutes ago, JorgeB said:

    If using macvlan try switching to ipvlan:

    i was using macvlan for one docker container, but have switched it to ipvlan now.

     

    @ich777 thanks for the pm.

    • Like 1
    Link to comment
    5 hours ago, JorgeB said:

    Anyone with this issue using ipvlan? If using macvlan try switching to ipvlan

     

    I'll have to check my configs after my current Safe Mode test is done tomorrow, but I do run a docker network, which I believe is macvlan but I'd have to verify that. 

    • Like 1
    Link to comment
    5 hours ago, JorgeB said:

    Anyone with this issue using ipvlan? If using macvlan try switching to ipvlan:

     

    (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right))

    I have changed to ipvlan in the docker settings now, let's see how it goes.

    • Like 1
    Link to comment
    11 hours ago, CiscoCoreX said:

    And again I can't kill qbittorrent. It always qbittorrent. When i try to kill it from gui, its says "Server Error".
    SSH into the server and run "docker restarte qbittorrent"

    I hate jumping to conclusions, but I also experience this with binhex's version of qBittorrent when my systems locks up (though it didn't last night after the removal of some of the above plugins, so we'll see).

     

    6 hours ago, JorgeB said:

    Anyone with this issue using ipvlan? If using macvlan try switching to ipvlan:

    Everything I have is using macvlan.  I'm going to follow old troubleshooting lore and only change one thing at a time.  I'll make this modification if/when the next system lockup occurs and keep you posted.

    • Like 1
    Link to comment

    Checking in. It's been over 24hrs since I removed 7 plugins in the top post for testing.

     

    I have been running my machine as I normally would besides my torrents saving to the array instead of an unassigned device. Haven't had any crashes yet like I was having before. 

     

    My dockers are using macvlan, and I wont be changing to ipvlan just to keep my machine the same has it has been since starting the plugin test.

     

    Will continue with updated info when needed.

    • Like 1
    Link to comment

    IDK, if related, since update to 6.11.X Windows VM freeze in about one or two hours. There is no syslog or VM log saying anything. Just freeze. Initially I was toying with virtiosfs, so.

     

    I create a new VM configuration from the scratch and the same happens.

     

    The below log dump, has with the Windows VM (Windows 11Test) in freeze state. It happens after midnight and before 8:00 AM today.

     

    Will rollback to 6.10 and report and/or remove virtiosfs and post back.

     

     

     

     

     

    maxraid-diagnostics-20221014-0849.zip

    Link to comment

    I recently u pdated to 6.11.1 from 6.10 stable.  this morning the WebGUI was unresponsive and could only see the unraid banner at the top of the screen.  I SSH'd and ran Diags and I am seeing the same as above.

     

    Oct 14 05:51:28 Debo-Server kernel: BUG: kernel NULL pointer dereference, address: 0000000000000096
    Oct 14 05:51:28 Debo-Server kernel: #PF: supervisor read access in kernel mode
    Oct 14 05:51:28 Debo-Server kernel: #PF: error_code(0x0000) - not-present page
    Oct 14 05:51:28 Debo-Server kernel: PGD 0 P4D 0 
    Oct 14 05:51:28 Debo-Server kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
    Oct 14 05:51:28 Debo-Server kernel: CPU: 0 PID: 27478 Comm: Disk Tainted: P           O      5.19.14-Unraid #1
    Oct 14 05:51:28 Debo-Server kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C36/PRESTIGE X570 CREATION (MS-7C36), BIOS 1.D2 04/09/2021
    Oct 14 05:51:28 Debo-Server kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
    Oct 14 05:51:28 Debo-Server kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
    Oct 14 05:51:28 Debo-Server kernel: RSP: 0000:ffffc90003fe7cc0 EFLAGS: 00010246
    Oct 14 05:51:28 Debo-Server kernel: RAX: 0000000000000062 RBX: 0000000000000062 RCX: 0000000000000062
    Oct 14 05:51:28 Debo-Server kernel: RDX: 0000000000000001 RSI: ffff888b2f3f46d8 RDI: 0000000000000062
    Oct 14 05:51:28 Debo-Server kernel: RBP: 0000000000000000 R08: 000000000000001c R09: ffffc90003fe7cd0
    Oct 14 05:51:28 Debo-Server kernel: R10: ffffc90003fe7cd0 R11: ffffc90003fe7d48 R12: 0000000000000000
    Oct 14 05:51:28 Debo-Server kernel: R13: ffff888173992f78 R14: 00000000001b03de R15: ffff888173992f80
    Oct 14 05:51:28 Debo-Server kernel: FS:  0000151592c9c6c0(0000) GS:ffff88900e800000(0000) knlGS:0000000000000000
    Oct 14 05:51:28 Debo-Server kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 14 05:51:28 Debo-Server kernel: CR2: 0000000000000096 CR3: 0000000a16c50000 CR4: 0000000000750ef0
    Oct 14 05:51:28 Debo-Server kernel: PKRU: 55555554
    Oct 14 05:51:28 Debo-Server kernel: Call Trace:
    Oct 14 05:51:28 Debo-Server kernel: <TASK>
    Oct 14 05:51:28 Debo-Server kernel: __filemap_get_folio+0x98/0x1ff
    Oct 14 05:51:28 Debo-Server kernel: ? _raw_spin_unlock+0x14/0x29
    Oct 14 05:51:28 Debo-Server kernel: filemap_fault+0x6e/0x524
    Oct 14 05:51:28 Debo-Server kernel: __do_fault+0x30/0x6e
    Oct 14 05:51:28 Debo-Server kernel: __handle_mm_fault+0x9a5/0xc7d
    Oct 14 05:51:28 Debo-Server kernel: handle_mm_fault+0x113/0x1d7
    Oct 14 05:51:28 Debo-Server kernel: do_user_addr_fault+0x36a/0x514
    Oct 14 05:51:28 Debo-Server kernel: exc_page_fault+0xfc/0x11e
    Oct 14 05:51:28 Debo-Server kernel: asm_exc_page_fault+0x22/0x30
    Oct 14 05:51:28 Debo-Server kernel: RIP: 0033:0x1515974f27cd
    Oct 14 05:51:28 Debo-Server kernel: Code: 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 89 f8 48 83 fa 20 72 23 <c5> fe 6f 06 48 83 fa 40 0f 87 a5 00 00 00 c5 fe 6f 4c 16 e0 c5 fe
    Oct 14 05:51:28 Debo-Server kernel: RSP: 002b:0000151592c9b808 EFLAGS: 00010202
    Oct 14 05:51:28 Debo-Server kernel: RAX: 000015157801b710 RBX: 00001515780062f8 RCX: 0000151592c9ba40
    Oct 14 05:51:28 Debo-Server kernel: RDX: 0000000000004000 RSI: 000014f00e7de5a3 RDI: 000015157801b710
    Oct 14 05:51:28 Debo-Server kernel: RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
    Oct 14 05:51:28 Debo-Server kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
    Oct 14 05:51:28 Debo-Server kernel: R13: 0000151592c9bac0 R14: 0000000000000003 R15: 0000151578005030
    Oct 14 05:51:28 Debo-Server kernel: </TASK>
     

    Posting complete diagnostics as well.

    debo-server-diagnostics-20221014-0805.zip

    Link to comment
    40 minutes ago, mpiva said:

    since update to 6.11.X Windows VM freeze in about one or two hours.

    This is likely a different issue, unless you get the same call trace as in the OP, and there's not one in the diags posted.

    Link to comment
    6 minutes ago, B_Sinn3d said:

    I am seeing the same as above.

    Yes this is the same problem, you can try running without the plugins listed above and/or switching to ipvlan, we are still investigation, and still not clear what causes this issue.

    Link to comment
    On 10/13/2022 at 5:33 AM, JorgeB said:

    Anyone with this issue using ipvlan? If using macvlan try switching to ipvlan

     

    My Safe Mode test completed 2 1/2 days of uptime so I'm calling that a pass. So this leaves any issues caused by the VM Manager, Docker, or plugins.

     

    I started my next test with just the docker macvlan switched to ipvlan and we'll see how it goes. Looking to see another 2-3 days of uptime without errors and I'll reevaluate.

    Edited by JesterEE
    • Like 1
    Link to comment

    It happens again right now, can't kill or restart qbittorrent.
    It has to be something with this new unraid version (6.11.1) and any torrent program.
    Never had problems with v.6.10.3

     

    Oct 15 23:03:00 Pegasus kernel: eth0: renamed from veth734cdbc
    Oct 15 23:09:29 Pegasus kernel: BUG: kernel NULL pointer dereference, address: 0000000000000076
    Oct 15 23:09:29 Pegasus kernel: #PF: supervisor read access in kernel mode
    Oct 15 23:09:29 Pegasus kernel: #PF: error_code(0x0000) - not-present page
    Oct 15 23:09:29 Pegasus kernel: PGD 0 P4D 0 
    Oct 15 23:09:29 Pegasus kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
    Oct 15 23:09:29 Pegasus kernel: CPU: 6 PID: 13670 Comm: Disk Tainted: P           O      5.19.14-Unraid #1
    Oct 15 23:09:29 Pegasus kernel: Hardware name: ASUS System Product Name/PRIME B560M-K, BIOS 1605 05/13/2022
    Oct 15 23:09:29 Pegasus kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
    Oct 15 23:09:29 Pegasus kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
    Oct 15 23:09:29 Pegasus kernel: RSP: 0000:ffffc90003763cc0 EFLAGS: 00010246
    Oct 15 23:09:29 Pegasus kernel: RAX: 0000000000000042 RBX: 0000000000000042 RCX: 0000000000000042
    Oct 15 23:09:29 Pegasus kernel: RDX: 0000000000000001 RSI: ffff888204e58490 RDI: 0000000000000042
    Oct 15 23:09:29 Pegasus kernel: RBP: 0000000000000000 R08: 0000000000000014 R09: ffffc90003763cd0
    Oct 15 23:09:29 Pegasus kernel: R10: ffffc90003763cd0 R11: ffffc90003763d48 R12: 0000000000000000
    Oct 15 23:09:29 Pegasus kernel: R13: ffff88822b3a2f78 R14: 0000000000001017 R15: ffff88822b3a2f80
    Oct 15 23:09:29 Pegasus kernel: FS:  0000151b43f21b30(0000) GS:ffff88883c180000(0000) knlGS:0000000000000000
    Oct 15 23:09:29 Pegasus kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 15 23:09:29 Pegasus kernel: CR2: 0000000000000076 CR3: 0000000248a7c004 CR4: 00000000007726e0
    Oct 15 23:09:29 Pegasus kernel: PKRU: 55555554
    Oct 15 23:09:29 Pegasus kernel: Call Trace:
    Oct 15 23:09:29 Pegasus kernel: <TASK>
    Oct 15 23:09:29 Pegasus kernel: __filemap_get_folio+0x98/0x1ff
    Oct 15 23:09:29 Pegasus kernel: filemap_fault+0x6e/0x524
    Oct 15 23:09:29 Pegasus kernel: __do_fault+0x2d/0x6e
    Oct 15 23:09:29 Pegasus kernel: __handle_mm_fault+0x9a5/0xc7d
    Oct 15 23:09:29 Pegasus kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a
    Oct 15 23:09:29 Pegasus kernel: handle_mm_fault+0x113/0x1d7
    Oct 15 23:09:29 Pegasus kernel: do_user_addr_fault+0x36a/0x514
    Oct 15 23:09:29 Pegasus kernel: exc_page_fault+0xfc/0x11e
    Oct 15 23:09:29 Pegasus kernel: asm_exc_page_fault+0x22/0x30
    Oct 15 23:09:29 Pegasus kernel: RIP: 0033:0x151b466937b5
    Oct 15 23:09:29 Pegasus kernel: Code: 8b 48 08 48 8b 32 48 8b 00 48 39 f0 73 09 48 8d 14 08 48 39 d6 eb 0c 48 39 c6 73 0b 48 8d 14 0e 48 39 d0 73 02 0f 0b 48 89 c7 <f3> a4 66 48 8d 3d 59 b7 22 00 66 66 48 e8 d9 d8 f6 ff 48 89 28 48
    Oct 15 23:09:29 Pegasus kernel: RSP: 002b:0000151b43f20900 EFLAGS: 00010212
    Oct 15 23:09:29 Pegasus kernel: RAX: 00001517aa3b7010 RBX: 0000151b43f20a70 RCX: 0000000000004000
    Oct 15 23:09:29 Pegasus kernel: RDX: 00001512fce1b3d3 RSI: 00001512fce173d3 RDI: 00001517aa3b7010
    Oct 15 23:09:29 Pegasus kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000151b43f20718
    Oct 15 23:09:29 Pegasus kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
    Oct 15 23:09:29 Pegasus kernel: R13: 0000151b43f20ae0 R14: 0000151afdd76f80 R15: 0000151b43f20a60
    Oct 15 23:09:29 Pegasus kernel: </TASK>
    Oct 15 23:09:29 Pegasus kernel: Modules linked in: ipvlan nvidia_uvm(PO) cmac cifs asn1_decoder cifs_arc4 cifs_md4 oid_registry dns_resolver xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle macvlan vhost_net tun vhost vhost_iotlb tap xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod nct6775 nct6775_core hwmon_vid efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls ipv6 e1000e r8169 realtek i915 iosf_mbi nvidia_drm(PO) drm_buddy i2c_algo_bit nvidia_modeset(PO) ttm x86_pkg_temp_thermal intel_powerclamp wmi_bmof coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel drm_display_helper nvidia(PO) aesni_intel crypto_simd drm_kms_helper cryptd rapl intel_cstate drm intel_uncore intel_gtt ahci i2c_i801 agpgart libahci i2c_smbus i2c_core input_leds joydev led_class
    Oct 15 23:09:29 Pegasus kernel: syscopyarea corsair_psu sysfillrect sysimgblt thermal fb_sys_fops fan wmi tpm_crb tpm_tis video tpm_tis_core backlight tpm acpi_tad acpi_pad button unix [last unloaded: e1000e]
    Oct 15 23:09:29 Pegasus kernel: CR2: 0000000000000076
    Oct 15 23:09:29 Pegasus kernel: ---[ end trace 0000000000000000 ]---
    Oct 15 23:09:29 Pegasus kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
    Oct 15 23:09:29 Pegasus kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
    Oct 15 23:09:29 Pegasus kernel: RSP: 0000:ffffc90003763cc0 EFLAGS: 00010246
    Oct 15 23:09:29 Pegasus kernel: RAX: 0000000000000042 RBX: 0000000000000042 RCX: 0000000000000042
    Oct 15 23:09:29 Pegasus kernel: RDX: 0000000000000001 RSI: ffff888204e58490 RDI: 0000000000000042
    Oct 15 23:09:29 Pegasus kernel: RBP: 0000000000000000 R08: 0000000000000014 R09: ffffc90003763cd0
    Oct 15 23:09:29 Pegasus kernel: R10: ffffc90003763cd0 R11: ffffc90003763d48 R12: 0000000000000000
    Oct 15 23:09:29 Pegasus kernel: R13: ffff88822b3a2f78 R14: 0000000000001017 R15: ffff88822b3a2f80
    Oct 15 23:09:29 Pegasus kernel: FS:  0000151b43f21b30(0000) GS:ffff88883c180000(0000) knlGS:0000000000000000
    Oct 15 23:09:29 Pegasus kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 15 23:09:29 Pegasus kernel: CR2: 0000000000000076 CR3: 0000000248a7c004 CR4: 00000000007726e0
    Oct 15 23:09:29 Pegasus kernel: PKRU: 55555554

     

    image.thumb.png.b10f7157cab3cd87f8861490a9780f83.png

     

    Edited by CiscoCoreX
    • Like 1
    Link to comment
    7 hours ago, B_Sinn3d said:

    I switched to ipvlan and GUI crashed again on me today.

    Thx, I guess we can rule that out as the problem, are you also running any torrent program? Could it be related to how torrents write files partially and out of order? For anyone using torrents does enabling pre-allocating all files makes any difference?

    Link to comment

    Just an update from me:  It's been nearly 3 days without a failure for me.  This is what I uninstalled from a plugin perspective:

    • ca.backup2.plg - 2022.07.23 (Up to date)

    • dynamix.active.streams.plg - 2020.06.17 (Up to date)

    • file.activity.plg - 2022.08.19 (Up to date)

     

    Again, I do run binhex's qbittorrent client, largely writing to an unassigned drive.  But also again, no failures since removing these plugins.  I'm cautiously optimistic. 

    • Like 1
    Link to comment
    1 hour ago, sundown said:

    Just an update from me:  It's been nearly 3 days without a failure for me.  This is what I uninstalled from a plugin perspective:

    • ca.backup2.plg - 2022.07.23 (Up to date)

    • dynamix.active.streams.plg - 2020.06.17 (Up to date)

    • file.activity.plg - 2022.08.19 (Up to date)

     

    Again, I do run binhex's qbittorrent client, largely writing to an unassigned drive.  But also again, no failures since removing these plugins.  I'm cautiously optimistic. 

    Hi,

     

    I was on day 4 without any problems, when i happens for couple days ago, and yesterday again.
    The thing is, why it is always the trorrent program. All other containers are working normally.
    I believe it have to do something with the torrent program.

     

    I have one dedicated 1 TB SSD disk for only downloads under the Pool Devices.
     

    I only have SSD disks on my unraid.

     

    image.thumb.png.183e55c0fde8b50cbb3e5154292c34d8.png

    Edited by CiscoCoreX
    Link to comment
    3 hours ago, JorgeB said:

    Thx, I guess we can rule that out as the problem, are you also running any torrent program? Could it be related to how torrents write files partially and out of order? For anyone using torrents does enabling pre-allocating all files makes any difference?

    Hi,

     

    Mine is off. Should i try to have it enabled?

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.