-
unable to shutdown array .. root: umount: /mnt/disk4: not mounted.
cheers mate that did the trick. i will have a look to find a better way to shrink the array.
-
unable to shutdown array .. root: umount: /mnt/disk4: not mounted.
i did try to remount it but i dont seem to be clever enough.
-
unable to shutdown array .. root: umount: /mnt/disk4: not mounted.
maybe , i had unbalanced the drive to move all the data off and run the clear drive script.
-
unable to shutdown array .. root: umount: /mnt/disk4: not mounted.
hi i seem to be in a bit of a loop here .trying to shutdown array and getting this message in logs. Dec 21 17:52:47 unraid emhttpd: Unmounting disks... Dec 21 17:52:47 unraid emhttpd: shcmd (117243): umount /mnt/disk4 Dec 21 17:52:47 unraid root: umount: /mnt/disk4: not mounted. Dec 21 17:52:47 unraid emhttpd: shcmd (117243): exit status: 32 Dec 21 17:52:47 unraid emhttpd: Retry unmounting disk share(s)... Dec 21 17:52:52 unraid emhttpd: Unmounting disks... Dec 21 17:52:52 unraid emhttpd: shcmd (117244): umount /mnt/disk4 Dec 21 17:52:52 unraid root: umount: /mnt/disk4: not mounted. Dec 21 17:52:52 unraid emhttpd: shcmd (117244): exit status: 32 Dec 21 17:52:52 unraid emhttpd: Retry unmounting disk share(s)... Dec 21 17:52:57 unraid emhttpd: Unmounting disks... is there any way to give it a kick (nicely of course)? cheers in advance..
-
system errors
hi i have just changed it.strangely i read about this and changed it previously i have no idea how it got changed back. lets see what happens. cheers.....
-
hilljiffy started following system errors
-
system errors
hi all,i have been having lots of problems with my server for a little while.i am running 3 dockers plex,sonarr and pihole.The problems seemed to start after i added more arr dockers but as i had to rebuild the cache after a crash (i converted to zfs to see if that made a difference) i didnt put them back in.the next thing that happened was that i couldnt shut down the array or the server.I added Dynamix Stop Shell to see if that would sort the problem.so i was doing a Parity-Check and noticed this morning it had paused and the logs showed an error so i thought i would ask for help. Dec 18 15:57:59 unraid kernel: WARNING: CPU: 9 PID: 22366 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Dec 18 15:57:59 unraid kernel: Modules linked in: ccp vhost_net tun vhost kvm_intel kvm md_mod xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_iotlb udp_diag 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 nvidia_uvm(PO) xfs tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs 8021q garp mrp macvtap macvlan tap bridge stp llc mlx4_en mlx4_core tg3 nvidia_drm(PO) nvidia_modeset(PO) zfs(PO) zunicode(PO) zzstd(O) intel_rapl_msr zlua(O) intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) nvidia(PO) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel mgag200 sha512_ssse3 sha256_ssse3 drm_shmem_helper sha1_ssse3 i2c_algo_bit video drm_kms_helper aesni_intel crypto_simd drm cryptd ipmi_ssif mxm_wmi rapl backlight i2c_core Dec 18 15:57:59 unraid kernel: mei_me intel_cstate ahci syscopyarea sysfillrect input_leds intel_uncore sysimgblt megaraid_sas joydev led_class mei ipmi_si fb_sys_fops libahci wmi acpi_power_meter button unix [last unloaded: md_mod] Dec 18 15:57:59 unraid kernel: CPU: 9 PID: 22366 Comm: kworker/u24:4 Tainted: P O 6.1.64-Unraid #1 Dec 18 15:57:59 unraid kernel: Hardware name: Dell Inc. PowerEdge T430/0XNNCJ, BIOS 2.10.5 08/08/2019 Dec 18 15:57:59 unraid kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Dec 18 15:57:59 unraid kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Dec 18 15:57:59 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 Dec 18 15:57:59 unraid kernel: RSP: 0018:ffffc90000444d98 EFLAGS: 00010202 Dec 18 15:57:59 unraid kernel: RAX: 0000000000000001 RBX: ffff88826c4eb000 RCX: 15131dc954c0f732 Dec 18 15:57:59 unraid kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88826c4eb000 Dec 18 15:57:59 unraid kernel: RBP: 0000000000000001 R08: 75f756366e5f869a R09: 51359781d1fe98c1 Dec 18 15:57:59 unraid kernel: R10: dedb96c57abed8a3 R11: ffffc90000444d60 R12: ffffffff82a14d00 Dec 18 15:57:59 unraid kernel: R13: 000000000003b877 R14: ffff888271e09d00 R15: 0000000000000000 Dec 18 15:57:59 unraid kernel: FS: 0000000000000000(0000) GS:ffff888c4fc40000(0000) knlGS:0000000000000000 Dec 18 15:57:59 unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 18 15:57:59 unraid kernel: CR2: 000014f584cc6ca0 CR3: 000000000420a005 CR4: 00000000001706e0 Dec 18 15:57:59 unraid kernel: Call Trace: Dec 18 15:57:59 unraid kernel: <IRQ> Dec 18 15:57:59 unraid kernel: ? __warn+0xab/0x122 Dec 18 15:57:59 unraid kernel: ? report_bug+0x109/0x17e Dec 18 15:57:59 unraid kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Dec 18 15:57:59 unraid kernel: ? handle_bug+0x41/0x6f Dec 18 15:57:59 unraid kernel: ? exc_invalid_op+0x13/0x60 Dec 18 15:57:59 unraid kernel: ? asm_exc_invalid_op+0x16/0x20 Dec 18 15:57:59 unraid kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Dec 18 15:57:59 unraid kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Dec 18 15:57:59 unraid kernel: ? nf_nat_inet_fn+0x60/0x1a8 [nf_nat] Dec 18 15:57:59 unraid kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Dec 18 15:57:59 unraid kernel: nf_hook_slow+0x3d/0x96 Dec 18 15:57:59 unraid kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Dec 18 15:57:59 unraid kernel: NF_HOOK.constprop.0+0x79/0xd9 Dec 18 15:57:59 unraid kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Dec 18 15:57:59 unraid kernel: __netif_receive_skb_one_core+0x77/0x9c Dec 18 15:57:59 unraid kernel: process_backlog+0x8c/0x116 Dec 18 15:57:59 unraid kernel: __napi_poll.constprop.0+0x2b/0x124 Dec 18 15:57:59 unraid kernel: net_rx_action+0x159/0x24f Dec 18 15:57:59 unraid kernel: __do_softirq+0x129/0x288 Dec 18 15:57:59 unraid kernel: do_softirq+0x7f/0xab Dec 18 15:57:59 unraid kernel: </IRQ> Dec 18 15:57:59 unraid kernel: <TASK> Dec 18 15:57:59 unraid kernel: __local_bh_enable_ip+0x4c/0x6b Dec 18 15:57:59 unraid kernel: netif_rx+0x52/0x5a Dec 18 15:57:59 unraid kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Dec 18 15:57:59 unraid kernel: ? _raw_spin_unlock+0x14/0x29 Dec 18 15:57:59 unraid kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Dec 18 15:57:59 unraid kernel: process_one_work+0x1ab/0x295 Dec 18 15:57:59 unraid kernel: worker_thread+0x18b/0x244 Dec 18 15:57:59 unraid kernel: ? rescuer_thread+0x281/0x281 Dec 18 15:57:59 unraid kernel: kthread+0xe7/0xef Dec 18 15:57:59 unraid kernel: ? kthread_complete_and_exit+0x1b/0x1b Dec 18 15:57:59 unraid kernel: ret_from_fork+0x22/0x30 Dec 18 15:57:59 unraid kernel: </TASK> Dec 18 15:57:59 unraid kernel: ---[ end trace 0000000000000000 ]--- Dec 18 17:49:44 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:44 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:44 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:44 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:44 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:44 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:45 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:45 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:46 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:46 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 17:49:50 unraid kernel: net_ratelimit: 2 callbacks suppressed Dec 18 17:49:50 unraid kernel: br0: received packet on eth0 with own address as source address (addr:f4:52:14:43:51:c0, vlan:0) Dec 18 23:54:39 unraid monitor: Stop running nchan processes Dec 19 02:00:01 unraid root: /etc/libvirt: 1022.1 MiB (1071779840 bytes) trimmed on /dev/loop3 Dec 19 02:00:01 unraid root: /var/lib/docker: 27.6 GiB (29675724800 bytes) trimmed on /dev/loop2 Dec 19 06:00:02 unraid Plugin Auto Update: Checking for available plugin updates Dec 19 06:01:57 unraid Plugin Auto Update: Community Applications Plugin Auto Update finished Dec 19 06:08:57 unraid emhttpd: spinning down /dev/sdg Dec 19 06:08:57 unraid emhttpd: spinning down /dev/sdd Dec 19 08:30:01 unraid kernel: mdcmd (37): nocheck pause Dec 19 08:30:01 unraid kernel: Dec 19 08:30:01 unraid kernel: md: recovery thread: exit status: -4 Dec 19 08:30:07 unraid emhttpd: read SMART /dev/sdg Dec 19 08:30:07 unraid emhttpd: read SMART /dev/sdd Dec 19 08:57:01 unraid webGUI: Successful login user root from 10.1.1.5 i will enclose the diags as well. thank you if you can help.... unraid-diagnostics-20231219-0913.zip
hilljiffy
Members
-
Joined
-
Last visited