Leaderboard

The posts can be found in this topic: I guess I should have just started a new "6.7.3-rc" main topic. Wasn't expecting it to drag on like it has. And now it looks like the SQLite DB corruption issue is fixed but using same -rc series to tackle "Very slow array concurrent performance": The idea is that we want to solve these two issues, with minimum changes in a new 6.7 stable release without forcing everyone to move to 6.8-rc1 (which is held back now until these two issues are solved).

So I have installed a 6.6.7 unRAID with freshly formatted HDD. I tested around 10 movies hosted on rclone mount and NO ISSUE so far !!! It seems to be working flawlessly, I am so relieved

There is an rc4, but it doesn't fix the slow array problem.

Personally I wouldn't ever trust any IOT device to be on the same network as everything. Security isnt the highest priority for the manufacturers as they try and gain market share. Sent from my NSA monitored device

Sneak peak, Unraid 6.8. The image is a custom "case image" I uploaded.

MODERATOR NOTE: NONE OF THE APPLICATIONS DISCUSSED HERE ARE CURRENTLY AVAILABLE ANYMORE ON DOCKER HUB AND ARE CURRENTLY BLACKLISTED AUTHOR NOTE: I NO LONGER USE UNRAID OR DOCKER. DOCKER HUB HAS REMOVED THE ABILITY TO BUILD IMAGES WITHOUT A PAID SUBSCRIPTION SO AT THIS POINT I HAVE NO WAY TO BUILD, TEST, OR DEPLOY IMAGES PREVIOUSLY LISTED HERE.

Hi all! Firstly, I've been using UnRaid on and off for the last couple of years for different projects, just testing stuff out and getting a feel for compatibility and such. So, the last month or so, I've been getting hold of some server grade hardware and CPUs for a bigger project and have run into a little bit of a snag.. Secondly, sorry for the wall of text! My end goal is to have 1 computer running 4 VMs for gaming, GPU and USB passthrough for hot plug. The idea is simple and UnRaid can definitely do all of that. My hardware is not "new", but it does the job and works well with UnRaid. However, like many others, I am having issues with USB 3.0 "SuperSpeed" passthrough.. Yes, I'm talking about the infamous PEXUSB3S44V from StarTech... I would like to share my findings so far, because I refuse to give up on this card. So, the PEXUSB3S44V, which we all know, supports UASP ("USB Attached SCSI Protocol"), great for USB storage devices requiring that little extra speed, bad for us people trying to pass it through to a VM.. I believe the issue may be related to this controller using 2 drivers (correct me if I'm wrong), drivers "pcieport" (for the UAS part of this card) and "xhci_hcd" (for the USB 3.0 part). Using IOMMU, everything seems fine, all in seperate groups, almost too perfect, right? IOMMU group 26: [12d8:2608] 81:00.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch IOMMU group 27: [12d8:2608] 82:01.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch IOMMU group 28: [12d8:2608] 82:02.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch IOMMU group 29: [12d8:2608] 82:03.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch IOMMU group 30: [12d8:2608] 82:04.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch IOMMU group 31: [1912:0015] 83:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) IOMMU group 32: [1912:0015] 84:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) IOMMU group 33: [1912:0015] 85:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) IOMMU group 34: [1912:0015] 86:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) Trying to attach devices to this card (with IOMMU on), does nothing, nothing is showing up, no drives or devices detected by either UnRaid or the VM (Windows 10 VM, "Code 10" error, USB Root Hub not starting). However, UnRaid can properly utilize this card, but ONLY when IOMMU is disabled. Attaching devices to this card with IOMMU off, works just fine. So, armed with the knowledge that UnRaid can use this card "normally", I started my journey trying to get it to work with passthrough. What I have tried so far: The obvious stuff (startup parameters); 1. vfio-pci.ids=1912:0015 (with and without the PCI bridge for this card, 12d8:2608) 2. pci-stub.ids=1912:0015 (with and without the PCI bridge for this card, 12d8:2608) 3. intel_iommu=on iommu=pt (with either vfio-pci.ids or pci-stub.ids) The not so obvious stuff; 1. xen-pciback.hide=(81:00.0)(82:01.0)(82:02.0)(82:03.0)(82:04.0)(83:00.0)(84:00.0)(85:00.0)(86:00.0) 2. modprobe_blacklist=xhci_hcd 3. initcall_blacklist=xhci_init Last two in hopes that disabling the xhci driver might cause a fall-back to the ehci or ohci driver (forcing USB 2.0?). It is still initialized tho, I cannot get it to not start. Then I read that the xhci driver may be started via the "uas" driver/protocol, but I have not found what the init call function for this is yet or how to disable it.. (someone more into Linux might know this..). Not even sure UnRaid has UASP support, I believe I read somewhere that the kernel needs to be recompiled with "CONFIG_USB_UAS" directive (or something like it), to enable the support, but obviously those who have tried, said it made no difference, atleast not for this card. So, where am I now? My thoughts so far moving forward; Trying to disable both UASP support and the "xhci_hcd" driver from loading, in an attempt to force a fall-back. Can it be done? Trying to install "compatible" xhci drivers as modules (*.ko files?) and getting the card to use them. Can it be done? I hope my little adventure and wall of text concerning this card, can both help and inspire someone to reach a working solution for getting passthrough working properly. Final thoughts, IMHO, is that I believe this to be a driver issue, not a hardware issue. Driver issues can be corrected. Disclaimer: English is not my first language, so apologies for any typos or grammatical errors. Thank you.

The cache drive isn't full. Your problem is that you've set the minimum free space for the cache drive to be 1TB. When entering in numbers without a GB, MB (eg) suffix, the value is assumed to be in K. Fix it in Settings - Global Share Settings

Now thats a constructive reply!

The fix that Auto Update is applying is the same fix that is in the up coming (soon) 6.8

Due to a change at docker hub unraid always reports an update is available. Installing the auto update plugin (even if it's not enabled will fix this for you) Sent from my NSA monitored device

I've just checked and I've got 8 years of content (2946 days) so I'll never get around to watching all of it, so yep I'm a hoarder! To counter the large library problem I've been considering using https://github.com/adamgot/python-plexlibrary which @Spladge shared with me. Although I find the plex random recommendations e.g. 'top unplayed movies' 'top movies in history' to be useful

Just found those instructions myself and jumped over here hoping to find that the @ symbol have been fixed or was about to be fixed... Guess not. Any hint on where I would look to find the reason the @ symbol is verboten?

You can run the CLI command (this updates the files in the specific folder) /usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker -b2 -a "/mnt/disk5/iTunes/Music/Wolfgang Haffner/Kind of Cool"

It is not clear if there will ever be a 6.7.3 stable release or whether the next stable release will be 6.8.

Would be nice to see this properly fixed in 6.7.3 rather than hacking up a solution.

Tools -> Config Parity1 can be trusted to avoid a re-sync, parity2 if it exists will need a re-sync.

To be sure: You go to windows explorer > your unraid box > mount_clone (not unionfs folder) and go to Movies > your movie folder > movie.mkv and you play it. And then it causes problems?

For those who have problem with AMD grahpics in hackintosh (DP/HDMI sound not work, reset bug or etc): I've spent days to get my rx560 works well in Mojave(iMacPro1,1)/Catalina(MacPro7,1) both with metal support(also the hevc and h264 acceralation) and DP/HDMI sound, even without Lilu/WEG/AppleALC. It should work properly for RX570/RX580 too(other cards such as nvidia and vms should doing thos too to get rid of problems). You guys have to make sure in vm xml the graphic sound device are in same bus as video but different function.Then the sounds will work OOB. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2d' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/mojave/Sapphire.RX560.4096.170419.rom'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2d' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </hostdev> like the xml I've post , the video (0000:2d:00) and sound (0000:2d:01) should in same bus "0x01" but different function (video is "0x0" and sound is "0x1"). The unraid GUI won't do it automaticly(it just split the two functions of the card into multiple difference bus,maybe we can make it enhanment?) so you guys have to mannually edit the xml. After doing that ,you will find the AMD reset bug hardly appears,the sound works, and hardware acceralation works OOB without any kext, everything works like charm. Edit: I found someone have mentioned before, from here.

nope, its been requested a number of times by users on the plex forum but its apparently a bit 'tricky', at this time you have two options:- 1. as previously mentioned, roll back to 6.6.7 and/or 2. buy yourself a cache drive and relocate plex config to the cache. im assuming you are running unraid 6.7.x and im also assuming you have /config for plex defined as /mnt/user/appdata (which will target array) and dont have a cache drive, right?

It looks like it's from the Netdata Docker container.

Hi @robsch, I will have to think about how to do that and test it out. Right now it can only move the final video to "/output". Also, I kinda like everything for me to be in the root of /output so I would have to make it an optional setting at startup. I'll let you know what I come up with. My first guess would be to end the script with "mv $1 /output$1". Easiest way I can think of right off hand, it would move for example "/watch/movie/movie.mp4" to "/output/watch/movie/movie.mp4" would that work for you? The comskip.ini is only for comskip settings like commercial detection schemes, cpu threads, etc.

There is already a bug report- https://forums.unraid.net/bug-reports/stable-releases/dockers-wanting-to-update-but-dont-in-the-end-r618/ The fix will be included in 6.8, but in the meantime you can make sure that CA Auto Update is current. It will apply the fix automatically.

We may have got to the bottom of this. Please try new version 6.7.3-rc3 available on next branch.

Try testing individual modules in different slots to see if it is a specific RAM module or a specific slot giving the errors.

I'll let someone else address the VM question, except to ask a question of you. Do any of your VMs require direct hardware access (passthrough)? The configuration of each of your dockers is stored in templates on the flash drive. The Previous Apps feature on the Apps page uses these templates to reinstall your dockers exactly as they were. You should be able to: Create a new docker image in the system share. This happens when you first enable the docker service. Copy all the appdata into the appdata share so it will be there for your dockers to use when you reinstall them just as before. Use the Previous Apps feature to reinstall your dockers. The Previous Apps feature takes care of getting all the mappings, etc. from the templates on flash. Of course, this assumes that nothing you currently have depends on the specific disks and only works with User Shares for locating the media files, etc. that the docker applications work with.

No, no, no. Just replace each drive one at a time and let it rebuild to a new larger disk. This is what unRAID is designed to do.