FreeNAS Services Missing CIFS but has SMB

Status
Not open for further replies.

Thousandbuckle

Contributor
Joined
Jul 9, 2014
Messages
136
Hello all, I have been struggling to get permissions to work on my FreeNAS 9.10 box and I think I know why now. As you can see below in the image on the left CIFS is missing from the services list but it has SMB. This box I can not get Windows permission to work at all. The box on the right as you see has the CIFS service but no SMB and I can get Windows permissions to work just fine.

Why is the box on the left missing CIFS and why does it have SMB where the box on the right has CIFS but no SMB? I need the box on the left to work like the one of the right. Can I just reinstall FreeNAS and import the disks?

This box I can not get permissions to work. This box I can get permissions to work just fine.
FreeNAS box missing CIFS but has SMB FreeNAS box has CIFS but does not have SMB
FreeNAS-9.10.1-U1 (ff51a5d) FreeNAS-9.10-STABLE-201606270534 (dd17351)

upload_2016-10-11_21-17-27.png
upload_2016-10-11_21-17-34.png
 

Attachments

  • upload_2016-10-11_21-14-12.png
    upload_2016-10-11_21-14-12.png
    30 KB · Views: 477

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
They are the same thing, they just changed the name in the GUI. Your permission issues are from something else.

Sent from my Nexus 5X using Tapatalk
 

Thousandbuckle

Contributor
Joined
Jul 9, 2014
Messages
136
Okay, thanks for the information on the GUI name change. I was hoping I had found my problem.

Would a reinstall of FreeNAS from scratch reset any permission issues I would have or would there be some bad permissions left on the data set? If so how can I reset all permissions and share type on the data set?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Under sharing => windows(SMB) => select share => edit => check 'Apply Default Permissions' and click OK. This will set some kind of sane permissions on the dataset associated with that share. I'm assuming the permission type on your datasets is windows?
 

Thousandbuckle

Contributor
Joined
Jul 9, 2014
Messages
136
I think when I created the data set it was Unix by default and I then changed it to Windows. Would that cause a problem and if so is there a way to reset that flag in the data set?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
that is fine, windows permission on the dataset you are trying to share using cifs/smb is perfect. After you have set the apply default permission you can connect to the share using the owner and password associated with that user. Then you can use the windows gui to change permissions to what ever you want.
 

Thousandbuckle

Contributor
Joined
Jul 9, 2014
Messages
136
Okay, finally figured out the issue after weeks of banging my head. The top level data set was set to Unix where the lower data set I was sharing in the path to CIFS was Windows. Once I changed the top level data set to Windows, reset permissions and did a reboot it is now working like it should.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Okay, finally figured out the issue after weeks of banging my head. The top level data set was set to Unix where the lower data set I was sharing in the path to CIFS was Windows. Once I changed the top level data set to Windows, reset permissions and did a reboot it is now working like it should.
No. You should not modify the root dataset. You need to fix that. I hope you don't have any jails because you will need to rebuild all of them now.

Sent from my Nexus 5X using Tapatalk
 

Thousandbuckle

Contributor
Joined
Jul 9, 2014
Messages
136
So what I changed was the share type for the green shaded section called "data" from Unix to Windows. The CIFS share is pointing at the yellow shaded section called "data_pool" which has been Windows all along. Like I said for some reason changing the green "data" from Unix to Windows fixed my issue. It is not clear for me why changing the "data" from Unix to Windows affects the jails but why doesn't it also affect the "data_pool?


upload_2016-10-12_8-0-48.png
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Yep, you should never do that. Don't change the root dataset. Now you should really rebuild everything.

Sent from my Nexus 5X using Tapatalk
 

Thousandbuckle

Contributor
Joined
Jul 9, 2014
Messages
136
So why does the root data set have options for Unix, Windows, and Mac if it should always be Unix?

I am not running any jails on this box yet so can I just change it back or do you think the install is messed now? When you say rebuild everything what does that mean exactly, does it mean just a reinstall of the FreeNAS OS or does the data on the drives need to be wiped and redone?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
It has options because you can change it if you want. The problem is if you do it jails will be broken because you will apply permissions recursively at some point and you will break your jails. Feel free to keep it the way it is but in the long run its going to cause you problems.

You either have to remove the permissions which requires a couple cli commands or delete your data and start over.

Sent from my Nexus 5X using Tapatalk
 

Thousandbuckle

Contributor
Joined
Jul 9, 2014
Messages
136
Sorry but I want to be clear on what I HAVE to do. So my changing the root data set from Unix to Windows back to Unix should only affect any jails I had created and not any data in the data set I am sharing in CIFS? If that is the case then my data outside of the jails should be fine so why would I need to delete the data outside of the jail and start over?

Can I just delete the jail data set and let FreeNAS recreate it?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
OK, if it's working just leave it the way it is. Just know things will be funky and if you run into problems it's because of this.

Sent from my Nexus 5X using Tapatalk
 
Status
Not open for further replies.
Top