Flamingo

Fix Common Problems - binhex-krusader (newbie) question

6 posts in this topic Last Reply

Recommended Posts

Hello fellow Unraiders,

 

My very first post and I'm already messing or missing something here...

 

So I get the below error in Fix Common Problems :

 

Docker application binhex-krusader has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option

 

Can someone please steer me in the right direction with this one? I checked the settings but couldn't see any slave options... The Unraid environmental is new to me so I didn't experiment with settings.

 

Many thanks in advance,

 

Flamingo

Share this post


Link to post

Many thanks trurl,

 

I take this is the part for me:

 

Quote

"Generally, to have a docker application be able to see files located on another server, or stored outside the array, you would use the plugin called "Unassigned Devices" to mount the appropriate shares.

However, on versions of unRaid prior to 6.2beta 20, in order for any docker application to see the files mounted by Unassigned Devices, you must stop the entire docker service (Settings - Docker), and then restart it.

If you are running unRaid 6.2beta 20+, then you need to adjust your volume mappings mode (usually either RW or Read Only) to be RW:Slave or Read Only:Slave)"

 

 

However I don't know how to adjust your volume mappings mode in binhex-krusader to RW:Slave (RW would be needed as I use this docker to move previously backed up data to the array).

Share this post


Link to post
Posted (edited)
59 minutes ago, Flamingo said:

However I don't know how to adjust your volume mappings mode in binhex-krusader to RW:Slave (RW would be needed as I use this docker to move previously backed up data to the array).

 

Go to the Docker tab.  Find the Binhex-Krusader in the Dockers list.  Click on it (see picture below) and select "Edit".

154563787_Krusader-edit.jpeg.0a5a8fc90c2292e7c7d1629d21bd3ec5.jpeg

 

The Binhex-Krusader Docker edit screen pops up.  Go down the list until you see the /mnt/disks/ for the container path for unassigned.  Click the "Edit" button to the right of it.

 

 

1352482715_Krusader-unassignededit.jpeg.7e0f169313ae698f130640698b30c938.jpeg

 

 

The details pop-up for the unassigned devices paths.  Go down the list to "Access Mode" and change that to "RW/Slave" and then save.

 

361440269_Krusader-unassignedslave.jpeg.bd5747b232b59914f7344e348b7b5e5f.jpeg

Edited by DoItMyselfToo
  • Like 1

Share this post


Link to post

Thank you DoItMyselfToo!

 

This was exactly what I was looking for! Many thanks for holding my hand during these challenging hours 😀

 

The warning is now gone.

 

All the best,

 

Flamingo

Share this post


Link to post

No problem.  Sometimes when you're so into how unRAID all works, it's easy to forget that a "simple" thing isn't so simple to someone just starting out.  Keep at it.  It's so worth it.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.