[SOLVED] Lost Shares and Docker

[JohnJay829]

After trying a update of a docker system froze and was unable to proper shutdown. After reboot now no shares are present and docker is failing to start. terminal is showing /mnt/user empty. Checked usb on windows pc and no errors on chkdisk. Also tried starting in safemode 

mejoservertv-diagnostics-20200501-2308.zip

[trurl]

May  1 22:55:32 MeJoServerTv emhttpd: shcmd (94): mkdir -p /mnt/cache
May  1 22:55:32 MeJoServerTv emhttpd: shcmd (95): mount -t xfs -o noatime,nodiratime /dev/sdb1 /mnt/cache
May  1 22:55:32 MeJoServerTv kernel: XFS (sdb1): Mounting V5 Filesystem
May  1 22:55:33 MeJoServerTv kernel: XFS (sdb1): Ending clean mount
May  1 22:55:33 MeJoServerTv emhttpd: shcmd (96): sync
May  1 22:55:33 MeJoServerTv emhttpd: shcmd (97): mkdir /mnt/user0
May  1 22:55:33 MeJoServerTv emhttpd: shcmd (98): /usr/local/sbin/shfs /mnt/user0 -disks 30 -o noatime,allow_other  |& logger
May  1 22:55:33 MeJoServerTv shfs: use_ino: 1
May  1 22:55:33 MeJoServerTv shfs: direct_io: 0
May  1 22:55:33 MeJoServerTv emhttpd: shcmd (99): mkdir /mnt/user
May  1 22:55:33 MeJoServerTv emhttpd: shcmd (100): /usr/local/sbin/shfs /mnt/user -disks 31 2048000000 -o noatime,allow_other -o remember=root  |& logger
May  1 22:55:33 MeJoServerTv shfs: fuse: invalid parameter in option `remember=root'
May  1 22:55:33 MeJoServerTv shfs: fuse_main exit: 3
May  1 22:55:33 MeJoServerTv emhttpd: shcmd (100): exit status: 3

/mmt/cache mounts, then /mnt/user0 (user shares excluding cache), but /mnt/user doesn't. I've never noticed that 'remember=root' invalid parameter before. Looking at syslogs from other working systems, that 'remember' parameter looks like it is supposed to be a number, so I don't know what that is about.

 

But, I suspect your cache is corrupt in some way even though it is mounting.

 

Then it can't mount libvirt or docker img because user shares don't mount.

 

And I am pretty sure you have corrupted docker image even though it doesn't try to mount it, because you have it set to 200G. Only 20G should be more than enough and if it fills it is because you have one or more applications writing to a path that isn't mapped. Making docker image larger will not fix a filling docker image, it will just make it take longer to fill.

 

See if you can go to Settings - Docker and disable dockers and go to Settings - VM Manager and disable VMs. Then reboot and post new diagnostics.

 

Since your cache is XFS maybe we can see if repairing its filesystem gets us anywhere. Don't even try to enable dockers and VMs again until everything else is fixed, then we can set that docker image to 20G and try to figure out what you did wrong.

[trurl]

OK. Looking at your post history, I see you already did this to yourself before:

 

 

Try the fix in that thread again. Then if we get user shares going we can work on your ridiculously large docker image.

[JohnJay829]

Wow no idea how i enabled nfs again. setting just switches to root even after i save 330 in there. i just disabled it again. thanks for the help