jamesy829
Members-
Posts
33 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
jamesy829's Achievements
Rookie (2/14)
1
Reputation
-
I'm using ZFS Master version 2022.08.21.54
-
Hi @IkerI was on v6.10.3 and seeing the below issue so I reinstalled the plugin but I'm still seeing the error. I tried upgraded to unraid v6.11.0 but the error still persisted. Any recommendation?
-
jamesy829 started following VM Freezes up , Case icon requests , [Support] binhex - Plex and 2 others
-
[Support] SpaceinvaderOne - Macinabox
jamesy829 replied to SpaceInvaderOne's topic in Docker Containers
Thank you @SpaceInvaderOnefor the updated Macinabox! I've been a long fan and been using Macinabox since it came out! Prior to the new version, I had accidentally destroyed my Mojave disk by breaking the EFI partition. With the new Macinabox release, I decided to go Monterey as my work MBP is using that. With the similar working configuration (Mojave) for Monterey and passthrough the GPU (Sapphire Pulse RX580) and USB3 controller, I am not able to get any display to show up. When I use VNC, I can control the keyboard and mouse which is connected to the USB3 controller so I know that passthrough for USB worked. I was wondering if anyone else ran into the no display issue, I found 2 suggestions by doing some research on my end Add `agdpmod=pikera` to the NVRAM boot-args and that didn't work for me Use the display port instead of the HDMI port on the GPU which I can't because I don't have a 40m DP cable. Below is my yml for reference, thank you in advance! <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='6' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Macinabox Monterey</name> <uuid>9669c422-5523-44b5-9abd-e7ccb47fa18b</uuid> <description>MacOS Monterey</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="osx"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <iothreads>1</iothreads> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='20'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='21'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='22'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='23'/> <vcpupin vcpu='8' cpuset='6'/> <vcpupin vcpu='9' cpuset='24'/> <vcpupin vcpu='10' cpuset='7'/> <vcpupin vcpu='11' cpuset='25'/> <emulatorpin cpuset='1,19'/> <iothreadpin iothread='1' cpuset='1,19'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/9669c422-5523-44b5-9abd-e7ccb47fa18b_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='6' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='vmx'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Macinabox Monterey/Monterey-opencore.img' index='2'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/Macinabox Monterey/macos_disk.img' index='1'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xa'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xb'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:06:c8:bd'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-6-Macinabox Monterey/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x17' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/sapphire pulse rx 580.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x17' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check'/> </qemu:commandline> </domain> -
Hi everyone, all of sudden my WebGUI doesn't start up (it was working for a long long time). And checking the logs, i'm seeing a weird error, with the line `...Floating point exception...` 2021-04-15 08:48:58,049 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists [info] Patching NZBGet config file for WebDir and ConfigTemplate locations... 2021-04-15 08:48:58,494 DEBG 'nzbget' stderr output: /home/nobody/start.sh: line 26: 295 Floating point exception/usr/local/bin/nzbget/nzbget -c /config/nzbget.conf -s 1>&- 2021-04-15 08:48:58,494 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22718133147120 for <Subprocess at 22718116771888 with name nzbget in state STARTING> (stdout)> 2021-04-15 08:48:58,494 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22718116788128 for <Subprocess at 22718116771888 with name nzbget in state STARTING> (stderr)> 2021-04-15 08:48:58,494 INFO exited: nzbget (exit status 136; not expected) 2021-04-15 08:48:58,494 DEBG received SIGCLD indicating a child quit 2021-04-15 08:48:58,494 INFO gave up: nzbget entered FATAL state, too many start retries too quickly Has anyone run into this issue and have a resolution for this?
-
Is it possible to have an image for the Corsair 900D and Rosewill RSV-R4100 made as well? For the 900D, can you also add the IcyDock HDD cage?
-
[SOLVED] VM Start-up/Shutdown crashes UNRAID
jamesy829 replied to JustOverride's topic in VM Engine (KVM)
I am also seeing the same issue with the x299 platform, did you end up fixing the issue for your MacOS vm? -
UNRAID kernel: DMAR: DRHD: handling fault status reg 40
jamesy829 replied to george_karl's topic in VM Engine (KVM)
Just bumping this to ask if this has been resolved? I am also running into this issue, passing through AMD RX580 to a OSX VM and it locks up unraid server -
Hi all, I have just encountered a repeatable issue where my VM would freeze up and my VM tab would not be accessible, then my server would shut down. This has happened for a few times now and I'm not exactly sure what is going on. Can I please get support for this issue? I pasted below the logs before it shut down my server as well as diagnostic reports after the server booted up. System spec Motherboard - EVGA Corp. X299 FTW K bio v1.24 CPU - 10980xe RAM - 128GB (4x32GB) G.Skill Ripjaws V 3600 Mhz CL18 Dec 29 13:06:47 Zoo kernel: sdi: sdi1 sdi2 Dec 29 13:06:47 Zoo rc.diskinfo[12677]: SIGHUP received, forcing refresh of disks info. Dec 29 13:06:47 Zoo unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_500GB_S2RANX0J423685P', mountpoint 'Samsung_SSD_850_EVO_500GB_S2RANX0J423685P-part2' is not set to auto mount. Dec 29 13:06:47 Zoo unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_500GB_S2RANX0J423685P', mountpoint 'EFI' is not set to auto mount. Dec 29 13:06:47 Zoo unassigned.devices: Don't spin down device '/dev/sdi'. Dec 29 13:06:47 Zoo unassigned.devices: Don't spin down device '/dev/sdi'. Dec 29 13:08:46 Zoo nginx: 2020/12/29 13:08:46 [error] 15144#15144: *1169005 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.208, server: , request: "POST /plugins/dynamix.vm.manager/include/VMajax.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.138", referrer: "http://192.168.1.138/Dashboard" Dec 29 13:09:52 Zoo kernel: vfio-pci 0000:17:00.0: enabling device (0100 -> 0103) Dec 29 13:09:52 Zoo kernel: vfio_ecap_init: 0000:17:00.0 hiding ecap 0x19@0x270 Dec 29 13:09:52 Zoo kernel: vfio_ecap_init: 0000:17:00.0 hiding ecap 0x1b@0x2d0 Dec 29 13:09:52 Zoo kernel: vfio_ecap_init: 0000:17:00.0 hiding ecap 0x1e@0x370 Dec 29 13:09:52 Zoo kernel: vfio-pci 0000:17:00.1: enabling device (0100 -> 0102) Dec 29 13:10:44 Zoo kernel: DMAR: DRHD: handling fault status reg 40 Dec 29 13:11:33 Zoo kernel: DMAR: DRHD: handling fault status reg 40 Dec 29 13:11:43 Zoo kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Dec 29 13:11:43 Zoo kernel: rcu: 14-...0: (11 GPs behind) idle=842/1/0x4000000000000000 softirq=82647151/82647151 fqs=14345 Dec 29 13:11:43 Zoo kernel: rcu: (detected by 29, t=60002 jiffies, g=120045541, q=2514330) Dec 29 13:11:43 Zoo kernel: Sending NMI from CPU 29 to CPUs 14: Dec 29 13:11:43 Zoo kernel: NMI backtrace for cpu 14 Dec 29 13:11:43 Zoo kernel: CPU: 14 PID: 8335 Comm: qemu-system-x86 Tainted: P O 4.19.107-Unraid #1 Dec 29 13:11:43 Zoo kernel: Hardware name: EVGA Corp. X299 FTW K/X299 FTW K, BIOS 1.24 10/20/2020 Dec 29 13:11:43 Zoo kernel: RIP: 0010:qi_submit_sync+0x154/0x2db Dec 29 13:11:43 Zoo kernel: Code: 30 02 0f 84 40 01 00 00 4d 8b 96 b0 00 00 00 49 8b 42 10 83 3c 30 03 75 0b 41 bc f5 ff ff ff e9 27 01 00 00 49 8b 06 8b 48 34 <f6> c1 10 74 68 49 8b 06 8b 80 80 00 00 00 c1 f8 04 41 39 c3 75 57 Dec 29 13:11:43 Zoo kernel: RSP: 0018:ffffc9002926fba0 EFLAGS: 00000093 Dec 29 13:11:43 Zoo kernel: RAX: ffffc9000003e000 RBX: 0000000000000100 RCX: 0000000000000000 Dec 29 13:11:43 Zoo kernel: RDX: 0000000000000001 RSI: 0000000000000244 RDI: ffff88a01f035080 Dec 29 13:11:43 Zoo kernel: RBP: ffffc9002926fc00 R08: 000000000000008f R09: 0000000000000009 Dec 29 13:11:43 Zoo kernel: R10: ffff88a01f035080 R11: 0000000000000090 R12: 0000000000000910 Dec 29 13:11:43 Zoo kernel: R13: ffff88a01f035080 R14: ffff88a01f023200 R15: 0000000000000046 Dec 29 13:11:43 Zoo kernel: FS: 0000147373db6e00(0000) GS:ffff88a01f980000(0000) knlGS:0000000000000000 Dec 29 13:11:43 Zoo kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 29 13:11:43 Zoo kernel: CR2: 00000001213bb000 CR3: 000000010cb08004 CR4: 00000000003626e0 Dec 29 13:11:43 Zoo kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 29 13:11:43 Zoo kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Dec 29 13:11:43 Zoo kernel: Call Trace: Dec 29 13:11:43 Zoo kernel: qi_flush_dev_iotlb+0x98/0xb4 Dec 29 13:11:43 Zoo kernel: iommu_flush_dev_iotlb.part.0+0x5f/0x7b Dec 29 13:11:43 Zoo kernel: intel_iommu_unmap+0xde/0x129 Dec 29 13:11:43 Zoo kernel: __iommu_unmap+0xa5/0x10f Dec 29 13:11:43 Zoo kernel: vfio_unmap_unpin+0x136/0x2a6 Dec 29 13:11:43 Zoo kernel: vfio_remove_dma+0x12/0x3b Dec 29 13:11:43 Zoo kernel: vfio_iommu_type1_ioctl+0x647/0x758 Dec 29 13:11:43 Zoo kernel: ? kvm_vm_ioctl+0x303/0x7b2 [kvm] Dec 29 13:11:43 Zoo kernel: vfs_ioctl+0x19/0x26 Dec 29 13:11:43 Zoo kernel: do_vfs_ioctl+0x533/0x55d Dec 29 13:11:43 Zoo kernel: ksys_ioctl+0x37/0x56 Dec 29 13:11:43 Zoo kernel: __x64_sys_ioctl+0x11/0x14 Dec 29 13:11:43 Zoo kernel: do_syscall_64+0x57/0xf2 Dec 29 13:11:43 Zoo kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 29 13:11:43 Zoo kernel: RIP: 0033:0x1473755a44b7 Dec 29 13:11:43 Zoo kernel: Code: 00 00 90 48 8b 05 d9 29 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a9 29 0d 00 f7 d8 64 89 01 48 Dec 29 13:11:43 Zoo kernel: RSP: 002b:00007ffd5439daa8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Dec 29 13:11:43 Zoo kernel: RAX: ffffffffffffffda RBX: 00007ffd5439dbd0 RCX: 00001473755a44b7 Dec 29 13:11:43 Zoo kernel: RDX: 00007ffd5439dac0 RSI: 0000000000003b72 RDI: 000000000000002c Dec 29 13:11:43 Zoo kernel: RBP: 00001473733a9a00 R08: 0000000000000000 R09: 0000000090000000 Dec 29 13:11:43 Zoo kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd5439dac0 Dec 29 13:11:43 Zoo kernel: R13: 00007ffd5439dab0 R14: 00001473733a9a00 R15: 0000000000000000 Dec 29 13:12:05 Zoo kernel: DMAR: DRHD: handling fault status reg 40 zoo-diagnostics-20201229-1321.zip
-
[Support] SpaceinvaderOne - Macinabox
jamesy829 replied to SpaceInvaderOne's topic in Docker Containers
Thanks @cat2devnull! I figured that was the issue so I looked up after I posted, but I forgot to update the post. Now I need to know the magical number to create the img so I can dd into a ssd. -
[Support] SpaceinvaderOne - Macinabox
jamesy829 replied to SpaceInvaderOne's topic in Docker Containers
@SpaceInvaderOne I notice a bug, where I specified the size of physical disk is 500G, but when everything is up and running, the total storage size is actually 536.87GB? I wanted to be 500G as I want to convert the img to a physical disk so it would be running off my SSD instead of using the cache drive. Should this be consider a bug and is there a simple way to resize the img? -
[Support] SpaceinvaderOne - Macinabox
jamesy829 replied to SpaceInvaderOne's topic in Docker Containers
hey @mSedek how did you show your CPU properly? I'm giving my hackintosh 14 cores but it would only display as `3 GHz Unknown`, I've configured to use iMac Pro 1,1 as well in the PlatformInfo. -
[Support] SpaceinvaderOne - Macinabox
jamesy829 replied to SpaceInvaderOne's topic in Docker Containers
I just want to give a big shoutout to @SpaceInvaderOne for his hard work for both version of macinabox! It has simplify the process of running mac in a vm much simpler! He deserves to be appraised and his YouTube channel are very informative for anything unraid and even outside of unraid! Beers coming up @SpaceInvaderOne, thanks again for your amazing work and future works to come! *wink* *wink* -
[SOLVED] Data Re-build drop from 80MB/sec to 500KB/sec
jamesy829 replied to jamesy829's topic in General Support
Thanks @Vr2Io for your help! Unfortunately I didn't discover whether any hardware failure (hopefully there isn't ha...) I'll look into the nvidia build when I get my windows and hackintosh VM up and running again thanks again! -
[SOLVED] Data Re-build drop from 80MB/sec to 500KB/sec
jamesy829 replied to jamesy829's topic in General Support
So.... I suspect its one of my parity (I got 2) that went bad, either when it did parity swap or prior to parity swap. I verified yesterday with a trial unraid usb and connecting them, seems fine when I left it running for 2 hours with no plug-in, dockers or any config, so I couldn't rule out any hardware issues, which is very frustrating. Then I did a reset config parity and disk (shifted order of disks as I like to sort them haha) on my unraid usb and parity sync finished after 1 and half day. Now its running fine (cross fingers) but I get a lot of multiple bar for nvidia, likely due to unraid nvidia no longer available to I need to rebuild the kernel and upgrade to rc1. -
[SOLVED] Data Re-build drop from 80MB/sec to 500KB/sec
jamesy829 replied to jamesy829's topic in General Support
Hey @Vr2Io just providing some updates, after doing the no parity, start array and using for a few hours, there were no issues so I decided to reboot and do the process again. Unfortunately it still got stuck, this time at 66%, so I decided to reset both parity and disk array, letting the parity rebuild instead. Knock on wood, its going well at 66% as we speak and parity will be done in another 13 hours... Will update as things progress, thanks!