At this point, all limitations listed in my first post have been removed or mitigated. Here is a quick summary of the current status of each resolved/mitigated limitation listed earlier:
- The two NICs are configured in failover mode only, and teamed, meaning two active network connections cannot be established. This is a significant limitation if trying to use the DX4000 as a low-cost centralized storage server for Hyper-V and/or VMware.
By installing the lastest Intel drivers and management tools for the two onboard NICs, it is possible to remove the teaming configuration from the NICs and concomitantly end up with two independent NICs. In my configuration, one NIC has now been dedicated to iSCSI traffic and the other NIC for remote access to the DX4000 via RDP. - Given that the DX4000 ships with WSS 2008 R2 Essentials, iSCSI support otherwise available from Microsoft in non-Essentials versions of WSS, is not provided. This significantly limits the ability of the DX4000 to act as a centralized storage server for Hyper-V and/or VMware. Although theorectically the DX4000 supports NFS, which would allow one method of leveraging the DX4000 in an ESXi environment, out-of-the-box WD documentation and tools do not indicate in any way whatsoever how to install support for and configure NFS, and it does NOT ship with NFS support already configured.
NFS has now been enabled on the DX4000. However, with regard to use with ESXi 5.0, StarWind Sofware’s free iSCSI target software has been installed and configured. The ESXi host, using an iSCSI storage adapter, is connecting over the dedicated iSCSI network to iSCSI targets defined on the DX4000 via the StarWind iSCSI SAN Software. - Although capable of supporting two power sources, the DX4000 only ships with one laptop-style power brick. However, additional DX4000-compatible power bricks are available for about $65 (including shipping and handling).
Second power brick has been ordered and will be installed this week. When installed, testing of automatic power failover will be performed to ensure the additional investment keeps the DX4000 running smoothly. - The DX4000 ships with only 2 GB of RAM installed, which imposes a perceptible limitation on throughput speed. Despite the low cost of RAM today, Western Digital does not provide an officially sanctioned, or described, method of installing additional RAM.
Removed the DX4000 shell, removed the six screws holding the DX4000 motherboard to the top of the interior drive cage, carefully removed the motherboard from the unit, and exposed the single SODIMM (2 GB). Note that there is indeed only a single SODIMM slot, despite CPU-Z indicating otherwise. Replaced the 2 GB SODIMM with a 4GB with same specs, carefully reinserted the vertical PCB extender into the motherboard as I remounted it on top of the drive cage, and finished re-assembling DX4000. Turned on the unit, connected via RDP, and WS 2008 R2 reported 4 GB of RAM in use.
As time permits, I intend to post more detailed instructions and other pertinent information related to each of the above limitation remediations.
As an illustration of the two NICs operating independently, here is a screenshot of Task Manager on the DX4000 with three VMs running on a separate ESXi host using three iSCSI targets hosted on the DX4000:
Technical Odds and Ends 
28 responses to “Hacking the Western Digital Sentinel DX4000 Update 1”
Using the Microsoft iSCSI target software is highly preferable to using a free third-party add-on. Will have to give the install another try.
Interesting that you were able to get Microsoft’s iSCSI target software installed. I was unable to get it to install and read that Microsoft intentionally blocks install of their iSCSI target software on Storage Server Essentials. Are you running Essentials or did you upgrade it? Or has the block vis-a-vis Essentials been removed?
@chrisccs & troyswalker
Thank you, this should help with performance, I installed Microsoft iSCSI Software Target 3.3 on it today and it works great.
204pin SODIMM, DDR3 1333
this is what i put in, been running very well for a week now.
http://www.newegg.com/Product/Product.aspx?Item=N82E16820139190
I usually get my memory from Crucial, but in this case I think I had an unused SODIMM left over from a laptop upgrade. Here are the specs, courtesy of Speccy (v 1.18). Note that the tool incorrectly reports two slots available. The custom motherboard only has a single slot available.
RAM
Memory slots
Total memory slots 2
Used memory slots 1
Free memory slots 1
Memory
Type DDR3
Size 4096 MBytes
Channels # Single
DRAM Frequency 399.0 MHz
CAS# Latency (CL) 6 clocks
RAS# to CAS# Delay (tRCD) 6 clocks
RAS# Precharge (tRP) 6 clocks
Cycle Time (tRAS) 15 clocks
Command Rate (CR) 2T
Physical Memory
Memory Usage 60 %
Total Physical 3.99 GB
Available Physical 1.59 GB
Total Virtual 9.96 GB
Available Virtual 7.09 GB
SPD
Number Of SPD Modules 1
Slot #1
Type DDR3
Size 4096 MBytes
Manufacturer Samsung
Max Bandwidth PC3-10700 (667 MHz)
Part Number M471B5273DH0-CH9
Serial Number 626669DF
Week/year 26 / 11
SPD Ext. EPP
JEDEC #5
Frequency 685.7 MHz
CAS# Latency 9.0
RAS# To CAS# 9
RAS# Precharge 9
tRAS 25
tRC 34
Voltage 1.500 V
JEDEC #4
Frequency 609.5 MHz
CAS# Latency 8.0
RAS# To CAS# 8
RAS# Precharge 8
tRAS 22
tRC 30
Voltage 1.500 V
JEDEC #3
Frequency 533.3 MHz
CAS# Latency 7.0
RAS# To CAS# 7
RAS# Precharge 7
tRAS 20
tRC 27
Voltage 1.500 V
JEDEC #2
Frequency 457.1 MHz
CAS# Latency 6.0
RAS# To CAS# 6
RAS# Precharge 6
tRAS 17
tRC 23
Voltage 1.500 V
JEDEC #1
Frequency 381.0 MHz
CAS# Latency 5.0
RAS# To CAS# 5
RAS# Precharge 5
tRAS 14
tRC 19
Voltage 1.500 V
Can you let us know which 4 GB SODIMM you purchased. I was thinking of doing this but would like to purchase the ram prior to disassembling the unit.
The authors at the “We Got Served” blog detailed two ways to do an Essentials install on a headless HP Windows Home Server box. The techniques they described should work equally well for the DX4000.
You can read more here: http://www.wegotserved.com/2012/10/12/install-windows-server-2012-essentials-hp-mediasmart-server/
nice find on the starwind iscsi software.. added deduplication is awesome.
the power requirements have been minimal, i have the APC XS 1500 monitoring and it was only using 45watts
i was considering an attempt at putting WS2012 essentials, but can’t get my head wrapped around doing the headless install with it….
Loading Linux would not be ideal given that the price premium Western Digital is charging for the product is largely attributable to the WSS 2008 R2 license that comes with the product. A much more cost effective solution, and higher-performing (e.g., using full AMD and/or Intel processors rather than the Atom that ships with the Sentinel) Linux approach would be to go with something like a Thecus NAS offering (of which I own the NAS4100PRO). If not intending to use WSS 2008 R2, I would think there are many other more desirable alternatives, from building your own device and loading FreeNAS onto it, or buying a Linux-based solution from Buffalo, Synology, NetGear, etc.
As to power consumption, I haven’t measured it using something like Kill-A-Watt but the device uses a laptop-style brick and ships with a 250 Watt power supply. Fully loaded with four hard drives, I’ll guess it’s using between 150 to 200 watts. If I get a chance to measure it, I’ll add the details to the post.
Have you looked into the possibility of loading Linux onto this and using it as a more general purpose server?
Also, what is the power consumption of this device under normal operating conditions?