I have been troubleshooting now for about 2 days as to what could be causing this. I have come to the conclusion that there is a bug or Unraid doesn't support it unless someone else can find evidence of something else causing the issue.

 

I just received a 1tb Samsung 960 Evo that I have had high hopes for and after two days I am about ready to throw in the towel of getting it to work. When I try to add a share and set to cache only I get a message that the share was deleted.

 

tower-diagnostics-20170804-2041.zip

8 hours ago, sirkuz said:

I have been troubleshooting now for about 2 days as to what could be causing this. I have come to the conclusion that there is a bug or Unraid doesn't support it unless someone else can find evidence of something else causing the issue.

 

I just received a 1tb Samsung 960 Evo that I have had high hopes for and after two days I am about ready to throw in the towel of getting it to work. When I try to add a share and set to cache only I get a message that the share was deleted.

 

tower-diagnostics-20170804-2041.zip

I believe this is a browser related issue.    Try using a different browser.

I had tried a couple browsers. I don't think that is it. A message is getting logged about there being no space and the following:

 

"shfs/user: err: shfs_mkdir: assign_disk:"

IIRC this error was related to browser or adbock, whatever it is it's easy to get around, with your desktop browse to \\tower\cache and create a new folder called binga, now go to the shares page at it should be there as a new share, choose your settings, it should't be needed but stop/restart the array if it doesn't immediately appear.

Well I will give it another try shortly however I did try this with default edge on brand new windows install. I will see if I can have better luck with the work around as well. Will update shortly

No luck with that either. \cache doesn't show. I tried via shell and created the directory under /mnt/cache and then it shows the share. However, it still reports there is no space available when you try to copy to the share.

 

Aug 5 14:01:56 Tower emhttp: shcmd (487): chmod 0777 '/mnt/user/binga'
Aug 5 14:01:56 Tower emhttp: shcmd (488): chown 'nobody':'users' '/mnt/user/binga'
Aug 5 14:03:16 Tower shfs/user: cache disk full
Aug 5 14:03:16 Tower shfs/user: err: shfs_create: assign_disk: binga/Windows100816.iso (28) No space left on device
Aug 5 14:03:16 Tower shfs/user: cache disk full

Edited August 5, 20178 yr by sirkuz

If I'm reading your diags correctly your cache floor is set at 2TB, hence the out of space, instead of all those zeros use a suffix, e.g. 2GB

I had left it at the default 0KB. I have not ever had to adjust this with standard disks as cache. My understanding is you set that as the largest single file size you'd plan on copying to the share, correct? I have tried dozens of settings but with the nvme drive it hadn't helped in the past. I will give it another try right now.

 

6 minutes ago, sirkuz said:

I had left it at the default 0KB

 

It's not set at 0, it's

 

shareCacheFloor="2000000000"

 

Adjusting the Minimum free space setting does not make a difference. Is there a configuration file I can manually check to see if that setting is being correctly saved?

On your flash drive, in the config folder, share.cfg, look for shareCacheFloor=

Setting is changed under Settings -> Global Share Settings

its not that setting unfortunately. adjusted it to 2GB and it shows correct, 2000000000 in the config.

 

 

Then setting changed for v6.4, that setting would make sense since you're getting an out of space error on the cache device, if it's not that I'm out of ideas, it's not because you're using a NVMe device, as many users are using one, including myself.

You can create a "cache only" share on your NVME and then write to it without a problem? I only noticed this because I was carefully paying attention to when I had it set to preferred or yes and had just upgraded to 10gbe. That made it very noticeable that something was not right with the cache drive.

 

I have no problem it I put a sata/ahci flash device in there and set it to cache only. But my samsung NVME it doesn't like something about it. I can write to it fine outside of the share. If I manually copy my folders over to it then it will run my containers and their app data. However trying to copy anything to it via the unraid share fails with an out of space message.

6 minutes ago, sirkuz said:

You can create a "cache only" share on your NVME and then write to it without a problem?

 

Yes, in fact all my current cache shares are cache only.

hmmm very odd. Maybe I'll verify I haven't hosed my unraid config unknowingly causing this and load a demo up on a new usb drive to boot and look at. 

 

You saying it does in fact work fine frustrates me even more  Once I get going on something like this it takes over and I can't stop until I get it narrowed down.

4 minutes ago, sirkuz said:

Maybe I'll verify I haven't hosed my unraid config unknowingly causing this and load a demo up on a new usb drive to boot and look at. 

 

That's a good idea.

Well freaking A..... it works fine in the demo. Now what the heck did I managed to do to my current config?

 

Going forward any recommendations on just wiping and redoing my licensed USB? I really don't want to redo all my plugins, containers etc lol 

 

can't believe its working....haha

If I can get this working I can finally realize the potential of faster transfers