April 8, 20179 yr Hi Guys, This is a tutorial for using a GUI file manager in unRAID. You will learn how to install and configure Sparklyballs' docker container 'Krusader' in a docker container so you can easily manage your file, folders and shares. You will see how to easily transfer data to your server when setting up a new build. Also, you will see how to backup data and move data around the array. You will see how to compare and sync folders and connect to other servers and computer with the file manager. To finish you will see some tips for getting the most out of Krusader. Hope some of you find it useful Easily move copy and sync files to unRAID, within unRAID and from unRAID using Krusader Edited April 8, 20179 yr by gridrunner
April 8, 20179 yr One comment: When setting up the /UNASSIGNED folder mapped to /mnt/disks, the access mode should be set to Read/Write:Slave If you do not do this, then there are circumstances where Krusader (or any docker app) will display the /UNASSIGNED folder, but will always show it as empty. This should be done for all mounts done by unassigned devices
April 8, 20179 yr Question: why does transferring data via the remote connection using smb in krusader use less bandwidth than using unassigned devices remote share mount in krusader? see image.
April 9, 20179 yr Author On 08/04/2017 at 3:09 PM, 1812 said: Question: why does transferring data via the remote connection using smb in krusader use less bandwidth than using unassigned devices remote share mount in krusader? see image. @1812 I have no idea!
April 9, 20179 yr Author On 08/04/2017 at 2:16 PM, Squid said: One comment: When setting up the /UNASSIGNED folder mapped to /mnt/disks, the access mode should be set to Read/Write:Slave If you do not do this, then there are circumstances where Krusader (or any docker app) will display the /UNASSIGNED folder, but will always show it as empty. This should be done for all mounts done by unassigned devices 1 Thanks squid i didnt know that. So i guess the main mapped directory path to /mnt/should also be set as r/w slave, as well as the custom one i set up as you can get to the unassigned from that aswell. Edited April 9, 20179 yr by gridrunner
April 9, 20179 yr On 4/8/2017 at 9:16 AM, Squid said: One comment: When setting up the /UNASSIGNED folder mapped to /mnt/disks, the access mode should be set to Read/Write:Slave If you do not do this, then there are circumstances where Krusader (or any docker app) will display the /UNASSIGNED folder, but will always show it as empty. This should be done for all mounts done by unassigned devices How do I go in and change this? When I go into the installed apps and select setting it looks like it only allows me to add a new folder. Question being, do I need to delete the original and recreate the UNASSIGNED folder?
April 9, 20179 yr 12 minutes ago, shanelovell said: How do I go in and change this? When I go into the installed apps and select setting it looks like it only allows me to add a new folder. Question being, do I need to delete the original and recreate the UNASSIGNED folder? Just edit the container, then hit edit on the unassigned folder. Change the access mode to RW:Slave
April 9, 20179 yr 7 minutes ago, Squid said: Just edit the container, then hit edit on the unassigned folder. Change the access mode to RW:Slave Right, I originally looked in the Unassigned App, and not the Krusader app. Thanks for your patience and tolerance.
Archived
This topic is now archived and is closed to further replies.