locked
SBS2008 Standard Complete PC Restore failed with (0x80070495) RRS feed

  • Question

  • Urgent help needed!  I am trying to recover my SBS2008 standard machine after 
    a RAID controller failure.  I removed the dead adaptec 51645 and am using 2 
    1TB RAID1 on the ICH9R.  I then proceeded to initiate Windows complete PC 
    restore with the SBS2008 standard disc.
    
    The old RAID on the 51645 is only 720GB large so the new 1TB RAID1 should be 
    large enough for the restore.
    
    But I keep on getting "The Volume ID could not be found. (0x80070495)" 
    error.  Nothing seems to be helping.
    
    So please help!!!!
    Sunday, October 11, 2009 2:07 PM

Answers

  • I somehow managed to rescue the server thru a lot of brute force efforts.....  Essentially, the problem seems to be that the bootsect config has been corrupted on the backup images.

    Symptoms:
    1)  No concrete errors from WSB eventlog.
    2)  When trying the repair option from the SBS2008DVD, Unknown on Unknown device, Windows 2008 may appear at the Select OS to repair dialog box.  Or it could be blank for the new drive.
    3)  When attempting complete PC Restore, operation will fail despite having enough HD space with error:
    "The Volume ID could not be found. (0x80070495)"

    When I ended up doing:
    1)  Find a Server 2008 machine.  I need WSB that to access the backup image from the backup drive.  Logon with admin rights.
    2)  Attached the drive containing the backup to the Server 2008 machine.  The drive will be automatically assigned a letter but the user may not have access to the backup drive's content (yet).
    3)  Launch WSB.
    4)  Attempt some recovery operation with WSB.  For eg, restore some directories from the backup image onto a temp location.  This gives the system access to the backup drive contents.
    5)  At this point, open up a windows explorer, and look for the backup VHDs on the backup drive via the drive letter.  Copy them out to a separate directory.  The VHDs will be named with GUIDs, rename them to shorter filenames.
    6)  Find a WS2008R2 or Windows 7 machine.  They have native VHD mounting capabilities.
    7)  Mount the VHDs via disk managements.
    8)  Use HDD cloning applications to clone the different VHDs to other hard disks.  I used Norton Ghost14 on my W7 machine.  Make sure to clone the system drive (C:) with options to set bootable(active) and copy MBR.
    9)  Move the cloned disk(s) back to the original server.  And reset BIOS to boot from the correct disk with the restored system partition.
    10)  Try booting.  If everything is ok, you will get an error regarding something about ntloader.exe.
    11)  Boot with the SBS2008DVD again.  Choose repair.  Go into a command prompt.
    12)  CD into C:\windows\system32.  This should be your restored system drive.
    13)  fire up bcdedit.  Output will probably show unknown in several entries.
    14) Reset the unknown entries with commands like bcdedit /set {default} device partition=C:

    At this point, reboot.  I was able to successfully recover the server this way.  Definitely a real hassle.  How the BCD on the backup images got corrupted, I have no idea.  And this shouldn't be so difficult to fix as all the underlying data is fine........

    • Marked as answer by laim Wednesday, October 14, 2009 3:07 AM
    Wednesday, October 14, 2009 3:04 AM

All replies


  • Please confirm if you are using the option "Recreate Disks" to restore to new hard-disk.

    You can use the following CLI command
    wbadmin start sysrecovery  -version:<VersionIdentifier> -backupTarget:{<VolumeHostingBackup> | <NetworkShareHostingBackup>}
    [-machine:<BackupMachineName>] [-restoreAllVolumes] [-recreateDisks]
    for more details about the command line please refer http://technet.microsoft.com/en-us/library/cc742118(WS.10).aspx




    Thanks, Chirag G [MSFT] -------------------------------------------------------------------------------- - This posting is provided "AS IS" with no warranties, and confers no rights
    • Proposed as answer by Chirag Gupta Monday, October 12, 2009 5:52 AM
    Monday, October 12, 2009 5:52 AM
  • I just used the Complete PC Recovery GUI.  Is that the same?
    Monday, October 12, 2009 2:21 PM
  • Please select option "Format and repartition disks" on the "Choose additional restore options" page while doing the recovery and update if you still see any issues.

     

    Please refer http://technet.microsoft.com/en-us/library/cc755163.aspx for UI flow details.


    Thanks, Chirag G [MSFT] -------------------------------------------------------------------------------- - This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, October 13, 2009 2:20 AM
  • Please select option "Format and repartition disks" on the "Choose additional restore options" page while doing the recovery and update if you still see any issues.

     

    Please refer http://technet.microsoft.com/en-us/library/cc755163.aspx for UI flow details.


    Thanks, Chirag G [MSFT] -------------------------------------------------------------------------------- - This posting is provided "AS IS" with no warranties, and confers no rights

    Already checked and still no go.  Same error.  I am giving up and rebuilding the SBS2008, which will be a pain......
    Tuesday, October 13, 2009 2:22 AM
  • In worst case, you can recover your system by creating volume by hand and recovering volumes instead of complete system; and then fixing the boot entries. I will share the details once you share the logs with me.

    Please share the following details
    1. Logs present in \windows\logs directory.

    you can send the details to chgupta-nospam@microsoft.com
    please use only the highlighted part in the email address. this is to avoid spam.
    Thanks, Chirag G [MSFT] -------------------------------------------------------------------------------- - This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, October 13, 2009 5:08 AM
  • Thanks Gupta, By logs, are you talking about in the Complete PC recovery environment?
    Tuesday, October 13, 2009 5:09 AM
  • I somehow managed to rescue the server thru a lot of brute force efforts.....  Essentially, the problem seems to be that the bootsect config has been corrupted on the backup images.

    Symptoms:
    1)  No concrete errors from WSB eventlog.
    2)  When trying the repair option from the SBS2008DVD, Unknown on Unknown device, Windows 2008 may appear at the Select OS to repair dialog box.  Or it could be blank for the new drive.
    3)  When attempting complete PC Restore, operation will fail despite having enough HD space with error:
    "The Volume ID could not be found. (0x80070495)"

    When I ended up doing:
    1)  Find a Server 2008 machine.  I need WSB that to access the backup image from the backup drive.  Logon with admin rights.
    2)  Attached the drive containing the backup to the Server 2008 machine.  The drive will be automatically assigned a letter but the user may not have access to the backup drive's content (yet).
    3)  Launch WSB.
    4)  Attempt some recovery operation with WSB.  For eg, restore some directories from the backup image onto a temp location.  This gives the system access to the backup drive contents.
    5)  At this point, open up a windows explorer, and look for the backup VHDs on the backup drive via the drive letter.  Copy them out to a separate directory.  The VHDs will be named with GUIDs, rename them to shorter filenames.
    6)  Find a WS2008R2 or Windows 7 machine.  They have native VHD mounting capabilities.
    7)  Mount the VHDs via disk managements.
    8)  Use HDD cloning applications to clone the different VHDs to other hard disks.  I used Norton Ghost14 on my W7 machine.  Make sure to clone the system drive (C:) with options to set bootable(active) and copy MBR.
    9)  Move the cloned disk(s) back to the original server.  And reset BIOS to boot from the correct disk with the restored system partition.
    10)  Try booting.  If everything is ok, you will get an error regarding something about ntloader.exe.
    11)  Boot with the SBS2008DVD again.  Choose repair.  Go into a command prompt.
    12)  CD into C:\windows\system32.  This should be your restored system drive.
    13)  fire up bcdedit.  Output will probably show unknown in several entries.
    14) Reset the unknown entries with commands like bcdedit /set {default} device partition=C:

    At this point, reboot.  I was able to successfully recover the server this way.  Definitely a real hassle.  How the BCD on the backup images got corrupted, I have no idea.  And this shouldn't be so difficult to fix as all the underlying data is fine........

    • Marked as answer by laim Wednesday, October 14, 2009 3:07 AM
    Wednesday, October 14, 2009 3:04 AM
  • Although I am glad to have everything back up and running without the need to recreate AD and everything else that goes with it, I do believe there are some concerns from this approach.

    1)  Can WSB be more intelligent and gives more concrete warnings on the images that it made?  Pretty obvious that the BCD was corrupted on the image (could be on the original disks as well) and it will not be able to be restored.  When didn't it record as such in the eventlogs?
    2)  The Complete PC recovery should be more intelligent in explaining the issue.  I also find no concrete reference of the error in Technet knowledge base.  The only thing that pointed me to restoring via the VHDs themselves were another post here earlier (kudos to him) that had similar problem and was able to mount via Hyper-V R2.
    3)  Potential Serious Security issue.  I was able to mount  the VHD on WS2008R2 and W7 machines on a different domain from the original SBS2008 server.  I was able to browse the hard disks after taking ownership of restricted directories.........
    Wednesday, October 14, 2009 3:21 AM
  • I had the same problem, and I believe I found a better solution than the one presented here.  In my case all I had to do to restore our server was to run the restore command from the command line.  I spent a foolish 12 hours trying to get Microsoft's "Complete PC Restore" wizard to run the job and trying all kinds of work arounds similar to the one above, before I finally went back to the starting point and tried the wbadmin command.  It is easier than I had expected.  Here's what you do.


    1. List the backups you have:

    wbadmin get versions -backupTarget:E:  

     

    (change "E:" to the drive that has your backups on it.  If you aren't sure which drive has the backups take a step back and just try "dir c:", "dir d:", etc until you find the drive that has a directory in it called "WindowsImageBackups" or something similar)

     

    2. Initiate restore:


    wbadmin start sysrecovery -version:03/31/2011-09:00 -backuptarget:E: -Recreateddisks

    (Change the version and backup target in this example to match the version of your backup, which you identified in step 1.  I recommend also that you disconnect any extraneous drives aside from your drive containing the backups and the drive you are restoring onto; this is not necessary, but it eliminates the possibility of a mistake.)


    That's it. Quick and easy.  There is more info on wbadmin here: http://technet.microsoft.com/en-us/library/cc754015(WS.10).aspx


    Good luck,

    Dylan Hall

    Geeks on Wheels

    www.geeks-on-wheels.net


    Dylan Hall Small Business Specialist Geeks on Wheels www.geeks-on-wheels.net
    • Proposed as answer by Dan McTavish Monday, August 29, 2011 8:29 PM
    Tuesday, August 2, 2011 6:45 PM
  • I had the same problem, and I believe I found a better solution than the one presented here.  In my case all I had to do to restore our server was to run the restore command from the command line.  I spent a foolish 12 hours trying to get Microsoft's "Complete PC Restore" wizard to run the job and trying all kinds of work arounds similar to the one above, before I finally went back to the starting point and tried the wbadmin command.  It is easier than I had expected.  Here's what you do.


    1. List the backups you have:

    wbadmin get versions -backupTarget:E:  

     

    (change "E:" to the drive that has your backups on it.  If you aren't sure which drive has the backups take a step back and just try "dir c:", "dir d:", etc until you find the drive that has a directory in it called "WindowsImageBackups" or something similar)

     

    2. Initiate restore:


    wbadmin start sysrecovery -version:03/31/2011-09:00 -backuptarget:E: -Recreateddisks

    (Change the version and backup target in this example to match the version of your backup, which you identified in step 1.  I recommend also that you disconnect any extraneous drives aside from your drive containing the backups and the drive you are restoring onto; this is not necessary, but it eliminates the possibility of a mistake.)


    That's it. Quick and easy.  There is more info on wbadmin here: http://technet.microsoft.com/en-us/library/cc754015(WS.10).aspx


    Good luck,

    Dylan Hall

    Geeks on Wheels

    www.geeks-on-wheels.net


    Dylan Hall Small Business Specialist Geeks on Wheels www.geeks-on-wheels.net

    Thank you Dylan, your information was a total life saver.

    Dan

    Monday, August 29, 2011 8:29 PM
  • I had the same problem, and I believe I found a better solution than the one presented here.  In my case all I had to do to restore our server was to run the restore command from the command line.  I spent a foolish 12 hours trying to get Microsoft's "Complete PC Restore" wizard to run the job and trying all kinds of work arounds similar to the one above, before I finally went back to the starting point and tried the wbadmin command.  It is easier than I had expected.  Here's what you do.


    1. List the backups you have:

    wbadmin get versions -backupTarget:E:  

     

    (change "E:" to the drive that has your backups on it.  If you aren't sure which drive has the backups take a step back and just try "dir c:", "dir d:", etc until you find the drive that has a directory in it called "WindowsImageBackups" or something similar)

     

    2. Initiate restore:


    wbadmin start sysrecovery -version:03/31/2011-09:00 -backuptarget:E: -Recreateddisks

    (Change the version and backup target in this example to match the version of your backup, which you identified in step 1.  I recommend also that you disconnect any extraneous drives aside from your drive containing the backups and the drive you are restoring onto; this is not necessary, but it eliminates the possibility of a mistake.)


    That's it. Quick and easy.  There is more info on wbadmin here: http://technet.microsoft.com/en-us/library/cc754015(WS.10).aspx


    Good luck,

    Dylan Hall

    Geeks on Wheels

    www.geeks-on-wheels.net


    Dylan Hall Small Business Specialist Geeks on Wheels www.geeks-on-wheels.net

    Thank you Dylan, your information was a total life saver.

    Dan

    Dear Dylan,

     

    thank you so much for your solution, you have saved me a lot of trouble. Your solution works perfect without any trouble and i appreciate very much your suggestion to solve the problem.

    In don't understand the difference between the GUI and command line way, but recovery dosn't work with GUI. In my opinion MS should pay for all the trouble. It is not acceptable that they don't fix such problems and you have to search hours in the web for a solution.

    Thanks

    Manuel

     

    Sorry for my bad english but i'm comming from germany ;-)

    Saturday, October 29, 2011 10:06 AM
  • I had to do some extra activity around using wbadmin:

    1. Use DISKPART to clean my existing drive (which still worked OK in my case); list disk, select disk 0, clean, exit.

    2. After using wbadmin start..., at the confirmation question of Yes or No, unplug my USB boot device which I used to get the DOS prompt up on a bare metal instance.

    Hope that helps.

    Thursday, June 6, 2013 1:00 AM
  • Could anyone advise me how to do this on a VMware  vm?

    If I restore using disk image vmware has not yet acquired an ip address and if I install to the point where the ip is known I get sent back to boot from disk so I can never get to the path of the backup, obviously there must be a way.... anyone got any Noob pointers?


    sparky

    Wednesday, July 17, 2013 8:26 AM
  • Congratulation Dylan :

    I've restored a sbs2008 on another RAID with your command : wbadmin start sysrecovery -version:03/31/2011-09:00 -backuptarget:E: -RecreateDisks

    Thanks a lot.

    dav

    Sunday, January 26, 2014 3:33 PM
  • wbadmin start sysrecovery -version:03/31/2011-09:00 -backuptarget:E: -Recreateddisks

    Those with multiple partitions saved as part of the backup might want to add the "-restoreAllVolumes" option

    https://technet.microsoft.com/en-us/library/cc742118(v=ws.10).aspx

    revising Dylan's example...

    wbadmin start sysrecovery -version:03/31/2011-09:00 -backuptarget:E: -restoreAllVolumes -Recreateddisks


    • Edited by tricky300 Tuesday, August 11, 2015 2:29 PM
    Monday, August 10, 2015 11:17 PM
  • I wasted about 12 hours on this very same issue.  Thank you for pointing out that reverting to the command line is often the solution... I preach this and was very thankful to see your post about it.  These situations are kind of one-offs, but when they happen your advice is so timely.  Thanks again.
    Sunday, September 10, 2017 4:41 AM