Jump to content

trurl

Moderators
  • Posts

    44,361
  • Joined

  • Last visited

  • Days Won

    137

Everything posted by trurl

  1. If I understand you correctly, you have told Plex to use TRANSCODE for the transcode directory. You have the host path /mnt/disks/Transcode mapped to the container path /config/Transcode, so in Plex, you would tell it to use /config/Transcode.
  2. Sorry. Yes, go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post. I usually spell it out just like that but since you have been around a while I assumed you would know what I meant.
  3. The "official" plex docker doesn't have a support thread here in this forum. You would have to go to the plex website for that. Possibly your issue isn't related to any particular docker implementation of plex. Maybe something about your plex appdata, do you have a backup? Maybe something about your docker setup in general. Do you have any other dockers? Are they working OK? Post your diagnostics.
  4. You have posted this on 2 different threads now. Which of these dockers were you using when you first had the problem?
  5. And to further elaborate, if they don't have a .plg then they aren't installed after a reboot. Keep in mind that the contents of flash is not the Unraid OS. The Unraid OS is in RAM. It is loaded from the archives on flash. And .plg files are used to load plugins. No .plg then plugin not loaded.
  6. This is exactly what the Previous Apps feature on the Apps page does for you. It will let you reinstall any and all dockers exactly as they were using those user templates.
  7. Sorry for dragging this offtopic. Parity check isn't going to affect filesystem one way or the other, since even a correcting parity check will only write parity, and has no effect on the filesystem of any data disk. If the power failure causes a filesystem corruption, that would have to be dealt with on its own. So whether you complete a parity check now or later is a separate issue. Best to have an UPS as mentioned and avoid these potential issues.
  8. You should have an UPS on your server. The parity check you get from an unclean shutdown may not be the only consequence of frequent power loss. Filesystem corruption is another possibility if a data write is unable to complete, for example.
  9. User Scripts plugin https://forums.unraid.net/topic/48286-plugin-ca-user-scripts/
  10. These folders are builtin and can't be removed.
  11. Maybe some BIOS setting? Does it actually power off or is it just going to sleep?
  12. Did you instead mean you copied files back to cache?
  13. I think a similar question, complete with screenshots, was already discussed on this page. Also, the Help for this plugin might clear things up for you.
  14. The point he was making was there is no need to update Unraid separately. This "plugin" itself is actually a custom build of Unraid. Simply installing the rc8 version of this "plugin" IS installing Unraid rc8, but customized with the necessary drivers.
  15. The instructions given insure that your old NZBget isn't touched. It creates a completely new one with a different name, different version, and a different appdata folder, as indicated by the highlights. Up to you whether or not you want to keep the old one around or not.
  16. So did you update Unraid to rc8, or did you update the "plugin" to rc8? The plugin is actually a custom build of Unraid, so if you install a new version of Unraid, you have effectively removed the "plugin".
  17. A Genesis fan! Just a guess but maybe the scraper is having a problem with some character in your file or folder name.
  18. Did you read the link? Edit that last mapping in your second screenshot above.
  19. Post docker run as explained in this first link from the Docker FAQ: https://forums.unraid.net/topic/57181-real-docker-faq/?do=findComment&comment=564345
  20. Do you have those mapped in slave mode? https://forums.unraid.net/topic/57181-real-docker-faq/?do=findComment&comment=564314
  21. That is larger than the default so you must have set it. And some lines in your log suggest it may be corrupt, though I'm not familiar with those specific messages. In any case, it is easy enough to delete and recreate it to see if that helps. Go to Settings - Docker then delete and recreate your docker image at the more reasonable size of 20G. Then you can reinstall all your dockers exactly as they were before using the Previous Apps feature on the Apps page.
  22. Changed Status to Closed Changed Priority to Other
×
×
  • Create New...