Years ago when I setup Unraid I setup the appdata folder incorrectly and spread the share across the array. I recently decided to fix that and move the appdata folder to the cache drive only by following this posting -

And it all worked except that the appdata share is empty even though I have it configure to be cache only.

 

Is there a way to manually force the share to only look in at cache/appdata?

29 minutes ago, dexdiman said:

the appdata share is empty even

What do you mean by that?

The share folder on the server root dir is empty. (\\servername)

 

But if I navigate to /cache/appdata it's completely populated with all my docker containers.

 

How do I get the share "appdata" to be /cache/appdata?

It I worth checking your drives to see if you have an ‘appdata’ folder with same spelling but different capitalisation (e.g. Appdata).    Linux is case sensitive for file names while Samba (shares) is not.    In the case of there being folders with the same spelling but different capitalisation at the Linux level then only one of them will be visible at the samba (share) level. 

I gone through and deleted all the appdata folders on the individual drives, and I've also run the command rm -rvf /mnt/disk*/appdata for each drive.

 

I've deleted the share and tried recreating it. I've noticed when I create the share I can select anything under the "use cache only" drop down, but if I select "yes" the server acts like it created the share but it doesn't. If I select "no" or "prefer" it creates the share but it's still empty. I've also tried creating a share called anything other than "appdata" with the "use cache only" set to "yes" and it still won't create a share.

 

Is there a way to create a share and force it to be /cache/appdata via the cli?

Do you have a folder named "cache" on any of your array disks?

There was a random folder labeled "cache" on one of the disks and I removed it but it's still not creating a share when selecting cache only. I did look through the logs and found this error when it was trying to create the share:

 

Oct 16 16:33:40 Coruscant emhttpd: req (39): shareNameOrig=&shareName=appdata&shareComment=&shareAllocator=highwater&shareFloor=0&shareSplitLevel=&shareInclude=&shareExclude=&shareUseCache=only&shareCOW=auto&cmdEditShare=Add+Share&csrf_token=****************
Oct 16 16:33:40 Coruscant emhttpd: shcmd (6358): mkdir '/mnt/user/appdata'
Oct 16 16:33:40 Coruscant root: mkdir: cannot create directory '/mnt/user/appdata': No medium found
Oct 16 16:33:40 Coruscant emhttpd: shcmd (6358): exit status: 1
Oct 16 16:33:40 Coruscant emhttpd: shcmd (6359): rm '/boot/config/shares/appdata.cfg'
Oct 16 16:33:40 Coruscant emhttpd: Starting services...
Oct 16 16:33:40 Coruscant emhttpd: shcmd (6361): /etc/rc.d/rc.samba restart
Oct 16 16:33:42 Coruscant root: Starting Samba: /usr/sbin/nmbd -D
Oct 16 16:33:42 Coruscant root: /usr/sbin/smbd -D
Oct 16 16:33:42 Coruscant root: /usr/sbin/winbindd -D

 

What does that error mean?

7 minutes ago, dexdiman said:

Oct 16 16:33:40 Coruscant root: mkdir: cannot create directory '/mnt/user/appdata': No medium found

Do you have a cache drive?  This implies that you've set your appdata to be cache-only (which is possible if due to a misconfiguration of an app it created a cache folder), but you don't actually have one.  Post your diagnostics.

I do have a cache drive.

 

 

 

coruscant-diagnostics-20191018-0312.zip

ttt

 

Can anyone offer any more help?

It might be worth posting the output of the following command:

Quote

ls -l /mnt/disk* /mnt/cache

as this will help us see if there is any folder somewhere on your system that might be causing a problem with creating the share.

/mnt/cache:
total 0
drwxrwxrwx 19 nobody users 266 Oct 19 21:12 appdata/

/mnt/disk1:
total 8
drwxrwxrwx  6 nobody users   98 Sep  3 17:50 backup/
drwxrwxrwx  2 nobody users    6 Nov  2  2017 downloads/
drwxrwxrwx  4 nobody users   34 Mar 24  2016 home/
drwxrwxrwx 25 nobody users 4096 Oct  8  2018 install/
drwxrwxrwx 38 nobody users 4096 Dec  9  2016 movies/
drwxrwxrwx  3 nobody users   29 Nov 23  2016 music/
drwxrwxrwx  7 nobody users  119 Sep 24  2017 tv/

/mnt/disk10:
total 4
drwxrwxrwx  4 nobody users   33 Sep  3 17:49 backup/
drwxrwxrwx  7 nobody users  186 Nov  7  2017 downloads/
drwxrwxrwx  4 nobody users   34 Aug  5 18:54 home/
drwxrwxrwx  9 nobody users  172 Jun 28 13:00 install/
drwxrwxrwx 51 nobody users 4096 Aug  9 23:33 movies/
drwxrwxrwx  3 nobody users   26 Jun 27 21:37 music/
drwxrwxrwx  3 nobody users   21 Jun 27 21:38 system/
drwxrwxrwx 11 nobody users  195 Jun 28 09:33 tv/
drwxrwxrwx  2 nobody users    6 May 12 10:52 vm/

/mnt/disk11:
total 0
drwxrwxrwx 4 nobody users 33 Sep  3 17:50 backup/
drwxrwxrwx 7 nobody users 78 Nov  7  2017 downloads/
drwxrwxrwx 2 nobody users  6 Sep  8 18:15 tv/

/mnt/disk2:
total 0

/mnt/disk3:
total 0
drwxrwxrwx 3 root root 20 Apr  6  2018 backup/

/mnt/disk4:
total 24
drwxrwxrwx 119 nobody users 8192 Aug  6  2018 movies/
drwxrwxrwx 111 nobody users 4096 Aug 23  2016 music/
drwxrwxrwx   3 nobody users   21 Jan 10  2016 recorded\ tv/
drwxrwxrwx  21 nobody users 4096 Oct  7  2017 tv/

/mnt/disk5:
total 4
drwxrwxrwx 13 nobody users 4096 Jan  1  2016 movies/
drwxrwxrwx  4 nobody users   46 Jan  1  2016 tv/

/mnt/disk6:
total 12
drwxrwxrwx 99 nobody users 4096 Mar 28  2016 movies/
drwxrwxrwx 50 nobody users 4096 Jan  8  2016 music/

/mnt/disk7:
total 4
drwxrwx---  7 nobody users  172 Oct 21 21:39 Nextcloud/
drwxrwxrwx  2 nobody users    6 Oct 19 20:33 appdata/
drwxrwxrwx  3 nobody users   20 Sep  3 17:50 backup/
drwxrwxrwx  7 nobody users   78 Nov  7  2017 downloads/
drwxrwxrwx  3 nobody users   19 Mar 24  2016 home/
drwxrwxrwx  3 nobody users   24 Oct 11 16:50 install/
drwxrwxrwx 25 nobody users 4096 Oct 18 12:23 movies/
drwxrwxrwx  4 nobody users  111 Sep  9 17:22 music/
drwxrwxrwx  8 nobody users   89 Oct 19 20:34 surveillance/
drwxrwxrwx  4 nobody users   57 Oct  5 21:55 tv/

/mnt/disk8:
total 8
drwxrwxrwx  3 nobody users   19 Aug 30  2018 backup/
drwxrwxrwx  9 nobody users  127 Nov  7  2017 downloads/
drwxrwxrwx  4 nobody users   34 Mar 24  2016 home/
drwxrwxrwx 15 nobody users  292 Oct  8  2018 install/
drwxrwxrwx 42 nobody users 4096 Dec 23  2017 movies/
drwxrwxrwx  9 nobody users  142 Nov 23  2016 music/
drwxrwxrwx 20 nobody users 4096 Jul 15 20:16 tv/

/mnt/disk9:
total 4
drwxrwxrwx 25 nobody users 4096 Mar 28  2016 movies/
drwxrwxrwx  3 nobody users   31 Jan  1  2016 music/
drwxrwxrwx  9 nobody users  133 Jan  1  2016 tv/

/mnt/disks:
total 0
drwxrwxrwx 1 root root 0 Oct 15 18:54 backup-backblaze/

This is finally resolved. My Unraid server took a dump and wouldn't boot anymore after a routine shutdown. I backed up the flash drive, wiped it, and installed a new Unraid instance. I moved over super.dat and my key file and the system booted. I then proceeded to move over a .cfg file and reboot. I did that till everything was restored. All credit goes to johnnie.black for pointing me in the right direction and allowing me to get my server back without having to rebuild it from scratch.

Edited August 2, 20205 yr by dexdiman

Double Check your system. There's an appdata folder on disk7.

 

That wasn't the problem. I created the appdata folder on d7 as a test to see if I could figure out where the appdata share was actually pointing. Either way the issue has been resolved with a fresh Unraid install so the issue wasn't a rouge appdata folder but Unraid pointing the appdata folder to the incorrect location no matter what I did.