January 31, 20206 yr System rebooted. Lost shares and docker after restart. Still under trial account would like to not have to rebuild mejoservertv-diagnostics-20200131-1443.zip
January 31, 20206 yr Community Expert 3 hours ago, JohnJay829 said: Lost shares Jan 31 11:38:57 MeJoServerTv shfs: fuse: invalid parameter in option `remember=root' Remove whatever/wherever you inserted that option, it's invalid and making the user shares mount abort. Docker service should start normally once that's fixed.
February 1, 20206 yr Author 2 hours ago, johnnie.black said: Jan 31 11:38:57 MeJoServerTv shfs: fuse: invalid parameter in option `remember=root' Remove whatever/wherever you inserted that option, it's invalid and making the user shares mount abort. Docker service should start normally once that's fixed. Thanks for checking. I am unaware of what i did to even get that option. Only changes i have tried was setting up some nfs shares to my qnap and windows server. Any easy way to remove that setting or should i start fresh
February 1, 20206 yr It'll be in /config on the flash drive, probably some file named fuse-extra or the like.
February 1, 20206 yr Author 40 minutes ago, Squid said: It'll be in /config on the flash drive, probably some file named fuse-extra or the like. can you give me the cd commands to get to the folder. i have tried cd /boot/config root@MeJoServerTv:/boot/config# ls -l total 800 -rw------- 1 root root 1317 Jan 31 14:35 DISK_ASSIGNMENTS.txt -rw------- 1 root root 256 Jan 26 17:30 Trial.key -rw------- 1 root root 10522 Jan 31 18:09 disk.cfg -rw------- 1 root root 323 Jan 27 16:12 docker.cfg -rw------- 1 root root 198 Jan 31 19:17 domain.cfg -rw------- 1 root root 7 Jan 31 17:32 drift -rw------- 1 root root 71 Jan 26 18:23 go -rw------- 1 root root 704 Jan 31 18:08 ident.cfg -rw------- 1 root root 33 Jan 26 17:28 machine-id -rw------- 1 root root 750 Jan 31 11:32 network-rules.cfg -rw------- 1 root root 106 Jan 26 18:23 network.cfg -rw------- 1 root root 293 Jan 31 13:21 parity-checks.log -rw------- 1 root root 1286 Jan 26 17:35 passwd drwx------ 12 root root 32768 Jan 31 14:30 plugins/ drwx------ 2 root root 32768 Jan 27 17:19 plugins-removed/ -rw------- 1 root root 512 Jan 31 18:05 random-seed -rw------- 1 root root 710 Jan 26 17:35 shadow -rw------- 1 root root 579 Jan 31 11:20 share.cfg drwx------ 2 root root 32768 Jan 31 14:35 shares/ -rw------- 1 root root 141 Jan 26 17:40 smb-extra.conf -rw------- 1 root root 101 Jan 26 17:35 smbpasswd drwx------ 2 root root 32768 Jan 26 17:28 ssh/ drwx------ 3 root root 32768 Jan 26 17:28 ssl/ -rw------- 1 root root 4096 Jan 31 18:09 super.dat drwx------ 2 root root 32768 Jan 26 17:28 wireguard/
February 1, 20206 yr It was extra.cfg, but it's not there, so no real idea where / how you enabled that option. @limetech?
February 1, 20206 yr Community Expert OK, I see where you did it, go to Settings - NFS and change Tunable (fuse_remember) back to default, which is 330. Then re-start the array.
February 1, 20206 yr Author 4 hours ago, johnnie.black said: OK, I see where you did it, go to Settings - NFS and change Tunable (fuse_remember) back to default, which is 330. Then re-start the array. Wow that did the trick. I turned it off. I assume i need to change it from root. When i enabled the nfs share the default is root. Should I change it to 330
February 1, 20206 yr Community Expert 18 minutes ago, JohnJay829 said: When i enabled the nfs share the default is root. No, default is 330, it can only be a number, somebody changed that.
February 1, 20206 yr Author 51 minutes ago, johnnie.black said: No, default is 330, it can only be a number, somebody changed that. Ok thanks for help. Marking solved
June 11, 20206 yr On 2/1/2020 at 6:54 AM, johnnie.black said: No, default is 330, it can only be a number, somebody changed that. The default is definitely root as I had this same issue. Under the NSF settings page whenever you select "RESET" or just delete the entry and apply, it automatically defaults to "root". Any way we can get this fixed?
June 12, 20206 yr Community Expert 7 hours ago, sunbear said: The default is definitely root as I had this same issue. It's not the normal default, unclear what might be causing this, but AFAIK you're only the second user this happens to.
Archived
This topic is now archived and is closed to further replies.