Jump to content
RESET Forums (homeservershow.com)
diehard

STORAGE BAD: Western Digital DX4000 Small Office Storage Server

Recommended Posts

diehard

Hi Guys,

 

I'll be updating this post as things change.

 

As a Microsoft Windows Home Server MVP, a few months back, I found out from my Microsoft Team Leader that Western Digital would soon be releasing the DX4000 Small Office Storage Server. And that I should contact Western Digital to see if I can get a unit for review. I did. Thanks Western Digital. :D

 

The DX4000 comes with the Windows Storage Server 2008 R2 Essentials software. I'll write a few post on this in the future, so look for that. I'll also tweet when I do and discuss it on future podcasts.

 

So, on the the nitty gritty of why I'm writing this post.

Let me start by saying that if you know me, I like to bang on my server until something breaks, and then figure out how to fix it. This also helps the community just in case you unfortunately find yourself with the same issue.

 

So this post is not to say how Western Digital's product is flawed in some way.

 

OK, so while putting the screws to this box, I successfully managed to kill it to a point where I was getting a "STORAGE BAD" error on the LCD display. Not fun at all. Repeated reboots didn't resolve this. Things were looking grim. So as the type of guy I am, break first, then read the instructions to find a fix, I turn to the User Manual, http://www.wdc.com/w...4779-705064.pdf

 

 

 

UPDATE:

 

Ok, so after refering to the pdf and getting a reply from an email to Western Digital ( thanks for that WD), I found out that I messed up the RAID array. Time to rebuild the array.

 

How do you do this with a headless box with no access to the BIOS or OS ?

Since this box is headless, WD allows you to download a full copy of the OS that includes a few options. According to the pdf, you create a bootable USB stick <512 meg and boot off of that. Then you will get some details from the LCD screen as to your progess. It look 7 hours to rebuild the drives, OUCH that took a while. But in the end, of course it worked.

 

Then I wanted to reinstall the OS. That involves a similar process to the making the repair RAID USB stick, but you need a 8GB stick because it will hold the OS. ( This is similar to how it's done with the MediaSmart Server but the OS is on the USB stick instead of the PC.)

 

So now I'm all up and running fine.

 

Now to try and break it with some Add-ins.

 

If you have any questions on the Western Digital's DX4000, I'll give support on this box as long as I can until I have to return it.

 

Soon to be continued..... :ph34r:

Share this post


Link to post
Share on other sites
jmwills

So that's what that little book is for???

Share this post


Link to post
Share on other sites
ImTheTypeOfGuy

You're a nut. I bet you are like a kid in a candy store. Have fun.

Share this post


Link to post
Share on other sites
ikon

I'm just surprised to find out diehard can read :D

Share this post


Link to post
Share on other sites
diehard

Funny guys :P

Share this post


Link to post
Share on other sites
unrealshots

hey John,

 

the $64,000 question is - would you recommend a WD4000?

 

My wifes' works WHS v1 threw a disk today, and after several hours, I've recovered all bar a few files from the failed drive...

 

first port of call will be to replace the dead disk, and get the v1 box running again, but looking for a longer term fix... I've had my eye on a WD4000 for some time, and now it's quite an attractive option at $1530 for a 6TB model...

 

I know I could buy a N40L and jack it up to 8GB RAM, but by the time I got a RAID controller and and 3x 3TB or 4x 2TB disks, and put it together, the WD4000 is cheaper!

 

your thoughts?

 

Cheers,

 

Andrew

Edited by unrealshots

Share this post


Link to post
Share on other sites
ikon

Andrew, quick question: I'm wondering why you're fixing your wife's employer's WHS? Don't they have a contract with someone to look after their IT, or is that you? :)

Share this post


Link to post
Share on other sites
Helzy

I've got one. Set it up, went to transfer some data via the USB 3 port - dead. Had transferred multiple terabytes of data on to it via network and set it free in a semi-production environment. NIC's drop their IP every few days,.  For the USB 3 problem, WD will not ship me a mainboard even though it was days old. THey wanted me to pack the whole effing thing up and send it to them. No thanks. Bought a 16TB DS6100 at the same time. Second time restarting it after setup, one of the boot drives lost it's config. 8 hours later to rebuild the boot volume...

 

Meh not impressed with these units. Definitely not impressed with WD policy of no cross shipping. I even offered them a credit card to ensure the core return. Nope, pack it up and send it at my own expense to them. Will not buy another.

Share this post


Link to post
Share on other sites
Yiw Keong

Dear diehard,

 

I was counter same issue 'Storage Bad' . Initial my last DX4000 hardware failure , it keep restart when 'startup initiallzation' . I was email to WD support team, they advised bought same model DX4000 and migrate 4 (2TB) drives into new DX4000. I was follow those step, but DX4000 LCD screen show 'Storage Bad' . Can you advise , how can I fix my issue ? Thanks in advance

 

 

Below step provided by WD support team:

 

Counter issue during Step 16 - 17, when I go back my PC click Next system not found DX4000 server and DX4000 show 'Storage Bad'.

 

I was capture video as below:

https://www.dropbox.com/s/nopn2nm1hcmpunv/VID_20151121_110442.mp4?dl=0

 

 

Based on the error, it seems that the device is unable to boot up to its OS.

 

We would like to suggest you to perform a system recovery.

 

Please follow the steps below:

 

1. Connect the PC and Sentinel to the same router/network . Make sure both devices are on the same network.

2. Download the ISO from support.wdc.com to the PC.

 

http://support.wdc.com/product.aspx?ID=1601&lang=en

 

3. Unzip the ISO.

4. Connect 16GB USB drive to PC. The USB thumb drive should only be 16 or 32.

 

SPECIAL NOTE: http://wdc.custhelp.com/app/answers/detail/a_id/9889

Based on our USB compatibility tests, the following limitations have been found:

 

1. The USB Flash Drive must be a USB 2.0 flash drive (not USB 3.0).

2. Despite what the message says, The USB Flash Drive must have a capacity of 16 GB or 32 GB in size.

3. A USB Flash Drive with a storage capacity greater than 32 GB will not work.

 

5. Run the setup.exe from the ISO recovery file you unzipped.

6. Choose 3rd option ---- do system recovery.

7. The setup.exe will scan for the USB drive. Once it finds USB drive, click next to erase drive and burn the recovery ISO file to the drive.

8. After the setup is finished, do not close the setup page on your computer. Leave the page open in your PC.

9. Disconnect the USB drive from your PC.

10. Make sure you have turned off the sentinel first before following the below procedures.

11. Connect the USB drive to the Sentinel.

12. Hold the reset button of the Sentinel using a paper clip.

13. While holding the reset button, power on the Sentinel.

14. Once you see the message 'Loading Recovery' on the LCD panel of the Sentinel, release the reset button.

15. Once you see recovery started on LCD, go back to setupexe window on your computer and then click Next.

16. Setupexe will scan the local network for the Sentinel.

17. Once setupexe finds the Sentinel, it gives you options.

18. Restore to a backup or factory restore.

19. Choose factory restore.

20. It will ask to reinstall system only, reset to factory settings without deleting the data OR a full factory reset which will delete everything then reinstall the system.

21. Choose the first option that will not affect the data. Setup will ask you to confirm everything you want to do

22. Once confirmed, then click Next.

23. It will take 3-8 hours to do recovery. Make sure your computer will not go to sleep mode.

24. It will reboot for several times.

25. After you can see the IP address on LCD monitor which means the recovery is done.

image.jpg

image.jpg

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • tswalker
      By tswalker
      So, it has been a very long time since I've been able to contribute to this community...  but I creep in every so often
       
      Some may know of this NAS that Western Digital offered back in 2012 called the DX4000.. flavors included storage up to 16TB and it ran Windows Server 2008 R2.  I made a few articles on my blog, showing how to convert it to use Windows Server 2012 R2 back then, and it had been running like a champ ever since, last month.  I decided to re-purpose it as a firewall, and began searching for alternatives to pfSense...  I naturally gravitated to OPNsense, and experimented with getting it to run on the metal.

      It may seem strange to want to do this with a device built to be a storage server, but I've outgrow the storage... and it actually had decent adapters on-board (2x Intel 82574L), the form factor was small, and included redundant power supply capabilities.

      To make it possible, there had been some advancements by the community on how to access the BIOS on the machine, found here on YT posted by Martin Meise.  A BIG "Thank You" to that guy for showing how to mod the PCB to include a serial converter.  I picked up a USB to TTL serial cable from Adafruit.com, soldered some extension wires to the PCB on the DX4000 (which currently stick out the side).. and had instant terminal bliss.  I can plug/un-plug the adapter when needed this way, just a note...  the RS on board will plug into the TX on the adapter, as does the TX onboard to the RS on the cable.. anyway.  works great.  (just a note, the PCB has what seemed like a polyurethane coating on the pads, and I had to dissolve/scrape it off to get the solder onto them)

      The only setting on the BIOS that needed to be changed was to switch the controller from RAID mode to AHCI.. which allows you to use independent storage without the needed RAID setup.

      I picked up one of those ICY DOCK 2.5" to 3.5" converters a while ago to use for this, and an in-expense Kingston 120GB SSD on Amazon for 20$USD.  It was a tight fit, but works great.

      The difficult part in this setup was to get FreeBSD installed on this thing...  I tried dozens of times using the OPNSense ISO and serial versions to get it going, and gave up after while defeated.  I also tried other FW flavors like pfSense, and Sophos.. all failed to use the serial terminal to complete installations.  I gave IPFire a shot and actually got it working accidently after modifying the serial console to use TTYS1 instead of TTYS0.. and a light in my head got turned on...  it had that I.D.10.T message.
       
      I went back and built a USB with OPNsense serial version image on it.. fired up a FreeBSD VM on my windows workstation.  note, the USB must be 'offline' in windows to use as an attached disk in hyper-v... just take it offline in disk manager, and add the usb as an iscsi disk in the vm settings.

       
      * startup FreeBSD in the VM, logon as root and mount the device.  For me this ended up being device /DEV/DA1A   (mount /dev/da1a /mnt/usb )
      * cd to /mnt/usb/boot , you can copy the loader.conf file to loader.conf.local or just VI a new file called "loader.conf.local"  (it is important to have a local file so your changes are not auto-overwritten)
      * include the following into loader.conf.local:
      hw.uart.console="io:0x2f8,br:115200" bitmap_load="NO" comconsole_port="0x2f8" comconsole_speed="115200" console="comconsole" boot_serial="YES" ** it is important to note that after installation is complete, you may NEED to do this again and add a loader.conf.local file to the system to access the things via ttyS1
       
      I was now able to use my usb to serial cable connected to my workstation to open PuTTy (mod the BIOS) and step through a serial installation of OPNsense...  it was defaulting to use ttyS0, instead of ttyS1 which is what is needed for this machine.
       
      The only things I have NOT been able to manage getting to work are the fan speed controls, and my BackUps powersupply over USB for monitoring power.. other than those, this little thing has been solid.
       
      So far, I've been able to get the LCD working great using LCDd... i get all the goodies i need being displayed... and I apologize that I have no pictures of my lovely PCB soldering nor of the LCD working.  I'll try to get some in the coming days, and post a new blog on my blugged.wordpress.com site.. but i've been super busy with a new software engineering position these past 9 months, and just don't get much free personal time anymore.
       

       
      I hope someone has enjoyed this quick write-up!
       
      -tswalker
       
    • diehard
      By diehard
      Looks like Western Digital's DX 4000 supports only 3 models of hard drives.

      http://www.manualowl.com/m/Western%20Digital/WDBLGT0080KBK/Manual/237696?page=13
    • diehard
      By diehard
      FYI.
       
       
       
       
      My backup to the Western Digital DX4000 failed. Since this is a headless server, it's nice to see that the LCD shows the warning. It hasn't cleared off the LCD, which is good, because you always have that message staring you in the face to fix it.
       
      Hopefully it will when the backup is fixed.


×
×
  • Create New...