SMB CIFS Shares Broken in RancherOS After 11.2 Upgrade

[Yusuf Limalia]

Hello there!

After upgrading to FreeNAS11.2 my SMB Shares from RancherOS weren't working.

Narrowed down the problem to FreeNAS 11.2 requiring a minimum of SMB version 2.

So if I run the command:

Code:

mount -t cifs "//192.168.0.250/Videos" -o username=someusername,password=somepassword,vers=3\.0 /media/videos

The share mounts nicely and all's good in the world.
However the storage doesn't persist on reboot.

The way to persist storage is to create a yaml file:

Code:

mounts:
- - //192.168.0.250/Videos
  - /media/videos
  - cifs
  - username=someusername,password=somepassword,vers=3.0

Then merge with the config:

Code:

sudo ros config merge -i mount.yaml

Then reboot.

This used to work before (Minus the vers=3.0 option) just fine.
But now this doesn't work.

I'm guessing something is wrong with the way i'm adding the SMB version number in my mount file.

Hopefully one of the clever people can point me in the right direction :)

Thanks in Advance!

 

[KrisBee]

Try changing your mount.yaml file to:

Code:

runcmd:
    - sudo mount -t cifs "//192.168.0.250/Videos" -o username=someusername,password=somepassword,vers=3.0 /media/videos

 

[Pseudolife]

I just updated to 11.2 today, and my existing Rancher OS install (on an old desktop tower not a VM in FreeNAS) is also now failing to automatically connect to the network shares it once consistently connected to under 9.10.

Unfortunately I don't think KrisBee's fix is working for me. I have a sudo mount command that works fine from the SSH line, but if I put that exact same command into runcmd like KrisBee said, the network share isn't available on reboot. I've just done "ros config export", and I can confirm the command is there, so I'm a bit confused.

 

[KrisBee]

@Pseudolife Does using vers=2.1 in your rancheros yaml file make a difference? And/or does adding the auxiliary parameter server min protocol=NT1 to Services->SMB on FreeNAS make a difference?

 

[Pseudolife]

Does using vers=2.1 in your rancheros yaml file make a difference? And/or does adding the auxiliary parameter server min protocol=NT1 to Services->SMB on FreeNAS make a difference?

I just tried setting vers=2.1 in both the runcmd and then mounts sections of the yaml and they didn't help. I then tried putting the yaml back to how it was (mounts) and tried adding the aux parameter to SMB service in FreeNAS and that sadly didn't seem to solve it either.

By the way, I do appreciate you trying to help.

 

[Pseudolife]

I also just tried setting minimum SMB version to 1 and 2 in FreeNAS. Setting it to 1 prevented the service from starting. Setting it to 2 didn't fix anything, even if I set the vers=2.1 in the yaml file on the RancherOS side.

I'm still confused I can connect from the shell, or ssh, but not getting it to work at start up.

 

[dir_d]

I had the same issues and never got them resolved. I added 3.0 and got it to work a couple times manually but never auto through the .yaml file. I always got the error that it was trying to connect and was timing out. I scraped RancherOS since i was only using it for Radarr and Sonarr and used the plugins instead.

 

[KrisBee]

@Pseudolife I'm guilty of not reading your first post carefully. As you're not running rancheros as a Vm on FreeNAS, have you upgraded rancheros to the latest version? ( See: https://rancher.com/docs/os/v1.2/en/upgrading/ )

 

[Pseudolife]

I updated to the latest version Rancher a few week weeks ago, well before I did the FreeNAS upgrade. There were no problems with the system mounting network shares from freenas 9.10.

As a temporary work around, at the moment I've all the docker containers that require access to the network shares set to not start automatically, and I made a bash script I can run quickly to mount all the network drives.

I did try setting the yaml/config to run that bash script at start-up but that also failed to work.