- WD Community
- News & Assistance
- New to Community
- Forum Feedback
- Software & Apps
- WD Software
- WD Mobile Apps
- Software & Accessory Ideas
- WD TV Live Streaming
- Live Streaming Discussions
- Live Streaming Firmware
- Live Streaming Ideas
- Live Streaming Issues
- WD TV Live Hub
- Hub Discussions
- Hub Firmware
- Hub Themes
- WD TV Live Hub Ideas
- WD TV Live Hub Issue Reporting
- WD TV Play
- WD TV Play
- Live & Live Plus
- Live Discussions
- Live Firmware
- Elements Play
- Elements Play
- External Drives
- Mac Externals
- PC Externals
- Portable Drives
- External Drive Ideas
- Network Devices
- Networking Devices
- Live Duo
- My Book Live
- Other Network Drives
- Network Product Ideas
- Internal Drives
- Desktop & Portable
- Internal Drive Ideas
- Nuevo a La Comunidad
- Los Productos de WD
- Software y Accesorios
- Reproductores Multimedia
- Unidades de Red
- Unidades Externas
- Unidades Internas
- Neu in der Community
- WD Produkte
- WD Programme
- WD TV Media Player
- Netzwerk Laufwerke
- Externe Laufwerke
- Interne Laufwerke
- Annunci e Novita'
- Nuovo per La Comunita'
- Prodotti WD
- Programmi & Accessori
- Riproduttori Multimediali
- Dischi di Rete
- Dischi Esterni
- Dischi Interni
- WD TV Legacy
- Hub Network
- Live Networking
- WD TV HD
- WD TV Mini
- WD Photos
- Other Software & Accessories
- Hard Drives
- WD ShareSpace
- Other Externals
- Other Internal Drives
10-07-2011 07:46 AM
All of you - just wan't to share last state of my SS trouble.
It's been returned to retailer this week.
After successfull raid rebuild (for unknown reason, unit restarted once while rebuilding, which caused the whole proccess to start again, btw); back on working system, while copying data back from backup, another disk failed (previous hdd failed once, marked some bad sectors, which I was able to get rid of, using some dos wd disk tool (wriring zeroes to whole hdd) = the hdd was acctually ok, only the SS thought it was bad).
Failure of second hdd, was a definite signal to me to not trust this unit any longer.
I erased it, packed it , and brought it back to retailer.
"Funny" is, that he wasn't surprised at all - said to me he had a lot of negative feedback + too many warranty claims of this SS product.
Currently I am waiting to get my money back and hopefully will buy another nas (much better rated) from the q... company.
Sorry, but will probably never get back to this forum.
Thank you all, for helping, pushing to the right directions...) - I learned a lot of new things.
10-09-2011 10:37 AM
Wish I had looked on here before trying to upgrade this morning. Unit firmware went fine and got message that the unit is rebooting. Afterthat, the browser timed out and the unit has been unresponsive since. Nothing answering on the previously set static ip address, WD Discovery finds nothing, scanning the network does not show any devices for the SS.
Not too many people have multiple spare backup drives to handle 4TB of data. That's what this unit was for. However, I have backups of the most precious data elsewhere. But my problem seems that the unit is simply not connecting to the network to even be able to manage it or do anything. On startup, it appear all of the LED's are doing what they are supposed to. From the looks of it, the SS thinks it is working perfectly fine.
This **bleep**. Anyone else have any luck? Can you take it to an authorized service place and have them put the old firmware back on? Not sure what to do from here.
10-09-2011 09:10 PM
Used the reset on the back and then the Discovery was able to located it. However, the services (as outlined in detail of this thread) are not running such as http, ssh, etc.
Not sure where to go from here without trying the radical linux box route. Has anyone heard a response from WD on support tickets? Is there a way for them or an authorized tech to help on this?
10-10-2011 10:52 AM
Are they getting you one back with the data still on it? There has to be a way to plug the unit in and fix the firmware which is all that this issue is. Http, ssh, etc. is simply not running and there is no way to access the unit to change that. I would hope they have some method of manipulating it without having to can the data.
10-10-2011 01:25 PM
After updating firmware, that seemed to be fine, I reboot my Sharespace and gone it was. http is gone and the smb is gone. I can´t reset it with resetbotton on back so the only way to reboot it is to unplug the power but that doesn´t help eather.
I just want to downgrade to previous firmware. I run Mac OS Lion and that was also my reason for update.
10-19-2011 06:46 PM
I have the same problem as a few of you seem to have.
I cannot get to the device at all with the Browser and it's IP address.
Also, no good mapping the drive. Just doesn't connect.
I can get to the TwonkyMedia server part, but this is no good to me, as I don't have any data there.
Have called WD support and gone to their level 2 guys, but all they can offer is to use the Linux method to back up the drives and and them put in an RMA. Luckily, it is still under warranty, just.
I think they need to restructure there server interface and at least have a backout method to the previous verson of firmware.
10-22-2011 07:52 PM
They need to add direct USB connectivity or something so you can get access to the unit when it gets bricked by their firmware. This is incredibly dissappointing and frustrating. Most people buy these for backup / redundancy and don't have another drive of this capacity to backup data when you run a firmware update. There no solution other than rma and data loss really stinks.
Has anyone had any success attaching four drives into a linux box using raid 5? I am going to be trying to do this in the morning as my last ditch effort / hail Mary!
10-23-2011 11:31 AM
Well... I am hesitant to say, but it appears that I have sucessfully rebuilt the raid 5 array using a computer and a Ubuntu LiveCD. I am currently transferring the files off of the drives onto my new storage and will take some time as it is around 2.3 TB worth. Once the transfer is done, I will spend the time to retrace my steps and prepare a more complete and informative tutorial.
I know that I am not the only one with this issue. I can't understand why WD hasn't addressed this. It had been many weeks since this firmware came out and started bricking units. I, unfortunately, did not look at this forum prior to my applying the firmware update. This had to have been a known issue for WD by the time my unit downloaded the firmware and ruined my device. Why would they not take it down?
I need to give credit to this link: http://www.linuxjournal.com/article/8874?page=0,1 The info there was invaluable!
You will need a computer with a CD rom drive or usb port to use an Ubuntu bootable jump drive and a hard drive controller capable of handling the number of drives you have. It doesn't have to be anything fancy and can even be a system you already have sitting around. I had to go and buy a four port serial ATA card for $25 at compusa to plug into an old system I had. No biggy, I guess. You need to remove the drives from the Sharespace and label them in order from top to bottom. Attach them to your temporary computer disk controller making sure that you attach them in the same order by adding one at a time, booting and checking the system or controller bios, which ever is applicable. I recommend you disconnect any other drives from the controller if you are using a functioning system with other existing drives. You should really be able to do this without effecting the existing system as you should be able to just plug the existing drives back in when you are done. I am using my network to transfer the files off of the drive onto my new system. Perhaps you could use an external usb drive and would be faster, but may muck up the drive numbering in Ubuntu. If you use an external USB drive, I recommend waiting and plugging it in after you have the raid rebuilt. Note that booting to the LiveCD creates a temporary session of linux and anything you do in that session in terms of configuration is lost on reboot. If you need to reboot for any reason, you will effectively have to restart.
Once you have the drives from your worthless WD box attached to the temporary computer properly, boot up using the LiveCD and click on the "Try Ubuntu..." to load the operating system. Once the system is loaded, you will need to load a terminal shell by clicking on Applications->Accessories->Terminal.
To set yourself as the roof user and not have to type "sudo" 1000 tims, once in terminal, type:
sudo su -
You will need to install the raid softward and LVM2 to access the drive partitions. Type:
apt-get install mdadm lvm2
If the drives are connected properly, they should be the devices as follows:
Drive 1: /dev/sda
Drive 2: /dev/sdb
Drive 3: /dev/sdc
Drive 4: /dev/sdd
You can check this by typing fdisk -l and it will list the drives and associated partition information. Each of my drives had four partitions on them and are labeled sda1. sda2, sda3, sda4 for drive 1 and sdb1, sdb2, etc. for the subsequent drives.
Only the fourth partitoin sdx4 is the one with the data and you need to recreate that raid array. You do this by typing:
mdadm --assemble /dev/md0 /dev/sda4 /dev/sdb4 /dev/sdc4 /dev/sdd4
You should get a message that the raid is functioning. You can check the status by typing:
mdadm --detail /dev/md0
Your raid is now reassembled, but the WD uses lvm2. If you try to use the standard mounting with autodetect you will get an error of unknown fs type LVM2 something or other. This is where it gets tricky and I need to go back and recreate to know the exact steps. You need to use the utilities from LVM2.
To get the volume name type:
The volume on yours should be the same. Mine was called "vg0"
vgchange vg0 -a y
You should get a message telling you that your logical volume is active. From here you only need to mount the drive to the file system. My logical volume was called "lvo"
First create a directory to mount to by typing:
I am not sure if this is necessary, but I went ahead and completely opened up the permissions to the folder by typing:
chmod 777 /mnt/raid
Then mount the drive to that folder by typing:
mount -t auto /dev/vg0/lv0 /mnt/raid
Your files should now be accessible through the file browser. Go to Places->Computer, then click on "File System" on the left. Then, navigate to the mnt/raid folder in the main window. I found that there were strange permissions on my files so I went ahead and removed all restrictions using the chmod on the raid drive by typing the following into the terrminal window:
chmod 777 -R /mnt/raid
As I said, I am currently dumping the files onto my new system as I type. I wil go back and clean this tutorial up when I get done and possibly add some images, etc.
Hope this helps someone else out! What a nightmare WD provided me.
10-29-2011 11:38 PM - edited 10-29-2011 11:55 PM
I am having much the same issue as others here - no access to the GUI through IP or name, I can access Twonky on port 9000.
I don't have a spare box or the knowledge of Linux to do the solutions suggested in this thread, nor do I have the space to do a backup of the files if I did. So, is there any way I can get access to my files or restore my box without losing my data? The box serves as my main iTunes library and you know how Apple is about re-downloading purchases. *sigh*
I do know I can't connect through http, ftp, or Windows sharing. WD-Discovery sees the box (had to use the reset button on the back before it or my router could see it), but can't configure or browse the shares. About all I can do is turn on/off the discovery LED.
I don't think this is under warranty any more, so I don't know if calling WD would do any good. Doesn't sound too promising from the posts in this thread.
Thanks for any suggestions you may have.
Update: I can't access through SSH either. Connection refused.