Are you using performance monitor to check the throttling? When you said you never found a solution, do you mean that you never got it running stably or that sometimes after an install it would work and continue to work, and other installs it would just never work?
A combination of the WD Monitoring within the Essentials Dashboard - which showed the high temps and low fan speed - and task manager which showed the clock speed had dropped as low as possible.
I never found a solution in that some installs would work and other installs it wouldn’t - without pinpointing what the trigger was. That, and combined with the fact the AFP sharing doesn’t function on 2016 made me stick with 2012R2.
Ah. How did you go back to 2012? Unfortunately I don’t have the WD “version” of 2012 R2. Do you think the generic version from MS will work along with your 2016 procedure to get the WD utilities installed? Does that add the WD specific feature to the dashboard?
Wish I never did the upgrade. While I have backups with Veeam, they are BSOD when I restore it.
see if it will boot into safe mode
-
Is to hold shift and press F8 repeatedly. I’ve heard this work and I’ve heard this doesn’t work so your mileage may vary.
-
Boot to the Server 2012 R2 disc and you can select Troubleshoot and then Command Prompt. You type in the commands below and when you restart the server and get to the boot screen you won’t see a “press F8 for Advanced options” but press F8 anyway and you will be brought to the advanced menu.
bcdedit /set {bootmgr} displaybootmenu Yes
bcdedit /set {bootmgr} timeout 15
I do have a recovery image available - it was created using the original WD WIM file in conjunction with a custom boot environment so all the drivers were integrated. I don’t know what the legality is around sharing this though.
Have you tried resetting your BIOS to defaults, then restoring a backup?
If it’s still BSOD’ing, does it stay on screen long enough to determine what the error message is? As that will hint as to what setting is wrong.
I don’t know what happend, but now I can’t see my OS drive at all. I’ve reset my BIOS, disabled secure booting and booted to both a 2016 and 2012 USB key. When I try loading the marvel drivers and hide incompatible drivers is checked, nothing appears. When unchecked, I see the mvs94xx.inf
This is a total mystery, as I was able to load the drivers a few days ago.
did the drive die? Good connections?
@Gramps not exactly sure. At this point I’m going to do a cross shipment replacement and get my data off. I did one in Oct of last year as well.
I just ordered a Intel NUC and use that as my backup server and recoup my losses by selling the DS. Too bad it’s been so unreliable.
Wish I had read this thread before buying one at Auction. Thought if nothing else I could install Linux on it to make a NAS but even a live Linux does not see the drives to install on it. Maybe they need to be formatted first? I thought they were SSD boot drives but am sure they are are 2.5 regular HDD
Most likely 2.5" 320GB WD AV drives (WD AV-25 WD3200BUCT). I’ve had a 1/2 dozen of these DS6100’s over the years and the rust spinners from WD have been literally the worst drives I’ve ever encountered for reliability.
