The driver detected a controller error on \Device\Harddisk1\DR1

Mukesh Yadav 1 Reputation point
2022-08-01T11:41:21.017+00:00

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
226678-image.png

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,202 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,556 questions
0 comments

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Tony Pombo 6 Reputation points
    2022-08-26T00:23:14.977+00:00

    This is not a hardware problem. This began with Hyper-V Server 2019 and still exists with 2022.

    We have numerous virtualized clusters on several Hyper-V clusters. As we upgraded each host cluster from Windows Server Datacenter 2016 to 2019, every virtualized cluster starting having the problem you describe. It didn't matter if the guest OS was 2016 or 2019. It doesn't matter what vendor/model the server is.

    We've been dealing with this for years.

    Some of our host clusters are now running Windows Server Datacenter 2022 and the problem remains. We do not yet have any 2022 guest clusters to see if that helps.

    This is a Microsoft software bug/problem. If you find a fix, I would LOVE to hear about it. We currently receive 3500+ of these errors across all our guests VM each month.

    1 person found this answer helpful.
  2. Tom Phillips 17,716 Reputation points
    2022-08-01T14:34:00.553+00:00

    I can't answer your specific problem. But there are many posts on the HP forums about this error due to driver issues. I suggest you contact HP for a possible solution.

    0 comments
  3. Docs 15,146 Reputation points
    2022-08-03T04:57:05.36+00:00

    Please run:

    a) HD Tune: (free or trial version) (test all drives)
    Post images or share links into this thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    b) Sea Tools for Windows (test all drives)
    https://www.seagate.com/files/www-content/support-content/downloads/seatools/_shared/downloads/SeaToolsWindowsInstaller.exe
    https://www.seagate.com/support/kb/how-to-use-seatools-for-windows-202435en/
    Long generic test
    Post images or share links into this thread.

    c) Run HD Sentinel (free or trial version)
    Post images for results on these tabs:
    a) Overview
    b) Temperature
    c) SMART

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .

    0 comments
  4. سالم الانصاري 6 Reputation points
    2022-08-29T08:18:36.937+00:00

    Dear Tony

    I am also having the same issue as described by Mukesh in the First comment but i am running production environment with this error just wanted to know your experience if you found any impact on the servers or it can just be ignored.

    Thanks
    Salim

  5. Jure Purgar 11 Reputation points
    2022-09-02T12:00:08.373+00:00

    I also have the same problem. When we upgraded hosts from 2016 to 2022 these events started to occur in our guest clusters that are using VHD sets. It does not seem to have any negative effect on the cluster roles. Did anyone try to contact MS support about that? I'm thinking of doing that, but it might be a waste of time if they don't have a solution yet.