Mover errors cause shares to disappear

[smick]

I'm new to Unraid and I've been experimenting with dockers and VMs. Unraid is amazing! I've gone through many of the excellent Spaceinvader One tutorials and in the process I have installed and uninstalled dockers and VMs many times to get things working.  At at some point the user shares would be gone in the morning and I'd have to reboot to get them back. I have narrowed the problem down to the mover process in the scheduler. Running it manually the log shows the attached errors and the shares disappear. Any suggestions on how to proceed?

[Squid]

Post your diagnostics before you reboot (Tools - Diagnostics)

[trurl]

syslog snippets are seldom sufficient

 

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

[smick]

Here are the diagnostics taken when the shares are not available.

myunraid-diagnostics-20191229-1144.zip

[Squid]

Dec 29 10:16:30 MyUnRAID emhttpd: shcmd (38): mount -t btrfs -o noatime,nodiratime /dev/sdc1 /mnt/cache
Dec 29 10:16:30 MyUnRAID root: mount: /mnt/cache: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
Dec 29 10:16:30 MyUnRAID emhttpd: shcmd (38): exit status: 32
Dec 29 10:16:30 MyUnRAID emhttpd: /mnt/cache mount error: No file system
Dec 29 10:16:30 MyUnRAID emhttpd: shcmd (39): umount /mnt/cache

This looks to be the root of the problem.  I'm assuming that the cache drive should have file(s) on it?

[trurl]

Did you actually format cache after adding it to your server?

[smick]

I think the problem was the ancient SSD I was using as a cache for testing. I know I formatted it when I set it up so I just switched to a 500gb nvme I had and its working with mover now. I suspect it will work from here. Thanks.