relink

I didn’t even know there was a ticket system 😅 but I’ll do that. I ended up buying a new pro license and tying it to some pos flash drive I had laying around just so I could get my work done last night. I’d really like to suggest to Lime Tech that when a license issue arises that maybe unraid could revert to a shortened trial mode, something like 5days or so. Something long enough that you can get in touch with support to get it resolved. Right now that felt like a bit of a “middle finger” to just be dead in the water with zero ways to get back online other than to buy another license and use another flash drive.

I already contacted support, but I doubt I'm going to hear back before morning. I accidentally blacklisted my USB. I have 2 servers and recently bought a new USB for one of them and I transferred the wrong key to the new USB and now I cant start my array on the other. I'll buy a new key if I need to, I'd prefer not to as it was a Pro key, but I just need to get my unraid server back up asap. Theres has to be something I can do?

Hmmm. I tried your XML with the VNC portion removed and still I'm getting nothing, monitor wont even wake up.

Some help would be greatly appreciated, I have been at this for over a day now, and tried 2 different GPU's with the exact same results. My unraid host is: Ryzen 5 2600 80GB DDR4 Unraid 6.10-rc4 I have setup macOS Monterey using the @SpaceInvaderOne Macinabox container. I left everything to default, and got the VM up and running no problem. I used the built in VNC to get macOS setup, create an account, etc. I then changed the allocations to 4 cpus and 12GB of ram, ran the helper script, and started the VM to verify the changes took, and they did. So using VNC macOS runs fine. I am trying to passthrough my AMD HD7870 to the macOS VM, this card is still fully and officially supported in the latest versions of macOS, and I have used it in several bare-metal Hackintoshes before with zero issues. I have the ACS override patch enabled and set to both, I went to "System Devices" and checked both the GPU and its Audio to stub to vfio and rebooted. I then dumped the vbios and added the GPU, vbios, and audio to the VM. Here is the problem, if I remove the VNC graphics adapter and start the VM I just get a blank screen on the monitor attached to the HD7870, the monitor doesn't even wake up. I have tried both HDMI and VGA (Using DVI to VGA adapter), Id try DVI but I cant find my DVI cable right now. However if I keep both the VNC adapter and the HD7870 then I get the boot picker and macOS boot process on the VNC adapter and while the VNC adapter is showing the boot process the HD7870 is doing nothing, the monitor doesn't even come out of standby. Once macOS has finished booting the VNC adapter just continues to show the last part of the boot process forever, but now the monitor attached to the HD7870 wakes up but all I see is the default macOS Monterey purple wallpaper. I installed the AMD vendor reset patch and rebooted unraid, now when I boot with just the HD7870 I still get nothing same as before. But when I boot with VNC and the HD7870, I still get nothing on the HD7870, and the VNC adapter now just shows the message "Guest has not initialized the display (yet)." I tried the exact same steps with an RX570 and got identical results. I'm not really sure what else to try at this point, either of these GPUs should have literally been plug and play with macOS... Below is the VM log and unraid diag with the VM running using VNC and the HD7870. XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-3-Macinabox Monterey/.config' \ /usr/local/sbin/qemu \ -name 'guest=Macinabox Monterey,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-Macinabox Monterey/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/5ad5f709-3506-4953-b339-152a9fa799c3_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-4.2,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,topoext=on,host-cache-info=on,l3-cache=off \ -m 12288 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":12884901888}' \ -overcommit mem-lock=off \ -smp 4,sockets=1,dies=1,cores=2,threads=2 \ -uuid 5ad5f709-3506-4953-b339-152a9fa799c3 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=35,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device '{"driver":"pcie-root-port","port":8,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x1"}' \ -device '{"driver":"pcie-root-port","port":9,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x1.0x1"}' \ -device '{"driver":"pcie-root-port","port":10,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x1.0x2"}' \ -device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ -device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ -device '{"driver":"pcie-root-port","port":11,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x1.0x3"}' \ -device '{"driver":"pcie-pci-bridge","id":"pci.7","bus":"pci.1","addr":"0x0"}' \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pcie.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pcie.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pcie.0","addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pcie.0","addr":"0x7.0x2"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.2","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Macinabox Monterey/Monterey-opencore.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device '{"driver":"ide-hd","bus":"ide.2","drive":"libvirt-3-format","id":"sata0-0-2","bootindex":1,"write-cache":"on"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Monterey-install.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device '{"driver":"ide-hd","bus":"ide.3","drive":"libvirt-2-format","id":"sata0-0-3","write-cache":"on"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Macinabox Monterey/macos_disk.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.4","addr":"0x0","drive":"libvirt-1-format","id":"virtio-disk4","write-cache":"on"}' \ -netdev tap,fd=37,id=hostnet0,vhost=on,vhostfd=38 \ -device '{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:3b:a6:7d","bus":"pci.3","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0"}' \ -chardev socket,id=charchannel0,fd=39,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \ -k en-us \ -device '{"driver":"qxl-vga","id":"video0","ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"max_outputs":1,"bus":"pci.7","addr":"0x1"}' \ -device '{"driver":"vfio-pci","host":"0000:07:00.0","id":"hostdev0","bus":"pci.5","addr":"0x0","romfile":"/mnt/user/isos/vbios/HD7870_vbios.rom"}' \ -device '{"driver":"vfio-pci","host":"0000:07:00.1","id":"hostdev1","bus":"pci.6","addr":"0x0"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/001/005","id":"hostdev2","bus":"usb.0","port":"2"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/001/003","id":"hostdev3","bus":"usb.0","port":"3"}' \ -usb \ -device usb-kbd,bus=usb-bus.0 \ -device '************************' \ -smbios type=2 \ -cpu Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-04-20T14:58:25.992004Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2022-04-20T14:58:25.992094Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-04-20T14:58:25.993776Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2022-04-20T14:58:25.993795Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-04-20T14:58:25.995221Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2022-04-20T14:58:25.995239Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-04-20T14:58:25.996604Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2022-04-20T14:58:25.996621Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] qxl_send_events: spice-server bug: guest stopped, ignoring 2022-04-20T15:01:55.412615Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] serverus-diagnostics-20220420-1104.zip

I got Monterey up and running perfectly fine, allocated some more CPU cores and RAM, tested again, still worked just fine. Now I am trying to pass-through my AMD HD7870(along with its HD audio) as the 2nd GPU with VNC as the 1st and I get stuck at the Apple logo, the progress bar gets about 1/3 full and then never goes any further. I also tried with the HD7870 as the only GPU and it also wouldn't boot into macOS. The HD7870 is still fully and officially supported by Apple as macOS compatible, and I have used it multiple times in bare-metal Hackintoshes. This card should just work™ without needing to do anything special. This is normally the point where I would take my Opencore USB to another system and add the "verbose" boot flag and try to start troubleshooting. However, I have no idea how to access the "config.plist" file with this setup. Is there a key I can hold down at the boot picker to get verbose output? Does anyone have any tips on how I can get this VM to boot with the GPU passed through? I have made plenty of bare-metal installs using Opencore before, but it's a little easier to know where something went wrong when you spend hours making the config and adding kexts yourself.

Got it, I hadn't considered it from that angle. I only ran it once so far and all my data is still intact. Luckily I had the foresight to only test it on a show that is easily replaced if needed. At this point can I safely delete the copy on the cache disk and not affect the copy on the array? I think ill take a bit easier of an approach to this for now, and use a spare SSD in unassigned devices for these movies/shows, copy them over, and then add a ".plexignore" file to the originals so Plex doesn't index the array copy and the SSD copy, only the cache copy.

Technically yes, that was intentional. The sync only goes 1 way, from the share on the Array > Cache, and I was under the impression that If a file exists on the array, and it also exists in the exact same location on the cache drive that when the mover is ran it will simply fail to move those files and skip them. Correct me if Im wrong. I have actually read that before. But in the description of the first post it's talking about "If a user attempts to copy files from a disk included in a user share, to the user share", which is technically not what I am trying to do. I am copying files from a user share to a disk that "technically" isn't directly part of the user share. I have tested this with one show so far, and it seems to have worked If I am completely wrong in my thinking of how to accomplish this, then what would be the best way for me to remove the data from the cache disk without risking the data in the share on the array?

literally over 90% of what causes my Array to be spun up is my kids watching the same hand full of movies and shows. So I setup rsync to copy certain directories back to the cache drive, this way they will be on the cache AND the array. So when those shows or movies are watched my array wont need to spin up, but they are also still protected by the array. In this example, the show I tested with is downloaded from Youtube using Tubesync. I want to be able to use the --delete option with rsync so that anything removed from the Array will also get removed from the cache the next time my rsync userscript is ran. However I also realized that if Tubesync grabs a new episode it will place it on the cache drive, and if my userscript runs before the download is finished wouldn't rsync delete the in progress download? Current Rsync command: rsync -av --progress --delete "/mnt/user/Video/Youtube/video/show" "/mnt/cache/Video/Youtube/video/" I have a couple of solutions but they all have potential issues: 1. just remove the --delete option. But then I would have to remember to manually remove the cache drive copy wouldn't I? or would unraid know to delete both? 2. Modify the mover script to exclude those directories and reverse my rsync command. But I really don't want to modify the mover or any "system" files. Im ok if the files get moved from cache to array and then copied back to cache. 3. Use "Mover Tuning" to only run my command after the mover finishes. This seems like it may work, but I'm still concerned about in-progress downloads? I'm sure the mover is smart enough not to move them, but is rsync smart enough not to delete them? 4. Create separate shares for these files. But I'd prefer not to, I might use this for other files too, and things could get confusing fast. OR maybe I'm overthinking the whole thing and there is a better way to do this...

No unfortunately I still haven’t found a reliable way to do this automatically. And I opted to not do anything manual or janky that I’d end up forgetting I did a year from now. Honestly Im surprised this just isn’t a built in feature yet. A read cache seems like such an obvious thing to have. I might consider taking a crack at it myself at some point but I have never used anything like inotify before. My scripting skills are mostly just from piecing together Google searches. Lol

I hope you don’t think I’m being obstinate with my response. That FAQ has been the first reply to almost every post I have made in the last year. And each time I reread it to make sure I didn’t miss anything. I believe I have done everything mentioned in that FAQ, and have double checked it all more than once. But I will double check again.

-I have updated my BIOS (within the last 6mo) -I have disabled global c-states even though im 2nd gen -I have set the Idle control setting appropriately. -No ram overclock -No CPU overclock -I have recently ran the latest version of memtest for over 2 days without error. -I have tried different ram, different ram configurations/number of DIMMS. If there is anything else in that post I need to check I am clearly missing what it is.

I've lost count of how many times I have read that post in the last year.

Im thinking this was the issue, g2g, xteve, and Plex were all updating around midnight, so if g2g or xteve wasn't done yet and plex did its import that would explain why my guide would have been empty. So what I did was changed the cron.txt so that g2g updates at 9:00pm, I set xteve to update at 10:00pm, and left Plex at its default of between 11:00pm-Midnight. This way there is absolutely zero chance any one of them will ever overlap.

I can certainly try it if nothing else works, but I've had bigger lineups than that working for almost a year, on the same system with 32GB ram. I think ill check into this first, as the g2g cron, xteve, and Plex all update at the exact same time. Im going to try and stagger them. However I am going on 2 days and I still have guide data so far....

Yup, I ran it manually and everything worked fine. Im not sure I follow, I have 3 lineups all very small, 79 channels , 19 channels and 9 channels. and each one has its own yaml. All 3 are set to download 14 days of guide data, and the cron is whatever the default in the container is. Part of the issue seems to be that already downloaded data is being replaced by nothing. I ran cron manually today, and currently have data but there is a good chance I will wake up tomorrow and have no guide data again.

My guide ends up blank almost every morning. I’ve been running your Xteve guide2go container for a couple years now. A few weeks ago I started loosing guide data almost every morning. I changed IPTV providers last week so I took the opportunity to start over from scratch, new cron.sh, new yaml files, everything should be new. I thought I fixed it, but I woke up today to no guide data again. not sure what else to check?

I've been using the same router for years now, im not sure what exactly id be looking for.

I know this post is about 2 weeks old, but I am having nearly the same issue with my "Dashboard" and "main" pages. Except I can confirm that the same issue happens in Firefox and Chrome (Brave), as well as in any browser on my iPhone. So this doesn't seem isolated to one particular browser or device. -All graphs are missing (Always, except immediately following a reboot) -All storage devices are missing (visually) (Always, except immediately following a reboot) -Sometimes Disk Location is missing but not always -Sometimes Docker containers are missing (visually) but not always. -Sometimes only the top bar loads and none of the dashboard page loads at all until I refresh the page a few times. I'm not sure at what point this issue is happening, it'll usually go several days before it starts happening. So far the only way I have been able to fix it is to reboot. Screenshots below, and diagnostics attached. EDIT: I just rebooted so I could have my dash back and even after a fresh reboot it takes 10-15sec for the missing parts to show up. serverus-diagnostics-20211029-1048.zip

Wow, I’m starting to think the syslog server built into my Synology isn’t very good…I searched for “macvlan” and it found nothing.

When I went through the previous logs I noticed something mentioned about Plex. Just recently my Plex server went offline, the container says it’s running and I can still access the unRaid UI but Plex is not loading. I attached a current diagnostics to see if it helps out at all. serverus-diagnostics-20210529-1945.zip

Good to know, I didn't know that. Diag is attached. serverus-diagnostics-20210527-0817.zip

I have been having issues with kernel panics ever since updating to 6.9.x, however in my last post about a month ago I seemed to have figured it out, my server has been up since that last post. Until 3 days ago... Out of the blue it's locked up again, cant even ssh kind of locked up. So I unfortunately had to do a hard reboot. This was in the middle of the night so I didn't troubleshoot I just went back to bed, and everything was fine in the AM. Yesterday it happened again around 2:08PM, and once again no SSH or anything, so I had too hard reboot. This time I made sure to pull the logs from the syslog server on my Synology, I do apologize it only exports as a .csv or .html, but it is attached. I also tried to grab a new diagnostics but despite the fact that everything seems to be running fine, I cant get the diagnostics to download. All_2021-5-26-15_32_30.csv serverus-diagnostics-20210527-0817.zip

Thank you for laying that out for me, I had no idea those steps were required to make this plugin work. But it is definitely working now. oom errors are rare, but it's nice to have a safety net now.