ados

Using the new config wipes the array but keeps the data as is on the individual drives. We can have a another member weigh in but at this point you will be rebuilding the array new and will need to ensure you know which drive/s are parity.

Welcome to the UNRAID forum. For me to help you best can you please provide: Your full hardware specs and logs for me and others What did you reinstall? Have you reviewed your VM configuration for quick issues like cache drive missed or CPU pinning? Can you conduct a general performance test using a docker app that will push the system.

Hi Max, just quickly reviewing your shares and while not all require using cache drive you do have system only on prefer. Providing your running Docker this would cause unintended spin up. What do you think?

There seems to be two issues here, one is that Intel QuickSync is supported natively with Tdarr builds. If your having issues using the commands see examples. You must have a compatible CPU and there is debates but I prefer HW over SW transcode. The other issue from log is relating to protected DVD content which I wouldn't be able to elaborate on.

As specified by the docker material, Tdarr supports Handbrake and FFMPEG without any extra installing. Handbrake is good for beginners but I would suggest jumping into the deepen and go with FFMPEG. Its more powerful and generally with the right configuration outputs in better quality. However, as far as I am aware FFMPEG cannot work with ISO files as they are containers to multiple files which are not all video and in most cases are fragmented to make ripping harder for copywrite. You would need to look at Handbrake within Tdarr. You could also depending on how many ISO files you have use BDinfo which will allow the identification of the main stream which can be placed into a watched folder by Tdarr for FFMPEG processing.

I wrote many of my own plugins which resolved this requirement.

Hey guys, got a real specific/odd request could use some assistance with. I'm downloading (legally) podcasts from a distributer that allows so as long as its for personal use to your own storage. Now the file is video/audio but I want to use Tdarr to convert it to audio only via an extraction or other method. Seems Tdarr is not designed to do this with all plugins and manual methods requiring video codec information at some point or even AC3 as a saving extension is not allowed, would this be impossible?

PIA is not compatible with many dockers at the moment due to large changes in their server infrastructure. The new nextgen servers are not working with port forwarding outside of their specific app. Their new servers are also causing issues with connections when port forwarding is not in place, as these dockers use leak tables when the connection is not established in a desired way the app refuses to function.

Need more information please.

It will take a few minutes to confirm, set the repository to only 1X version and test your plugins. I was using a low version for the same reasons.

PIA has been a solid 100% no complaint service but these Next Gen servers have really killed the functionality to the point its barely useable. It would be fine if they didn't jump the gun and close their old servers forcing the new near 0 support for Linux platform. Seems their focus is on Windows/Mac/Mobile and don't think Linux is worth the support particularly with OpenVPN files.

You must remain within the 1.X range for plugin support. Many are no longer updated and so are not compatible with 2.0X

@grither docker apps cannot see each other unless specifically configured, the activity app is for SMB activity. Have you paused your suspected apps, unless you have them configured with different schedules they can be set to keep drive activity to a minimum. I can view all content files in list through SMB without triggering the drives if the file itself is not opened.

@grither happy to help p.s If you have stuck files on the cache drive that will not move even when manual is used, this is generally caused by miss config of the cache setting. There are 2: 1. Cache Settings - located in your Settings -> Global Share Settings 2. The share itself for minimum disk space SSDs need to be equal or less than 80% of their total usable capacity which is what setting 1 is for The share setting capacity is designed for the drives in your array, however, if the cache drive is enabled on the share then the setting applies to the cache drive too; subsequently overriding the Global Share Setting.

@grither Had a quick look at your settings. If you manually force a spin down of the drives and they fire backup straight away then you have I/O activity on your drives from 1 or more sources. If you are sure you have no activity from yourself and others then it is most likely from your docker. I can see that your cache settings are mixed on the shares. You need appdata and any constant activity based functions i.e. VMs, APPs on 'only' mode for cache. That way you avoid unnecessary drive spin ups. You can also use the view share to verify if a share your expecting to only have storage on the cache is true:

@Two Wire This should be the instructions:

I second this request. I have 8TB drives so a healthy 90% full to allow for faster write speeds means 800MB free space. To have a SSD that would work with that would be 1TB and give me 200MB of working drive space, that makes no sense. Even better would be to have individual disk space settings as I have some smaller 4 TB drives and you currently cannot have both a larger drive i.e. 8TB and smaller 4TB at 90% as you would have to choose. UNRAID is all about drive mixing so how has this not been implemented

Seems like UNRAID needs a feature to fill this I think. I do appreciate your help with this, close at your leisure.

F#%@ that was it, must have changed it at some point and forgot. I think I was trying to stay at 90% on my drives, is that possible with a cache drive

I thought thats the purpose of this setting, otherwise how does one not red line their larger drives

Faulty share: PlexMedia Just conducted a test. Test.txt file copied to PlexMedia and test shares. The PlexMedia went straight to the array despite 'yes' set on the share test share worked perfectly unraid-diagnostics-20200403-2119.zip

unraid-diagnostics-20200403-2109.zip

Dang I feel bad for creating another thread. To my defense its easy to read that as an instruction without the 'I'. Just ran two moves but there is nothing to move at the moment unraid-diagnostics-20200403-2036.zip

I have noticed my cache drive has stopped working for one share only which is set to 'yes' There are two issues: Some files were stuck in the cache drive regardless of the amount of 'move requests' All new files go to the array and bypass the cache drive I played around with enabling and disabling the cache setting on the share but no luck I thought I could fix it by disabling the cache setting on the share and deleting the corresponding top down folder with that share name as the remaining files were few and had little value. The share then changed to the green color indicating no link to the share (seemed good) and then enabled the share to use the cache drive but it did not create the directory expected. Then when I complete more tests there was no caching, all files to the array and more so the array would no longer stop with the cache drive halting the process until I disabled the cache setting on the share. I decided to create the top directory myself and test further but it never saves to the cache drive and never makes any sub folders I then tested this with a new created test share and with a few sub directories everything worked perfectly At this point I'm thinking the share needs to go but I cannot loose the mountain of data within it and you cannot delete the share without deleting the data. Is there a better way to fix this, thanks in advance.

Ok, thanks