-
6.9.2 cannot stop array cleanly.
unfortunately, with force power off and the emhttp is unresponsive so i cannot collect diagnostics.. unless there's a cli way. the diagnostics data only contains logs for a fresh reboot. so it doesnt help. that syslog message was the moment i click stop array and still had a terminal open. this section.. it's weird i did not have this issue with 6.9.0 or 6.9.1 that i can remember. this only surface in 6.9.2 Aug 19 11:22:21 Tower emhttpd: Stopping services... Aug 19 11:22:22 Tower unraid.usbip-gui: Info: rc.unraid.usbip-gui Reset Connected Status Aug 19 11:22:22 Tower emhttpd: shcmd (8277271): /etc/rc.d/rc.libvirt stop Aug 19 11:22:22 Tower root: Waiting on VMs to shutdown Aug 19 11:22:22 Tower root: Stopping libvirtd... Aug 19 11:22:22 Tower dnsmasq[14857]: exiting on receipt of SIGTERM Aug 19 11:22:22 Tower kernel: general protection fault, probably for non-canonical address 0x660a30093a736f70: 0000 [#1] SMP NOPTI Aug 19 11:22:22 Tower kernel: CPU: 6 PID: 14747 Comm: rpc-worker Tainted: P U W O 5.10.28-Unraid #1 Aug 19 11:22:22 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B460M Steel Legend, BIOS P1.60 08/31/2020 Aug 19 11:22:22 Tower kernel: RIP: 0010:rb_first+0xb/0x18
-
6.9.2 cannot stop array cleanly.
so i have this problem for sometime now not sure what's causing it. a reboot or an array stop operation causes the unraid server to unresponsive. i would have to force power off and on to get back into server. Today i was doing an simple array stop after manually stopping all dockers and vms. i got this error in syslog before having to force poweroff. can anyone help interpret the kernel error message below? Aug 19 11:07:40 Tower kernel: vethbe17882: renamed from eth0 Aug 19 11:07:40 Tower kernel: docker0: port 2(vethfcffd0e) entered disabled state Aug 19 11:07:40 Tower kernel: docker0: port 2(vethfcffd0e) entered disabled state Aug 19 11:07:40 Tower kernel: device vethfcffd0e left promiscuous mode Aug 19 11:07:40 Tower kernel: docker0: port 2(vethfcffd0e) entered disabled state Aug 19 11:08:00 Tower kernel: veth31d7e47: renamed from eth0 Aug 19 11:08:00 Tower kernel: docker0: port 3(veth521f7ae) entered disabled state Aug 19 11:08:00 Tower kernel: docker0: port 3(veth521f7ae) entered disabled state Aug 19 11:08:00 Tower kernel: device veth521f7ae left promiscuous mode Aug 19 11:08:00 Tower kernel: docker0: port 3(veth521f7ae) entered disabled state Aug 19 11:08:17 Tower kernel: veth80e7a2a: renamed from eth0 Aug 19 11:08:25 Tower kernel: vethf7f095a: renamed from eth0 Aug 19 11:08:42 Tower kernel: vethf27f4f6: renamed from eth0 Aug 19 11:19:38 Tower kernel: vetha3d31df: renamed from eth0 Aug 19 11:19:45 Tower kernel: veth163acd6: renamed from eth0 Aug 19 11:19:45 Tower kernel: docker0: port 1(vethfc38c52) entered disabled state Aug 19 11:19:45 Tower kernel: docker0: port 1(vethfc38c52) entered disabled state Aug 19 11:19:45 Tower kernel: device vethfc38c52 left promiscuous mode Aug 19 11:19:45 Tower kernel: docker0: port 1(vethfc38c52) entered disabled state Aug 19 11:19:54 Tower kernel: veth63f72b2: renamed from eth0 Aug 19 11:20:01 Tower kernel: veth5cf435f: renamed from eth0 Aug 19 11:20:08 Tower kernel: vethd324632: renamed from eth0 Aug 19 11:20:24 Tower kernel: vethec0455d: renamed from eth0 Aug 19 11:21:03 Tower kernel: br0: port 2(vnet0) entered disabled state Aug 19 11:21:03 Tower kernel: device vnet0 left promiscuous mode Aug 19 11:21:03 Tower kernel: br0: port 2(vnet0) entered disabled state Aug 19 11:21:51 Tower kernel: veth9d33b8d: renamed from eth0 Aug 19 11:22:15 Tower kernel: mdcmd (36): nocheck cancel Aug 19 11:22:16 Tower emhttpd: Spinning up all drives... Aug 19 11:22:16 Tower emhttpd: spinning up /dev/sdj Aug 19 11:22:16 Tower emhttpd: spinning up /dev/sdk Aug 19 11:22:16 Tower emhttpd: spinning up /dev/sdh Aug 19 11:22:16 Tower emhttpd: spinning up /dev/sdg Aug 19 11:22:16 Tower emhttpd: spinning up /dev/sdd Aug 19 11:22:16 Tower emhttpd: spinning up /dev/sde Aug 19 11:22:16 Tower emhttpd: spinning up /dev/sdf Aug 19 11:22:16 Tower emhttpd: spinning up /dev/sdl Aug 19 11:22:16 Tower emhttpd: spinning up /dev/sdi Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdj Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdk Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdh Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdg Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdd Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sde Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdb Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdf Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdc Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdl Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sdi Aug 19 11:22:21 Tower emhttpd: read SMART /dev/sda Aug 19 11:22:21 Tower emhttpd: Stopping services... Aug 19 11:22:22 Tower unraid.usbip-gui: Info: rc.unraid.usbip-gui Reset Connected Status Aug 19 11:22:22 Tower emhttpd: shcmd (8277271): /etc/rc.d/rc.libvirt stop Aug 19 11:22:22 Tower root: Waiting on VMs to shutdown Aug 19 11:22:22 Tower root: Stopping libvirtd... Aug 19 11:22:22 Tower dnsmasq[14857]: exiting on receipt of SIGTERM Aug 19 11:22:22 Tower kernel: general protection fault, probably for non-canonical address 0x660a30093a736f70: 0000 [#1] SMP NOPTI Aug 19 11:22:22 Tower kernel: CPU: 6 PID: 14747 Comm: rpc-worker Tainted: P U W O 5.10.28-Unraid #1 Aug 19 11:22:22 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B460M Steel Legend, BIOS P1.60 08/31/2020 Aug 19 11:22:22 Tower kernel: RIP: 0010:rb_first+0xb/0x18 Aug 19 11:22:22 Tower kernel: Code: 45 0c eb 06 ff 45 10 45 31 e4 4c 89 ee 48 89 ef e8 c1 48 37 00 5a 44 89 e0 5d 41 5c 41 5d c3 48 8b 07 48 85 c0 74 0f 48 89 c2 <48> 8b 40 10 48 85 c0 75 f4 48 89 d0 c3 48 8b 07 48 85 c0 74 0f 48 Aug 19 11:22:22 Tower kernel: RSP: 0018:ffffc90000c27d88 EFLAGS: 00010202 Aug 19 11:22:22 Tower kernel: RAX: 660a30093a736f70 RBX: ffff888190ea5000 RCX: 000000000000000a Aug 19 11:22:22 Tower kernel: RDX: 660a30093a736f70 RSI: ffff888105e49f00 RDI: ffff88812914c000 Aug 19 11:22:22 Tower kernel: RBP: 0000000000000000 R08: ffff888190ea5064 R09: 0000000000000000 Aug 19 11:22:22 Tower kernel: R10: ffff88883f7a2380 R11: ffff88883f7a2400 R12: 0000000000000001 Aug 19 11:22:22 Tower kernel: R13: ffff88812914c000 R14: ffff88883f9e354c R15: ffff88818ca85140 Aug 19 11:22:22 Tower kernel: FS: 0000152c19298700(0000) GS:ffff88883f780000(0000) knlGS:0000000000000000 Aug 19 11:22:22 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 19 11:22:22 Tower kernel: CR2: 0000152bd800dea0 CR3: 0000000193a34003 CR4: 00000000007706e0 Aug 19 11:22:22 Tower kernel: PKRU: 55555554 Aug 19 11:22:22 Tower kernel: Call Trace: Aug 19 11:22:22 Tower kernel: fq_reset+0x66/0xd6 Aug 19 11:22:22 Tower kernel: qdisc_reset+0x19/0xd0 Aug 19 11:22:22 Tower kernel: qdisc_destroy+0x28/0x6b Aug 19 11:22:22 Tower kernel: dev_shutdown+0x3e/0x59 Aug 19 11:22:22 Tower kernel: rollback_registered_many+0x277/0x4ad Aug 19 11:22:22 Tower kernel: unregister_netdevice_queue+0x95/0xed Aug 19 11:22:22 Tower kernel: __tun_detach+0x218/0x26d [tun] Aug 19 11:22:22 Tower kernel: tun_chr_close+0x30/0x48 [tun] Aug 19 11:22:22 Tower kernel: __fput+0xf7/0x1ba Aug 19 11:22:22 Tower kernel: task_work_run+0x70/0x81 Aug 19 11:22:22 Tower kernel: exit_to_user_mode_prepare+0x51/0xc6 Aug 19 11:22:22 Tower kernel: syscall_exit_to_user_mode+0x45/0x53 Aug 19 11:22:22 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Aug 19 11:22:22 Tower kernel: RIP: 0033:0x152c1b0725bb Aug 19 11:22:22 Tower kernel: Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 13 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 51 fc ff ff 8b 44 Aug 19 11:22:22 Tower kernel: RSP: 002b:0000152c192978e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 Aug 19 11:22:22 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000152c1b0725bb Aug 19 11:22:22 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: 000000000000001d Aug 19 11:22:22 Tower kernel: RBP: 0000152c1929795c R08: 0000000000000000 R09: 0000000000000007 Aug 19 11:22:22 Tower kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000 Aug 19 11:22:22 Tower kernel: R13: 0000000000000000 R14: 0000000000000001 R15: 000000000000000b Aug 19 11:22:22 Tower kernel: Modules linked in: xt_mark xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap nvidia_uvm(PO) veth xt_nat xt_tcpudp macvlan xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs md_mod amdgpu gpu_sched ttm nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) kvmgt vfio_mdev mdev i915 iosf_mbi i2c_algo_bit drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 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 libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul wmi_bmof intel_wmi_thunderbolt crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel Aug 19 11:22:22 Tower kernel: crypto_simd r8125(O) cryptd glue_helper r8169 i2c_i801 ahci rapl i2c_smbus i2c_core video intel_cstate realtek wmi intel_uncore libahci backlight button acpi_pad Aug 19 11:22:22 Tower kernel: ---[ end trace a8682f7bc8f8a248 ]--- Aug 19 11:22:22 Tower kernel: RIP: 0010:rb_first+0xb/0x18 Aug 19 11:22:22 Tower kernel: Code: 45 0c eb 06 ff 45 10 45 31 e4 4c 89 ee 48 89 ef e8 c1 48 37 00 5a 44 89 e0 5d 41 5c 41 5d c3 48 8b 07 48 85 c0 74 0f 48 89 c2 <48> 8b 40 10 48 85 c0 75 f4 48 89 d0 c3 48 8b 07 48 85 c0 74 0f 48 Aug 19 11:22:22 Tower kernel: RSP: 0018:ffffc90000c27d88 EFLAGS: 00010202 Aug 19 11:22:22 Tower kernel: RAX: 660a30093a736f70 RBX: ffff888190ea5000 RCX: 000000000000000a Aug 19 11:22:22 Tower kernel: RDX: 660a30093a736f70 RSI: ffff888105e49f00 RDI: ffff88812914c000 Aug 19 11:22:22 Tower kernel: RBP: 0000000000000000 R08: ffff888190ea5064 R09: 0000000000000000 Aug 19 11:22:22 Tower kernel: R10: ffff88883f7a2380 R11: ffff88883f7a2400 R12: 0000000000000001 Aug 19 11:22:22 Tower kernel: R13: ffff88812914c000 R14: ffff88883f9e354c R15: ffff88818ca85140 Aug 19 11:22:22 Tower kernel: FS: 0000152c19298700(0000) GS:ffff88883f780000(0000) knlGS:0000000000000000 Aug 19 11:22:22 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 19 11:22:22 Tower kernel: CR2: 0000152bd800dea0 CR3: 0000000193a34003 CR4: 00000000007706e0 Aug 19 11:22:22 Tower kernel: PKRU: 55555554
-
[Plugin] USB_Manager
wow! passing in the usb hub actually works. steamvr can see headset. setup and calibration pass. it works but there is a weird blur or jittery view when looking around in the headset. like some kind of video lag. i think the video lag might be parsec since... this is a headless unraid server. I will have to experiment with direct attached monitor.
-
[Plugin] USB_Manager
Nevermind. thanks for your help. I think I've reach the end of the road here. my mobo cannot create an isolated IOMMU group for the 2nd usb controller card. and it seems like this is a requirement for HTC Vive to vm passthrough. your plugin seems to be closer than anything I've seen to getting around this requirements but the folks at lime tech have say so in this post...
-
[Plugin] USB_Manager
I should have bookmarked... I can only find this now. is this relevant? https://ybalrid.info/2018/03/install-and-run-steamvr-on-archlinux-for-using-an-htc-vive-and-do-opengl-openvr-developement/
-
[Plugin] USB_Manager
Here is the output. I had tried both port mapping and device mapping and same result. also tried qemu 3.0 usb controller. currently have all mapping rules removed. I have seen some post about creating a dev rule to lump all these devices into one "group" or device but that was for running htc vive natively on Arch linux. seems interesting since the htc vive usb hub brings in 8 devices but it should be all considered one logic device. here is the usb insert event log from Unraid as well as usb.ini. remove event root@Tower:~# cat /usr/local/emhttp/state/usb.ini [HTC_CB_USB2] ishub = 1 connected = "" bus = 001 dev = 073 ID_VENDOR_FROM_DATABASE = "HTC (High Tech Computer Corp.)" ID_VENDOR_ID = "0bb4" ID_MODEL = "CB_USB2" ID_MODEL_ID = 2210 [SMSC_USB2137B] ishub = 1 connected = "" bus = 001 dev = 074 ID_VENDOR_FROM_DATABASE = "HTC (High Tech Computer Corp.)" ID_VENDOR_ID = "0bb4" ID_MODEL = "USB2137B" ID_MODEL_ID = 2134 [Broadcom_Corp_BCM2045A0_404E3618003F] ishub = "" connected = "" bus = 001 dev = 075 ID_VENDOR_FROM_DATABASE = "HTC (High Tech Computer Corp.)" ID_VENDOR_ID = "0bb4" ID_MODEL = "BCM2045A0" ID_MODEL_ID = 0306 [HTC_HTC_Vive_2075397F5250] ishub = "" connected = "" bus = 001 dev = 076 ID_VENDOR_FROM_DATABASE = "HTC (High Tech Computer Corp.)" ID_VENDOR_ID = "0bb4" ID_MODEL = "HTC_Vive" ID_MODEL_ID = "2c87" [Valve_Software_Watchman_Dongle_D6373D9514] ishub = "" connected = "" bus = 001 dev = 077 ID_VENDOR_FROM_DATABASE = "" ID_VENDOR_ID = "28de" ID_MODEL = "Watchman_Dongle" ID_MODEL_ID = 2101 [Valve_Software_Lighthouse_FPGA_RX_LHR-27B63959] ishub = "" connected = "" bus = 001 dev = 079 ID_VENDOR_FROM_DATABASE = "" ID_VENDOR_ID = "28de" ID_MODEL = "Lighthouse_FPGA_RX" ID_MODEL_ID = 2000 [Alpha_Imaging_Tech_HTC_Vive] ishub = "" connected = "" bus = 001 dev = 080 ID_VENDOR_FROM_DATABASE = "HTC (High Tech Computer Corp.)" ID_VENDOR_ID = "0bb4" ID_MODEL = "HTC_Vive" ID_MODEL_ID = "2c87"root@Tower:~#
-
Automatic USB hotplugging for specific USB ports
Hello, first off this plugin is amazing. thank you. I was finally able to passthru my USB devices that came with the htc vive vr headset to my win10 vm however I seem to be missing 2 USB device in the list to map. Unraid sees 8 devices (057 - 064) and plugin only sees 6. probably because of the 2 duplicate devices (061 and 062 have duplicate ID as well as 060 and 064). it's also why steam vr still cannot see the headset. unfortunately I cannot isolate the usb controller into a separate IOMMU group even when adding a 2nd usb pci controller. any suggestion is welcome. thanks again.
-
[Support] binhex - MineOS-node
Yea i just started having this issue. Kinda gave up. Moving the world to a new Minecraft docker from itzg/docker-Minecraft-server. So far so good no more running as root. Java 11 default. Spigot is easily defined. Startup is fast.
-
[Support] binhex - MineOS-node
Yup on top of mineos backup snapshots. (rdiff-backup) You’ve essentially double the file counts. There’s also a ton of git repo files it’s downloaded during builds. Bottom line there’s a ton of files to be doing setfacl every reboot. My mineos container reboots everynight because of CA app data backup plugin. Sent from my iPhone using Tapatalk
-
[Support] binhex - MineOS-node
same here. I had to console into the docker and comment out the permissions rewrite. the more files u have in /config.. the longer it takes. /home/nobody/start.sh #setfacl -R -d -m o::rwx /config and #chmod -R 777 /config && cat
Fireblast3r
Members
-
Joined
-
Last visited