I had recently change my file system from reiserfs to xfs using a swap disk. After doing that, I found that I am not able to create new shares. When attempting to create a new share, the service seems to hang and require to stop and restart the array before it works again. 

 

I also noticed that when I add the new share, in the include or exclude drive, I can't find my Disk 3 in there. 

 

Even though I clearly have Disk 3 in the array. 

 

Attached is my diagnostics log. Hope someone can point me in a direction to solve this. Thanks.

tower-diagnostics-20210811-0050.zip

Global Share Settings excludes disk3

Oh man! That was such an amateur mistake!!! Thanks for pointing out.

 

However, I am still unable to create an appdata share that is cache only. Did I misconfigure anything? Please advise.

I don't know unless appdata is reserved for docker and you haven't set that up yet?

2 hours ago, yahsh said:

Oh man! That was such an amateur mistake!!! Thanks for pointing out.

 

However, I am still unable to create an appdata share that is cache only. Did I misconfigure anything? Please advise.

what happens when you try and change the Use Cache setting for that share to ‘only’ instead of ‘no’.

8 hours ago, itimpi said:

what happens when you try and change the Use Cache setting for that share to ‘only’ instead of ‘no’.

The system would still retain an appdata folder in the disk3. If I delete the appdata folder in disk3, the share would also disappear. Is this the expected behavior? If yes, could you enlightened me why that is so? Thanks.

8 minutes ago, yahsh said:

The system would still retain an appdata folder in the disk3. If I delete the appdata folder in disk3, the share would also disappear. Is this the expected behavior? If yes, could you enlightened me why that is so? Thanks.

The other issue is that if I only set the appdata to cache only, I can't start the docker containers properly. E.g plex. The system complains that /mnt/user/appdata: no media found. I had actually upgraded this unraid from a rather old version. Is it worth backing up the .key file in the /boot/config/, reinstall the unraid OS on the same thumbdrive, restore the .key file and redo create all the shares again? 

3 hours ago, yahsh said:

The system would still retain an appdata folder in the disk3. If I delete the appdata folder in disk3, the share would also disappear. Is this the expected behavior? If yes, could you enlightened me why that is so? Thanks.

This is expected behaviour.    A User Share will give a consolidated view of all top level folders  (appdata in this case) on each drive in the array and any pools to give a unified view of the share across all drives.   When you delete the folder from disk3 then if there is no ‘appdata’ folder yet created on cache the share will disappear.

 

A point you may have missed is that when you change the Use Cache setting to ‘Only’ that applies to new files - not existing ones.    The mover application takes no action on shares that have Use Cache set to ‘Only’ so any files/folders already existing on the array are left there.    If you want mover to transfer files/folders for a share from the array to cache then you need the Use Cache=Prefer setting.    This is explained in the help built into the GUI if you activate that.

2 hours ago, itimpi said:

This is expected behaviour.    A User Share will give a consolidated view of all top level folders  (appdata in this case) on each drive in the array and any pools to give a unified view of the share across all drives.   When you delete the folder from disk3 then if there is no ‘appdata’ folder yet created on cache the share will disappear.

 

A point you may have missed is that when you change the Use Cache setting to ‘Only’ that applies to new files - not existing ones.    The mover application takes no action on shares that have Use Cache set to ‘Only’ so any files/folders already existing on the array are left there.    If you want mover to transfer files/folders for a share from the array to cache then you need the Use Cache=Prefer setting.    This is explained in the help built into the GUI if you activate that.

Apologies, I still don't get it. After I set appdata to cache-only, I tried to install plexmediaserver. However, I run into the below error.

It seems that I cannot create any new folder in /mnt/user/appdata if I set it to cache-only. I can only create a new folder in /mnt/user/appdata if I set the share to cache-prefer. But if I set it to cache-prefer, the application data will end up on /mnt/disk3/appdata instead of on /mnt/cache/appdata. It is quite confusing.

Can you post a new set of diagnostics

26 minutes ago, Squid said:

Can you post a new set of diagnostics

Please see attached. Thanks.

tower-diagnostics-20210811-1857.zip

Does a reboot fix?

58 minutes ago, Squid said:

Does a reboot fix?

Tried that. Unfortunately, didn't work. I get the error: "Error response from daemon: error while creating mount source path '/mnt/user/appdata/Plex-Media-Server/transcode': mkdir /mnt/user/appdata/Plex-Media-Server: no medium found." whenever I set the appdata to cache-only.

Are you sure you can write to cache at all?

1 hour ago, trurl said:

Are you sure you can write to cache at all?

Yes, I could mkdir and copy file to /mnt/cache.
 

I gave up and "reinstall" the flash drive. After doing that, everything is working now. Thanks for the help!

A point you may have missed is that when you change the Use Cache setting to ‘Only’ that applies to new files - not existing ones. surveyzop

Edited August 20, 20214 yr by aonesur

21 minutes ago, aonesur said:

A point you may have missed is that when you change the Use Cache setting to ‘Only’ that applies to new files - not existing ones. 

This looks suspiciously like this:

On 8/11/2021 at 3:31 AM, itimpi said:

A point you may have missed is that when you change the Use Cache setting to ‘Only’ that applies to new files - not existing ones.

I am expecting spam forthcoming from @aonesur

10 minutes ago, trurl said:

This looks suspiciously like this:

I am expecting spam forthcoming from @aonesur

Missed that. Good catch. We shall see.