remotevisitor

Members
  • Posts

    412
  • Joined

  • Last visited

Everything posted by remotevisitor

  1. If you had a very old version of Unraid on the USB drive (which sounds likely from your description) then the license file will be in the top level of the flash drive rather than in the config folder. Also look for any file ending in ".key" in the top level. if all that fails and you haven’t got license files saved elsewhere (like on the original email which it was sent to you) then you will need to contact [email protected] with as much details as possible so support can find your license in their records and they can arrange to send a replacement.
  2. For the share in question what is the "minimum free space" setting set to? The setting needs to be a value which is the size of the largest (or larger) file that will be written to the share. If the setting value is too small it will write files to the cache disk that will not fit (resulting in the out of space error you are seeing) rather than writing them to a data disk.
  3. Does the directory "Movies/Police Academy 3 Back in Training (1986)" already exist on a data disk (maybe on one that is very full)? If so then mover will always attempt to move that film to that disk due to the split level setting, whether or not there is enough space on the disk. The split level setting over-rides all other decisions when selecting a disk to write to.
  4. Yes. the steps are more like ... 1. Move data from disk1 to disk2. 2. Put array into maintenance mode. 3. Format disk1 to XFS. 4 Start array. disk1 was never removed from the array so no need to add it back.
  5. Yes. A format will remove any existing files/directories on the drive. So you will need to copy the contents to somewhere else, reformat a drive and then copy the contents back onto the newly formatted drive.
  6. You did have file system corruption and the last run should have fixed it. if you start the array, does the problem directory/file still exist, and if so can you now successfully delete it. It looks like a bunch of files have been recovered into the lost+found directory. Unfortunately they will not have sensible names, so unless you can identify them by their content there isn’t much you can do with them. The question is what caused the file system corruption .... has your system lost power or been force powered off without shutting down in the past? That could possibly cause corruption if it was writing to the disk at the time. Otherwise I suspect you will not know what caused the problem.
  7. I suggest checking the file system on that disk to see if the issue is caused by a file system issue: https://wiki.unraid.net/UnRAID_6/Storage_Management#Checking_a_File_System
  8. What is your Settings -> Global Share Settings -> Tunable (support hard links) set to?
  9. It counts if it is plugged in when you try to start the array. It doesn’t count if it is plugged in after the array has been started.
  10. Split level trumps all disk selection methods. You have set it to never split directories because you are manually going to create them. So if the directory you are copying to only exists on disk 5 then it will not attempt to split it to another disk, causing disk 5 to fill up.
  11. If I have understood your setup correctly.... In Unraid host you have the folder /mnt/user/Movies. In the Plex docker you access it as /unraid_shares/Movies
  12. Did you read the release notes for 6.9.0-beta25, specifically the section on ssh improvements? it will have already created a symlink /root/.ssh -> /boot/config/ssh/root which will make your command in the go file to create /root/.ssh fail.
  13. As a licensed version of Unraid has to be able to work without an internet connection the blacklist has to be built in to each release. The trial version specifically has a requirement that it has a internet connection so it can use a more dynamic blacklist mechanism. The trial version is deliberately set up the way it is to prevent people just continually getting a trial version and never actually buying a license.
  14. Unfortunately this would allow widespread mis-use of the Unraid license. The updated blacklist is issued with each Unraid release. So if your suggestion is implemented I could buy 1 license and then use the unlimited transfers to create as many boot drives as I liked which would all work on the current release. Then when Unraid is upgraded I just buy a bunch of new usb drives and use the unlimited transfer to create new boot drives that work on that release.
  15. Look for the "User Scripts" plugin in Community Applications; i think it it should allow you to do what you want.
  16. This only appears if you are ‘Advanced’ mode rather than ‘Basic’. Took me a while to find the delete the first time I wanted to do this.
  17. A drive that has been blacklisted is *never* removed from the blacklist ... even if you contact support they will not do this. The blacklist is built into all subsequent releases of Unraid and therefore cannot be retrospectively removed. You need to acquire another usb drive to use for Unraid and follow the documented process for transferring your license to the new key. If you have problems doing this then Limetech support can help with any issues you have doing this.
  18. Have you read the manual ..... https://wiki.unraid.net/UnRAID_6/Changing_The_Flash_Device This page is accessible from the Unraid home page from a link at the bottom.
  19. Interesting that the official Rasberry Pi site now has its own disk imager program on the downloads page and no longer links to Etcher like it used to.
  20. Another setting it is worth checking if it makes any difference in your tests is Settings -> Global Share Settings -> Tunable (support Hard Links) set to No.
  21. You might want to experiment on turning on case sensitive names on your SMB share and see if it improves your use case performance. It can be found on a share‘s settings on the SMB Security Settings. By default directory/file names are case insensitive on SMB but as Linux uses case sensitive file systems the SMB server has to emulate the case insensitive behaviour and as the number of entries in a directory increases the overhead increases significantly.
  22. Are you sure the flash drive is being successfully mounted on /boot? If you run the following command what files/folders do you see? ls /boot