Jump to content
We're Hiring! Full Stack Developer ×

BOGu

Members
 View Profile  See their activity

  • Posts

    8

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

BOGu's Achievements

Noob

Noob (1/14)

0

Reputation

  1. BOGu
    Introduction Recently, I encountered a strange issue after replacing my cache disk from an NVMe SSD to a SATA SSD. The system's disk IO wait time would spike and speeds would drop to around a few Mb/s when writing large amounts of data continuously. Initially, I thought it was a problem with the SATA SSD, so I repurchased a Crucial SATA SSD. However, the issue persisted. Troubleshooting Process Since the problem remained after replacing the SSD, I began to suspect an issue with the unraid system itself. I thoroughly searched the unraid official forums and community but couldn't find any solutions for similar issues. Eventually, I decided to try downgrading the system version and then upgrading it back to the latest version. Solution To my surprise, downgrading the system version and then upgrading it back to the latest version resolved the issue! I've been monitoring the system since, and it has been running smoothly without any slowdowns or disk dropouts. Summary This experience made me realize that the stability of the unraid system can sometimes be affected by unknown factors. If you encounter similar issues, I recommend trying to downgrade the system version and then upgrade it back to the latest version to resolve them. Additional Notes My HPE Microserver GEN10 Plus Server configuration is as follows: CPU: Intel® Xeon® E-2136 CPU @ 3.30GHz RAM: 40GB Cache: Crucial MX500 1TB SATA SSD The unraid version I was using is 6.12.10. I hope my sharing can help those who encounter similar problems. Here are some additional tips: Before changing hardware, it is recommended to back up important data. If you are unsure of how to proceed, consult experienced users on the unraid official forums or community. Always keep your unraid system up to date. Happy unraiding!
  2. BOGu started following Macvlan Error Causing Unraid System Inaccessibility and Unraid cache drive speed drops to 1-2MB/s under heavy write load
  3. BOGu
    Hello everyone, I'm having an issue with my Unraid server and I'm hoping to get some help. I've added a J.ZAO 3 Series 2.5" 960GB SATA SSD to my array as a cache drive. The drive has been successfully detected, partitioned, formatted, and mounted at /mnt/cache. The issue I'm having is that when I write a large amount of data to the cache drive, the write speed drops from several hundred MB/s down to 1-2MB/s. I've checked the SMART information for the drive and there are no errors or warnings. The drive's write cache and read cache are both enabled. Here is some information that may be relevant to the issue: hdparm -Tt /dev/sde /dev/sde: Timing cached reads: 34382 MB in 1.98 seconds = 17372.10 MB/sec Timing buffered disk reads: 576 MB in 3.00 seconds = 191.98 MB/sec iostat output: 05/10/2024 09:37:49 AM avg-cpu: %user %nice %system %iowait %steal %idle 0.75 0.00 0.84 61.89 0.00 36.52 Device r/s rkB/s rrqm/s %rrqm r_await rareq-sz w/s wkB/s wrqm/s %wrqm w_await wareq-sz d/s dkB/s drqm/s %drqm d_await dareq-sz f/s f_await aqu-sz %util sde 0.00 0.00 0.00 0.00 0.00 0.00 6.00 3888.00 0.00 0.00 1430.33 648.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 8.58 100.00 Drive logs： Apr 29 11:02:04 HOME-unRAID kernel: ata4: SATA max UDMA/133 abar m2048@0x87613000 port 0x87613280 irq 130 Apr 29 11:02:04 HOME-unRAID kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 29 11:02:04 HOME-unRAID kernel: ata4.00: ATA-11: J.ZAO 3 SERIES 2.5 INCH 960GB SATA SSD, SN12155, max UDMA/133 Apr 29 11:02:04 HOME-unRAID kernel: ata4.00: 1875385008 sectors, multi 1: LBA48 NCQ (depth 32), AA Apr 29 11:02:04 HOME-unRAID kernel: ata4.00: configured for UDMA/133 Apr 29 11:02:04 HOME-unRAID kernel: sd 4:0:0:0: [sde] 1875385008 512-byte logical blocks: (960 GB/894 GiB) Apr 29 11:02:04 HOME-unRAID kernel: sd 4:0:0:0: [sde] Write Protect is off Apr 29 11:02:04 HOME-unRAID kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00 Apr 29 11:02:04 HOME-unRAID kernel: sd 4:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Apr 29 11:02:04 HOME-unRAID kernel: sd 4:0:0:0: [sde] Preferred minimum I/O size 512 bytes Apr 29 11:02:04 HOME-unRAID kernel: sde: sde1 Apr 29 11:02:04 HOME-unRAID kernel: sd 4:0:0:0: [sde] Attached SCSI disk Apr 29 11:04:07 HOME-unRAID emhttpd: J.ZAO_3_SERIES_2.5_INCH_960GB_SATA_SSD_NBN380T000280 (sde) 512 1875385008 Apr 29 11:04:07 HOME-unRAID emhttpd: import 30 cache device: (sde) J.ZAO_3_SERIES_2.5_INCH_960GB_SATA_SSD_NBN380T000280 Apr 29 11:04:07 HOME-unRAID emhttpd: read SMART /dev/sde Apr 29 11:04:16 HOME-unRAID emhttpd: shcmd (42): mount -t xfs -o noatime,nouuid /dev/sde1 /mnt/cache Apr 29 11:04:16 HOME-unRAID kernel: XFS (sde1): Mounting V5 Filesystem Apr 29 11:04:16 HOME-unRAID kernel: XFS (sde1): Ending clean mount May 10 09:27:39 HOME-unRAID kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA I've tried searching the Unraid forums for similar issues but haven't been able to find anything that has helped. Has anyone else experienced a similar issue? Any advice or help would be greatly appreciated. System Information: Unraid version:6.12.10 Hardware: HPE Microserver GEN10 Plus Server Cache drive: J.ZAO 3 Series 2.5" 960GB SATA SSD home-unraid-diagnostics-20240507-1541.zip
  4. BOGu
    05/09/2024 01:42:09 PM avg-cpu: %user %nice %system %iowait %steal %idle 1.67 0.00 0.83 25.63 0.00 71.87 Device r/s rkB/s rrqm/s %rrqm r_await rareq-sz w/s wkB/s wrqm/s %wrqm w_await wareq-sz d/s dkB/s drqm/s %drqm d_await dareq-sz f/s f_await aqu-sz %util sde 0.00 0.00 0.00 0.00 0.00 0.00 60.00 2180.00 4.00 6.25 103.70 36.33 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 6.22 100.00 When updating containers and there is a lot of other write activity to disk, the IO wait situation is
  5. BOGu
    System: HPE Microserver GEN10 Plus Server Single PCIe slot Cache drive: SATA SSD (previously M.2 SSD) Issue: After replacing the M.2 SSD cache drive with a SATA SSD, I am experiencing high CPU IO wait when updating docker container images. I have checked the disk logs and there are no errors. Additional Information: I have migrated all data to the new SATA SSD cache drive. I have been using the SATA SSD cache drive for a few weeks now. I have tried restarting the Docker service and the Unraid server. I have attached the system diagnostics report to this post. Please help me troubleshoot and resolve this issue. Thank you. Additional Questions: Could the switch from an M.2 SSD to a SATA SSD be causing this issue? Are there any specific configuration settings that I need to adjust for using a SATA SSD as a cache drive? Thank you for your time and assistance. home-unraid-diagnostics-20240507-1541.zip
  6. BOGu
    Hello everyone, I'm encountering a critical issue with my unRAID system, and I could really use some assistance in troubleshooting it. The problem has been causing my system to become inaccessible, and I'm getting the following error message in my logs: Jul 24 16:51:30 HOME-unRAID kernel: ------------[ cut here ]------------ Jul 24 16:51:30 HOME-unRAID kernel: WARNING: CPU: 4 PID: 12624 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: Modules linked in: macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap veth nfsd auth_rpcgss oid_registry lockd grace sunrpc xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_nat 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 efivarfs 8021q garp mrp bridge stp llc bonding tls igb intel_rapl_msr intel_rapl_common iosf_mbi intel_pmc_core_pltdrv intel_pmc_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel mgag200 sha512_ssse3 drm_shmem_helper Jul 24 16:51:30 HOME-unRAID kernel: ipmi_ssif aesni_intel drm_kms_helper crypto_simd cryptd drm rapl backlight intel_cstate syscopyarea nvme sysfillrect ahci i2c_algo_bit mei_me sysimgblt acpi_ipmi intel_uncore fb_sys_fops i2c_core mei nvme_core libahci intel_pch_thermal wmi ipmi_si acpi_tad acpi_power_meter button unix [last unloaded: igb] Jul 24 16:51:30 HOME-unRAID kernel: CPU: 4 PID: 12624 Comm: kworker/u24:13 Tainted: P O 6.1.38-Unraid #2 Jul 24 16:51:30 HOME-unRAID kernel: Hardware name: HPE ProLiant MicroServer Gen10 Plus/ProLiant MicroServer Gen10 Plus, BIOS U48 01/12/2023 Jul 24 16:51:30 HOME-unRAID kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Jul 24 16:51:30 HOME-unRAID kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Jul 24 16:51:30 HOME-unRAID kernel: RSP: 0018:ffffc90000200d98 EFLAGS: 00010202 Jul 24 16:51:30 HOME-unRAID kernel: RAX: 0000000000000001 RBX: ffff8883ed873e00 RCX: df39c6a6af487b6b Jul 24 16:51:30 HOME-unRAID kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8883ed873e00 Jul 24 16:51:30 HOME-unRAID kernel: RBP: 0000000000000001 R08: 594bdfbccc8db56d R09: b04b8ad271ad270a Jul 24 16:51:30 HOME-unRAID kernel: R10: 111bd9a8ef71afa8 R11: ffffc90000200d60 R12: ffffffff82a11d00 Jul 24 16:51:30 HOME-unRAID kernel: R13: 000000000001f16e R14: ffff8881c9b67500 R15: 0000000000000000 Jul 24 16:51:30 HOME-unRAID kernel: FS: 0000000000000000(0000) GS:ffff88846eb00000(0000) knlGS:0000000000000000 Jul 24 16:51:30 HOME-unRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 24 16:51:30 HOME-unRAID kernel: CR2: 0000564f588bd000 CR3: 00000001dab62001 CR4: 00000000003706e0 Jul 24 16:51:30 HOME-unRAID kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 24 16:51:30 HOME-unRAID kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jul 24 16:51:30 HOME-unRAID kernel: Call Trace: Jul 24 16:51:30 HOME-unRAID kernel: <IRQ> Jul 24 16:51:30 HOME-unRAID kernel: ? __warn+0xab/0x122 Jul 24 16:51:30 HOME-unRAID kernel: ? report_bug+0x109/0x17e Jul 24 16:51:30 HOME-unRAID kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: ? handle_bug+0x41/0x6f Jul 24 16:51:30 HOME-unRAID kernel: ? exc_invalid_op+0x13/0x60 Jul 24 16:51:30 HOME-unRAID kernel: ? asm_exc_invalid_op+0x16/0x20 Jul 24 16:51:30 HOME-unRAID kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: ? nf_nat_inet_fn+0x60/0x1a8 [nf_nat] Jul 24 16:51:30 HOME-unRAID kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: nf_hook_slow+0x3a/0x96 Jul 24 16:51:30 HOME-unRAID kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jul 24 16:51:30 HOME-unRAID kernel: NF_HOOK.constprop.0+0x79/0xd9 Jul 24 16:51:30 HOME-unRAID kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jul 24 16:51:30 HOME-unRAID kernel: __netif_receive_skb_one_core+0x77/0x9c Jul 24 16:51:30 HOME-unRAID kernel: process_backlog+0x8c/0x116 Jul 24 16:51:30 HOME-unRAID kernel: __napi_poll.constprop.0+0x28/0x124 Jul 24 16:51:30 HOME-unRAID kernel: net_rx_action+0x159/0x24f Jul 24 16:51:30 HOME-unRAID kernel: __do_softirq+0x126/0x288 Jul 24 16:51:30 HOME-unRAID kernel: do_softirq+0x7f/0xab Jul 24 16:51:30 HOME-unRAID kernel: </IRQ> Jul 24 16:51:30 HOME-unRAID kernel: <TASK> Jul 24 16:51:30 HOME-unRAID kernel: __local_bh_enable_ip+0x4c/0x6b Jul 24 16:51:30 HOME-unRAID kernel: netif_rx+0x52/0x5a Jul 24 16:51:30 HOME-unRAID kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 24 16:51:30 HOME-unRAID kernel: ? _raw_spin_unlock+0x14/0x29 Jul 24 16:51:30 HOME-unRAID kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Jul 24 16:51:30 HOME-unRAID kernel: process_one_work+0x1a8/0x295 Jul 24 16:51:30 HOME-unRAID kernel: worker_thread+0x18b/0x244 Jul 24 16:51:30 HOME-unRAID kernel: ? rescuer_thread+0x281/0x281 Jul 24 16:51:30 HOME-unRAID kernel: kthread+0xe4/0xef Jul 24 16:51:30 HOME-unRAID kernel: ? kthread_complete_and_exit+0x1b/0x1b Jul 24 16:51:30 HOME-unRAID kernel: ret_from_fork+0x1f/0x30 Jul 24 16:51:30 HOME-unRAID kernel: </TASK> Jul 24 16:51:30 HOME-unRAID kernel: ---[ end trace 0000000000000000 ]--- My system details are as follows: unRAID version: 6.1.38 Hardware: HPE ProLiant MicroServer Gen10 Plus/ProLiant MicroServer Gen10 Plus BIOS version: U48 (updated on 01/12/2023) The issue seems to be related to nf_conntrack based on the log entry. I am not certain what exactly caused this error or how to go about resolving it. I've attempted some basic troubleshooting steps like rebooting the system and checking for any recent changes to plugins or configurations, but the problem persists. I'm hoping that someone in the community can help shed some light on this matter and guide me towards a solution. If you need any additional information or logs, please let me know, and I'll provide them promptly. Thank you in advance for your time and support. Any assistance will be greatly appreciated! Best regards,
  7. BOGu started following Unraid OS version 6.12.0-rc2 available and Error Message Causing System Inaccessibility - Need Help!
  8. BOGu
    Hello everyone, I'm encountering a critical issue with my unRAID system, and I could really use some assistance in troubleshooting it. The problem has been causing my system to become inaccessible, and I'm getting the following error message in my logs: Jul 24 16:51:30 HOME-unRAID kernel: ------------[ cut here ]------------ Jul 24 16:51:30 HOME-unRAID kernel: WARNING: CPU: 4 PID: 12624 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: Modules linked in: macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap veth nfsd auth_rpcgss oid_registry lockd grace sunrpc xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_nat 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 efivarfs 8021q garp mrp bridge stp llc bonding tls igb intel_rapl_msr intel_rapl_common iosf_mbi intel_pmc_core_pltdrv intel_pmc_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel mgag200 sha512_ssse3 drm_shmem_helper Jul 24 16:51:30 HOME-unRAID kernel: ipmi_ssif aesni_intel drm_kms_helper crypto_simd cryptd drm rapl backlight intel_cstate syscopyarea nvme sysfillrect ahci i2c_algo_bit mei_me sysimgblt acpi_ipmi intel_uncore fb_sys_fops i2c_core mei nvme_core libahci intel_pch_thermal wmi ipmi_si acpi_tad acpi_power_meter button unix [last unloaded: igb] Jul 24 16:51:30 HOME-unRAID kernel: CPU: 4 PID: 12624 Comm: kworker/u24:13 Tainted: P O 6.1.38-Unraid #2 Jul 24 16:51:30 HOME-unRAID kernel: Hardware name: HPE ProLiant MicroServer Gen10 Plus/ProLiant MicroServer Gen10 Plus, BIOS U48 01/12/2023 Jul 24 16:51:30 HOME-unRAID kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Jul 24 16:51:30 HOME-unRAID kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Jul 24 16:51:30 HOME-unRAID kernel: RSP: 0018:ffffc90000200d98 EFLAGS: 00010202 Jul 24 16:51:30 HOME-unRAID kernel: RAX: 0000000000000001 RBX: ffff8883ed873e00 RCX: df39c6a6af487b6b Jul 24 16:51:30 HOME-unRAID kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8883ed873e00 Jul 24 16:51:30 HOME-unRAID kernel: RBP: 0000000000000001 R08: 594bdfbccc8db56d R09: b04b8ad271ad270a Jul 24 16:51:30 HOME-unRAID kernel: R10: 111bd9a8ef71afa8 R11: ffffc90000200d60 R12: ffffffff82a11d00 Jul 24 16:51:30 HOME-unRAID kernel: R13: 000000000001f16e R14: ffff8881c9b67500 R15: 0000000000000000 Jul 24 16:51:30 HOME-unRAID kernel: FS: 0000000000000000(0000) GS:ffff88846eb00000(0000) knlGS:0000000000000000 Jul 24 16:51:30 HOME-unRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 24 16:51:30 HOME-unRAID kernel: CR2: 0000564f588bd000 CR3: 00000001dab62001 CR4: 00000000003706e0 Jul 24 16:51:30 HOME-unRAID kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 24 16:51:30 HOME-unRAID kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jul 24 16:51:30 HOME-unRAID kernel: Call Trace: Jul 24 16:51:30 HOME-unRAID kernel: <IRQ> Jul 24 16:51:30 HOME-unRAID kernel: ? __warn+0xab/0x122 Jul 24 16:51:30 HOME-unRAID kernel: ? report_bug+0x109/0x17e Jul 24 16:51:30 HOME-unRAID kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: ? handle_bug+0x41/0x6f Jul 24 16:51:30 HOME-unRAID kernel: ? exc_invalid_op+0x13/0x60 Jul 24 16:51:30 HOME-unRAID kernel: ? asm_exc_invalid_op+0x16/0x20 Jul 24 16:51:30 HOME-unRAID kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: ? nf_nat_inet_fn+0x60/0x1a8 [nf_nat] Jul 24 16:51:30 HOME-unRAID kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Jul 24 16:51:30 HOME-unRAID kernel: nf_hook_slow+0x3a/0x96 Jul 24 16:51:30 HOME-unRAID kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jul 24 16:51:30 HOME-unRAID kernel: NF_HOOK.constprop.0+0x79/0xd9 Jul 24 16:51:30 HOME-unRAID kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jul 24 16:51:30 HOME-unRAID kernel: __netif_receive_skb_one_core+0x77/0x9c Jul 24 16:51:30 HOME-unRAID kernel: process_backlog+0x8c/0x116 Jul 24 16:51:30 HOME-unRAID kernel: __napi_poll.constprop.0+0x28/0x124 Jul 24 16:51:30 HOME-unRAID kernel: net_rx_action+0x159/0x24f Jul 24 16:51:30 HOME-unRAID kernel: __do_softirq+0x126/0x288 Jul 24 16:51:30 HOME-unRAID kernel: do_softirq+0x7f/0xab Jul 24 16:51:30 HOME-unRAID kernel: </IRQ> Jul 24 16:51:30 HOME-unRAID kernel: <TASK> Jul 24 16:51:30 HOME-unRAID kernel: __local_bh_enable_ip+0x4c/0x6b Jul 24 16:51:30 HOME-unRAID kernel: netif_rx+0x52/0x5a Jul 24 16:51:30 HOME-unRAID kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 24 16:51:30 HOME-unRAID kernel: ? _raw_spin_unlock+0x14/0x29 Jul 24 16:51:30 HOME-unRAID kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Jul 24 16:51:30 HOME-unRAID kernel: process_one_work+0x1a8/0x295 Jul 24 16:51:30 HOME-unRAID kernel: worker_thread+0x18b/0x244 Jul 24 16:51:30 HOME-unRAID kernel: ? rescuer_thread+0x281/0x281 Jul 24 16:51:30 HOME-unRAID kernel: kthread+0xe4/0xef Jul 24 16:51:30 HOME-unRAID kernel: ? kthread_complete_and_exit+0x1b/0x1b Jul 24 16:51:30 HOME-unRAID kernel: ret_from_fork+0x1f/0x30 Jul 24 16:51:30 HOME-unRAID kernel: </TASK> Jul 24 16:51:30 HOME-unRAID kernel: ---[ end trace 0000000000000000 ]--- My system details are as follows: unRAID version: 6.1.38 Hardware: HPE ProLiant MicroServer Gen10 Plus/ProLiant MicroServer Gen10 Plus BIOS version: U48 (updated on 01/12/2023) The issue seems to be related to nf_conntrack based on the log entry. I am not certain what exactly caused this error or how to go about resolving it. I've attempted some basic troubleshooting steps like rebooting the system and checking for any recent changes to plugins or configurations, but the problem persists. I'm hoping that someone in the community can help shed some light on this matter and guide me towards a solution. If you need any additional information or logs, please let me know, and I'll provide them promptly. Thank you in advance for your time and support. Any assistance will be greatly appreciated! Best regards,
  9. BOGu
    Yes, I'm having this problem too! I am a Chinese user
  10. BOGu
    Mar 29 15:53:02 HOME-unRAID emhttpd: spinning down /dev/sde Mar 29 15:54:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 29 16:54:03 HOME-unRAID emhttpd: spinning down /dev/sde Mar 29 16:55:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 29 17:55:03 HOME-unRAID emhttpd: spinning down /dev/sde Mar 29 17:56:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 29 18:56:03 HOME-unRAID emhttpd: spinning down /dev/sde Mar 29 18:57:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 29 19:57:03 HOME-unRAID emhttpd: spinning down /dev/sde Mar 29 19:58:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 29 20:58:03 HOME-unRAID emhttpd: spinning down /dev/sde Mar 29 20:59:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 29 22:52:03 HOME-unRAID emhttpd: spinning down /dev/sde Mar 29 22:53:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 29 23:53:02 HOME-unRAID emhttpd: spinning down /dev/sde Mar 29 23:54:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 30 00:54:02 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 00:55:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 30 01:55:02 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 01:56:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 30 02:56:03 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 02:57:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 30 04:40:39 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 04:41:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 30 05:41:02 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 05:42:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 30 06:42:02 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 06:43:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 30 07:43:02 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 07:44:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 30 08:44:02 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 09:45:02 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 09:46:08 HOME-unRAID emhttpd: read SMART /dev/sde Mar 30 10:46:03 HOME-unRAID emhttpd: spinning down /dev/sde Mar 30 10:47:08 HOME-unRAID emhttpd: read SMART /dev/sde After updating my unraid system to 6.12.0-rc2, the hard drive cannot sleep. I have set the system to automatically sleep after one hour of no read/write activity. However, upon checking the hard drive logs, I discovered that the system automatically wakes it up after it sleeps. What could be causing this?
×
×
  • Create New...