none
Event ID 58 - Disk signature error only while backup job

    Question

  • Hi,

    Host 2012R2 with Hyper-V-role, Backups are done with DPM 2012R2.

    While job is working, three warnings are recorded in event-log of the guest:

    partmgr / Event ID 58 / The disk signature of disk 2 is equal to the disk signature of disk 1.

    partmgr / Event ID 58 / The disk signature of disk 2 is equal to the disk signature of disk 1.

    partmgr / Event ID 58 / The disk signature of disk 3 is equal to the disk signature of disk 0.

    This happens in all guests (with different disk numbers). No corresponding error on Host or DPM. Registry of each guest is growing in these keys:

    HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2

    The popular hint "attach the VHDs, bring them on- and offline, detach" brings no solution. As Mike Jacquet from Microsoft told in this thread, it is a problem of Hyper-V and not DPM.

    Has anyone a solution for this? Thanks!

    Monday, May 5, 2014 9:25 AM

Answers

  • Hi,

    Here you can find another thread with the same problem:

    http://social.technet.microsoft.com/Forums/en-US/120ceb2f-5bc5-4a73-8b13-81b5dc25f348/disk-signature-error-while-backup-virtual-machine?forum=winserverhyperv

    I hope your problem will be resolved.

    Cheers.

    David Ortega


    David Ortega

    Monday, May 5, 2014 10:08 AM

All replies

  • Hi,

    Here you can find another thread with the same problem:

    http://social.technet.microsoft.com/Forums/en-US/120ceb2f-5bc5-4a73-8b13-81b5dc25f348/disk-signature-error-while-backup-virtual-machine?forum=winserverhyperv

    I hope your problem will be resolved.

    Cheers.

    David Ortega


    David Ortega

    Monday, May 5, 2014 10:08 AM
  • Hi,

    thanks for reply - but this thread is the one with the not working hint and it is marked as answered...

    Regards

    Monday, May 5, 2014 10:16 AM
  • can't believe no one has the same problem or solution...
    Wednesday, May 7, 2014 9:08 AM
  • Hi,

    I don’t found the issue, please install all the update then try the backup action again.

    Through the error message it clearly mentions Disk Signature conflict, please try the following troubleshooting steps, then tell us the result.

    1. Download DEVNODECLEAN.zip from http://www.microsoft.com/en-pk/download/details.aspx?id=42286 and extract it on the affected server.

    2. Now using an elevated command prompt change directory to the folder where contents of DevNodeClean.zip are extracted.

    3. Run the command DevNodeClean.exe /N >PhantomDev.txt

    4. After the above command run another command DEVNODECLEAN.exe

    5. After the command is executed you will see an output to conform it has deleted the Phantom devoices you can run the command from step 4 again and the output shall be blank.

    6. After this you can try to run the DPM Consistency Check again and check if the same events are getting logged as before complaining about Duplicated Disk and Signatures.

    More information:

    Fixing Disk Signature Collisions

    http://blogs.technet.com/b/markrussinovich/archive/2011/11/08/3463572.aspx

    Hope this helps.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Thursday, May 8, 2014 7:41 AM
    Moderator
  • Hi,

    thanks for reply. I tried your suggestion, but sadly it didn't help...

    output before execution: 

    DevNodePhantomCleaner:  SCSI\DISK&VEN_MSFT&PROD_VIRTUAL_DISK\6&362C8C22&0&000100 will be removed.
    DevNodePhantomCleaner:  SCSI\DISK&VEN_MSFT&PROD_VIRTUAL_DISK\6&362C8C22&0&000101 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUME\{B29043CC-97A8-11E3-B807-00155DE4CC00}#0000000000004400 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUME\{B29043CC-97A8-11E3-B807-00155DE4CC00}#0000000002100000 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUME\{B29043CE-97A8-11E3-B807-00155DE4CC00}#0000000000100000 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUME\{B29043CE-97A8-11E3-B807-00155DE4CC00}#0000000006500000 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUMESNAPSHOT\HARDDISKVOLUMESNAPSHOT2 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUMESNAPSHOT\HARDDISKVOLUMESNAPSHOT3 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUMESNAPSHOT\HARDDISKVOLUMESNAPSHOT4 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUMESNAPSHOT\HARDDISKVOLUMESNAPSHOT1 will be removed.

    output after execution was blank, so the tool worked as expected.

    After next backup, the same events are getting logged in every guest with OS newer than Server 2003.

    next output:

    DevNodePhantomCleaner:  SCSI\DISK&VEN_MSFT&PROD_VIRTUAL_DISK\6&362C8C22&0&000100 will be removed.
    DevNodePhantomCleaner:  SCSI\DISK&VEN_MSFT&PROD_VIRTUAL_DISK\6&362C8C22&0&000101 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUME\{46924B33-D6BA-11E3-B949-00155DE4CC00}#0000000000004400 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUME\{46924B33-D6BA-11E3-B949-00155DE4CC00}#0000000002100000 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUME\{46924B35-D6BA-11E3-B949-00155DE4CC00}#0000000000100000 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUME\{46924B35-D6BA-11E3-B949-00155DE4CC00}#0000000006500000 will be removed.
    DevNodePhantomCleaner:  STORAGE\VOLUMESNAPSHOT\HARDDISKVOLUMESNAPSHOT1 will be removed.
    

    As I understand Mark's blog, the signature collisions are the consequence from cloning. And every backup will use some kind of cloning, so this error will come up every time until Microsoft will fix this (perhaps in suppressing the ID 58 in eventlog if there's a backup). Am I right?

    Friday, May 9, 2014 5:36 AM
  • Im having the same results as above, and several other threads.

    I have a HP Proliant servers connected to a HP san.

    All servers are fresh installed with Server 2012 R2 datasenter

    Cluster is managed with SCVMM 2012 r2, and backed up with SCDPM 2012 r2.

    Hardware snapshots are NOT used.

    As of now only test vms reside on the cluster. I first thought i created the problem by cloning test vms. But all vms and templates have been deleted. New fresh installed server 2012 r2 is installed to vm from standard ISO.

    All updates and integration services are installed. The VM's are gen2.

    When doing a backup, snapshots are taken and the volumes are mounted in the vm. When this happens i get a error:

    Event 58 partmgr The disk signature of disk 1 is equal to the disk signature of disk 0.

    Then when the backup is done, i get the warning :

    Event 157 disk Disk 1 has been surprise removed.

    If i just add a new empty disk to the vm, and do another recoverypoint from DPM we get the same warnings as above but also: 

    Event 58 partmgr The disk signature of disk 2 is equal to the disk signature of disk 0.

    and when backup is finished:

    Event 157 disk Disk 2 has been surprise removed

    Event 157 disk Disk 3 has been surprise removed

    Devnodeclean removes old entries, but new ones are generated at every backup. This is annoying but can easily be fixed with a scheduled task.

    When i check disk signature with Diskpart, disk 0 and 1 have different signatures. But the event log is stating that disk 1 and 0 have same signature? Same with disk 2, but why does it not complain about the signature of disk 3...?

    Since not everyone is getting theese signature warnings, what is causing it?




    Tuesday, May 13, 2014 9:07 AM
  • Hi,

    Having the same problem, did you ever figure this one out?

    Monday, August 18, 2014 12:08 PM
  • I'm seeing similar problem, the post marked as an answer is not and answer, and the post it references also is not a proper awnser
    Thursday, October 30, 2014 10:08 AM
  • Having the same issue here.
    Friday, November 21, 2014 1:25 PM
  • I have the same warning messages when a backup is run from the Hyper-V host. I see them within a new Server 2012R2 guest a setup. Although the backup completes without issue and there are no other issues on the system.
    Friday, November 21, 2014 2:21 PM
  • Found a solution - or even better: Three possible solutions, #2 worked for me in this case.

    Found it here: http://www.ugg.li/windows-server-event-58-von-partmgr-die-signatur-des-datentraegers/

    Google translate: https://translate.google.com/translate?hl=en&sl=de&tl=en&u=http%3A%2F%2Fwww.ugg.li%2Fwindows-server-event-58-von-partmgr-die-signatur-des-datentraegers%2F

    In my case, I had to change the (duplicated) disk id to a new ohne with diskpart, reboot and the error was gone.

    Tuesday, December 2, 2014 5:19 PM