Having a cache disk and setting Plex appdata to /mnt/cache seems to help with some users but not othersĬutting the link between Plex and Sonarr seems to help The db corruption looks have no clear pattern (and not reproducible to those not affected e.g. The issue affects a minority of users and not others Reading through this topic again, here is how I would summarize it And to brutally honest, if you can't be bothered to help yourself, we can't be bothered to help you.
![file2folder reviews file2folder reviews](https://www.howtogeek.com/wp-content/uploads/2010/02/sshot291.png)
I know the "we'll ignore you" seems harsh but adding noisy info can be worse than not having the info. Perhaps we should have limetech have a separate topic with the first post updating the details for each user reporting the issue. The key idea is to get all affected users within sufficiently small boundary that a clear pattern can emerge from all the noise.
![file2folder reviews file2folder reviews](https://www.howtogeek.com/wp-content/uploads/2010/02/sshot162.png)
File2folder reviews update#
Have you set your appdata to /mnt/cache (or for those without cache, /mnt/disk1)? If you haven't, we'll ignore you.ĭo you have a link between Sonarr and Plex? If yes, have you disable it? If you haven't, we'll ignore you.ĭo you have automatic library update on change / partial change? If yes, have you set it to hourly? If you haven't we'll ignore you. Roughly how large is your collection? I think file count, even a rough estimate, is more important here. How about this - for anyone who reports the problem, also report: I think with complex issues like this, we need to be scientific and methodological instead of having anyone and everyone reporting problem and telling each other to try this or that.
File2folder reviews full#
Having been to both sides, I can tell you the other side certainly looks greener but is full of cow excretion that, if you are not careful, can explode in your face. The grass always looks greener on the other side. That is probably more complicated to code on Unraid (because it's not RAID) so it will probably be a while before it's implemented. That feature + the file integrity plugin should make Unraid self-repairing regardless of file system. If you want self-repairing, what you need to request is a partial rebuild feature.īecause we can infer where a file is located on a drive, that section (or those sections) of the drive can be reconstructed from the rest of the drives + parity. ZFS can be self-repairing because of its RAID design.īringing the ZFS file system over to Unraid will not automatically make it self-repairing, because Unraid isn't RAID (i.e. It sounds to me like you are trying to make Unraid into a FreeNAS clone, which it isn't. I do still tend to go over to the FreeNAS forums and salivate over ZFS from time to time.