locked
Yet another "Cannot Mount Drive" Problem with error reporting problem RRS feed

  • Question

  • Using the current WHS, I too have a problem with the "Cannot Mount Drive" error at 81% with my Win7 (32 bit) computer when trying to open a backup. I have done a chkdsk on the server as well as all of the other suggestions that people made in order to fix this problem. However, no problem is ever found.

    Note that the exact same machine booted into WinXP works successfully. I can open and view files. Thus, I don't think that there is a problem with the server or its backup files themselves, just using Win7 to open the backups and not being able to mount the virtual disk. I installed the toolkit and ran the "Send Error Report" on the Win7 machine. While it seems to generate the log files, it fails to send them with the following error report:

    Problem signature:
      Problem Event Name:    Simple
      Problem Signature 01:    TALQ
      OS Version:    6.1.7600.2.0.0.256.48
      Locale ID:    1033

    I can send the Win7 log files if it would help, but the program seems to be unable to do so. The Server log files have been sent - CAB 870284483.

    The Win7 machine is a Core 2 Duo E5200 with 4 GB RAM on an ASUS P5QL Pro MB. The WHS machine is an Intel ATOM D510 MB with 4 GB of RAM and a 1TB WD Green Drive.

    I have been dealing with this for about 20 days and I am about ready to give up since there does not seem to be a solution to this problem for me. A backup program without the ability to restore is useless. Any help would be appreciated.

    Thank you.

    Mike

    Tuesday, June 8, 2010 1:39 PM

All replies

  • Exactly what version of Windows Home Server do you have? You can find out by opening the console, selecting Settings, then Resources. The version numbers for Windows Home Server components will be shown. Also, note that if you don't have Power Pack 3 installed, you should definitely upgrade to it, as it includes better support for Windows 7 in a number of areas.

    That said, your issue points to a client problem rather than a server problem. 81% errors are usually related to the installation/configuration of the virtual device driver that Windows Home Server uses to allow browsing a backup as though it was a mounted drive. There appears to be something happening on that client which is preventing the VDD from loading successfully.

    You should submit a bug on Connect, and include log files from your server and the client having the problem. If you have trouble with the toolkit uploading logs, you can attach them directly to the bug report. Without a bug report, unfortunately your uploaded logs will probably never get reviewed by an actual human, and they will expire pretty quickly from where they get stored in any case so uploading again when you submit the bug report would be a good idea.


    I'm not on the WHS team, I just post a lot. :)
    Tuesday, June 8, 2010 2:36 PM
    Moderator
  • Ken:

    I have the latest 6.0.2423.0 on all of the modules. PP3 is installed as well as all of the updates. Yes, I agree that the problem is with the virtual device driver used to mount the virtual drive.Is there any way to ensure the the VDD is installed and working?

    When I tried to submit feedback on "Connect" all I saw was ways to submit feedback on Vail - "Windows Home Server code name 'Vail' Public Preview Bug Reporting Form". Is there any other place to do this for the current version of WHS?

    Whenever I submit the bug report for 'Vail' Public Preview Bug Reporting Form", it keeps telling me that I am missing a "required information" field even though everything is filled in. It is frustrating as there does not seem to be any way to submit the bug report.

    Thanks for any help and advice.

    Mike

    Tuesday, June 8, 2010 2:59 PM
  • I am in the process of returning the product since I cannot get it to work. I did run across the following entry in the "MountBackup.060810_2044.log" file in the WindowsHomeServer\logs directory:

    ---more stuff before

    AM 1530] OnProgress: UI progress = 81%
    [6/8/2010 9:13:57 AM  a88]       Cluster reads=59, writes=21, errors=0.  [782240:1]
    [6/8/2010 9:13:57 AM 1530] OnProgress: UI progress = 81%
    [6/8/2010 9:13:58 AM 1530] OnProgress: UI progress = 81%
    [6/8/2010 9:13:59 AM 1530] OnProgress: UI progress = 81%
    [6/8/2010 9:14:00 AM 1530] OnProgress: UI progress = 81%
    [6/8/2010 9:14:01 AM 1530] OnProgress: UI progress = 81%
    [6/8/2010 9:14:02 AM 1530] OnProgress: UI progress = 81%
    [6/8/2010 9:14:03 AM 1530] OnProgress: UI progress = 81%
    [6/8/2010 9:14:04 AM  110] ERROR: waiting for the read/write drive to appear failed at restoreoffproc.exe -v 0 -X 645925392
    [6/8/2010 9:14:04 AM  110] MountedRestoreHelper::UnMount() - Success with IOCTL_BACKUPREADER_DELETE_VOLUME IOCTL
    [6/8/2010 9:14:04 AM 1530] OnProgress: UI progress = 81%
    [6/8/2010 9:14:04 AM 1530] ERROR: RestoreHelper::Unable to mount drive. Error 10
    [6/8/2010 9:14:04 AM  a88] MountedRestoreHelper::GetClusterRequestFromDriver() - IoCtl returned 0x5
    [6/8/2010 9:14:04 AM  a88] Got a invalid cluster request, this is okay
    [6/8/2010 9:14:04 AM  a88] MountedRestoreHelper::GetClusterRequestFromDriver() - returned 0x3EE
    [6/8/2010 9:14:04 AM  a88] RestoreHelper::T_ClusterThread - an error occurred (22), closing up the driver
    [6/8/2010 9:14:04 AM  a88] Total cluster reads=59, writes=24, errors=0.
    [6/8/2010 9:14:04 AM  110] Exiting thread...
    [6/8/2010 9:14:33 AM 1130] Calling m_Restore.UnMountDrive
    [6/8/2010 9:14:33 AM 1130] m_Restore.UnMountDrive returned

    ---end

    Note there were a large amount of successful operations before the above. I am not sure if the above sheds any light on the issue, especially the first ERROR, since we already know that the problem is related to the client not being able to mount the virtual drive, but perhaps someone here can decipher what is really going on and hopefully a solution.

    Thanks for any help.

    Mike

    Thursday, June 10, 2010 5:11 AM