Finally updated to 6.1.6 from 5.0.4 and following the instructions I wiped, reinstalled, copying across cfg files, share directory, etc. so that I didn't lose everything.

 

However, the "Shares" tab in the GUI has no user shares listed after this. BUT, the shares ARE listed on the dashboard, and can be seen/accessed OK. And yes, User Shares are set to yes, and I've cycled the setting/system to no avail.

 

Anyone got any ideas? Is there some hidden posting I missed?

Whitelist your server url in any adblockers.

Whitelist your server url in any adblockers.

Cheers for that, though I've no idea why it'd get stopped by adblock.

 

Now just got to work out how to have a drive for dockers that isn't a cache; and what the best route is for moving files between drives to shift from reiser to xfs (unbalance seems abandoned).

Whitelist your server url in any adblockers.

Cheers for that, though I've no idea why it'd get stopped by adblock.

 

Now just got to work out how to have a drive for dockers that isn't a cache; and what the best route is for moving files between drives to shift from reiser to xfs (unbalance seems abandoned).

Why are you against using a cache drive for dockers? It is certainly the easiest and most common way.

 

There is a sticky in v6 General Support all about moving files around while converting filesystems.

 

Don't know why you think unBalance is abandoned. The author has posted to the thread several times in the last week.

Why are you against using a cache drive for dockers? It is certainly the easiest and most common way.

Not against the docker part, just against the cache drive part - ever since I found out it could easily fill up and wasn't working as a true cache. Want the drive for docker and VM, and not cache.

 

There is a sticky in v6 General Support all about moving files around while converting filesystems.

 

Don't know why you think unBalance is abandoned. The author has posted to the thread several times in the last week.

 

Ahh, must be looking at the wrong thread then - quite possible. Something to make it easy, rather than mucking about with command lines.

You should assign a cache drive then disable cache on your shares. That will accomplish what you want

 

Or look at the unassigned devices plugin

You should assign a cache drive then disable cache on your shares. That will accomplish what you want

 

Or look at the unassigned devices plugin

Yeah, that's what I was looking at. Seemed to be a toss up between the two approaches, and the unassigned devices would be needed anyway.

 

It is also possible to add a command to the 'go' file to mount a drive and then the corresponding command to the 'stop' file (creating it if necessary) to umount it.  This has the advantage that the drive remains mounted even if the array is stopped.  If that does not matter then the Unassigned devices is probably the easiest way to go.

You should assign a cache drive then disable cache on your shares. That will accomplish what you want

 

Or look at the unassigned devices plugin

Yeah, that's what I was looking at. Seemed to be a toss up between the two approaches, and the unassigned devices would be needed anyway.

Not really a tossup. Much simpler to do a cache drive for apps and don't cache user shares. unRAID already manages the cache drive for you. More stuff for you to take care of if you try to put apps on a drive that unRAID doesn't manage, such as with Unassigned Devices.

You should assign a cache drive then disable cache on your shares. That will accomplish what you want

 

Or look at the unassigned devices plugin

Yeah, that's what I was looking at. Seemed to be a toss up between the two approaches, and the unassigned devices would be needed anyway.

 

Agree with trurl, using a cache does not require "unassigned devices"  You are mistaken.

You should assign a cache drive then disable cache on your shares. That will accomplish what you want

 

Or look at the unassigned devices plugin

Yeah, that's what I was looking at. Seemed to be a toss up between the two approaches, and the unassigned devices would be needed anyway.

 

Agree with trurl, using a cache does not require "unassigned devices"  You are mistaken.

Didn't mean that the cache needed 'unassigned devices', more that I did so that I could attach USB drives and backup the share contents to offline storage.

 

Intend to have a hack at the weekend and will probably try the no-cache cache option first, then move to 'unassigned devices' if that doesn't seem to do the job. Need those dockers working to get back to the functionality I had - then move on from there.

You should assign a cache drive then disable cache on your shares. That will accomplish what you want

 

Or look at the unassigned devices plugin

Yeah, that's what I was looking at. Seemed to be a toss up between the two approaches, and the unassigned devices would be needed anyway.

 

Agree with trurl, using a cache does not require "unassigned devices"  You are mistaken.

Didn't mean that the cache needed 'unassigned devices', more that I did so that I could attach USB drives and backup the share contents to offline storage.

 

Intend to have a hack at the weekend and will probably try the no-cache cache option first, then move to 'unassigned devices' if that doesn't seem to do the job. Need those dockers working to get back to the functionality I had - then move on from there.

The "no-cache cache option" will definitely work and is the way almost everyone is doing it, including me. If you have some problem just ask before abandoning that approach because trying the other approach will not fix the problem and will likely give you more.