2 NAS servers both with 802.3ad bonded gigE nics based on the Realtek 8169 chip.
The highest MTU I could set was 7000 even though the D-Link DGS-1210-24 Rev. A switch can support up to 10k.
Below is just a single sample, but all tests stayed within 57x Mbits for MTU=1500 and 77xMbits for MTU=7000.
The important bits.
iperf was used for this testing.
[ 3] 0.0-10.0 sec 687 MBytes 576 Mbits/sec
[ 3] 0.0-10.0 sec 926 MBytes 777 Mbits/sec
Reformatted a bit to fit on page.
I have 6 of these (2TB) in each NAS Raid5 setup plus motherboard, AMD cpus, RAM etc.
This page is for researching a replacement PSU.
2.8.1 Power consumption
Power requirements for the drives are listed in Table 2 on page 15. Typical power measurements are based on an average of drives tested, under nominal conditions, using 5.0V and 12.0V input voltage at 25°C ambient temperature.
• Spinup power Spinup power is measured from the time of power-on to the time that the drive spindle reaches operating speed.
A lot of ST32000542AS drives come with the CC34 firmware. Apparently it has various known problems, one of which is an annoying click (click of death). The first thing you’ll want to do is upgrade the firmware to CC35. A Link to the instructions is in the references section below.
Once that is done, the next step, if it exists, is removing HPA from the drive.
You’ll know it has HPA enabled by running hparm. HPA results in less capacity and so it’s not a good thing in an array.
We’ll be using Debian 6.0 (squeeze).
hparm -N /dev/sdb
Since Debian squeeze doesn’t appear to include pre-built iscsitarget kernel modules, the iscsitartget-dkms must be installed. This is a source package and will install gcc etc to compile. It should compile automatically.
apt-get install iscsitarget-dkms
Here is a list of iscsi related packages I installed on my secondary NAS:
iscsitarget 18.104.22.168-1 iSCSI Enterprise Target userland tools
iscsitarget-dkms 22.214.171.124-1 iSCSI Enterprise Target kernel module source – dkms version
open-iscsi 2.0.871.3-2squeeze1 High performance, transport independent iSCSI implementation
I found this info in a bug report through google after I received a module not found error when issuing a /etc/init.d/iscsitarget restart
I wanted a centralized home storage system that could feed all my other toys. Data stored on this will include MySQL datafiles, our MP3 collection, website directories and all our receipts printed out in PDF format (Yay! CutePDF) among other things. And so the fun began…
I did some test installs of various “turnkey” solutions such as Openfiler.
Openfiler just didn’t seem stable enough. Arrays would claim to have faulty drives and start rebuilding the arrays at the strangest times. Only to find out, via 3rd party tools, that the drive was fine. The web interface was ok but I would have organized it differently. Minus that, Openfiler has a lot of potential.