CPU Selection for a first timer

[Dood]

I'm in the process of building my first FreeNAS build and trying to come up the final hardware shopping list before I put money down. I live in Australia so items do cost more and don't have as a wide selection. While realising that server components do cost more than consumer, Im am trying to keep the costs down as much as possible without sacrificing reliability.

The NAS will be used for file storage though CIFS and NFS to Windows, a Mac and XBMC on a Raspberry Pi. Also wanted to be able to run SABNZBd+ and OpenCloud. There is no need for encryption or transcoding.

So far I have sorted out the following:
Supermicro - X10SLM-F
Intel - Pentium G3420
Samsung - M391B1G73BH0-CK0 - 2x 8GB The only Ram I have found listed as compatible from SuperMicro.
Western Digital Red Drives 4TB x 6 - Raid Z2
Antec - TPC-450 Power Supply. Tried to find a device that was Gold certified and around the 500W mark.
All of this will be placed into a Xigma Gigas case.

The main thing I am looking at is whether the Pentium would be enough to run everything or should I move upto a i3 4310?

http://www.scorptec.com.au/product/CPU/Intel_Socket_1150/51370-BX80646I34130

 

[Yatti420]

PSU is a little steep.. CPU is fine..

 

[cyberjock]

Just as a warning mixing CIFS and NFS with the same files is a recipe for data corruption. Files should be shared by one or the other.. not both.

 

[joelmusicman]

My G3220 runs all of the above (almost exactly!) just fine. Note that Raspbmc can access CIFS shares just fine. I also run AFP for Time Machine. The only thing I wasn't satisfied with was Plex transcoding.

 

[cyberjock]

My G3220 runs all of the above (almost exactly!) just fine. Note that Raspbmc can access CIFS shares just fine. I also run AFP for Time Machine. The only thing I wasn't satisfied with was Plex transcoding.

And you are taking that risk.. we mention that mixing of protocols isn't recommended. There's plenty of people who do it and then one day they wonder why 1/2 their movie library is corrupt and unplayable. Or why whole directories are just missing.

You're welcome to do what you feel is best with your data. It's been discussed many times that mixing and matching protocols is a bad idea. I'm simply trying to prevent someone else from learning this lesson the hard way.

From the manual:

NOTE:
while the GUI will let you do it, it is a bad idea to share the same volume or dataset using multiple types of access methods. Different types of shares and services use different file locking methods. For example, if the same volume is configured to use both NFS and FTP, NFS will lock a file for editing by an NFS user, but a FTP user can simultaneously edit or delete that file. This will result in lost edits and confused users. Another example: if a volume is configured for both AFP and CIFS, Windows users may be confused by the extra filenames used by Mac files and delete the ones they don't understand; this will corrupt the files on the AFP share. Pick the one type of share or service that makes the most sense for the types of clients that will access that volume, and configure that volume for that one type of share or service. If you need to support multiple types of shares, divide the volume into datasets and use one dataset per share.

But hey, feel free to ignore the manual warnings. It doesn't affect *my* data. We put the warnings in there, but we can't force you to obey them.

 

[Yatti420]

And you are taking that risk.. we mention that mixing of protocols isn't recommended. There's plenty of people who do it and then one day they wonder why 1/2 their movie library is corrupt and unplayable. Or why whole directories are just missing.

You're welcome to do what you feel is best with your data. It's been discussed many times that mixing and matching protocols is a bad idea. I'm simply trying to prevent someone else from learning this lesson the hard way.

I just made my NFS shares read-only again.. Just in case.. I doubt it will protect me in all cases but better then nothing.. I forgot why I had NFS read-only.. I typically only use one or the other at one time.. I want to serve as many protocols as I can..:( I'll use CIFS for doing any graphical changes..

 

[cyberjock]

Yatti420:

You should know better! You've told a few people to RTFM.. you not do it yourself? /shame

 

[joelmusicman]

And you are taking that risk.. we mention that mixing of protocols isn't recommended. There's plenty of people who do it and then one day they wonder why 1/2 their movie library is corrupt and unplayable. Or why whole directories are just missing.

You're welcome to do what you feel is best with your data. It's been discussed many times that mixing and matching protocols is a bad idea. I'm simply trying to prevent someone else from learning this lesson the hard way.

That's good to know. I had my CIFS share to the root of the zpool, and the AFP share pointed at the time machine folder which was listed as an exclusion in the CIFS settings so Windows doesn't see them along with some of the other datasets. I'll be sure to make a new folder for CIFS and migrate the data over...

 

[Yatti420]

I "Use" to have NFS set as read only.. I must of been changing something.. I've been the only user for last little while so not overly concerned.. I can see it now though with a few hundred users accessing the same files with different protocols.. Can't do good things.. Alot of clients support UPNP so I can always fire up the minidlna plugin..