-
7.2.3: Docker service can't start even after recreating the image
I removed the new RAM sticks, and everything seems OK now. The logs might still be useful, so I won’t delete this topic.
-
7.2.3: Docker service can't start even after recreating the image
Hello. Yesterday I upgraded from 6.12.13 to 7.2.3. Everything was fine until today. I added 16 GB of RAM to my server (48 GB total), and after rebooting I noticed that the Docker service won’t start. I checked the documentation and tried deleting and recreating the Docker image. As far as I can tell, the image file is being created, but the service still won’t start. Part of log: goroutine 17 gp=0xc000102380 m=nil [finalizer wait]: runtime.gopark(0xc000084660?, 0x4276bc?, 0xc0?, 0x36?, 0x550011?) /usr/local/go/src/runtime/proc.go:402 +0xce fp=0xc000084620 sp=0xc000084600 pc=0x440f6e runtime.runfinq() /usr/local/go/src/runtime/mfinal.go:194 +0x107 fp=0xc0000847e0 sp=0xc000084620 pc=0x41e107 runtime.goexit({}) /usr/local/go/src/runtime/asm_amd64.s:1695 +0x1 fp=0xc0000847e8 sp=0xc0000847e0 pc=0x478f01 created by runtime.createfing in goroutine 1 /usr/local/go/src/runtime/mfinal.go:164 +0x3d failed to start containerd: timeout waiting for containerd to start I’m not sure whether I should report this as a bug—maybe it’s a known issue. If you know any steps that could help get my server back up and running, I’d really appreciate it. nas-diagnostics-20260103-1458.zip
-
Upgrade from 6.12.13 to 7.2.3
The upgrade went smoothly. At first glance, everything works as before.
-
Upgrade from 6.12.13 to 7.2.3
I'm currently on Unraid 6.12.13 and I think it's time to upgrade to the latest version. I have a couple of Ubuntu VMs, XFS, a lot of Docker containers using "Custom: docker-network", and plugins/utilities like NUT, Tmux Manager, rclone, and Unassigned Devices. Do I need to reconfigure anything after the upgrade? I've done a few upgrades in the past, so I know the basic process, but are there any additional steps or things to watch out for now? Thanks!
-
Help choosing a silent UPS for Unraid setup
Hey everyone! I have a PC running Unraid 24/7, but lately, I’ve been dealing with monthly power outages for unknown reason. The computer is located near my bedroom, so I’m looking for a UPS that meets the following criteria: It should communicate with Unraid via USB, so in case of a power outage, it can send a shutdown signal to the system. It should be quiet when switching to battery power - no loud beeping - so it doesn't wake anyone up, just smoothly goes into battery mode and shuts down Unraid if needed. Budget is around 100 Euros, if possible. At the moment, I’m considering the Eaton 5E G2 USB 900VA/480W, but there aren’t many reviews online about this model. Any recommendations? Thanks in advance!
-
(SOLVED) Need Help: Dealing with constant hangs on Unraid 6.11.5
Thanks! I'll switch to lscr.io/linuxserver/qbittorrent:libtorrentv1 and see how it goes...
-
Unraid OS version 6.12.6 available
6.11.5 to 6.12.6. Currently everything seems ok.
-
[Plug-In] Community Applications
Could you please send me this file? I don't plan to switch to version 6.12 at the moment.
-
(SOLVED) Need Help: Dealing with constant hangs on Unraid 6.11.5
Yes, the Syslog is enabled. I'll provide additional logs after the next crash.
-
ND1 started following (SOLVED) Need Help: Dealing with constant hangs on Unraid 6.11.5
-
(SOLVED) Need Help: Dealing with constant hangs on Unraid 6.11.5
There seems to be a constant kernel panic occurring on version 6.11.5. I have been running Unraid without any issues or hardware changes for about a year. The problem began approximately one month ago when the system nearly completely froze, requiring a hard restart to resolve. For instance, I can initiate the "stop array" process from the UI, but some other pages appear blank. The second occurrence of this issue was about 24 hours ago, and the most recent happened only around 8 hours ago. Therefore, the time between these hangs seems to be decreasing. Also, I'm not sure if it's secure to run a parity check if a system hang is possible during the process. Could you please investigate the possible causes of this problem? Dec 2 23:57:43 NAS kernel: BUG: kernel NULL pointer dereference, address: 00000000000000f6 Dec 2 23:57:43 NAS kernel: #PF: supervisor read access in kernel mode Dec 2 23:57:43 NAS kernel: #PF: error_code(0x0000) - not-present page Dec 2 23:57:43 NAS kernel: PGD 0 P4D 0 Dec 2 23:57:43 NAS kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI Dec 2 23:57:43 NAS kernel: CPU: 3 PID: 5482 Comm: deluged Not tainted 5.19.17-Unraid #2 Dec 2 23:57:43 NAS kernel: Hardware name: ASUS System Product Name/PRIME B560M-A, BIOS 1203 10/27/2021 Dec 2 23:57:43 NAS kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21 Dec 2 23:57:43 NAS kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 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 Dec 2 23:57:43 NAS kernel: RSP: 0000:ffffc9000c0ebcc0 EFLAGS: 00010246 Dec 2 23:57:43 NAS kernel: RAX: 00000000000000c2 RBX: 00000000000000c2 RCX: 00000000000000c2 Dec 2 23:57:43 NAS kernel: RDX: 0000000000000001 RSI: ffff888092da1918 RDI: 00000000000000c2 Dec 2 23:57:43 NAS kernel: RBP: 0000000000000000 R08: 0000000000000034 R09: ffffc9000c0ebcd0 Dec 2 23:57:43 NAS kernel: R10: ffffc9000c0ebcd0 R11: ffffc9000c0ebd48 R12: 0000000000000000 Dec 2 23:57:43 NAS kernel: R13: ffff8881987c0638 R14: 00000000001453b5 R15: ffff8881987c0640 Dec 2 23:57:43 NAS kernel: FS: 0000146fae1f3b30(0000) GS:ffff88844c4c0000(0000) knlGS:0000000000000000 Dec 2 23:57:43 NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 2 23:57:43 NAS kernel: CR2: 00000000000000f6 CR3: 0000000185c08002 CR4: 00000000003706e0 Dec 2 23:57:43 NAS kernel: Call Trace: Dec 2 23:57:43 NAS kernel: <TASK> Dec 2 23:57:43 NAS kernel: __filemap_get_folio+0x98/0x1ff Dec 2 23:57:43 NAS kernel: filemap_fault+0x6e/0x524 Dec 2 23:57:43 NAS kernel: __do_fault+0x2d/0x6e Dec 2 23:57:43 NAS kernel: __handle_mm_fault+0x9a5/0xc7d Dec 2 23:57:43 NAS kernel: handle_mm_fault+0x113/0x1d7 Dec 2 23:57:43 NAS kernel: do_user_addr_fault+0x36a/0x514 Dec 2 23:57:43 NAS kernel: exc_page_fault+0xfc/0x11e Dec 2 23:57:43 NAS kernel: asm_exc_page_fault+0x22/0x30 Dec 2 23:57:43 NAS kernel: RIP: 0033:0x146fb284f3a0 Dec 2 23:57:43 NAS kernel: Code: 48 39 ca 75 f0 c3 48 89 f8 48 83 fa 08 72 14 f7 c7 07 00 00 00 74 0c a4 48 ff ca f7 c7 07 00 00 00 75 f4 48 89 d1 48 c1 e9 03 <f3> 48 a5 83 e2 07 74 05 a4 ff ca 75 fb c3 48 89 f8 48 29 f0 48 39 Dec 2 23:57:43 NAS kernel: RSP: 002b:0000146fae1f2998 EFLAGS: 00010206 Dec 2 23:57:43 NAS kernel: RAX: 0000146fae5867e0 RBX: 0000000000000000 RCX: 0000000000000800 Dec 2 23:57:43 NAS kernel: RDX: 0000000000004000 RSI: 0000146be31b5878 RDI: 0000146fae5867e0 Dec 2 23:57:43 NAS kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000146fae73cce0 Dec 2 23:57:43 NAS kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000002 Dec 2 23:57:43 NAS kernel: R13: 0000146fae37b260 R14: 00000001453b5878 R15: 0000000000004000 Dec 2 23:57:43 NAS kernel: </TASK> Dec 2 23:57:43 NAS kernel: Modules linked in: xt_nat xt_tcpudp 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 tcp_diag inet_diag efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls i915 iosf_mbi drm_buddy x86_pkg_temp_thermal intel_powerclamp i2c_algo_bit coretemp ttm crct10dif_pclmul nvme crc32_pclmul i2c_i801 crc32c_intel ghash_clmulni_intel wmi_bmof aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore drm_display_helper e1000e i2c_smbus nvme_core mpt3sas drm_kms_helper raid_class scsi_transport_sas ahci libahci drm intel_gtt agpgart input_leds joydev led_class i2c_core syscopyarea sysfillrect sysimgblt fb_sys_fops fan thermal wmi video backlight tpm_crb tpm_tis tpm_tis_core tpm acpi_pad acpi_tad button unix Dec 2 23:57:43 NAS kernel: CR2: 00000000000000f6 Dec 2 23:57:43 NAS kernel: ---[ end trace 0000000000000000 ]--- Dec 2 23:57:43 NAS kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21 Dec 2 23:57:43 NAS kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 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 Dec 2 23:57:43 NAS kernel: RSP: 0000:ffffc9000c0ebcc0 EFLAGS: 00010246 Dec 2 23:57:43 NAS kernel: RAX: 00000000000000c2 RBX: 00000000000000c2 RCX: 00000000000000c2 Dec 2 23:57:43 NAS kernel: RDX: 0000000000000001 RSI: ffff888092da1918 RDI: 00000000000000c2 Dec 2 23:57:43 NAS kernel: RBP: 0000000000000000 R08: 0000000000000034 R09: ffffc9000c0ebcd0 Dec 2 23:57:43 NAS kernel: R10: ffffc9000c0ebcd0 R11: ffffc9000c0ebd48 R12: 0000000000000000 Dec 2 23:57:43 NAS kernel: R13: ffff8881987c0638 R14: 00000000001453b5 R15: ffff8881987c0640 Dec 2 23:57:43 NAS kernel: FS: 0000146fae1f3b30(0000) GS:ffff88844c4c0000(0000) knlGS:0000000000000000 Dec 2 23:57:43 NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 2 23:57:43 NAS kernel: CR2: 00000000000000f6 CR3: 0000000185c08002 CR4: 00000000003706e0 Dec 2 23:57:43 NAS kernel: ------------[ cut here ]------------ Dec 2 23:57:43 NAS kernel: Voluntary context switch within RCU read-side critical section! Dec 2 23:57:43 NAS kernel: WARNING: CPU: 7 PID: 5482 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x6a/0x3b9 Dec 2 23:57:43 NAS kernel: Modules linked in: xt_nat xt_tcpudp 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 tcp_diag inet_diag efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls i915 iosf_mbi drm_buddy x86_pkg_temp_thermal intel_powerclamp i2c_algo_bit coretemp ttm crct10dif_pclmul nvme crc32_pclmul i2c_i801 crc32c_intel ghash_clmulni_intel wmi_bmof aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore drm_display_helper e1000e i2c_smbus nvme_core mpt3sas drm_kms_helper raid_class scsi_transport_sas ahci libahci drm intel_gtt agpgart input_leds joydev led_class i2c_core syscopyarea sysfillrect sysimgblt fb_sys_fops fan thermal wmi video backlight tpm_crb tpm_tis tpm_tis_core tpm acpi_pad acpi_tad button unix Dec 2 23:57:43 NAS kernel: CPU: 7 PID: 5482 Comm: deluged Tainted: G D 5.19.17-Unraid #2 Dec 2 23:57:43 NAS kernel: Hardware name: ASUS System Product Name/PRIME B560M-A, BIOS 1203 10/27/2021 Dec 2 23:57:43 NAS kernel: RIP: 0010:rcu_note_context_switch+0x6a/0x3b9 Dec 2 23:57:43 NAS kernel: Code: 75 2a 41 8b 84 24 0c 03 00 00 85 c0 7e 1e 80 3d cb c5 2a 01 00 75 15 48 c7 c7 35 97 0c 82 c6 05 bb c5 2a 01 01 e8 0e 7f 74 00 <0f> 0b 65 48 8b 04 25 c0 bb 01 00 8b 80 0c 03 00 00 85 c0 0f 8e bc Dec 2 23:57:43 NAS kernel: RSP: 0018:ffffc9000c0ebda0 EFLAGS: 00010086 Dec 2 23:57:43 NAS kernel: RAX: 0000000000000000 RBX: ffff888106ffa080 RCX: 0000000000000003 Dec 2 23:57:43 NAS kernel: RDX: 0000000000000002 RSI: 0000000000000003 RDI: 00000000ffffffff Dec 2 23:57:43 NAS kernel: RBP: ffff88844c5ece80 R08: 0000000000000000 R09: ffffc9000c0ebd38 Dec 2 23:57:43 NAS kernel: R10: 00007fffffffffff R11: 0000000000000000 R12: ffff888106ffa080 Dec 2 23:57:43 NAS kernel: R13: 0000000000000000 R14: ffff888106ffa080 R15: ffffc9000c0ebe60 Dec 2 23:57:43 NAS kernel: FS: 0000000000000000(0000) GS:ffff88844c5c0000(0000) knlGS:0000000000000000 Dec 2 23:57:43 NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 2 23:57:43 NAS kernel: CR2: 0000149c235b78c8 CR3: 0000000185c08005 CR4: 00000000003706e0 Dec 2 23:57:43 NAS kernel: Call Trace: Dec 2 23:57:43 NAS kernel: <TASK> Dec 2 23:57:43 NAS kernel: __schedule+0xa9/0x5f6 Dec 2 23:57:43 NAS kernel: ? get_futex_key+0x281/0x2ad Dec 2 23:57:43 NAS kernel: schedule+0x8e/0xc3 Dec 2 23:57:43 NAS kernel: __down_read_common+0x241/0x295 Dec 2 23:57:43 NAS kernel: do_exit+0x279/0x8e5 Dec 2 23:57:43 NAS kernel: make_task_dead+0xba/0xba Dec 2 23:57:43 NAS kernel: rewind_stack_and_make_dead+0x17/0x17 Dec 2 23:57:43 NAS kernel: RIP: 0033:0x146fb284f3a0 Dec 2 23:57:43 NAS kernel: Code: 48 39 ca 75 f0 c3 48 89 f8 48 83 fa 08 72 14 f7 c7 07 00 00 00 74 0c a4 48 ff ca f7 c7 07 00 00 00 75 f4 48 89 d1 48 c1 e9 03 <f3> 48 a5 83 e2 07 74 05 a4 ff ca 75 fb c3 48 89 f8 48 29 f0 48 39 Dec 2 23:57:43 NAS kernel: RSP: 002b:0000146fae1f2998 EFLAGS: 00010206 Dec 2 23:57:43 NAS kernel: RAX: 0000146fae5867e0 RBX: 0000000000000000 RCX: 0000000000000800 Dec 2 23:57:43 NAS kernel: RDX: 0000000000004000 RSI: 0000146be31b5878 RDI: 0000146fae5867e0 Dec 2 23:57:43 NAS kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000146fae73cce0 Dec 2 23:57:43 NAS kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000002 Dec 2 23:57:43 NAS kernel: R13: 0000146fae37b260 R14: 00000001453b5878 R15: 0000000000004000 Dec 2 23:57:43 NAS kernel: </TASK> Dec 2 23:57:43 NAS kernel: ---[ end trace 0000000000000000 ]--- nas-diagnostics-20231203-1120.zip syslog-127.0.0.1.log
-
Unraid 6.11.3 and Dell H310 LSI 9211-8i
Thank you!
-
Unraid 6.11.3 and Dell H310 LSI 9211-8i
Hello everyone! Currently my HDD's are connected by SATA cables directly to the motherboard. I want to switch HDD's from SATA connection to SAS with Dell H310 SAS HBA (LSI 9211-8i) card. Do I need to reconfigure something in Unraid before and after LSI card will be connected? Do I need to attach shares, or maybe discover Parity HDD again? Thanks.
-
Unraid OS version 6.11.3 available
Just made an upgrade from 6.10.3 to 6.11.3. No issues, thanks.
ND1
Members
-
Joined
-
Last visited