[Solved] There are no exportable user shares

[Ver7o]

Hello,

 

Today I decided to move specific shares to specific disks so the data is not scattered across multiple disks causing unneccessary disk spinups. Before moving the data Unbalance plugin kept telling me I should run "docker safe new permssions" as there were issues. I did run that and the plugin stopped reporting issues upon which I ran the mover. It is still running atm. Here is where the heart attack comes in.

 

I tried to access a share from my windows box just not and it wouldn't connect. So I checked Unraid shares tab and its saying "There are no exportable user shares".

 

A few google searches reveal a reboot can help, but I just want to have more info what to do right not before I risk rebooting and not being able to get diagnostics anymore.

 

syslog is spitting out something like this:

May 3 15:29:09 Tower smbd[27783]: [2021/05/03 15:29:09.281737, 0] ../../source3/smbd/service.c:841(make_connection_snum)
May 3 15:29:09 Tower smbd[27783]: make_connection_snum: '/mnt/user/Backup' does not exist or permission denied when connecting to [Backup] Error was Transport endpoint is not connected
May 3 15:29:09 Tower smbd[27783]: [2021/05/03 15:29:09.285374, 0] ../../source3/smbd/service.c:841(make_connection_snum)
May 3 15:29:09 Tower smbd[27783]: make_connection_snum: '/mnt/user/Backup' does not exist or permission denied when connecting to [Backup] Error was Transport endpoint is not connected
May 3 15:29:09 Tower smbd[27783]: [2021/05/03 15:29:09.288965, 0] ../../source3/smbd/service.c:841(make_connection_snum)
May 3 15:29:09 Tower smbd[27783]: make_connection_snum: '/mnt/user/Backup' does not exist or permission denied when connecting to [Backup] Error was Transport endpoint is not connected
May 3 15:41:10 Tower smbd[27783]: [2021/05/03 15:41:10.670767, 0] ../../source3/smbd/service.c:168(chdir_current_service)
May 3 15:41:10 Tower smbd[27783]: chdir_current_service: vfs_ChDir(/mnt/user/Downloads) failed: Transport endpoint is not connected. Current token: uid=1000, gid=100, 4 groups: 100 3003 3004 3005
May 3 15:41:10 Tower smbd[27783]: [2021/05/03 15:41:10.670896, 0] ../../source3/smbd/service.c:180(chdir_current_service)
May 3 15:41:10 Tower smbd[27783]: chdir_current_service: vfs_ChDir(/mnt/user/Downloads) failed: Transport endpoint is not connected. Current token: uid=1000, gid=100, 4 groups: 100 3003 3004 3005
May 3 15:41:10 Tower smbd[27783]: [2021/05/03 15:41:10.673892, 0] ../../source3/smbd/service.c:168(chdir_current_service)

 

 

tower-diagnostics-20210503-1333.zip

Edited July 7, 2021 by Ver7o

[JorgeB]

shfs segfaulted, rebooting will fix it.

[Ver7o]

This won't affect any files or Unbalance which is running?

 

Thanks!

[JorgeB]

The error or rebooting? Unbalance will run on the disk paths, so not affected by user shares, but rebooting will abort it.

[Ver7o]

Ah, only just realized how badly I worded the question. I meant if files will end up being affected because something crashed while Unbalance was still running.

[JonathanM]

14 minutes ago, Ver7o said:

I meant if files will end up being affected because something crashed while Unbalance was still running.

Quite possibly yes, since Unbalance typically copies then deletes, so you will likely have duplicate files until you rerun the Unbalance job.

[Ver7o]

Thankfully the files moved OK. Upon reboot, the shares were visible again. There were also the mentioned duplicates, but only of top level folder (the files inside those moved fine). Had to move those again and now everything is as it should be.

 

Thanks for helping guys, appreciate it.