I've had multiple setbacks.

[TremorAcePV]

Hello,

I've gotten most of what I wanted set up in FreeNAS. This includes sharing media on my NAS via CIFS and MiniDLNA.

However, after attempting to set up SSH (which failed spectacularly), I can't access my shares anymore.

If I attempt to enable CIFS after messing with the options, it won't start. The same is true of SMART as well and I don't know why.

If I restart the system, it allows me to start CIFS but then if I stop it and mess with the settings, it requires another reboot to enable again.

I want to point out that the WORKGROUP name on my computer that I wish to access this on is TREMOR just like in the settings shown below.

CIFS settings:

CIFS Shares settings:

Global Configuration:

Any help is appreciated. I'm not sure what I broke by attempting to enable SSH. The guide isn't very helpful. Some things it's not clear about how to do, so it's possible I messed something up while doing that.

I checked my settings against the guide I followed by Lifehacker to get this started (which seemed very simple to do), but they are all the same, so I have no idea what the problem is.

If you need anymore info or screenshots, let me know.

Thanks,
Vitalius.

 

[jgreco]

You can get some additional clues by going to System->Settings->Advanced->Show console messages in the footer and set that. You will need to log out and then back in for it to take full effect. You can then observe those messages to watch for errors, and you can click on it to see an extended view.

Enabling ssh probably shouldn't break anything, and FreeNAS generally isn't that fragile, but it is sometimes possible to do odd things which then cause it to break. My guess is that maybe you did some general bit of network configuration that is not quite right.

 

[William Grzybowski]

What version are you running?

 

[TremorAcePV]

You can get some additional clues by going to System->Settings->Advanced->Show console messages in the footer and set that. You will need to log out and then back in for it to take full effect. You can then observe those messages to watch for errors, and you can click on it to see an extended view.

Enabling ssh probably shouldn't break anything, and FreeNAS generally isn't that fragile, but it is sometimes possible to do odd things which then cause it to break. My guess is that maybe you did some general bit of network configuration that is not quite right.

Will do.

My current networking setup is the following:

Router/Modem (bridged): 192.168.10.1
Forwarding corresponding ports (8200, 3689, and 9091) to FreeNAS system (not Jail). Is this right or should I forward the ports needed to Jail?
FreeNAS system: 192.168.10.98
FreeNAS Jail: 192.168.10.97
MiniDLNA port: 8200
Firefly port: 3689
Transmission port: 9091
My computer: 192.168.10.99

The domain name is freenas.com, but I'm not sure what or how that, the netBIOS, and the domain name work. All netBIOS names are freenas anywhere it appears and the host name is freenas everywhere except under System > System Information where it's freenas.freenas.com .

Workgroup is TREMOR on everything.

The plugins work fine (Firefly, MiniDLNA, and Transmission). I just can't see the drives via sharing.

I say me attempting to set up SSH broke it because it worked before I tried and I haven't changed anything else otherwise.

This is the console when I click CIFS to activate the service. The first time 07:03:42 comes up is the moment I click it.

What version are you running?

FreeNAS 8.3.1 with the latest versions of Jail, and all plugins.

 

[William Grzybowski]

Sounds like a bug with the service notification, possibly fixed in 9.X.

Despite the error in the GUI the samba should be starting, or try workaround it with "service samba onestart" in SSH.

 

[TremorAcePV]

Sounds like a bug with the service notification, possibly fixed in 9.X.

Despite the error in the GUI the samba should be starting, or try workaround it with "service samba onestart" in SSH.

Thank you for the help.

That's the thing, before I tried messing with it, my computer could access it as a network drive via \\192.168.10.97\fileserver

However, now I can't do that. I can't access the drive whether CIFS is on, or not.

I couldn't ever get SSH to work either. Now only the plugins work for connecting to the drive, and that only lets me access the media files (video, pictures, and music).

 

[William Grzybowski]

Is this a virtual machine?

 

[TremorAcePV]

Is this a virtual machine?

No. It's running on a dedicated system installed on a USB drive with 8GB of RAM (non-ECC but that will soon be fixed) using ZFS.

This is the console when I have rebooted it and turned CIFS on. Starting at 07:23:26,

 

[William Grzybowski]

After:

# service samba onestart

Can you see smbd process running?

# ps auxww|grep smbd

 

[TremorAcePV]

After:

# service samba onestart

Can you see smbd process running?

# ps auxww|grep smbd

Yes, I can. After entering the first line, it started the process and entering the second line showed the process was running.

Image of what came up:

 

[William Grzybowski]

No, it is not running, its just the grep process.

Check /var/log/messages and /var/log/sm* for errors.

 

[TremorAcePV]

No, it is not running, its just the grep process.

Check /var/log/messages and /var/log/sm* for errors.

I need to research this more.

How do I check those? I assume I use shell?

 

[gpsguy]

Yes.

How do I check those? I assume I use shell?

There are a number of ways you could view the files. The easiest for you, might be cat.

cat /var/log/messages | more

ls -l /var/log/sm* [directory listing of sm* files, and use them with cat too]