Shares missing after moving to cache

[Wynter]

Is it normal for the appdata, system, and domains shares to disappear after setting to prefer and moving them to the cache?  How do I set them to Yes or No for their cache preference if they are no longer shown in the shares section? 

[trurl]

1 minute ago, Wynter said:

Is it normal for the appdata, system, and domains shares to disappear after setting to prefer and moving them to the cache?

No

 

If possible before rebooting and preferably with the array started
Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

[Wynter]

unraid-diagnostics-20210304-2154.zip

[trurl]

According to your diagnostics those shares do exist and they are all on cache as they should be.

 

What makes you think they have disappeared?

 

21 minutes ago, Wynter said:

they are no longer shown in the shares section

Have you cleared browser cache since upgrading to 6.9?

[Wynter]

They no longer show up on my network and they don't show on the shares tab of the main web interface.

[Wynter]

I cleared my browser cache and tried another browser without any change.  I should have 6 shares on the shares tab and I only have the 3 that are not system, appdata and domains.  The appdata share was exported but it no longer shows up on my network.

[trurl]

What do you get from the command line with this?

ls -lah /mnt/user

 

[Wynter]

I only see the shares that I see in the web interface and not appdata, system and domains...

[trurl]

Please post the exact results of the command, not your interpretation of them.

[trurl]

Also, what do you get with this?

ls -lah /mnt

 

[Wynter]

root@UNRAID:~# ls -lah /mnt/user
total 0
drwxrwxrwx  1 nobody users  61 Mar  4 22:29 ./
drwxr-xr-x 14 root   root  280 Mar  4 22:13 ../
drwxrwxrwx  1 nobody users  28 Dec 27 06:30 backup/
drwxrwxrwx  1 nobody users   6 Dec 14 11:51 isos/
drwxrwxrwx  1 nobody users  38 Jan 13 17:44 media/
root@UNRAID:~# 

 

[Wynter]

root@UNRAID:~# ls -lah /mnt
total 16K
drwxr-xr-x 14 root   root  280 Mar  4 22:13 ./
drwxr-xr-x 20 root   root  440 Mar  4 22:31 ../
drwxrwxrwx  1 nobody users  50 Mar  4 22:34 cache/
drwxrwxrwx  5 nobody users  61 Mar  4 22:34 disk1/
drwxrwxrwx  4 nobody users  45 Mar  4 22:34 disk2/
drwxrwxrwx  4 nobody users  45 Mar  4 22:34 disk3/
drwxrwxrwx  3 nobody users  19 Mar  4 22:34 disk4/
drwxrwxrwx  3 nobody users  19 Mar  4 22:34 disk5/
drwxrwxrwx  3 nobody users  19 Mar  4 22:34 disk6/
drwxrwxrwx  3 nobody users  19 Mar  4 22:34 disk7/
drwxrwxrwt  3 nobody users  60 Mar  4 22:13 disks/
drwxrwxrwt  2 nobody users  40 Mar  4 22:13 remotes/
drwxrwxrwx  1 nobody users  61 Mar  4 22:34 user/
drwxrwxrwx  1 nobody users  61 Mar  4 22:34 user0/
root@UNRAID:~#

[trurl]

What do you get with this?

ls -lah /mnt/cache

 

[Wynter]

root@UNRAID:~# ls -lah /mnt/cache
total 16K
drwxrwxrwx  1 nobody users  50 Mar  4 22:34 ./
drwxr-xr-x 14 root   root  280 Mar  4 22:13 ../
drwxrwxrwx  1 nobody users 104 Feb 19 22:56 appdata/
drwxrwxrwx  1 nobody users   0 Dec 14 11:51 domains/
drwxrwxrwx  1 nobody users  38 Jan 13 17:44 media/
drwxrwxrwx  1 nobody users  26 Dec 14 11:51 system/
root@UNRAID:~#

[trurl]

All of that seems to agree with what your diagnostics say, the folders exist and are on cache.

 

However, it doesn't look like cache has much if anything on it. And it is using the new 6.9 partitioning. What can you tell us about your upgrade to 6.9?

[Wynter]

I just did the upgrade earlier today, nothing out of the ordinary and seemed to go properly.  My dockers are working okay so I was pretty sure that the data was there still, but I tried to look at a file in appdata via the network share and it wasn't there.  I am not entirely sure if the issue started before the upgrade or started after...  should I try and restore rc2 and see if that corrects the issue?

[Wynter]

Recently I had used the mover to get everything off the cache and reformatted it to BTRFS from XFS, but I think the appdata share was working at that point.

[trurl]

After examining syslog, I see some things you didn't mention in your description of the upgrade.

 

You repartitioned and reformatted cache, then later you ran preclear on cache and formatted it again.

 

Since syslog restarts on reboot, I can't see anything from before the upgrade, and if you didn't have mover logging turned on it might not show anything anyway.

 

No evidence anything was ever moved off cache before you reformatted it. Maybe nothing on cache now except empty folders.

 

Are you saying your dockers are currently working?

 

What do you get from command line with this?

ls -lah /mnt/cache/appdata

 

[Wynter]

root@UNRAID:~# ls -lah /mnt/cache/appdata
total 16K
drwxrwxrwx 1 nobody users 104 Feb 19 22:56 ./
drwxrwxrwx 1 nobody users  50 Mar  4 23:04 ../
drwxrwxrwx 1 nobody users 136 Mar  4 22:29 bitwarden/
drwxrwxrwx 1 nobody users 116 Dec 24 05:36 emby/
drwxrwxrwx 1 nobody users  22 Mar  4 21:22 nzbget/
drwxrwxrwx 1 root   root   28 Jan 30 21:10 onlyoffice/
drwxrwxrwx 1 nobody users 114 Mar  4 23:04 radarr/
drwxrwxrwx 1 nobody users 220 Mar  4 21:23 readarr/
drwxrwxrwx 1 nobody users 224 Mar  4 22:41 sonarr/
drwxrwxrwx 1 nobody users 152 Mar  4 21:23 swag/
root@UNRAID:~#

 

All my dockers are functioning without issue.

[trurl]

Try stopping and starting the array.

[Wynter]

Still not showing those 3 shares...  

[trurl]

Reboot

[ddelorme]

I to after adding a brand new cache pool and setting appdata to prefer and selecting Move command my appdata shared folder has disappeared. Could it be because move has not finished? On Main page says "Mover is running"

readydata-diagnostics-20230622-2333.zip

[ddelorme]

ran this command output below:

 

/bin/ls: cannot access '/mnt/cache/appdata': Input/output error

[itimpi]

There is no SMART information for the cache drive so it looks like it has dropped offline.   That would explain the appdata share disappearing it it has all been moved to cache.    
 

I would carefully check cables (power and SATA) to the drive.   Then power cycle the server and post new diagnostics when it comes back.

 

I notice that the ‘system’ share is also set to be moved to the cache but currently has files on disk1.    If you want this to be moved then the docker and VM services need to be disabled when you run mover as the services keep files open which prevents them moving.