locked
Backup failure on 2nd desktop hard drive RRS feed

  • Question

  • Looking for help on a failed backup.

     

    My EX475 is working exactly as expected in the 12 hours it's been up and running except for one part of my backup.

     

    I have a Dell with two SATA drives in it. When running backup the c: drive backups up fine. The other drive (F: on my machine) has failed 2x to back up. Once as part of the intitial backup and then again as a manually forced 2nd backup attempt for this drive only.

     

    I get an I/O error with something called "COM exception"

     

    The drive works flawlessly otherwise.

     

    Friday, December 28, 2007 3:10 PM

Answers

  • Try running a chkdsk /r on the machine & drive that is giving you trouble.

    It sounds like there could be drive failure or possible corrupt data.

    Are you seeing anything in the event viewer? Specifically CRC errors?
    Friday, December 28, 2007 3:20 PM

All replies

  • Try running a chkdsk /r on the machine & drive that is giving you trouble.

    It sounds like there could be drive failure or possible corrupt data.

    Are you seeing anything in the event viewer? Specifically CRC errors?
    Friday, December 28, 2007 3:20 PM
  • Jon thanks for the quick response.

     

    The drive works fine but has nothing critical on it so i can copy data off and reformat if that will solve the issue.

     

    Just curious what the possible causes might be and how to avoid from recurrence.

     

    Steve

     

    Friday, December 28, 2007 3:26 PM
  • Thats a little extreme plus you will never know what caused the issue.

    Let's start by simple chkdsk /r and then maybe a defrag.

    Some times power outages or other forms of unexpected shutdowns may cause open file handles (specifially stale ones)

    The chkdsk should verify all indexes and correct any problem so long as there is not a physical sector damaged.

    So give it a go and post your results.
    Friday, December 28, 2007 3:30 PM
  • Jon

     

    Your suggestion worked. After running chkdsk, which uncovered some file errors, the drive backedup correctly.

     

    Thanks again for the help!

     

    Steve

     

    Saturday, December 29, 2007 12:42 AM
  • Glad I could help.

    Kindly mark my post as answered as to keep this board clean.

    Please do not hesitate to post me any questions you may have.

    I will always do my best to answer them promptly.
    Saturday, December 29, 2007 12:46 AM
  • Stupid question.

    I see threads that are marked answered but i don't see how to do it.
    Saturday, December 29, 2007 1:36 AM
  • Steve, you posted as a comment. I have switched the original post to a question, and marked Jon's answer.
    Saturday, December 29, 2007 2:41 AM
    Moderator
  • Jon,

     

    I am having the same exact problem.

     

    I have installed Windows Home Server and connected 3 PC’s to the server.

     

    The automatic backups are working fine for 2 of the PC’s.

     

    One of the PC’s is experiencing an error on the backup.

     

    The problem PC is a Dell XPS420 running Windows XP Professional Service Pack 2 (build 2600.)  The PC has 2 500GB Serial ATA hard drives.  The system is new as of January 2008.  There have not been any hardware failures.

     

    The backup of the drive C: completes OK.  The second drive that I have set as drive E: gets the following error:

    Failure Details for Volume (Local Disk):

    An unexpected exception occurred on the computer.

    NullReferenceException

    Object reference not set to an instance of an object.

     at

    Microsoft.HomeServer.Backup.BackupOp.BackupOperation.IsSamePath(DirectoryInfo di, String[] path)

     at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.GetExcl

     

    The event log shows:

    Received abort message from SYSA with reason 7.

     

    I have done some research on this and have followed your suggestion of running a CHKDSK E: /F /R.  I have taken the drive out of the backup.  I then deleted all backups of the PC and than run the CHKDSK.

     

    I am continuing to experience this error.

     

    I appreciate any help that may resolve this problem.

     

    Thanks.

     

    Curtis

    Thursday, April 10, 2008 1:49 PM