That recovery partition is a disappointment to me. To use it you actually have to boot to windows and hold down shift while clicking restart to get to it.
If you boot from recovery media you cannot access it because there are no raid drivers loaded. Now one time I was piddling with restores, loaded the raid driver, but canceled the restore. Well it showed up though I did not actually follow through to see what would happen.
I think you need to backup everything C: system, etc, except D: (Raid data) to be able to restore and not a bad idea to have your raid data backed up as well unless you do not need it.
I suggest you get a spare hard drive and fiddle with it till you are comfortable you can get to where you want to be.
I think there are too many risks/problems with running the machine as a dedicated 2016 hyper-v host so I am going to open it up again check if I can identify which boot drive is making all the noise and try replace it.
I am just going to do a restore now and probably keep it off my domain and just run everything in Hyper-V or ESXI.
I suppose I still could use it as the domain controller but all my VMs now will be 2016 which if either you havenāt tried, it runs very nice on this machine. I have 32GB ram now so each VM should be having around 6GB each and 2 cores.
Maybe WD will do some sort of official upgrade/support and then I can upgrade the host and retain the VMs, think the plan for me now is to try and keep as little services running dedicated on it.
Thanks for all the help and sorry for chickening out on going RAW 2016 on it.
Just discovered the noise I was hearing isnāt the drives. Removed the casing to listen to which 1 it was and couldnāt hear anything. Then I realised it was coil whine coming from the motherboard.
I suspected it was a refurb unit, looks like a chip has cracked the casing. Not sure if this is anything to worry about or not though.
Starting the 2016 upgrade process now that RTM is available.
Canāt get it to even boot to USB⦠going to try doing upgrade first see how that goes before I go back to a clean install. NIC teaming was a pain, disabled it but it kept being awkward.
Upgrade process is now running so will keep this updated.
If anyone knows how I can do a clean install from a USB stick that would be great, going to take the gamble and delete the partitions and start fresh. I have a backup should I brick my machine (hopefully I can restore it)
Itās all installed now on DC version, seems to work very well. Just setup hyper-v and thatās even let me import my VMs which were already on the the data drives.
If you got it installed you must not need the raid drivers. I think there is a setup bat in the oem tweaks file
just extract it/all to a c:\wd folder and run it with fingers crossed or a good bckup
For my 2016 installation, I extracted version 2.2.10.18 to WD in C drive and ran all the WD Apps except for WDBranding. Everything works fine, except the followings:
The Audible Alerts and About page under the MONITOR tab - no report
Microsoft Pinpoint under APPLICATIONS tab - does not connect at all
Server Manager reports error for WD Product Config and Aft - I set those service to manual to clear up
I upgraded yesterday from Server Essentials 2012R2 to Server Essentials 2016, then uninstalled all the original WD bits and reinstalled from Grampsā dropbox.
The audible alerts work for me.
The fan is running fast 1567rpm now (versus 770rpm)
The LCD service seems to die after a few hours.
I found a WD link : The LCD display and system fan acts abnormally when transmogging from Windows Server 2012 R2 Essentials to Server 2012 R2 Standard on a WD Sentinel DS series which advises āThe system fan and LCD controls are part of certain WD Components that run on Windows Server 2012 R2 Essentials. After the transition, Windows Server 2012 R2 Standard provides users with the option to completely remove all R2 Essential roles. Selecting this option prevents those WD Components and services from operating, causing the system fan and LCD display to misbehave.ā
Also, the site //server/connect fails ⦠I am investigating (//server works)
Iām not sure what you do, but I did a couple of successful install - attempted to use SSD. For the mean time, Iām using stock OS disk and plan to get a spare.
I did a fresh install this way. The data on my raid remains intact, just reconnect folders afterwards.
1- burn Windows Server 2016 to a DVD
2- plug USB DVD Reader w/ Win Server 2016 DVD
3- at boot up, press Del to get into Bios
4- in Bios boot menu, select DVD, save and exit
5- upon reboot, it will ask press any key to boot from DVD, press any key
6- now you will see DVD loading content
7- *do not select upgrade, pick the other option - I just donāt see the need to upgrade
8- at this point, you probably wonāt see any HD displayed
9- plug a USB drive w/ SATA Driver, like the one you can download from the previous post
10- now search for driver, go to that directory. If you donāt see USB drive, just hit back and try again
11- at this point, the HD should appears, OS 2xHD will appear as one, note the size
12- delete other partitions, install on this disk
13- once done installing, go to WD site and download current firmware, extract them in a WD folder in C drive
14- install all the app, go down the list, you can ignore Branding, it has no effect anyway and no need. note one that says preinstall, then click that firstā¦
15- reboot, everything should work except what I mentioned in the previous post
I know it works because I have done it a couple of times. Same result every time. Good luck! Hope you find that helpful and Iām not too redundant.