Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

jamesy829

Members
  • Joined

  • Last visited

  1. I'm using ZFS Master version 2022.08.21.54
  2. 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?
  3. 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>
  4. 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?
  5. 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?
  6. 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.
  7. @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?
  8. 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.
  9. 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*
  10. I am running into an issue since after the new years where running binhex/arch-plexpass will always buffer when watching anything. My system is ryzen 7, 3800x with 32gb of ram with no gpu, updated docker to latest. I tried playing the videos directly and it works fine so it's definitely not the video file. Then I observe when watching through plex, there would be very little cpu usage but when I pin the cpu (4 in this case) I will see it not buffer and all 4 cores spiking in usage.
  11. Thank you!! I think I'll try with raw format vdisk for now to compare with my close to maxed out cMP (Mac Pro 4,1) as it will mainly be used for software development and potentially a bit of photo/video editing. This sounds exciting! Not really sure how to apply any of this as I will try out the Spaceinvader One suggested approach to setup a hackintosh vm. Do you know what I would need to do to apply the opencore and Lilu changes?
  12. Thank you for starting this thread @Leoyzen ! I've been doing research to determine whether there is performance difference running MacOS in a vm using vdisk or using the baremetal approach (dedicated disk) from spaceinvader video. Reading this thread and other threads, I did not find any info related to this, could you shed some light?
  13. Thanks @cogliostro I will have to bite the bullet and try it sometime this weekend then!
  14. Hey @cogliostro thanks for the response! Does your approach imply that I need to re-create the library inside plex and re-add the people who have access to the library? If so, is there a workaround?
  15. Hi, I've been using binhex docker images for a while thanks to Spaceinvader's videos! I've been having issue with binhex-plexpass where the webui is never accessible so I've been managing my plex through app.plex.tv but its very annoying as I use OrganizrV2 and its not manageable from there. I've tried to remove the "perms.txt" file as I found on google that people facing similar issue have permission issue, but that didn't work. Please let me know if I need to provide more information!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.