After reading many alarming posts on this forum re. recovering DX4000’s, decided to test recovery on a non-crucial DX4000 4TB at one of my client’s sites.
NAS is fully functional, I can RDP in, Dashboard states: storage OK, 2x 2TB disks healthy.
I’m testing reset to factory defaults of a DX4000 .
Using EMEA_SvrRecovery_1_7_5_17.iso (http://download.wdc.com/sentinel/EMEA_SvrRecovery_1_7_5_17.iso)
md5 hash verified.
ISO mounted with Virtual Clonedrive.
Using 16GB Transcend USB stick.
PC + DX4000 connected to same switch. DHCP active on a router also connected to switch.
Step 1: Recreate my Storage … results in “Storage OK” on the DX display.
Step 2: Perform a recovery
Starting recovery in the usual way: insert USB stick, press Reset button until “Recovery loading”, waiting until DX displays “Recovery Started”.
At this point the setup.exe on the client detects the DX4000 - … “Finding your server… connection to your server is succesfull”
Next screens I choose (o) Reset to factory default settings - do not delete data - I understand…
“Click next to begin the reset process”.
Next screen gives error: “Could not reset the server to factory default settings. Your server was not reset to factory settings. Resolve the issue, and then restart the server recovery process. Error code: 0x80070002”
At this point I verified that the DX4000 is visible over IP, but does not respond to IP, this is exspected.
On the USB stick, ServerRecovery.log contains this :
[02/29/2016 12:11:17 6bc] Starting ServerRecovery.
[02/29/2016 12:11:17 6bc] AddFirewallException
[02/29/2016 12:11:17 6bc] Listener CListener created
[02/29/2016 12:11:17 6bc] Listener UDP listener created
[02/29/2016 12:11:17 6bc] Listener UDP listener created
[02/29/2016 12:11:17 6bc] Listener TCP listener created
[02/29/2016 12:11:17 6bc] ServerRecovery started and is listening for request.
[02/29/2016 12:13:22 6f0] Listener TCPListener::TcpEventCallbackStatic
[02/29/2016 12:13:22 6f0] Listener TcpEventCallback
[02/29/2016 12:13:22 6f0] Listener TCPListener::TcpConditionCallback
[02/29/2016 12:13:22 6f0] Listener TcpConditionCallback from 192.168.0.108
[02/29/2016 12:13:22 6f0] NumberUnauthenticatedSessions is called.
[02/29/2016 12:13:22 6f0] StartSession
[02/29/2016 12:13:22 6f0] Received connection.
[02/29/2016 12:13:22 510] Entering HandshakeThread
[02/29/2016 12:13:22 510] Exiting HandshakeThread
[02/29/2016 12:13:23 6f0] Processing query system disk request.
[02/29/2016 12:13:23 6f0] Found extent with VDS_DISK_EXTENT_TYPE = 4 that is not a volume.
[02/29/2016 12:13:23 6f0] Found extent with VDS_DISK_EXTENT_TYPE = 6 that is not a volume.
[02/29/2016 12:13:23 6f0] PopulateVolumePartition failed with hr = 0x80070002
[02/29/2016 12:13:23 6f0] PopulateDiskInfo failed with hr = 0x80070002
[02/29/2016 12:13:23 6f0] DoDisks failed with hr = 0x80070002
[02/29/2016 12:13:23 6f0] ForDisk failed with hr = 0x80070002
[02/29/2016 12:13:23 6f0] QuerySystemDisk failed with hr = 0x80070002
[02/29/2016 12:13:23 6f0] End processing query system disk request.
I tried different USB sticks, connecting pc directly to NAS using straight and crossed ethernet cable.
Also tried different ISO downloads, but 1_7_5_17 is the only I have a MD5 hash from, to rule that out.
Can anyone shed a light on this and any solutions / other test steps ?
NAS can be bricked completely if necessary, including taking disks out, formatting them externally etc.
Just looking to establish & document a repeatable reliable recovery procedure in case of…, preferably while retaining data on the NAS.