Leaderboard

Maybe Soon™.

I think this is resolved, we just need to be able to make the actual Nvidia build work now. No ETA

Fixed. Update again.

Any interest in a mobile interface? Something that will be redesigned to avoid having to massively zoom in order to read anything when using your phone?

You should let limetech know about your issues and concerns. After all, it's really limetech who should be providing you with a solution, not a third party like us. We do what we can (chbmb and bassrock put a lot of work into it) but there is only so much an outsider can do when they only have partial info and have to reverse engineer everything. As an example, qnap worked directly with plex employees to make sure their OS included the necessary drivers and packages to make sure transcoding worked with plex on their devices. We are neither the OS provider (limetech) or the client (plex/emby). We're just folks trying to give back to the community.

No worries. dlandon is the real hero, I'm just a guy that needed something done and figured out how to get it done. I'm sure he'll fix it very soon.

What do you get when you try to boot now? Possibly it is just a case of the BIOS resetting so it isn't trying to boot from the flash now.

No, most likely some issue with the filesytem, probably will need to re-format the pool, unless it finishes after a reboot.

Deleting the content of the codecs folder as it says in the post you quoted.

Short answer is "highly likely NOT" but first I need to correct a misconception found in the replies here. Nvidia does not "actively disable VM passthrough" (here I'm talking about GTX / RTX cards). The right word is "discourage". What the Nvidia driver does is if it detects being run in a virtualised environment, it will error out with code 43. Preferring AMD over Nvidia because of error code 43 is like preferring to stand under a coconut tree instead of a durian tree for fearing of having something dropped on your head. AMD cards are not problem free - they are notorious for reset issue. The bottom line is you shouldn't pick a brand but rather a specific model. There are many users on here who have successfully passed through Nvidia cards and AMD cards so you might want to look around the forum for success stories and use the exact same model. To reduce the chance of getting error 43 with Nvidia cards, you can follow these 3 tips: Boot Unraid in legacy mode (i.e. do NOT boot Unraid in UEFI) Do not use the to-be-passed-through GPU as your primary (i.e. what Unraid boots with) e.g. you can use the onboard as primary or buy a cheapo one to use as primary (assuming your mobo BIOS allows you to pick which slot to boot with e.g. Gigabyte X399 mobo). Dump your own vbios specific to your actual GPU (see SpaceInvaderOne guide on Youtube for how to do it) You don't have to follow all 3 right off the bat but chances are if you have error code 43, you will have to end up having to do them anyway. Now as to why I say "highly likely NOT" for your specific questions You didn't say what your exact spec is (and whether it supports IOMMU, virtualisation etc.). OnBoard GPU passthrough varies from hard to impossible. There's no easy way. So at the minimum, you are likely to need a 3rd GPU, even a cheapo one for the audio editing workstation - assuming you want to run 3 VMs simultaneously. Last but not least, mixing brands is fine. If a card can be passed through in its current slot, it doesn't care what other card is in the other slots on the mobo.

Unraid licensing is a steal for the years of value it provides!

Interesting those turkeys didn't test against 5.4 kernel which has been out a while now and is the next Long Term Supported kernel.

How is it if you're not transcoding at the same time? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 30086 nobody 20 0 1980108 266880 13300 R 476.5 0.4 22:25.85 Plex Tran+ 32559 nobody 20 0 5329376 1.8g 36160 S 52.9 2.9 68:29.85 Plex Medi+ Also, why not strictly related is there a reason you're running a 220G docker.img? You probably don't need more than 20G

Running btrfs on your array drives, brave man [emoji16] Sent from my CLT-L09 using Tapatalk

Hi aptalca. Appreciate the work the team does. I've filled out the contact form on the unraid website and expressed my interest for you guys to get the assistance you need to fix the issue. Hopefully others do as well.

Yup

General rule, you can set any path to go anywhere on your array. PS, just because its a user share doesn't mean that it has to sit on the array. Nothing is stopping you from creating a cache only user share. You're running 6.7.2 If you install CA Auto Update Applications, it will patch unRaid (whether or not you use the auto update) to reflect a change made at dockerHub that is causing an update to always show as being available. (Alternatively, update to 6.8)

In case it's helpful, I feel there are two use cases once you've got ZFS on unraid. One is your array where you can have multiple different sized disks and also crucially for home users, they all power off individually when not in use - so that would be the standard unraid array. The other is the data that you just don't want to ever lose through any kind of file corruption, like photos, important documents etc - that's ZFS. So Actually I run both. It does mean you have to lose two drives for parity, but many people do that anyway. I basically just run a simple single mirror on ZFS, the rest on unraid array with XFS.