none
Event ID: 10111 Error Failed to mount the virtual hard disk RRS feed

  • Question

  • I also have this question posed on the DPM forum, but I'm not sure if this is a VSS issue or a DPM issue.  When we try to create a recovery point in DPM, our Server 2008R2 Core Hyper-V server reports the following error event:

    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          1/19/2011 2:02:25 AM
    Event ID:      10111
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      server.lan.comDescription:
    Failed to mount the virtual hard disk '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy8\Hyper-V\abc\abc.vhd' for virtual machine 'ABC' (Virtual machine ID B6EE02C4-FDF7-47DD-B579-D879536E6440).

    VSSADMIN LIST WRITERS shows:

       Writer name: 'Microsoft Hyper-V VSS Writer'

       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

       Writer Instance Id: {de88412e-6663-4486-ac77-3781a8556a5f}

       State: [1] Stable

       Last error: Retryable error

    These errors started after applying Windows security updates, so there may be a correlation. 

    Any ideas how I might resolve this issue?

    Thanks.. Chris 

    Wednesday, January 19, 2011 5:04 PM

Answers

All replies

  • Hi!

    Since your HyperV VSS Writer is in a retryable state, your HyperV backups will continue to fail until you clear the fault. Only way I know is to reboot the Hyper-V host.

    You can check out this blog:

    http://robertanddpm.blogspot.com/

    This guy is the second person in the world to become MVP on DPM. I believe he has a post about this somewhere.

     

    Wednesday, January 19, 2011 6:31 PM
  • I tried rebooting the Hyper-V server last night and it came back up fine.  But as soon as DPM attempted to do its recovery points, the same errors returned and the last error returned to Retryable error. 

    I am able to use Windows Backup within the Hyper-V guest and create snapshots from Hyper-V, so it would appear that the HyperV VSS Writer is still working even though it is in a retryable state.

    Wednesday, January 19, 2011 7:06 PM
  • Hi,

     

    As you mentioned “I am able to use Windows Backup within the Hyper-V guest and create snapshots from Hyper-V”, so please try to use Windows Server Backup to backup the VMs to check whether you get the same issue, then we can narrow down the cause of the issue.

     

     

    Best Regards,

    Vincent Hu

     

    Friday, January 21, 2011 6:44 AM
    Moderator
  • Hi,

    I am able to run a Windows Server Backup from within a Hyper-V guest.  The Hyper-V host server is running Server 2008R2 Core.  Are you saying I should try to install the Windows Server Backup feature on Core and attempt to backup one of the Hyper-V guest's .VHD file?

    Thanks,
    Chris

    • Edited by rosenstc Friday, January 21, 2011 6:58 PM typo
    Friday, January 21, 2011 4:26 PM
  • Yes, you are able to install the Windows Server Backup feature on Server Core.

    From the Command Line: start /w ocsetup WindowsServerBackup 


    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )
    Friday, January 21, 2011 7:10 PM
  • Thanks for the updates... I did install the WindowsServerBackup feature on the Hyper-V host server and attempted to backup the .vhd file of one of the guests.  It failed with the following error:

    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          1/21/2011 11:35:03 AM
    Event ID:      521
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      server.lan.com
    Description:
    The backup operation that started at '‎2011‎-‎01‎-‎21T19:25:03.605000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348001'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    Friday, January 21, 2011 7:41 PM
  • There are two hotfixes needed for DPM that address Hyper-V.  I found that hotfix KB975921 was not installed on the Hyper-V host server.  Hotfix KB975354 was installed.  Although, now when you go to Microsoft for KB975354 (http://support.microsoft.com/kb/975354)  they only offer one file for fix287961 which extracts the patch: Windows6.1-KB975354-v2-x64.msu.

     

    Patch Windows6.1-KB975354-x64.msu (which should be installed first) is no longer available to download.    I have hotfix KB975354, so I’m not worried about reinstalling this hotfix.   

     

    I have to reboot tonight and reapply integration services, so I will see if this makes any difference.

    Saturday, January 22, 2011 12:14 AM
  • Hotfix KB975921 did not help, same errors as before.
    Monday, January 24, 2011 12:24 AM
  • Microsoft helped me resolve this issue:

    • Applied hotfix KB2155024 (this did not resolve the issue)
    • They discovered that my vmbus.sys file on the host Hyper-V server was not at the same level as the Hyper-V guests, so they had me apply hotfix KB981836 which has the latest version of the vmbus.sys file
    • They also had me apply hotfix KB977096 to update my vmms.exe file to the latest levels.
    • They also found that I was missing a registry entry for 'NoAutoMount'.  So, I had to manually create a REG_DWORD registry entry under: HKLM\System\CCS\Services\Mountmgr and set it to 0.

    That seemed to do the trick!

    • Marked as answer by rosenstc Tuesday, February 1, 2011 11:43 PM
    • Unmarked as answer by rosenstc Friday, March 9, 2012 7:12 PM
    Tuesday, February 1, 2011 11:43 PM
  • what you explained here is exactly the same i'm facing now. I can download KB975354 but it contains only fix287961. when i tried to apply to windows 2008 r2 sp1 server core, it still says "hotfix is not applicable to this platform". i'm seeking for the 1st file windows6,1-KB975354-x64.msu but i cannot find out any place to download. luckily i hit this forum and see you mentioned here. if possible, can you please share the copy of windows6,1-KB975354-x64.msu? that would be great to me., thanks in advanced.

    Tuesday, September 20, 2011 10:28 AM
  • This issue came back again after I applied additional security updates.  So, after working with Microsoft, they suggested I install SP1 for 2008R2 to the host machine first.  They then suggested I apply SP1 to the guests.  And then finally, reinstall the Hyper-V integration services.

    This has worked well for me, I haven't had any issues since applying SP1.

    Tuesday, September 20, 2011 3:38 PM
  • Unfortunately, this same issue has reared it's ugly head again.  The last time I dealt with the issue, I had to call Microsoft Support and they had me install SP1 for 2008R2 and reinstall the Hyper-V integration services.  This worked well for about 8 months, up until now when it started to fail again (VSS Retryable errors). 

     I do routinely install security updates to these servers, but other than that, there have been no other changes.

    I've tried rebooting the Hyper-V host server and re-installing the Hyper-V integration services to the guest machines.  I also applied the latest hotfix avail for DPM 2010 to no avail.  I also tried using Windows Backup, but it fails as well:

    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          3/9/2012 10:50:12 AM
    Event ID:      517
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Description:
    The backup operation that started at '‎2012‎-‎03‎-‎09T18:19:53.337312600Z' has failed with following error code '2155348301' (There was a failure in updating the backup for deleted items.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
    .
    .
    .

    I noticed that the vmbus.sys file versions are again mismatched on the Hyper-V host server and the guests.  The guests are running version 6.1.7601.17514 and the Hyper-V host is running version 6.1.7601.17617

    So the host server's vmbus.sys file is slightly newer.  I don't know how that happened, but I'm not sure what the best way is to make them match as all of these servers are running 2008R2 SP1. Hotfix KB981836 would not apply for SP1. Is it just a matter of copying the host's vmbus.sys file over to the guest machines?

    Any suggestions?

    thx... 




    • Edited by rosenstc Tuesday, March 20, 2012 5:01 PM typo
    • Marked as answer by rosenstc Thursday, March 22, 2012 9:53 PM
    • Unmarked as answer by rosenstc Thursday, March 22, 2012 9:54 PM
    Friday, March 9, 2012 7:10 PM
  • Microsoft support had me apply three hotfixes which updated the following files:

    1. http://support.microsoft.com/kb/2460912 - volsnap.sys

    2. http://support.microsoft.com/kb/2263829 - hvboot.sys

    3. http://support.microsoft.com/kb/2541014 - diskdump.sys

    In the future, I should not apply any security patches that list any of the above files to the host server, otherwise I risk this problem happening again. 

    • Marked as answer by rosenstc Thursday, March 22, 2012 9:57 PM
    Thursday, March 22, 2012 9:57 PM