共用方式為

Hyper-V and "Event ID: 58 - The disk signature of disk 2 is equal to the disk signature of disk 0"

  • 發行項

On Monday I talked about how we had changed backup in Windows Server 2012 R2 to make it scale better.  However, there is one annoying downside of this change that I did not discuss.  And that is Event ID 58.

As I mentioned - we now connect a copy of a virtual machines virtual hard disk back to itself in order to revert to the correct VSS snapshot.  When this happens - the copy of Windows running inside the virtual machine sees two hard disks with exactly the same disk signature.  In the real world - this is something that should never happen.  And the result is that the guest operating system will log a warning event (Event ID 58) that states that it has found two disks with the same signature (and that it is confused, scared and afraid).

Fortunately, this warning message can be safely ignored in this instance.  Unfortunately, it cannot be suppressed.

Cheers,
Ben

Comments

  • Anonymous
    April 06, 2015
    ".......this warning message can be safely ignored in this instance". That answer from MS has never been acceptable...and still isn't. If t isn't a legitimate warning, it should not occur.

  • Anonymous
    August 06, 2015
    This is incorrect. Warning messages are just warnings. If it was an error message, that would be an issue.

  • Anonymous
    June 10, 2016
    Is this only seen when reverting a snapshot? We have taken over a business this error is present on a hyper-V exchange server and logged everyday

    • Anonymous
      October 16, 2017
      How are you running backups? Does your backup process include taking a snapshot?

  • Anonymous
    November 03, 2016
    I agree, errors AND warnings that are not legitimate things to investigate should NEVER be logged in the Event Log.I DO understand that this could happen for a few months (the time between when it was noticed and when it was dealt with), but it should not be left to fill up the event logs for eternity.There are important things that IT personnel should be looking into. Researching things that should not be logged is NOT one of them.

  • Anonymous
    October 31, 2017
    "Fortunately, this warning message can be safely ignored in this instance."Thats all and well for you, but in OUR instance it cannot be ignored as it is causing VSS snapshot based backups to be corrupt.