Jump to content

dlandon

Community Developer
  • Posts

    10,397
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. What kind of a drive is your appdata share on? Is it on the array? Or on a cache or pool device? You should transcode to the tmp file system for fastest transcoding. Set '/transcode:' to '/tmp/transcode'.
  2. After you delete it, click on the 'Docker' tab, click on the 'Add Container', then click on 'Select a Template'. You'll see your docker container template just as you set it up under '[User Templates]'. Choose the Plex docker container and it will be put back exactly as you originally set it up. In the log, it doesn't look like the remote shares went off line. I suspect that Plex had some trouble with the remote shares and couldn't deal with it. Can you remove some stuff to provide more room? You should review your container template and be sure the mappings are appropriate. I suspect you have an incorrect mapping and are filling the container with files causing the docker container to fill up. Do this: - Delete your Plex docker container. - Delete and recreate your docker vdisk image. - Re-install Plex. When you reinstall Plex, post a screen shot of your mappings. You may have to click on 'Show More Settings' to see all of them.
  3. The files in the Recycle Bin are aged by the date they were put in the Recycle Bin. The atime (access time) is used to date the files. You might see the mtime (last modified time) as older than the access time because this is the last time they were modified.
  4. All the docker container data is mapped to the /appdata/ folder that remains when a docker container is removed. You can delete and reinstall a docker container without losing any configuration as long as you reinstall with the saved user template. You are currently using 41% of the 20G docker image. That should be enough. If all you run is one Plex docker, you need to check your allocations to see if the Plex is configured properly so it does not fill the docker container. As far as your remote shares, three of them are showing 100% usage. Is it possible that all 18T of space is used? This might be why they are having issues. No room for new files. //SQUIRRELSTOR/Movies 18T 18T 155G 100% /mnt/remotes/SQUIRRELSTOR_Movies //SQUIRRELSTOR/TVShows 18T 18T 155G 100% /mnt/remotes/SQUIRRELSTOR_TVShows //SQUIRRELSTOR/UnraidBackup 18T 18T 155G 100% /mnt/remotes/SQUIRRELSTOR_UnraidBackup //JESTER/Music 5.5T 1.5T 4.0T 27% /mnt/remotes/JESTER_Music
  5. I see what you are trying to show me. There are two issues. One is the label and the other seems to be an incorrect script file being executed. I can't reproduce either of these issues and it's not been reported by anyone else. With this limited amount of information, I can't figure anything out yet. Update UD to the latest version. Your diagnostics showed you are one version behind. I don't expect updating UD will fix anything, but I might want to send you a file with some diagnostics so I can get more information on what is happening. It would be best for you to be on the latest version if I decide to do that.
  6. What is the error? When you execute the script it doesn't show this disk label?
  7. I can reproduce this and I have reported the issue to Limetech.
  8. That's the physical disk label. I can be different than the mount point. Click on the mount point when the disk is not mounted and the current physical disk label will be shown. You can then change the mount point and the disk label will be updated.
  9. Remove the UD plugin and see if it clears up.
  10. Remove the UD plugin and see if the behavior changes. If not, the report this as a bug.
  11. There is currently no way to custom organize UD devices, and no plans to do that. If ZFS is ever included in the base Unraid, zpools would be handled by Unraid.
  12. Open the /flash/config/plugins/unassigned.devices/unassigned.devices.cfg and look under the device in question and see if the 'command.1' setting shows the proper script file. Look and see if there any strange entries with either of the scripts.
  13. You can set user access to all UD devices in UD settings. You can't set user access to a particular device share.
  14. I'm not seeing an error. That is the result of you executing the device script.
  15. Unraid does not recognize the file system. Put the disk in a computer with a partition manager and be sure there are no partitions other than the main XFS partition. There is probably a hidden partition getting in the way.
  16. This is the only thig I see: Oct 19 00:39:55 Tower unassigned.devices: Error: Cannot use that mount point! Share 'Temp' is already being used in the array or another unassigned device.
×
×
  • Create New...