FreeNAS setup help?

scottalanmiller

A big advantage to using Linux or FreeBSD directly is that the experience equates directly to something very useful for IT in general. Using FreeNAS doesn't really train you on business gear so you don't get the personal enrichment value that a project like this can bring.

Mike Ralston

@scottalanmiller
It's another type of system I can work with, so I'll figure out what I did wrong with this one, and then do the other.

scottalanmiller

@Mike-Ralston said:

It's another type of system I can work with, so I'll figure out what I did wrong with this one, and then do the other.

Sure, all learning is good learning. Some is more efficient though. If you want to learn the most, do straight FreeBSD and then OpenSuse.

I like FreeBSD myself. Never used FreeNAS in a buinsess environment. If you are going with something that simple it usually will end up being just a windows file server based NAS.

I'd look at GlusterFS on centos over freenas

scottalanmiller

@thecreativeone91 said:

I'd look at GlusterFS on centos over freenas

If building a cluster, definitely.

scottalanmiller

@thecreativeone91 said:

I like FreeBSD myself.

I love it, just not for storage tasks generally. It's its one major architectural weak point.

Mike Ralston

@coliver said:

I'm sure you've already seen this post but it may help to double-check your work:
https://forums.freenas.org/index.php?threads/cifs-windows-sharing-guide.20948/

I followed all of these steps, and everything looks to be set up properly, except, I can't enable the CIFS service, and it doesn't tell me why. It just says "This Service Could Not Be Started".

coliver

@Mike-Ralston said:

@coliver said:

I'm sure you've already seen this post but it may help to double-check your work:
https://forums.freenas.org/index.php?threads/cifs-windows-sharing-guide.20948/

I followed all of these steps, and everything looks to be set up properly, except, I can't enable the CIFS service, and it doesn't tell me why. It just says "This Service Could Not Be Started".

If I remember correctly that means that something is wrong with your config file. I haven't worked with CIFS shares on Linux in a while... Can you look into the log and see if there is an issue there? Generally it says the line number an error occurred on.

scottalanmiller

Ah, well that's a huge step. That the service isn't started means that there is no reason to be looking at firewalls and such. There is something wrong with the service.

We need to look a the logs and see what errors are being recorded.

Mike Ralston

@coliver Where do I find the Log?

scottalanmiller

Should be /var/log/daemon.log

coliver

@Mike-Ralston said:

@coliver Where do I find the Log?

I'm not sure with FreeBSD or FreeNAS. Generally it is in something like /var/log/messages. Although that may be different on this server.

scottalanmiller

@coliver said:

I'm not sure with FreeBSD or FreeNAS. Generally it is in something like /var/log/messages. Although that may be different on this server.

/var/log/messages is RHEL only.

coliver

@scottalanmiller Good to know.

Mike Ralston

@scottalanmiller None of those work. They actually do nothing but bring up the main page again.

scottalanmiller

@coliver said:

@scottalanmiller Good to know.

Even Ubuntu uses something different.

scottalanmiller

if you do this we can see all of the available logs...

ls /var/log

Mike Ralston

@scottalanmiller Doesn't work. Neither the virtualized WebUI console, nor the physical server, accept any commands.

All the logs are under /var/log but they are stored in memory and not preseistant. You need a syslog server if you want them presistant.