May 3, 20215 yr 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, 20214 yr by Ver7o
May 3, 20215 yr Community Expert The error or rebooting? Unbalance will run on the disk paths, so not affected by user shares, but rebooting will abort it.
May 3, 20215 yr Author 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.
May 3, 20215 yr 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.
May 3, 20215 yr Author 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.
Archived
This topic is now archived and is closed to further replies.