Permalink
Browse files

Fixed link.

  • Loading branch information...
Silvenga committed Jul 22, 2017
1 parent c49b356 commit ae73fd0d36f85708f2f7b40af10046473dabdbfb
Showing with 1 addition and 1 deletion.
  1. +1 −1 input/posts/virtual-disk-service-stalled.md
@@ -13,7 +13,7 @@ At first I noticed that I was having issues connecting to the Windows SNMP (Simp
Later I noticed that Windows Updates were taking forever, so wanting to know the bottleneck, I checked the Resource Monitor. No resource issues that I could find, however, no IO stats were showing either and no disks were shown under the Storage section. To double check this oddity, I enabled IO performance stats within [Task Manager](https://blogs.technet.microsoft.com/canitpro/2013/12/02/step-by-step-enabling-disk-performance-counters-in-windows-server-2012-r2-task-manager/) - this should pull from the same location as the Resource Monitor (IIRC). The Task Manager also failed to get disk information for me - as well as the Server Manager, which I tried later. At this point I was really questioning the integrity of this server, but ran a `fsck` check anyway (I didn't really think it would help, but why not?). After the reboot, nothing came up, this had no impact on my issue.
Oddly all these issues basically revolved around disk issues, time to check that part of the system? Now, I'm running this particular server in a software RAID-1 (it's a cheap server) using the same method I wrote about here (/raid1-windows-server-2016/). This is definitely not a standard solution in the Windows land, but I've tested this method in my testbed, and have never any had issues. I truly didn't believe this to be the problem, but I fired up Disk Management just to poke around. The message `Connecting to Virtual Disk Service...` greeted me and wouldn't leave (yes, the Virtual Disk service was enabled and running, I restarted it to make sure).
Oddly all these issues basically revolved around disk issues, time to check that part of the system? Now, I'm running this particular server in a software RAID-1 (it's a cheap server) using the same method I wrote about [here](https://silvenga.com/raid1-windows-server-2016/). This is definitely not a standard solution in the Windows land, but I've tested this method in my testbed, and have never any had issues. I truly didn't believe this to be the problem, but I fired up Disk Management just to poke around. The message `Connecting to Virtual Disk Service...` greeted me and wouldn't leave (yes, the Virtual Disk service was enabled and running, I restarted it to make sure).
## The Ultimate Solution

0 comments on commit ae73fd0

Please sign in to comment.