Can you please provide the steps you took to get your WD Shareshare to work with the new 2TB drives?
I have an existing 4TB WD Sharespace that I have been using for several years that has worked very well for me for the past few years. I recently ran out of disk space and purchased (4) 2TB WD10EADS drives, instead of the EARS version as I had read there were possible incompatibility issues with the “EARS” variant.
Here is the trouble I am having, I removed the cover, pulled the (4) existing 1TB drives and installed the (4) new 2TB WD10EADS drives, after powering on the power light just flashes. I pulled up the documentation on what the flashing light indicates one of the following:
System is booting
System is restoring to factory default
System is configuring RAID on the hard drive(s)
System is configuring RAID 0, Span, or RAID 5 on a volume User volume is not available
Since I am in no major hurry here, I just spent the past week painstakingly backing up the data from the original drives I decided to leave it alone and let it possibly do one of the above tasks, it has been nearly 60 hours later and the power light is still flashing and I can’t login to the web admin interface, the network adapter is lite however the device does not ARP on the network so the interface isn’t available (I believe the technical issue here is a bug in the firmware that doesn’t allow the ethernet interface to come up PRIOR to the disks being available, this is a terrible flaw… moving on)
I try to push the power button to no available, the only option is to unplug the power cord. I tried powering it back on and it goes right back to this blinking power light state. So I pull the 4 new 2TB drives out, put the original 4 1TB drive in and power it on, and it boots up fine and I can login to the web admin interface.
So now I have read these forums for the past 40 hours learning what people are doing to get a partial two disk volume installed and I just don’t have time to mess with trial and error. I’d like to review your steps and then I am going to take the time to create a step by step guide for others to follow when upgrading from the 4TB Share Space to the 8 TB Share Space including what drives are compatible, etc.
Can you explain to me what the jumpers are on pins 7&8? My original 4 1TB drives do not have any jumpers on those pins, is this something related to the “EARS” model? Right now I have booted up the NAS with the original 4 1TB drives and I have just reset it to factory defaults and it’s rebooted and now it’s in the process of building the RAID volume *sigh*. 1000minutes to go.
I am going to power it down and try someones suggestion of installing 2 drives and then resetting to factory defaults and then having it build a 2 disk volume, when completed I guess I will power down install 2 more drives and then hope to delete the old configuration again? You would think someone at WD would take an Engineer over there and re-create this issue of a 4TB to 8TB upgrade, document the issue and create a work around document for everyone with this issue and then create a firmware patch to resolve this issue.
WD Folks: Listen up, here are some recommendations to resolve this issue:
Enable the Network interface at boot up, allow users to web into the interface if there is a disk issue.
It’s possible the reason new disks aren’t initializing is due to custom volumes that were configured on the original disks and the only way to get rid of this information from the settings is to reset it to factory defaults, however you can’t reset the factory defaults if you have install the new drives. The unit won’t allow you to boot it or log into it.
This is a very simple resolution, why isn’t it being addressed?
Take a 4TB ShareSpare unit that has some custom configuration in it such as a couple users, a couple custom disk volumes, copy some random files to it and then process to try to upgrade it to an 8TB unit in a lab environment, you will be able to recreate exactly what is happening in 15 minutes and create a work around document for your CUSTOMERS to resolve this easily until you can create the next firmware patch to address the disk capacity upgrade issue.