Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

26 Good

About remotevisitor

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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.
  4. 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
  5. The best way to achieve this is to use the “User Scripts" plugin. Update: just read the earlier posts and realized this was already suggested.
  6. Have a read of this issue (towards the end there is a mention of a possible workaround) ...
  7. You are correct, just remove the "-R" option when using the "mv" command.
  8. The command you want to add to the script is: cp -R /mnt/disks/DELUGETorrents/Seedbox_Downloads/* /mnt/disks/DELUGETorrents/Sonarr_Pickup/ When you want to move the files rather than copy them change the "cp" to "mv".
  9. User Scripts plugin is probably the easiest way ... it supports running commands on a schedule.
  10. That’s incorrect. All connected drives, other than the USB boot drive, count towards the license count. This limit is checked when the data array is started. However once the array is started additional drives can be added to be used as unassigned drives. If the system is rebooted, these additional drives will count towards the limit so may need to be temporarily removed in order to get below the limit in order to start the data array
  11. To force the copy/delete behaviour you can make the move operation be ... 'move /mnt/user/Downloads/foo /mnt/user0/Books/’
  12. Click on the SMART status entry on the dashboard for the disk in question and select the Acknowledge option. CRC entries are never actually reset back to zero, but if the value changes again you will be warned. if you are already doing this, then you may have some issue saving the saved state back to the flash drive.
  13. How about: find /mnt/user/yourfolder -type f -mtime -0 -print
  14. The issue is rather subtle so I’m not surprised if you find it difficult to grasp what is exactly going on. I have the cache setting on the shares on my system which hold all my TV and films set YES even though 99% of the time I am reading from them, so unless you have a specific reason on why you must set it to NO then this is the easiest solution. For the other solution, no you do not need to create a second user. What you will find when your array has been started is that your shares appear under the directories /mnt/user and /mnt/user0. The difference is the /mnt/user ones include files that are on your cache + data drives, while the /mnt/user0 ones just include the files that are on your data disks. The /mnt/user0 directory is really a hangover from the old way that mover used to be implemented to copy files from the cache disk to the array. It has since been replaced with a dedicated mover program which understands how to move the files to/from the cache disk without using it. Tom has dropped hints that he would like to get ride of /mnt/user0, but some people have indicated they do have uses for it; so it may or may not disappear in a future release.
  15. I think the problem that a file has been created on a share which uses the cache disk, so the file is created on the cache disk. The file is then moved to the Media share, and rather surprisingly you find it is still on the cache disk in the Media share, even though the Media share is set to cache NO. This is actually expected behaviour and the reason is rather subtle. The caches setting on a share only affects the creation of new files and not files which already exist on a disk. Now as the file already exists on the cache disk and the cache disk is included in the Media share the cache setting does not apply so the file is moved into a directory in the Media share on the cache disk. There are 2 possible solutions: - Change the Media share to cache YES so the mover will move file to the data disks when it runs. - Move files to /mnt/user0/Media rather than /mnt/user/Media as that does not include the cache disk so the move is forced to do a copy & delete farther than just a rename.