Building a low cost NAS/file server

[mgdelhi]

Thank you for your suggestion guys.

The updated is, CAT6 wiring has been done in the house.

I installed OpenMediaVault as my NAS software with very useful suggestions and help of forum member dheerajjotwani.

I copied some sample data on HDD (1GB - 32GB rips). BR-ISOs played fine on HTPC and PCH C200. whereas Xtreamer and Raspberry Pi (100 mbps LAN port) play fine till 12GB Rips (Dont have anything in between - either 12GB rip or BR-ISOs).

I will check the functionality/reliability of OpenMediaVault for next few days and once satisfied, I will copy all my data to it.

 

[Thad E Ginathom]

Good, glad you've settled on something ...now don't forget your out-of-the-house backup

 

[mgdelhi]

Good, glad you've settled on something ...now don't forget your out-of-the-house backup

I have been doing that since last 3-4 years. hyeah:

 

[Thad E Ginathom]

:lol:

So have I. The next lesson I had to learn was keep it up to date!

 

[sam9s]

Thank you for your suggestion guys.

The updated is, CAT6 wiring has been done in the house.

I installed OpenMediaVault as my NAS software with very useful suggestions and help of forum member dheerajjotwani.

Mmmmmm well I guess u missed my this post on the second page.....

I would also like you to consider .....

1. recently I cam across this supposedly good NAS OS NAS4FREE ... this is not freenas as most of us get confused, but its has the same history. You can try if you like the interface, speed etc. Else FreeNAS is always there. YOu can reuse the drives you create on NAS4Free on freeNAS as both use the same architecture.
FreeNAS 8 I have heard is much more polished and "media" oriented than earlier versions .....
2. Another one is AMAHI
3. Last one is Open Media Vault OVM

 

[mgdelhi]

Mmmmmm well I guess u missed my this post on the second page.....

Oops. so sorry. I read it and forgot to mention. Actually I took a pause of 2-3 days and then Dheeraj sent me links to download and configure OMV. I did it while chatting with him on G-Talk.

Nevertheless, it was your NAS thread which started it all. :clapping:

 

[mowgli80]

Excellent choice OMV. The backend being Debian, it gives you lots of stability and flexibility. I have few suggestions.

1) Do not run a 24x7 download client on your NAS. Constantly spinning disks can lead to early failure. I would suggest a separate cheap computer like RPi running linux + transmission connected to a cheap USB disk as temporary download storage. You can then copy the data to your NAS, which means you only spin up the disks when you actually want to use the NAS. It also enables you to keep your NAS mostly off as suggested in next suggestion. It looks like your router is supported by ddwrt. You can use it as your download rig. I am using mine (asus n16 + debwrt(debian) + transmission) and it works very well .

2) Lot of FMs are running time based NAS. I would suggest exploring "wake on lan" to start the NAS only when you intend to use the data. Latest XBMC from GIT gives you an option to wake your NAS for remote drives using WOL on first access. Other media players may offer similar options. I also have a script running on boot on my Ubuntu based NAS which suspends (sleeps) the NAS if my media clients are not up. I have been using this setup for the past 4+ years and it just works . All in all, the NAS is on only for the period I want to use it which reduces disk failures as well as reduces power consumption. If you want, I can share that script. It should be compatible with Debian as well.

3) If you are willing to learn, I would suggest you go for RAID based setup. I read that you have multiple backups of your data. The problem with backup is keeping it in sync with your current data. In most cases, backup will NOT give you your complete data back because the latest data was not synced . Parity based RAID will ensure you can recover to the latest data copy in case of disk failure and allow you to sync your backup copy for future failures . If you use striping in your RAID, it will also give you better disk IO performance. Some hardware based RAID can also protect against "Bit Rot" aka silent corruption, but that is an expensive proposition. You can also explore ZFS if bit rot is a concern for the audiophile in you.

4) Do not run lots of media services (UPNP, DLNA etc.) on your NAS if you do not plan to use it. A NAS works best with KISS (Keep It Simple Stupid) philosophy. The more software you use, more points of failure there are.

 

[dheerajjotwani]

Excellent choice OMV. The backend being Debian, it gives you lots of stability and flexibility. I have few suggestions.

1) Do not run a 24x7 download client on your NAS. Constantly spinning disks can lead to early failure. I would suggest a separate cheap computer like RPi running linux + transmission connected to a cheap USB disk as temporary download storage. You can then copy the data to your NAS, which means you only spin up the disks when you actually want to use the NAS. It also enables you to keep your NAS mostly off as suggested in next suggestion. It looks like your router is supported by ddwrt. You can use it as your download rig. I am using mine (asus n16 + debwrt(debian) + transmission) and it works very well .

2) Lot of FMs are running time based NAS. I would suggest exploring "wake on lan" to start the NAS only when you intend to use the data. Latest XBMC from GIT gives you an option to wake your NAS for remote drives using WOL on first access. Other media players may offer similar options. I also have a script running on boot on my Ubuntu based NAS which suspends (sleeps) the NAS if my media clients are not up. I have been using this setup for the past 4+ years and it just works . All in all, the NAS is on only for the period I want to use it which reduces disk failures as well as reduces power consumption. If you want, I can share that script. It should be compatible with Debian as well.

3) If you are willing to learn, I would suggest you go for RAID based setup. I read that you have multiple backups of your data. The problem with backup is keeping it in sync with your current data. In most cases, backup will NOT give you your complete data back because the latest data was not synced . Parity based RAID will ensure you can recover to the latest data copy in case of disk failure and help you sync your backup copy to future failures . If you use striping in your RAID, it will also give you better disk IO performance. Some hardware based RAID can also protect against "Bit Rot" aka silent corruption, but that is an expensive proposition. You can also explore ZFS if bit rot is a concern for the audiophile in you.

4) Do not run lots of media services (UPNP, DLNA etc.) on your NAS if you do not plan to use it. A NAS works best with KISS (Keep It Simple Stupid) philosophy. The more software you use, more points of failure there are.

couldnt agree more. i run a simple setup in ubuntu but without raid. i would love to share notes with you since i can schedule a suspend on the comp but wol using dd-wrt only works within 5 secs of the machine going down. else it doesnt wake up.

the suspend command me using is
halt -p

and i made a simple cron entry in dd-wrt to wake up the nas every morning 11.30 but to no avail. can i urge you to help... would be great if you could share your suspend script too. i normally let it go to sleep around 3am but your idea of use based suspend is super !!! i am a noob with linux but its a great learning experience !!

 

[mowgli80]

@Dheeraj - You can try these steps
1) Follow one of the guides (first two steps) to enable wol on ubuntu.

2) "halt -p" will shutdown the system. You can use "pm-suspend" to make the system go to sleep mode. When WOL packet arrives, it will instantly start the system and there is no need to go through boot sequence.

3) I used the following command on my dd-wrt automation and it used to wake up my ubuntu NAS so should work for you - "/usr/sbin/wol -i 192.168.1.255 -p 9 <mac addr>". Change "192.168.1" based on your DHCP server settings. You can get your mac addr from ifconfig command on ubuntu.

This should get your current time based setup running. PM me your mail id and I will send you the suspend script in couple of days after cleaning it up a bit. However, from your sig, looks like your HTPC and NAS are the same. Not sure how the script will help you. In my case, the HTPC and NAS are different. My HTPC will wake up NAS with WOL. Once HTPC goes to sleep when I am not using it, the NAS will go to sleep as well.

 

[dheerajjotwani]

Thanks. I enabled wol with the ethtool and can successfully use wol through ddwrt provided I do it within 5 seconds of the halt -p. I altered lan to remain on in the halt config.

My mail id is my username here at gmail. If we could disxuss this over gtalk in your free time...

Currently not using xbmc from nas. Using a zotac id61 as a htpc plus the sqzbx so I guess thats not a concern...

tapped on Note II cdma

 

[dheerajjotwani]

thanks @mowgli80 for the insight and time. WOL and scheduled power down successfully implemented !!!! cheers Chirag !

 

[mgdelhi]

Ok guys, need to ask something.

I have six wires coming to my router and I have only four ports. Now since my home is fully wire-networked, I don't need a dual band / high end router. I have been using a TP-LINK TD-W8960N Wifi Modem Router (300 mbps wifi, 100 mbps LAN) which has very good range.

Now I have 2 options. Please see.

Please suggest which option should I choose. I prefer option 1 because of 2 devices instead of 3 means less clutter and less expensive (can give/sell dual band router to a friend). I understand, that with option 1, my wifi devices will connect only at 100 mbps with wired devices and I am OK with that becuase only Wifi devices are mobiles and laptop and I don't watch movies on them.

Also suggest if there is a better option than these two options.

Edit: I have already placed order for a TP-Link TL-SG1008D 8-Port Gigabit Desktop Switch which can be cancelled anytime before dispatch (if required) and TP-Link TL-SG1005D 5-Port Gigabit Desktop Switch (or any other switch) can be bought freshly.

 

[sam9s]

I prefer second option, simply for the fact that I do not like the idea of Router cum Modem, I like to keep things separate. In my case its like this ...

Airtel Broadband ===> D-link ADSL Modem ===> E2000 Linksys Gigabit router ===> Netgear 8 Port Gigabit Switch

E2000 LInksys ::::::: ====== >

Via LAN ..... >

1. WD TV LIve
2. HTPC
3. Synology NAS
4. To --- > Switch

via Wifi n ..... >

1. Thinkpad L420
2. HTC One
3. iPhone 4S
4. Nexus 7


Netgear 8 Port Switch ::::::: ====== >

1. RaspPi running LMS
2. i7 Desktop
3. ip Surveillance Camera
4. Old Laptop used as Radio Station Server
5. Unused
6. Unused
7. Unused

 

[Thad E Ginathom]

I prefer second option, simply for the fact that I do not like the idea of Router cum Modem, I like to keep things separate.

I don't mind at all. Currently I do have them separate, using Airtel's Betel Modem.

I don't know the current cost of these boxes. Wouldn't a Gigabyte wireless router be rather expensive? Anyway, you already have a wireless router, so, if I were you, I would not buy another one. I'm guessing you already have a Betel modem too.

Basically, I'd go for option 1... but I could easily go for another option using the betel modem, the 8-port switch, the W8960N just for wireless... My permutation would probably depend on which modem worked best. My airtel line is not so good that it doesn't make a difference.

Given that you are dealing with rather more bandwidth on your lan than you should ever need, it's academic, but in option 2, I'd connect the HTPC to the switch, not to the router. Let every path go through the minimum number of piece of equipment when communicating with another device on the LAN. Academic ...but neater.

 

[haisaikat]

I'd connect the HTPC to the switch, not to the router. Let every path go through the minimum number of piece of equipment when communicating with another device on the LAN. Academic ...but neater.

This might be subjective depending on how you plan to use the NAS and HTPC combo.

If they are not on the same network segment I have seen issues with autodiscovery of UPnP (although not everyone would be using it) no matter how hard you implement port forwarding

Also if the NAS is going to be used as nightly download setup then it makes sense to place it with the router to avoid keeping the switch on additionally.

I would suggest that if the switch has not yet been purchased, better buy a 4 port wired router and connect the file servers / NAS with that directly via gigabit lan along with HTPC and keep the wifi as a child of the main wired router. so that for downloading options and normal surfing you do not unnecessary share your wifi. Turn wifi on only when needed

 

[Thad E Ginathom]

I would keep everything on the the same net segment anyway, eg do not connect LAN socket on Modem to WAN socket on router if using separate modem/router --- connect it to one of router LAN ports. The "router" is not routing: it is just being a switch and wifi access point. If wifi not needed, no need at all for this box!

Doing it the other way requires a knowledge of network addressing that, although only basic, is something that most broadband users who have no idea what "168.0.0.1" actually represents will not have.

(I used to do it. For fun. I had a 10.something net between modem and router, and a 192.something net on the other side of the router. Then, one re-configuration day I gave it all up in the name of simplicity. A pro net guy, in a similar conversation on another forum, approved the simple way, adding that the two-net method passes everything through NAT twice and KIS was the way to go)

If security is an issue, that's another matter, and one that, ten-plus years out of the office, I'm not really qualified to comment on.

(By the way: on a two-box-modem/router setup, beware of having two DHCP servers active. It will probably be turned on on both by default. Make sure to turn it off on at least one or some quite unpleasant things can happen)

 

[argho]

I would keep everything on the the same net segment anyway, eg do not connect LAN socket on Modem to WAN socket on router if using separate modem/router --- connect it to one of router LAN ports. The "router" is not routing: it is just being a switch and wifi access point. If wifi not needed, no need at all for this box!

Doing it the other way requires a knowledge of network addressing that, although only basic, is something that most broadband users who have no idea what "168.0.0.1" actually represents will not have.

(I used to do it. For fun. I had a 10.something net between modem and router, and a 192.something net on the other side of the router. Then, one re-configuration day I gave it all up in the name of simplicity. A pro net guy, in a similar conversation on another forum, approved the simple way, adding that the two-net method passes everything through NAT twice and KIS was the way to go)

If security is an issue, that's another matter, and one that, ten-plus years out of the office, I'm not really qualified to comment on.

(By the way: on a two-box-modem/router setup, beware of having two DHCP servers active. It will probably be turned on on both by default. Make sure to turn it off on at least one or some quite unpleasant things can happen)

Thad,

Could you pls explain in simple terms what you would reccomend as a setup, if one needs more than 4 LAN ports.

I use a Beetel DSL modem, and a Linksys Wi-fi Router. I have used up all the ports on the router. Its a very old one, and I was planning to replace it with a router with more than 4 ports. The only one I found, is :
WD My Net N900 HD Dual-Band - WD: Flipkart.com

Its expensive, but reviews are good.

What would be your reccomendation for a simple but effective setup ?

Rgds...Argho

 

[haisaikat]

(By the way: on a two-box-modem/router setup, beware of having two DHCP servers active. It will probably be turned on on both by default. Make sure to turn it off on at least one or some quite unpleasant things can happen)

I have dhcp turned on it both and that is not a problem as long as two boxes are having separate LAN segment and one does not see other which is usually the case if you have a router as a client of the main modem.

But I do understand your point on simplicity just like I have nightmares about using a Linux device

 

[indialogue]

Do not run a 24x7 download client on your NAS. Constantly spinning disks can lead to early failure. I would suggest a separate cheap computer like RPi running linux + transmission connected to a cheap USB disk as temporary download storage.

You can then copy the data to your NAS, which means you only spin up the disks when you actually want to use the NAS. It also enables you to keep your NAS mostly off as suggested in next suggestion. It looks like your router is supported by ddwrt. You can use it as your download rig. I am using mine (asus n16 + debwrt(debian) + transmission) and it works very well .

You've made some really good suggestions - thanks! What you've stated is really accurate for one-time downloaders - that is download and stop seeding after a day or immediately. Lately, more and more private trackers are moving to very strict seeding policies and ratio policing - even a day off from seeding can result in a noticeable hit in ratios!! If people are into heavy downloading and need to use private trackers (like I do for music), then looking into seedbox solutions might be a better idea than having a home-based torrenting system

 

[josephjohnt]

Thad,

Could you pls explain in simple terms what you would reccomend as a setup, if one needs more than 4 LAN ports.

I use a Beetel DSL modem, and a Linksys Wi-fi Router. I have used up all the ports on the router. Its a very old one, and I was planning to replace it with a router with more than 4 ports. The only one I found, is :
WD My Net N900 HD Dual-Band - WD: Flipkart.com

Its expensive, but reviews are good.

What would be your reccomendation for a simple but effective setup ?

Rgds...Argho

@Argho,

The router you have linked has Gigabit LAN ports and 450Mbps wireless. If you dont need those premium features and your devices does not support it, there is no need to spend that money.
A simpler and cheaper option would be to buy a 5-port dlink or tplink switch which costs around Rs550, connect it to one port of your linksys router and use the other 4 ports to connect devices.