dglb99
-
Posts
30 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by dglb99
-
-
Updating unraid to 6.12.6 and installing the Realtek NIC Drivers plugin in community applications seems to have resolved these crashes. Server currently has 2 weeks uptime.
-
Updated the bios hoping the issue would be fixed. It still crashes every few days.
SpoilerOct 24 11:18:41 NASDex kernel: ------------[ cut here ]------------ Oct 24 11:18:41 NASDex kernel: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Oct 24 11:18:41 NASDex kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x14e/0x1c0 Oct 24 11:18:41 NASDex kernel: Modules linked in: udp_diag xt_mark wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha nvidia_uvm(PO) xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 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) i915 drm_buddy i2c_algo_bit ttm drm_display_helper intel_gtt agpgart tcp_diag inet_diag nct6683 ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs macvtap macvlan tap bridge stp llc e1000e r8169 realtek intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp nvidia_drm(PO) kvm_intel nvidia_modeset(PO) kvm nvidia(PO) crct10dif_pclmul crc32_pclmul Oct 24 11:18:41 NASDex kernel: crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd drm_kms_helper cryptd rapl mei_hdcp mei_pxp intel_cstate wmi_bmof intel_wmi_thunderbolt mxm_wmi drm nvme i2c_i801 mpt3sas intel_uncore i2c_smbus nvme_core mei_me i2c_core syscopyarea mei ahci sysfillrect sysimgblt input_leds fb_sys_fops raid_class led_class joydev libahci scsi_transport_sas thermal fan tpm_crb video tpm_tis tpm_tis_core tpm wmi backlight intel_pmc_core acpi_tad acpi_pad button unix [last unloaded: e1000e] Oct 24 11:18:41 NASDex kernel: CPU: 1 PID: 0 Comm: swapper/1 Tainted: P O 6.1.49-Unraid #1 Oct 24 11:18:41 NASDex kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C81/MAG B460 TOMAHAWK (MS-7C81), BIOS 1.50 08/28/2023 Oct 24 11:18:41 NASDex kernel: RIP: 0010:dev_watchdog+0x14e/0x1c0 Oct 24 11:18:41 NASDex kernel: Code: ca c4 00 00 75 26 48 89 ef c6 05 72 ca c4 00 01 e8 6a 23 fb ff 44 89 f1 48 89 ee 48 c7 c7 68 dd 16 82 48 89 c2 e8 56 9d 92 ff <0f> 0b 48 89 ef e8 32 fb ff ff 48 8b 83 88 fc ff ff 48 89 ef 44 89 Oct 24 11:18:41 NASDex kernel: RSP: 0018:ffffc900001d8ea8 EFLAGS: 00010282 Oct 24 11:18:41 NASDex kernel: RAX: 0000000000000000 RBX: ffff8881407a4448 RCX: 0000000000000003 Oct 24 11:18:41 NASDex kernel: RDX: 0000000000000104 RSI: 0000000000000003 RDI: 00000000ffffffff Oct 24 11:18:41 NASDex kernel: RBP: ffff8881407a4000 R08: 0000000000000000 R09: ffffffff8294e3f0 Oct 24 11:18:41 NASDex kernel: R10: 0000000000000000 R11: ffff888c7efaca1a R12: 0000000000000000 Oct 24 11:18:41 NASDex kernel: R13: ffff8881407a439c R14: 0000000000000000 R15: 0000000000000001 Oct 24 11:18:41 NASDex kernel: FS: 0000000000000000(0000) GS:ffff888c4e840000(0000) knlGS:0000000000000000 Oct 24 11:18:41 NASDex kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 24 11:18:41 NASDex kernel: CR2: 0000147084a0eeb0 CR3: 000000035c2dc004 CR4: 00000000007726e0 Oct 24 11:18:41 NASDex kernel: PKRU: 55555554 Oct 24 11:18:41 NASDex kernel: Call Trace: Oct 24 11:18:41 NASDex kernel: <IRQ> Oct 24 11:18:41 NASDex kernel: ? __warn+0xab/0x122 Oct 24 11:18:41 NASDex kernel: ? report_bug+0x109/0x17e Oct 24 11:18:41 NASDex kernel: ? dev_watchdog+0x14e/0x1c0 Oct 24 11:18:41 NASDex kernel: ? handle_bug+0x41/0x6f Oct 24 11:18:41 NASDex kernel: ? exc_invalid_op+0x13/0x60 Oct 24 11:18:41 NASDex kernel: ? asm_exc_invalid_op+0x16/0x20 Oct 24 11:18:41 NASDex kernel: ? dev_watchdog+0x14e/0x1c0 Oct 24 11:18:41 NASDex kernel: ? dev_watchdog+0x14e/0x1c0 Oct 24 11:18:41 NASDex kernel: ? psched_ppscfg_precompute+0x57/0x57 Oct 24 11:18:41 NASDex kernel: ? psched_ppscfg_precompute+0x57/0x57 Oct 24 11:18:41 NASDex kernel: call_timer_fn+0x6c/0x10d Oct 24 11:18:41 NASDex kernel: __run_timers+0x144/0x184 Oct 24 11:18:41 NASDex kernel: run_timer_softirq+0x2b/0x43 Oct 24 11:18:41 NASDex kernel: __do_softirq+0x126/0x288 Oct 24 11:18:41 NASDex kernel: __irq_exit_rcu+0x5e/0xb8 Oct 24 11:18:41 NASDex kernel: sysvec_apic_timer_interrupt+0x85/0xa6 Oct 24 11:18:41 NASDex kernel: </IRQ> Oct 24 11:18:41 NASDex kernel: <TASK> Oct 24 11:18:41 NASDex kernel: asm_sysvec_apic_timer_interrupt+0x16/0x20 Oct 24 11:18:41 NASDex kernel: RIP: 0010:cpuidle_enter_state+0x11d/0x202 Oct 24 11:18:41 NASDex kernel: Code: 20 22 a0 ff 45 84 ff 74 1b 9c 58 0f 1f 40 00 0f ba e0 09 73 08 0f 0b fa 0f 1f 44 00 00 31 ff e8 4c e3 a4 ff fb 0f 1f 44 00 00 <45> 85 e4 0f 88 ba 00 00 00 48 8b 04 24 49 63 cc 48 6b d1 68 49 29 Oct 24 11:18:41 NASDex kernel: RSP: 0018:ffffc9000010be98 EFLAGS: 00000246 Oct 24 11:18:41 NASDex kernel: RAX: ffff888c4e840000 RBX: ffff888c4e876460 RCX: 0000000000000000 Oct 24 11:18:41 NASDex kernel: RDX: 00008846fd8e8a41 RSI: ffffffff820ed4af RDI: ffffffff820ed9b8 Oct 24 11:18:41 NASDex kernel: RBP: 0000000000000002 R08: 0000000000000002 R09: 0000000000000002 Oct 24 11:18:41 NASDex kernel: R10: 0000000000000020 R11: 0000000000000053 R12: 0000000000000002 Oct 24 11:18:41 NASDex kernel: R13: ffffffff823205c0 R14: 00008846fd8e8a41 R15: 0000000000000000 Oct 24 11:18:41 NASDex kernel: ? cpuidle_enter_state+0xf7/0x202 Oct 24 11:18:41 NASDex kernel: cpuidle_enter+0x2a/0x38 Oct 24 11:18:41 NASDex kernel: do_idle+0x18d/0x1fb Oct 24 11:18:41 NASDex kernel: cpu_startup_entry+0x1d/0x1f Oct 24 11:18:41 NASDex kernel: start_secondary+0x101/0x101 Oct 24 11:18:41 NASDex kernel: secondary_startup_64_no_verify+0xce/0xdb Oct 24 11:18:41 NASDex kernel: </TASK> Oct 24 11:18:41 NASDex kernel: ---[ end trace 0000000000000000 ]---
-
What's the reasoning behind the sleep 10s?
-
Server crashed in about 6 days with flow control and offloading disabled. I'm looking into getting a new motherboard since I am already out of PCIE slots.
-
Very well then. I have disabled flow control and offloading. Will see how it goes.
-
-
Found my diagnostics on my laptop from before the unraid OS update. This is 6.11.5.
-
Hi all,
My unraid server has been crashing and the frequency has continued to increase and at this point I am not sure what to do. From the persistent syslog, once this error starts it loops forever until I hard reboot the server.
Sep 18 20:35:38 NASDex kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: Sep 18 20:35:38 NASDex kernel: TDH <0> Sep 18 20:35:38 NASDex kernel: TDT <7> Sep 18 20:35:38 NASDex kernel: next_to_use <7> Sep 18 20:35:38 NASDex kernel: next_to_clean <0> Sep 18 20:35:38 NASDex kernel: buffer_info[next_to_clean]: Sep 18 20:35:38 NASDex kernel: time_stamp <124b24440> Sep 18 20:35:38 NASDex kernel: next_to_watch <0> Sep 18 20:35:38 NASDex kernel: jiffies <124b26b80> Sep 18 20:35:38 NASDex kernel: next_to_watch.status <0> Sep 18 20:35:38 NASDex kernel: MAC Status <40080083> Sep 18 20:35:38 NASDex kernel: PHY Status <796d> Sep 18 20:35:38 NASDex kernel: PHY 1000BASE-T Status <3800> Sep 18 20:35:38 NASDex kernel: PHY Extended Status <3000> Sep 18 20:35:38 NASDex kernel: PCI Status <10> Sep 18 20:35:38 NASDex kernel: e1000e 0000:00:1f.6 eth0: Reset adapter unexpectedly Sep 18 20:35:38 NASDex kernel: br0: port 1(eth0) entered disabled state Sep 18 20:35:41 NASDex kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Sep 18 20:35:41 NASDex kernel: br0: port 1(eth0) entered blocking state Sep 18 20:35:41 NASDex kernel: br0: port 1(eth0) entered forwarding state Sep 18 20:35:44 NASDex kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: Sep 18 20:35:44 NASDex kernel: TDH <0> Sep 18 20:35:44 NASDex kernel: TDT <7> Sep 18 20:35:44 NASDex kernel: next_to_use <7> Sep 18 20:35:44 NASDex kernel: next_to_clean <0> Sep 18 20:35:44 NASDex kernel: buffer_info[next_to_clean]: Sep 18 20:35:44 NASDex kernel: time_stamp <124b27c40> Sep 18 20:35:44 NASDex kernel: next_to_watch <0> Sep 18 20:35:44 NASDex kernel: jiffies <124b28301> Sep 18 20:35:44 NASDex kernel: next_to_watch.status <0> Sep 18 20:35:44 NASDex kernel: MAC Status <40080083> Sep 18 20:35:44 NASDex kernel: PHY Status <796d> Sep 18 20:35:44 NASDex kernel: PHY 1000BASE-T Status <3800> Sep 18 20:35:44 NASDex kernel: PHY Extended Status <3000> Sep 18 20:35:44 NASDex kernel: PCI Status <10> Sep 18 20:35:46 NASDex kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: Sep 18 20:35:46 NASDex kernel: TDH <0> Sep 18 20:35:46 NASDex kernel: TDT <7> Sep 18 20:35:46 NASDex kernel: next_to_use <7> Sep 18 20:35:46 NASDex kernel: next_to_clean <0> Sep 18 20:35:46 NASDex kernel: buffer_info[next_to_clean]: Sep 18 20:35:46 NASDex kernel: time_stamp <124b27c40> Sep 18 20:35:46 NASDex kernel: next_to_watch <0> Sep 18 20:35:46 NASDex kernel: jiffies <124b28ac0> Sep 18 20:35:46 NASDex kernel: next_to_watch.status <0> Sep 18 20:35:46 NASDex kernel: MAC Status <40080083> Sep 18 20:35:46 NASDex kernel: PHY Status <796d> Sep 18 20:35:46 NASDex kernel: PHY 1000BASE-T Status <3800> Sep 18 20:35:46 NASDex kernel: PHY Extended Status <3000> Sep 18 20:35:46 NASDex kernel: PCI Status <10> Sep 18 20:35:48 NASDex kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: Sep 18 20:35:48 NASDex kernel: TDH <0> Sep 18 20:35:48 NASDex kernel: TDT <7> Sep 18 20:35:48 NASDex kernel: next_to_use <7> Sep 18 20:35:48 NASDex kernel: next_to_clean <0> Sep 18 20:35:48 NASDex kernel: buffer_info[next_to_clean]: Sep 18 20:35:48 NASDex kernel: time_stamp <124b27c40> Sep 18 20:35:48 NASDex kernel: next_to_watch <0> Sep 18 20:35:48 NASDex kernel: jiffies <124b292c0> Sep 18 20:35:48 NASDex kernel: next_to_watch.status <0> Sep 18 20:35:48 NASDex kernel: MAC Status <40080083> Sep 18 20:35:48 NASDex kernel: PHY Status <796d> Sep 18 20:35:48 NASDex kernel: PHY 1000BASE-T Status <3800> Sep 18 20:35:48 NASDex kernel: PHY Extended Status <3000> Sep 18 20:35:48 NASDex kernel: PCI Status <10> Sep 18 20:35:50 NASDex kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: Sep 18 20:35:50 NASDex kernel: TDH <0> Sep 18 20:35:50 NASDex kernel: TDT <7> Sep 18 20:35:50 NASDex kernel: next_to_use <7> Sep 18 20:35:50 NASDex kernel: next_to_clean <0> Sep 18 20:35:50 NASDex kernel: buffer_info[next_to_clean]: Sep 18 20:35:50 NASDex kernel: time_stamp <124b27c40> Sep 18 20:35:50 NASDex kernel: next_to_watch <0> Sep 18 20:35:50 NASDex kernel: jiffies <124b29a80> Sep 18 20:35:50 NASDex kernel: next_to_watch.status <0> Sep 18 20:35:50 NASDex kernel: MAC Status <40080083> Sep 18 20:35:50 NASDex kernel: PHY Status <796d> Sep 18 20:35:50 NASDex kernel: PHY 1000BASE-T Status <3800> Sep 18 20:35:50 NASDex kernel: PHY Extended Status <3000> Sep 18 20:35:50 NASDex kernel: PCI Status <10> Sep 18 20:35:52 NASDex kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: Sep 18 20:35:52 NASDex kernel: TDH <0> Sep 18 20:35:52 NASDex kernel: TDT <7> Sep 18 20:35:52 NASDex kernel: next_to_use <7> Sep 18 20:35:52 NASDex kernel: next_to_clean <0> Sep 18 20:35:52 NASDex kernel: buffer_info[next_to_clean]: Sep 18 20:35:52 NASDex kernel: time_stamp <124b27c40> Sep 18 20:35:52 NASDex kernel: next_to_watch <0> Sep 18 20:35:52 NASDex kernel: jiffies <124b2a240> Sep 18 20:35:52 NASDex kernel: next_to_watch.status <0> Sep 18 20:35:52 NASDex kernel: MAC Status <40080083> Sep 18 20:35:52 NASDex kernel: PHY Status <796d> Sep 18 20:35:52 NASDex kernel: PHY 1000BASE-T Status <3800> Sep 18 20:35:52 NASDex kernel: PHY Extended Status <3000> Sep 18 20:35:52 NASDex kernel: PCI Status <10> Sep 18 20:35:53 NASDex kernel: e1000e 0000:00:1f.6 eth0: Reset adapter unexpectedly Sep 18 20:35:53 NASDex kernel: br0: port 1(eth0) entered disabled state Sep 18 20:35:57 NASDex kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Sep 18 20:35:57 NASDex kernel: br0: port 1(eth0) entered blocking state Sep 18 20:35:57 NASDex kernel: br0: port 1(eth0) entered forwarding state Sep 18 20:35:59 NASDex kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:I will be posting the diagnostics soon but it will have to wait until I get home (the server is crashed at the moment). I was on 6.11.5 for a while and this was happening. I recently updated to 6.12.4 and it has not gotten any better. Motherboard is a MSI MAG B460 TOMAHAWK LGA 1200 which has two ethernet ports, 1gb NIC and 12.5gb NIC. Currently I am tied into just the 1gb NIC.
Other people's solutions seem to disable NIC flow control and NIC offloading, but it feels like a band-aid fix to me and I want to address the root problem.
-
The drive is in a Rosewill hotswappable cage and none of the other drives are having issues. Is it possible the hotswap cage is at fault you think?
-
-
I have been having this issue where my Disk 3 will error out and gets disabled. SMART data all looks good. I usually just restart the server, wipe the disk, and rebuild the array and it is fine, but it is starting to happen with greater frequency. Last time I pulled the disk and re-seated it in case there is a connection issue. Here is a copy of the unraid logs when the disk gets disabled.
May 17 17:46:58 NASDex kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221103000000), phy(3) May 17 17:46:58 NASDex kernel: scsi target1:0:3: enclosure logical id(0x500605b006287f10), slot(4) May 17 17:46:58 NASDex kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x00000000e7172b62) May 17 17:46:59 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:46:59 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:47:06 NASDex kernel: sd 1:0:3:0: attempting task abort!scmd(0x000000008f76039a), outstanding for 7395 ms & timeout 7000 ms May 17 17:47:06 NASDex kernel: sd 1:0:3:0: [sde] tag#3095 CDB: opcode=0x12 12 00 00 00 fe 00 May 17 17:47:06 NASDex kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221103000000), phy(3) May 17 17:47:06 NASDex kernel: scsi target1:0:3: enclosure logical id(0x500605b006287f10), slot(4) May 17 17:47:06 NASDex kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x000000008f76039a) May 17 17:47:06 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:47:07 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:47:37 NASDex kernel: sd 1:0:3:0: attempting task abort!scmd(0x000000007841706f), outstanding for 30035 ms & timeout 30000 ms May 17 17:47:37 NASDex kernel: sd 1:0:3:0: [sde] tag#3110 CDB: opcode=0x88 88 00 00 00 00 05 8b 1a d3 40 00 00 00 08 00 00 May 17 17:47:37 NASDex kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221103000000), phy(3) May 17 17:47:37 NASDex kernel: scsi target1:0:3: enclosure logical id(0x500605b006287f10), slot(4) May 17 17:47:37 NASDex kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x000000007841706f) May 17 17:47:37 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:47:38 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:47:44 NASDex kernel: sd 1:0:3:0: attempting task abort!scmd(0x0000000057f00eb9), outstanding for 7522 ms & timeout 7000 ms May 17 17:47:44 NASDex kernel: sd 1:0:3:0: [sde] tag#3073 CDB: opcode=0x12 12 00 00 00 fe 00 May 17 17:47:44 NASDex kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221103000000), phy(3) May 17 17:47:44 NASDex kernel: scsi target1:0:3: enclosure logical id(0x500605b006287f10), slot(4) May 17 17:47:45 NASDex kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x0000000057f00eb9) May 17 17:47:45 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:47:45 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:48:16 NASDex kernel: sd 1:0:3:0: attempting task abort!scmd(0x000000007bcdd088), outstanding for 30438 ms & timeout 30000 ms May 17 17:48:16 NASDex kernel: sd 1:0:3:0: [sde] tag#3090 CDB: opcode=0x12 12 00 00 00 24 00 May 17 17:48:16 NASDex kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221103000000), phy(3) May 17 17:48:16 NASDex kernel: scsi target1:0:3: enclosure logical id(0x500605b006287f10), slot(4) May 17 17:48:16 NASDex kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x000000007bcdd088) May 17 17:48:16 NASDex kernel: sd 1:0:3:0: attempting task abort!scmd(0x00000000f1a23639), outstanding for 30593 ms & timeout 30000 ms May 17 17:48:16 NASDex kernel: sd 1:0:3:0: [sde] tag#3089 CDB: opcode=0x88 88 00 00 00 00 05 57 5b 2f a8 00 00 00 90 00 00 May 17 17:48:16 NASDex kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221103000000), phy(3) May 17 17:48:16 NASDex kernel: scsi target1:0:3: enclosure logical id(0x500605b006287f10), slot(4) May 17 17:48:16 NASDex kernel: sd 1:0:3:0: No reference found at driver, assuming scmd(0x00000000f1a23639) might have completed May 17 17:48:16 NASDex kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x00000000f1a23639) May 17 17:48:16 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:48:17 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:48:23 NASDex kernel: sd 1:0:3:0: attempting task abort!scmd(0x00000000cb2e9456), outstanding for 7333 ms & timeout 7000 ms May 17 17:48:23 NASDex kernel: sd 1:0:3:0: [sde] tag#3082 CDB: opcode=0x12 12 00 00 00 fe 00 May 17 17:48:23 NASDex kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221103000000), phy(3) May 17 17:48:23 NASDex kernel: scsi target1:0:3: enclosure logical id(0x500605b006287f10), slot(4) May 17 17:48:23 NASDex kernel: sd 1:0:3:0: [sde] tag#3093 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=115s May 17 17:48:23 NASDex kernel: sd 1:0:3:0: [sde] tag#3093 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 May 17 17:48:23 NASDex kernel: I/O error, dev sde, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 May 17 17:48:23 NASDex kernel: I/O error, dev sde, sector 2932785624 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 17:48:23 NASDex kernel: md: disk3 write error, sector=2932785560 May 17 17:48:23 NASDex kernel: I/O error, dev sde, sector 2932785632 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 17:48:23 NASDex kernel: md: disk3 write error, sector=2932785568 May 17 17:48:23 NASDex kernel: I/O error, dev sde, sector 2932785640 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 17:48:23 NASDex kernel: md: disk3 write error, sector=2932785576 May 17 17:48:23 NASDex kernel: I/O error, dev sde, sector 2932785648 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 17:48:23 NASDex kernel: md: disk3 write error, sector=2932785584 May 17 17:48:23 NASDex kernel: I/O error, dev sde, sector 2932785656 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 17:48:23 NASDex kernel: md: disk3 write error, sector=2932785592 May 17 17:48:23 NASDex kernel: I/O error, dev sde, sector 2932785664 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 17:48:23 NASDex kernel: md: disk3 write error, sector=2932785600 May 17 17:48:23 NASDex kernel: I/O error, dev sde, sector 2932785672 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 17:48:23 NASDex kernel: md: disk3 write error, sector=2932785608 May 17 17:48:23 NASDex kernel: I/O error, dev sde, sector 2932785688 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 17:48:23 NASDex kernel: md: disk3 write error, sector=2932785624 May 17 17:48:23 NASDex kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x00000000cb2e9456) May 17 17:48:24 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:48:24 NASDex kernel: sd 1:0:3:0: Power-on or device reset occurred May 17 17:48:26 NASDex kernel: br-9ca54f048d75: port 8(veth0bbba04) entered disabled state May 17 17:48:26 NASDex kernel: vethb049206: renamed from eth0 May 17 17:48:26 NASDex avahi-daemon[13085]: Interface veth0bbba04.IPv6 no longer relevant for mDNS. May 17 17:48:26 NASDex avahi-daemon[13085]: Leaving mDNS multicast group on interface veth0bbba04.IPv6 with address fe80::c441:89ff:fe63:c4c9. May 17 17:48:26 NASDex kernel: br-9ca54f048d75: port 8(veth0bbba04) entered disabled state May 17 17:48:26 NASDex kernel: device veth0bbba04 left promiscuous mode May 17 17:48:26 NASDex kernel: br-9ca54f048d75: port 8(veth0bbba04) entered disabled state May 17 17:48:26 NASDex avahi-daemon[13085]: Withdrawing address record for fe80::c441:89ff:fe63:c4c9 on veth0bbba04. May 17 17:48:26 NASDex kernel: br-9ca54f048d75: port 8(veth5568b3c) entered blocking state May 17 17:48:26 NASDex kernel: br-9ca54f048d75: port 8(veth5568b3c) entered disabled state May 17 17:48:26 NASDex kernel: device veth5568b3c entered promiscuous mode May 17 17:48:26 NASDex kernel: br-9ca54f048d75: port 8(veth5568b3c) entered blocking state May 17 17:48:26 NASDex kernel: br-9ca54f048d75: port 8(veth5568b3c) entered forwarding state May 17 17:48:26 NASDex kernel: eth0: renamed from veth0e987c1 May 17 17:48:26 NASDex kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5568b3c: link becomes ready May 17 17:48:28 NASDex avahi-daemon[13085]: Joining mDNS multicast group on interface veth5568b3c.IPv6 with address fe80::40e6:aeff:fe78:8bac. May 17 17:48:28 NASDex avahi-daemon[13085]: New relevant interface veth5568b3c.IPv6 for mDNS. May 17 17:48:28 NASDex avahi-daemon[13085]: Registering new address record for fe80::40e6:aeff:fe78:8bac on veth5568b3c.*. May 17 17:49:01 NASDex sSMTP[17889]: Creating SSL connection to host May 17 17:49:01 NASDex sSMTP[17889]: SSL connection using TLS_AES_128_GCM_SHA256 May 17 17:49:02 NASDex sSMTP[17889]: Authorization failed (535 Authentication failed) May 17 17:49:02 NASDex sSMTP[17934]: Creating SSL connection to host May 17 17:49:02 NASDex sSMTP[17934]: SSL connection using TLS_AES_128_GCM_SHA256 May 17 17:49:03 NASDex sSMTP[17934]: Authorization failed (535 Authentication failed)It looks like the disk simply just stops responding for some reason, I am unsure what to make of this.
SMART data
-
Never mind I figured it out. Here is how I did it. I opened an unraid terminal from the top right in the webui. Then I ran
docker exec -it agendav /bin/bash cd .. php agendavcli migrations:migrateHope this helps anyone else that gets stuck on this.
-
How did you run "php agendavcli migrations:migrate"? I am using the 'console' option when clicking on a container and then doing this.
cd /var/www/agendav php agendavcli migrations:migrate
but am greeted with this error.
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /var/www/agendav/web/vendor/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php on line 2636 Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /var/www/agendav/web/vendor/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php on line 2665 Loading configuration from file: migrations.yml [Doctrine\DBAL\Exception\ConnectionException] An exception occured in driver: SQLSTATE[HY000] [1045] Access denied for user 'root'@'172.17.0.1' (using password: Y ES) [Doctrine\DBAL\Driver\PDOException] SQLSTATE[HY000] [1045] Access denied for user 'root'@'172.17.0.1' (using password: YES) [PDOException] SQLSTATE[HY000] [1045] Access denied for user 'root'@'172.17.0.1' (using password: YES) migrations:migrate [--write-sql] [--dry-run] [--query-time] [--allow-no-migration] [--configuration [CONFIGURATION]] [--db-configuration [DB-CONFIGURATION]] [--] [<version>]
-
It says that the command succeeds. And I don't know what changed but I logged into my unraid server today to mess with it more and the docker container was started, so I guess it's working now. Thank you for trying to help, sorry it was a waste of time though.
-
1
-
-
On 3/24/2022 at 10:15 PM, ich777 said:
Please post the Docker run command.
Change something in the container template and change it back to default after that click Apply and then take a screenshot from the output and post it here.
Sure, here you go.
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='uNmINeD-GUI' --net='bridge' --cpuset-cpus='9,19' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'DATA_PERM'='770' -e 'UMASK'='0000' -e 'UID'='99' -e 'GID'='100' -e 'CUSTOM_RES_W'='1280' -e 'CUSTOM_RES_H'='850' -p '8181:8080/tcp' -v '/mnt/user/appdata/unmined/data/':'/unmined/':'rw' -v '/mnt/user/appdata/unmined/worlds':'/unmined/worlds/':'ro' --restart=unless-stopped 'ich777/unmined' 5abe41fd4143814076dc375064a7f5c42da04ebef2f470e98d9af58628029e0f -
I'm getting execution error, server error with your uNmINeD-GUI docker container. Here are my docker mappings, any ideas?
-
On 12/1/2021 at 5:30 PM, coppit said:
Precisely. The version of Java inside the current container is 16. We need an updated container.
Here is he solution I found.
https://github.com/hexparrot/mineos-node/issues/450#issuecomment-989127314
In the docker console run
apt-get update && apt-get install -y openjdk-17-jre-headless
and then restart the docker container.
-
On 2/6/2021 at 10:04 AM, LushFire said:
What is the max temp you see on your chip, passing all 6c/12t to a windows vm running cinebench I see low 50's . I am not sure if my sensor readings are wrong or if something else is going on.
I get to the low 60 degrees C under load. Low 50's is fine I wouldn't worry about it.
-
On 11/20/2020 at 8:11 AM, konaboy said:
Shows same vainfo output you are getting:
https://discordapp.com/channels/623392507828371476/623799920574595092/748901930444783706
And what the fix [probably] is - both my update, and a followon from user ProZach in Discord:
https://discordapp.com/channels/623392507828371476/623799920574595092/748901930444783706
Would you mind posting what the suggested fix was? I don't believe we have access to that channel.
-
5 hours ago, Energen said:
You may want to read through this topic, seems that people have it working on the latest beta Unraid.
https://forums.unraid.net/topic/92910-is-intel-gen10-supported/
It looks like only one person got it working, everyone else is having issues, including the same as mine where /dev/dri shows up but the docker container cannot access VAAPI.
-
Just wanted to add another report of /dev/dri showing up but VAAPI not being accessed inside the docker containers with my i5 10400. I plan on trying to get the new intel media-driver working once I get a chance.
-
3 hours ago, dglb99 said:
Has anyone gotten Intel quicksync transcoding to work with 10th gen Intel? I have to use the 6.9 rc2 due to 2.5g lan drivers but I've really been struggling getting this to work.
I'm starting to think that I am not the only one with quicksync issues on 10th gen intel (comet lake) cpus. I've found a few other posts of people having issues as well, and then I cam across this.
From my limited knowledge of computing it looks like people had issues with the vaapi driver and comet lake processors, and they basically are saying comet lake isn't support and to use intel media-driver.
Is it possible to see what intel driver unmanic is using? Or is that packaged into the unRAID kernel?
-
Has anyone gotten Intel quicksync transcoding to work with 10th gen Intel? I have to use the 6.9 rc2 due to 2.5g lan drivers but I've really been struggling getting this to work.
-
21 hours ago, ich777 said:
Have you passed through the device '/dev/dri' in the template?
Have you the device /dev/dri on the host?
Open up a Unraid terminal and type in 'ls /dev/dri' if it says no auch file or directory your iGPU isn't working.
Yes, I have passed through the iGPU in the docker template per the docker template instructions using the extra parameters section. The card shows up under /dev/dri.
unRAID crashing with increasing frequency over the last few weeks - "e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:"
in General Support
Posted
Don't know what to you. The board has a Realtek RTL8125 2.5gb port, and seeing the note about 2.5gb ports causing issues in the changelog for the latest unRAID update I installed the recommended drivers and haven't had issues yet. Currently at just under 17 days of uptime.