none
Backup Status "Failed" RRS feed

  • Question

  • I recently had C drive fail on my XP Pro machine. I installed a new disk (larger) and did a successful recovery from WHS. Absolutely no problems, it went perfectly. Now I get the failed backup status on my regular backups. I tried today to do a manual backup and it starts but fails after 1%. The details in the backup manager states "an error occurred while reading or writing from the computers hard drive C: (I'm backing up 3 drives on that computer but it's not getting past C drive). I presently back up two computers on my WHS, a laptop and a desktop. The laptop backups are fine. The error is on the desktop.

    One other bit of information although it may not be relevant. The original disk was IDE and the new one is SATA. I don't know if that could possibly be the problem. I reconfigured the drives to backup after recovering. WHS sees the 3 drives as C,D and K. I was able to backup (separately) the other two IDE drives. It just seems to be the SATA drive © that is the problem. At least that's the only difference I can think of .

    I ran chkdsk /r /f and repaired quite a few clusters but.....the backup of C still fails in the first 1%. Another oddity is that it shows "backed up" in the Computers and Backup screen but a failed status in the view backups screen. I'll take another suggestion...I'm sure out of ideas.

    If anyone has had this problem after a recovery and found a solution I would appreciate any suggestions. Everything else is working fine. No problems with the computer or network access. The backups just fail.
    Friday, November 13, 2009 9:05 PM

Answers

  • Thanks Ken,

    I have, on several occasions, reconfigured the computer in the console. I have even reconfigured to back up D and K drives, completed them and then reconfigured for C only. The backups of D & K are good but I still get the failure almost immediately on C. Do you know, if I just rename the computer, would I be able to complete a separate round of backups without loosing my past backups of that computer? That way I might learn something but I'm not sure what!!!
    Renaming the computer won't allow a new backup set (WHS uses a GUID for identification, not the computer name).  Since the hard drive is obviously having issues (you said chkdsk "repaired quite a few clusters"), my guess is that hard drive is still failing (and, to be honest, should be replaced).  You could start by running chkdsk /r on the C drive again and see what happens.
    • Marked as answer by rtmichael Tuesday, November 24, 2009 1:57 PM
    Saturday, November 14, 2009 3:54 PM
    Moderator

All replies

  • You should start the Windows Home Server console and reconfigure backups for the computer causing the problem. Most probably, there is a phantom "C:" drive which is now "missing", and Windows Home Server is now treating the restored drive as a new one (which it is, really).
    I'm not on the WHS team, I just post a lot. :)
    Friday, November 13, 2009 9:31 PM
    Moderator
  • Thanks Ken,

    I have, on several occasions, reconfigured the computer in the console. I have even reconfigured to back up D and K drives, completed them and then reconfigured for C only. The backups of D & K are good but I still get the failure almost immediately on C. Do you know, if I just rename the computer, would I be able to complete a separate round of backups without loosing my past backups of that computer? That way I might learn something but I'm not sure what!!!
    Saturday, November 14, 2009 3:31 AM
  • Thanks Ken,

    I have, on several occasions, reconfigured the computer in the console. I have even reconfigured to back up D and K drives, completed them and then reconfigured for C only. The backups of D & K are good but I still get the failure almost immediately on C. Do you know, if I just rename the computer, would I be able to complete a separate round of backups without loosing my past backups of that computer? That way I might learn something but I'm not sure what!!!
    Renaming the computer won't allow a new backup set (WHS uses a GUID for identification, not the computer name).  Since the hard drive is obviously having issues (you said chkdsk "repaired quite a few clusters"), my guess is that hard drive is still failing (and, to be honest, should be replaced).  You could start by running chkdsk /r on the C drive again and see what happens.
    • Marked as answer by rtmichael Tuesday, November 24, 2009 1:57 PM
    Saturday, November 14, 2009 3:54 PM
    Moderator
  • Thanks for your assistance. I was traveling last week but upon return I ran chkdsk a few times until all bad clusters had been corrected and was able to get a successful backup yesterday.

    Thanks again!
    Tuesday, November 24, 2009 1:58 PM