- Joined
- Feb 21, 2008
- Location
- Baltimore, MD
So recently my computer builds and tweaking have been taking more of my interest lately. I was out of the loop (pun intended) for a little while, but after building my most recent gaming rig I wanted to do more.
I started with a Synology DS416 NAS and 4x2TB drives courtesy of cw. NAS setup was a breeze and I got my data transferred to it. It's a fairly low powered device with only a slow dual core, and 1GB of ram, but it's plenty for running the NAS itself. I briefly tried using the NAS itself as a Plex server, as I had the option to install the App, but it was woefully underpowered for anything but direct playback (no transcoding).
I had enough parts left over from my old computer that weren't really selling, so I decided to put them to use and build a nice-ish Plex server.
Parts:
Case: Antec Fusion Remote (mATX)
MB: Gigabyte GA-B85M-DS3H-A (mATX)
CPU: Intel Xeon E3-1231v3 (3.4GHz quad w/HT)
CPU cooler: Scythe Ninja-mini (running passive)
GPU: EVGA GT430
Storage: old WD blue 640GB just for the OS for now. I plan to swap it with an SSD when i find a cheapo one
OS: Win 7 Ultimate 64-bit (old copy I had lying around)
misc: cheapo SYBA dual RTL8111 gigabit NIC pcie x1
pics:
About the passive cooler. I did this for nothing else other than noise, and I believe the proximity of the 120mm case fans is sufficient to keep it cool enough. As a totally unrealistic test, I ran Prime 95 v29.3 (AVX enabled) and let it run for about 10 mins. Max temp was 89C; quite hot, but in limits. in real world loads sending files and transcoding, I've not seen the CPU over 65C. Since the case only has 2x120mm 1200rpms fans, it's very quiet. i only hear the HDD activity sometimes (which will go away when i swap it for an SSD).
About the NIC. This MB only has one gigabit port, and part of me felt it was stupid for the server to pull data from the NAS over the network, then send it back out over the network via the same port to the requested client. Maybe in real practice it won't matter and wouldn't be a bottle neck, but I feel it would just be cleaner if the server could grab data from the NAS directly, more like it was an attached HDD. Since the NAS has 2 gigabit ports, and this NIC has 2 ports, so i thought i could double the bandwidth by connecting both NAS and server directly with 2 ethernet cords (direct connection, no switch or router). The plan was to have a 2Gbps link between NAS<->server, then have the server send out data to whatever client wanted it. I couldn't quite get this to work properly. I was able to successfully get the 2 ports on the NIC bridged together, set a static IP route (different host than the main network, 192.168.2.xx0), and set the NAS ports to be bonded, also on the same different host, static IP (192.168.2.xx1). I could transfer data between them, BUT i was still limited to 1Gbps, it wouldn't go faster, from a quick google search it seemed to be a Windows 7 limitation, or maybe else. AND since Windows can't re-share and existing network share, no other computers on my network could access the NAS.
So I came up with a hybrid setup. I set static routes on the NAS for each port, but on separate hosts (192.168.1.xxx and 192.168.2.xxx). I set a static route to the server NIC connected to the NAS on the same 192.168.2.xxx, and a static route to the MB-NIC for 192.168.1.xxx. I then setup a mapped network drive pointing to the NAS defined by IP @ 192.168.2.xxx. And i configured the Plex Server to look for media on that mapped drive letter. This way when a file requested for playback by a Plex client, it gets pulled from the NAS directly, and set out over a different port. the router is also hooked to the other port on the NAS (the 192.168.1.xxx one) so any other client can access the NAS directly for regular fire transfers/backups/whatever.
connected this way:
"home network"<==(192.168.1.xxx)==>[NAS]<==(192.168.2.xxx)==>[PlexServer]<==(192.168.1.xxx)==>"home network"
after getting everything to work, I made the server full headless (as seen in the pics) and I just RDP into it for any configuration or tweaking I may need.
questions comments welcome! this is my first time setting up a real server like this so I'm quite noob with all this networking stuff. But I try to make up for it with decent Google-fu.
Thanks!
I started with a Synology DS416 NAS and 4x2TB drives courtesy of cw. NAS setup was a breeze and I got my data transferred to it. It's a fairly low powered device with only a slow dual core, and 1GB of ram, but it's plenty for running the NAS itself. I briefly tried using the NAS itself as a Plex server, as I had the option to install the App, but it was woefully underpowered for anything but direct playback (no transcoding).
I had enough parts left over from my old computer that weren't really selling, so I decided to put them to use and build a nice-ish Plex server.
Parts:
Case: Antec Fusion Remote (mATX)
MB: Gigabyte GA-B85M-DS3H-A (mATX)
CPU: Intel Xeon E3-1231v3 (3.4GHz quad w/HT)
CPU cooler: Scythe Ninja-mini (running passive)
GPU: EVGA GT430
Storage: old WD blue 640GB just for the OS for now. I plan to swap it with an SSD when i find a cheapo one
OS: Win 7 Ultimate 64-bit (old copy I had lying around)
misc: cheapo SYBA dual RTL8111 gigabit NIC pcie x1
pics:
About the passive cooler. I did this for nothing else other than noise, and I believe the proximity of the 120mm case fans is sufficient to keep it cool enough. As a totally unrealistic test, I ran Prime 95 v29.3 (AVX enabled) and let it run for about 10 mins. Max temp was 89C; quite hot, but in limits. in real world loads sending files and transcoding, I've not seen the CPU over 65C. Since the case only has 2x120mm 1200rpms fans, it's very quiet. i only hear the HDD activity sometimes (which will go away when i swap it for an SSD).
About the NIC. This MB only has one gigabit port, and part of me felt it was stupid for the server to pull data from the NAS over the network, then send it back out over the network via the same port to the requested client. Maybe in real practice it won't matter and wouldn't be a bottle neck, but I feel it would just be cleaner if the server could grab data from the NAS directly, more like it was an attached HDD. Since the NAS has 2 gigabit ports, and this NIC has 2 ports, so i thought i could double the bandwidth by connecting both NAS and server directly with 2 ethernet cords (direct connection, no switch or router). The plan was to have a 2Gbps link between NAS<->server, then have the server send out data to whatever client wanted it. I couldn't quite get this to work properly. I was able to successfully get the 2 ports on the NIC bridged together, set a static IP route (different host than the main network, 192.168.2.xx0), and set the NAS ports to be bonded, also on the same different host, static IP (192.168.2.xx1). I could transfer data between them, BUT i was still limited to 1Gbps, it wouldn't go faster, from a quick google search it seemed to be a Windows 7 limitation, or maybe else. AND since Windows can't re-share and existing network share, no other computers on my network could access the NAS.
So I came up with a hybrid setup. I set static routes on the NAS for each port, but on separate hosts (192.168.1.xxx and 192.168.2.xxx). I set a static route to the server NIC connected to the NAS on the same 192.168.2.xxx, and a static route to the MB-NIC for 192.168.1.xxx. I then setup a mapped network drive pointing to the NAS defined by IP @ 192.168.2.xxx. And i configured the Plex Server to look for media on that mapped drive letter. This way when a file requested for playback by a Plex client, it gets pulled from the NAS directly, and set out over a different port. the router is also hooked to the other port on the NAS (the 192.168.1.xxx one) so any other client can access the NAS directly for regular fire transfers/backups/whatever.
connected this way:
"home network"<==(192.168.1.xxx)==>[NAS]<==(192.168.2.xxx)==>[PlexServer]<==(192.168.1.xxx)==>"home network"
after getting everything to work, I made the server full headless (as seen in the pics) and I just RDP into it for any configuration or tweaking I may need.
questions comments welcome! this is my first time setting up a real server like this so I'm quite noob with all this networking stuff. But I try to make up for it with decent Google-fu.
Thanks!