Sunday, August 4, 2019

As not predicted....

As not predicted.... leading to NAS v2.0

My NAS build is an absolute power-hog. Using ~80W constantly and more when peaking.. It's added a significant cost to my monthly electricity bill.

I have found a nice solution:

Using a raspberry Pi to 'listen' to network traffic and act as a WOL server.

The idea here is to have a raspberry Pi running 24/7 and WOL the main server when it is needed. The idea is that this would be in 'sleep' mode and wake up when it gets triggered by the Raspberry Pi.

A long-running TCPdump looking for certain traffic:
Problem is, currently I use my NAS as a switch too (using Linux bridging). It means I don't need a seperate 1G/10G (maybe 100G in future) switch. So I'd better make sure the incoming network interface is the one that gets the WOL wakeup packet (mac address needs to match the interface).

Leading to NAS v2.0 

All good so far then. I will probably use a mini-nas built from a raspberry Pi M4 and a SATA Hat and have that wake up the 'bigger' NAS when it is needed.
I will probably add SATA SSDs to this NAS to keep it low-power and speedy.

I will have to find a solution for the 10Gig interfaces to the NAS directly, but my gut feeling says I probably will not need 10/100Gbit for my desktop for a while yet.
I currently have 4x250Gbyte SATA SSDs that I'll be using for this NAS build. Keeping it _really_ low power. I expect to stay under 20W. I will use the wireless interface for normal traffic and the wired interface for WOL activities.

I am also working on a 'compute power' server. It will have 2x 2930L, an Intel Phi 7120a and will be switched on/off my Philips Hue. It will use around 400W at it's peak, but it's scary fast in computing. It will be using my 'fast-NAS' for it's storage (using 100Gbit networking) Should be good :-)

No comments:

Post a Comment