You know I really do not know what I am saying, but if these are win 10 boxes I wonder if you have to enable SMB1 ?
Ok so I have a win 7 box that as in now it has connected and it is formatting. So it must be something with Win10 and server 2012r2
Yay, no nix 
server 2008r2…
When I tried to rebuild by using the recovery running on the 2012 server I figure they were so close it would not be a problem. There must be something being blocked preventing it from connecting.
After 3 attempts of a working recovery connection and getting error 0x80070002, no clue what is causing this, but as can bee seen by my other post I am trying to get Linux on this now. Thanks for your help, still might give it one more to recover try when my larger capacity drives arrive. If not hopefully I can get Linux on it and make some use out of the hardware as a simple backup drive with some level of RAID.
did you edit the whitelist file on the recovery thumb also?
Yes I changed it on the thumb drive. It gets through the format portion of the recovery, then I get the 0x80070002 error. Each time I have gone through every step I have seen. Pull the drives, clear with diskpart, reinstall drives, create thumb drive 1 with modified whitelist, run until complete. create a second thumb drive with a modified whitelist.
The only thing odd in the logs is this in the server.log file the ERROR WIMCreatFile:
[01/05/2020 09:47:20 5ac] Entering BeginResetThread
[01/05/2020 09:47:20 5ac] Executing Reset
[01/05/2020 09:47:20 5ac] DiskImaging::Reset, bCleanDisk = 1
[01/05/2020 09:47:20 5ac] pVdsDisk->GetPack failed with hr = 0x80042417
[01/05/2020 09:47:20 5ac] Ignore. One case is uninitialized disk.
[01/05/2020 09:47:20 5ac] Executing CreatePartition (0x6400000, 0x100000, style=2)
[01/05/2020 09:47:20 5ac] Calling CreatePartitionEx (0x6400000, 0x100000, style=2)
[01/05/2020 09:47:21 5ac] Executing CreatePartition (0x8000000, 0x6500000, style=2)
[01/05/2020 09:47:21 5ac] Calling CreatePartitionEx (0x8000000, 0x6500000, style=2)
[01/05/2020 09:47:21 5ac] Executing CreatePartition (0xf00000000, 0xe500000, style=2)
[01/05/2020 09:47:21 5ac] Calling CreatePartitionEx (0xf00000000, 0xe500000, style=2)
[01/05/2020 09:47:26 5ac] Executing CreatePartition (0xffffffffffffffff, 0xffffffffffffffff, style=2)
[01/05/2020 09:47:26 5ac] Calling CreatePartitionEx (0x1c2b31fbe00, 0xf0e500000, style=2)
[01/05/2020 09:47:36 5ac] Found extent with VDS_DISK_EXTENT_TYPE = 4 that is not a volume.
[01/05/2020 09:47:36 5ac] Found extent with VDS_DISK_EXTENT_TYPE = 5 that is not a volume.
[01/05/2020 09:47:36 5ac] WimApply (D:\sys.wim, 1, a:, 2, *)
[01/05/2020 09:47:36 5ac] Calling WIMCreateFile
[01/05/2020 09:47:36 5ac] ERROR: WIMCreateFile for file [D:\sys.wim] failed with error 2.
[01/05/2020 09:47:36 5ac] Cleanup
[01/05/2020 09:47:36 5ac] WimApply failed with hr = 0x80070002
[01/05/2020 09:47:36 5ac] Reset failed with hr = 0x80070002
[01/05/2020 09:47:36 5ac] BeginResetThread - backend Reset failed with hr = 0x80070002
[01/05/2020 09:47:36 5ac] Reset completed with hr = 0x80070002
[01/05/2020 09:47:36 5ac] Exiting BeginResetThread
[01/05/2020 09:55:18 784] RestoreProtocol::Disconnect is called.
[01/05/2020 09:55:18 784] RestoreProtocol::Disconnect - calling socket shutdown.
[01/05/2020 09:55:18 784] MC_Closed
[01/05/2020 09:55:18 784] Calling ~CSession.
[01/05/2020 09:55:18 784] SessionComplete: Number of active connections: 0.
[01/05/2020 09:55:18 784] StartSession - close socket
[01/05/2020 09:55:18 784] End StartSession
don’t know. The error is normally it is not happy with the drives.
But first you should verify you have a good download with the md5 hash thing.
I think you said you were using 1tb drives? I don’t know if it can only handle 2tb or larger,
All this said, and the effort you have put in, it is an old box and may not be worth the effort.
Please note the following (from experience):
- I only managed to successfully use WD RED drives (not in the original whitelist), nevr tried with others
- WD RED 6 Tb starts installing but at some point the process is stopped - i.e. maximum looks 4 Tb hard drives
- I always modified the whitelist files on the original virtual DVD and then created the thumb drives
- 90% an already used thumb USB drive did not work for another clean install. I had to recreate the USB from the virtual DVD from scratch
- Of course all disks “clean” from diskpart before install on DX4000
regards
Davide
FWIW I did not have any issue using 6TB WD Red drives. I edited the whitelist.xml and after install, I edited the systemconfig.xml to get the fans working at normal speed instead of max.
Also I don’t think there is a minimum size limitation, as I have a pair of 1TB WD drives in Raid1 that work just fine in the DX4000.
B.
Thanks for all the help and information guys. So it now has 2 x 4TB WD Enterprise drives in it and It will now format, and get most of the way to installing the OS, but crashes with This error from the logs:
[01/07/2020 21:57:48 5d8] Progress 73
[01/07/2020 21:57:51 5d8] ImageProcessingCallback (F:\Windows\winsxs\wow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.22728_none_d52693c4761e71da\shell32.dll) WIM_MSG_ERROR 1392
[01/07/2020 21:57:51 768] ERROR: WIMApplyImage for wim file [E:\os.swm] to target path [F:] with flags [2] failed with error 1392.
[01/07/2020 21:57:51 768] Cleanup
[01/07/2020 21:57:52 768] WimApply failed with hr = 0x80070570
[01/07/2020 21:57:52 768] Reset failed with hr = 0x80070570
[01/07/2020 21:57:52 768] BeginResetThread - backend Reset failed with hr = 0x80070570
[01/07/2020 21:57:52 768] Reset completed with hr = 0x80070570
[01/07/2020 21:57:52 768] Exiting BeginResetThread
[01/07/2020 21:58:09 5e8] RestoreProtocol::Disconnect is called.
[01/07/2020 21:58:09 5e8] RestoreProtocol::Disconnect - calling socket shutdown.
[01/07/2020 21:58:09 5e8] MC_Closed
[01/07/2020 21:58:09 5e8] Calling ~CSession.
[01/07/2020 21:58:09 5e8] SessionComplete: Number of active connections: 0.
[01/07/2020 21:58:09 5e8] StartSession - close socket
[01/07/2020 21:58:09 5e8] End StartSession
I checked the MD5 of the ISO and it matches, the date is correct.
SO digging around in the ISO, I found the OS swm files located in the “Reset” folder and did a manual attempt to compile to a wim file and sure enough, it balks at it being corrupt. Hmmmm… So I down load iso again… same thing… try again… BAM, I can combine the three swm files in to a wim with no error.
Copy these three swm files to my already made thumb drive and try again.
Success! It is loading the OS now for the first time. Let hope no more hickups.
curious, does the md5 match on your first dl and the one that works?
I checked them all, but I will double check again tonight after work. In theory this is impossible if both have the same MD5 which was why I was so shocked when one ISO would be corrupt and then next was not. Will post more tonight.
And thanks again for the help!
Well Today all three iso’s seem to result in a perfectly fine wim files. So something happened between last night and today. Not attempting to burn another ISO as everything seems to be working.
All three have the same MD5. So either I was doing something wrong and was not noticing it, i.e. using the wrong ISO, or yesterday was just bad luck. Either way I am saving the thumbdrive that worked last night and not touching it if I ever have to do this again.
What do you mean burn an ISO, you do not make a dvd with the iso
I mean make another thumb drive
