This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 7.000000000000001%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMY%3C/text%3E%3C/svg%3E)
Hello
I'm using Windows Server 2022 and I have this problem: The driver detected a controller error on \Device\Harddisk1\DR1
Here is the description of my environment
2 physical server with Windows Server 2022. Holding hyper V role and high availability cluster
Shared FC HPE storage
I have carted 3 VMs windows server 2019 to the hyper V ( first on node 1 and 2nd , 3rd on node 2)
Install SQL 2019 cluster on all 3 VMs. Data drive is created as VHD SET and that is reside on shared clustered volume
Everything is working fine but getting following error in the event viewer on the 2 passive nodes not in control of the disks produce. The 3rd VM where the disks active no error.
The driver detected a controller error on \Device\Harddisk1\DR1. Event ID 11
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 48%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
I did not have time to open a case with MS about this yet, however I found out that those events will happen on the same time that scheduled task "\Microsoft\Windows\Power Efficiency Diagnostics\AnalyzeSystem" running. If I start the task manually on non-owner node, shortly after events will be logged. I'm not sure what this task does or if it can safely be disabled, but I'm sure it causes those events. I'm planning to open a case with MS and ask what is going on.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 83%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
Did you ever get any more information on this or had it resolved? We are experiencing the same issue as described here and like in mr. TonyPombo's case (and I assume in yours too) it happens only on virtualized, nested clusters and apparently only on shared VHD Set drives. It doesn't appear to be impacting the clusters but it just looks really bad to have to deploy clusters to other teams which have an event log filled with errors from the start. You are also right that it happens when that scheduled task runs, since the errors don't occur anymore since I disabled that. However we have a Rubrik backup solution and that seems to trigger the same errors as well, every time it takes a backup. The backups do succeed though. Thanks in advance for any reply
I did open a case and get a response that this is a know issue in windows server 2019 (and 2022). Aparently there is a bug in svhdxflt fs filter driver on the host:
Rescan disks on the Guest Node that does not own the resource or a failover of the group happens
Using shared vhdx in guest cluster 2012-2019 creates event Id 11 in VM while rescaning disk or during failover
Large numbers of Disk event 11 and 153 are logged which quickly fill / spam the Windows Event Log, making it difficult to identify legitimate disk issues or monitor the overall storage health using monitoring tools, such as SCOM
There is no impact caused or implied by the of this Event ID on the cluster as this error message is harmless.
There is no public info available about this problem. According to MS the issue was discovered in May 2022 and will be fixed in the upcoming rollups, but there is no ETA at this point.
Thank you very much for getting back to me, I truly appreciate it. I have passed this info on to the other teams and we will wait for the update rollup. Good to know that it is truly harmless but as already remarked in the quote you've posted, it makes spotting genuine errors very difficult. I'm glad though that Microsoft is at least aware of it. For a while there I thought I had made a major configuration error in setting up the clusters and was frantically looking for a solution
Cheers and thanks again!
There is an old reddit post:
https://www.reddit.com/r/HyperV/comments/bo4ohs/help_identifying_source_of_repeated_the_driver/
Describing this same issue from 4 years ago. There are no solution there, but this proves that the problem has existed for a long time.
A colleague of mine directly messaged the poster back in November 2020, and this is what the poster said:
Almost 18 months later, we still have MS engineers on this case. It keeps getting bumped from one team to another. It turns out, it is in fact a bug. Kinda. Maybe more of just undesired behavior. And it actually make sense why it is being logged. Since only one of the nodes can be the owner of the disk(s), any time the passive node attempts any enumeration of the disks, which are essentially locked by the cluster service, the event gets generated. We have been assured it is harmless and have not experienced any adverse behavior beside the event log flooded with the entries. I would guess that give the cause, this has probably been occurring for YEARS and it surprises me we were the first to identify it. As such, there's probably little interest in fixing it as a fix may introduce more severe issues. But it is logged as a bug and we are not being charged Premier Support hours against this case.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 63%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I dont belive this Microsoft is just keeping its eye close. Issue remain years after years