focusedliskov
Cadet
- Joined
- Jun 25, 2018
- Messages
- 4
CIFS shares sometimes mount, sometimes does not after VM restart. Did anyone have issue like this?
Yes, 1 time and i just restarted RancherOS again and it showed upCIFS shares sometimes mount, sometimes does not after VM restart. Did anyone have issue like this?
mounts: - - //172.30.1.5/Media - /media/media - cifs - username=Downloaders,password=removed,iocharset=utf8,_netdev - - //172.30.1.5/Shared - /media/shared - cifs - username=Downloaders,password=removed,iocharset=utf8,_netdev
Yes, 1 time and i just restarted RancherOS again and it showed up
cat /var/log/syslog
I can see this error:Aug 22 18:29:16 rancher kernel: [ 28.031600] CIFS VFS: Error connecting to socket. Aborting operation. Aug 22 18:29:16 rancher kernel: [ 28.031667] CIFS VFS: cifs_mount failed w/return code = -115
Hi,
Anyone else having issues since the latest FreeNAS updates? After the update last month, my Samba share on RancherOS didn't mount. I updated the configuration, adding a "vers=2.1", to the options, and then it was mounting again, but now I notice that it does not have write access. The user provided definitely has write access, as I connect to it from my laptop and can upload items as that user.
Any ideas as to what is wrong with the mount and why it has no write permissions?
Thanks.
I could not connect at all after updating to U6. I want able to resolve it, so I downgraded to U5. And it works again.
I might have to revert to U5 as well. How does one do that? I don't recall seeing it on the upgrade page as an option. I am on the 11.2 Stable train.
Thanks.
Thanks. I reverted, but still do not have write access. I also recently updated my Plex container. I think that might have also changed something, or my attempts to fix it have broken something else.It's under System -> Boot. There you should see different boot options. Select 11.1-U5 then click Activate.
Thanks for the help. I found I had to add to the CIFS config, to mount as uid=1001, and gid=1001. Then I created a new Plex container, adding environment variables to set the Ples UID and GID to 1001. Once I did this, Plex was able to write again to the share.Thanks. I reverted, but still do not have write access. I also recently updated my Plex container. I think that might have also changed something, or my attempts to fix it have broken something else.
In RancherOS, I can create content in the mount when I do a sudo run command. The files all show as owned by root. In the Plex container, the files are also owned by root, and the Plex user has not write access, but root does in the container. Looks like I need to get the Plex user in the container to have access to those files.
Thanks.
How did you lay out the config?Thanks for the help. I found I had to add to the CIFS config, to mount as uid=1001, and gid=1001. Then I created a new Plex container, adding environment variables to set the Ples UID and GID to 1001. Once I did this, Plex was able to write again to the share.
mounts: - - //192.168.2.10/AlphaData_GlobalShare - /media/AlphaData - cifs - vers=2.1 - username=spencer,password=xxxx,iocharset=utf8,_netdev - - //192.168.2.10/AlphaMedia_GlobalShare - /media/AlphaMedia - cifs - vers=2.1 - username=spencer,password=xxxx,iocharset=utf8,_netdev - - //192.168.2.10/VMRoot_GlobalShare - /media/VMRoot - cifs - vers=2.1 - username=spencer,password=xxxx,iocharset=utf8,_netdev
Sorry to ask this in a 6 page thread, but what is the *definitive way* to mount my data back from the RancherOS VM?
I believe both NFS and CIFS are viable?
(https://forums.freenas.org/index.ph...i-ombi-deluge-w-openvpn-pia-sickrage-more.91/ <- that guide uses CIFS)
I want to play with docker a little, I've got RancherOS 1.40 up and running with Portainer and one container just for testing. Surprisingly all of this was quite easy under FreeNAS 11.2 Beta 3 - really slowly getting there.
That mapping back to the main data is the tricky part, so I'd like to do it right.
mounts: - - //192.168.2.10/AlphaData_GlobalShare - /media/AlphaData - cifs - username=xxx,password=xxx,iocharset=utf8,vers=3.0,uid=xxx,gid=xxx,_netdev - - //192.168.2.10/AlphaMedia_GlobalShare - /media/AlphaMedia - cifs - username=xxx,password=xxx,iocharset=utf8,vers=3.0,uid=xxx,gid=xxx,_netdev - - //192.168.2.10/VMRoot_GlobalShare - /media/VMRoot - cifs - username=xxx,password=xxx,iocharset=utf8,vers=3.0,uid=xxx,gid=xxx,_netdev
sudo ros config merge -i mount.yaml
, the just restart RancherOS and go from there. You can find the config at /var/lib/rancher/conf/cloud-config.yml if you want to edit your mounts.Honestly not 100% sure about the viability of RancherOS in its current config for long term solutions, when they introduce proper support for the linux kernel in the 11.2 update id recommend just running an Ubuntu Server VM with docker installed on it, then just make a RancherOS container and Portainer container to manager your stuff. Way more stable and better for the long term tbhThanks, that's the data which was included in the guide I saw. I'll have a play with it.
I would assume if the RancherOS VM is ever replaced, that data is then lost?
https://redmine.ixsystems.com/issues/50236
I'm trying to nudge the developers to find a long term solution to RancherOS updates, I believe (?) many people are frustrated that the update process of the VM is quite destructive for all the stuff.
So that YAML file will need to be considered (if they actually find a long term solution to migrating from old to a new VM or upgrading the existing VM)
Thanks again for reply, I'll have a fiddle with CIFS patching back to my data.
Honestly not 100% sure about the viability of RancherOS in its current config for long term solutions, when they introduce proper support for the linux kernel in the 11.2 update id recommend just running an Ubuntu Server VM with docker installed on it, then just make a RancherOS container and Portainer container to manager your stuff. Way more stable and better for the long term tbh
How did you lay out the config?
Code:mounts: - - //192.168.2.10/AlphaData_GlobalShare - /media/AlphaData - cifs - vers=2.1 - username=spencer,password=xxxx,iocharset=utf8,_netdev - - //192.168.2.10/AlphaMedia_GlobalShare - /media/AlphaMedia - cifs - vers=2.1 - username=spencer,password=xxxx,iocharset=utf8,_netdev - - //192.168.2.10/VMRoot_GlobalShare - /media/VMRoot - cifs - vers=2.1 - username=spencer,password=xxxx,iocharset=utf8,_netdev
How did you add the UID and GID into the file
EXTRA_CMDLINE: /init mounts: - - //192.168.1.10/Descargas - /media/Descargas - cifs - username=multimedia,password=PASSWORD,iocharset=utf8,_netdev - - //192.168.1.10/Anime - /media/Anime - cifs - username=multimedia,password=PASSWORD,iocharset=utf8,_netdev - - //192.168.1.10/Series - /media/Series - cifs - username=multimedia,password=PASSWORD,iocharset=utf8,_netdev - - //192.168.1.10/Peliculas - /media/Peliculas - cifs - username=multimedia,password=PASSWORD,iocharset=utf8,_netdev rancher: environment: EXTRA_CMDLINE: /init network: dns: nameservers: - 1.1.1.1 - 192.168.1.1 interfaces: eth0: address: 192.168.1.11/16 dhcp: false gateway: 192.168.1.1 mtu: 1500 eth1: address: 192.168.1.12/16 dhcp: false gateway: 192.168.1.1 mtu: 1500 password: PASSWORD resize_device: /dev/sda services_include: open-vm-tools: true volume-cifs: true state: dev: LABEL=RANCHER_STATE wait: true ssh_authorized_keys: []
mounts: - - //192.168.0.9/data/backup/dockerconfigs/guacamole - /media/guacamole - cifs - username=USERXX,password=XXPASSXX,iocharset=utf8,_netdev - - //192.168.0.9/data/backup/dockerconfigs/mysql - /media/mysql - -cifs - username=USERXX,password=XXPASSXX,iocharset=utf8,_netdev
mounts: - - //192.168.1.201/video - /media/video - cifs - username=plex,password=password,iocharset=utf8,vers=2.1,uid=1000,gid=100,_netdev
Nov 21 13:12:53 rancher kernel: [ 32.802025] CIFS VFS: Error connecting to socket. Aborting operation. Nov 21 13:12:53 rancher kernel: [ 32.803079] CIFS VFS: cifs_mount failed w/return code = -115