FreeNAS setup help?
-
@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. -
@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
-
@thecreativeone91 said:
I'd look at GlusterFS on centos over freenas
If building a cluster, definitely.
-
@thecreativeone91 said:
I like FreeBSD myself.
I love it, just not for storage tasks generally. It's its one major architectural weak point.
-
@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".
-
@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.
-
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.
-
@coliver Where do I find the Log?
-
Should be /var/log/daemon.log
-
@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.
-
@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.
-
@scottalanmiller Good to know.
-
@scottalanmiller None of those work. They actually do nothing but bring up the main page again.
-
-
if you do this we can see all of the available logs...
ls /var/log -
@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.
-
@Mike-Ralston said:
@scottalanmiller Doesn't work. Neither the virtualized WebUI console, nor the physical server, accept any commands.
Well that's another issue altogether. Maybe you need a working OS before trying to get the apps on top of it running
This is like telling your mechanic that something is wrong and you can't get to the store when you know that the issue is that the garage door hasn't been opened yet. Let's get the garage door open before we look at the car, the car might run just fine.What is a virtualized WebUI console? You have two FreeNAS devices, one virtual and one physical?
