locked
I am unable to back up 1 of my computers to the WHS. RRS feed

  • Question

  • I have 5 computers connected to the server and 4 of them back up great with no problems. This particular computer was backing up regularly until a couple weeks ago. It is the main computer for the server, (The one I initially installed the software on). I can still open up the console and do everything in there. When I try to configure backup it keeps saying it failed and to check that the computer is turned on and connected to the network. And if I do a manual backup it starts out okay but shortly there after it fails and says the volume can not be found.

    I am running windows XP with service pack 3, and the windows home serve with power pack 3.

    Any help would be great!

    Thanks!


    Monday, April 12, 2010 2:48 PM

All replies

  • First thing is to run a chkdsk /r of all your drives in the client computer you are having trouble with.
    --
    Monday, April 12, 2010 2:59 PM
  • First thing is to run a chkdsk /r  of all your drives in the client computer you are having trouble with.
    --
    Okay, I ran that and I am still getting the same errors.  Although, when I went to run it  it said that another process was currently using the volume and asked if I wanted to run it the next time windows booted up. So I did it that way. Could it be that this other process is blocking Windows Home Server from accessing the hard drive? And how can I find out what this process is?
    Monday, April 12, 2010 4:54 PM
  • The operating is using the disk - bit of cryptic message I guess.  What was the output of the chkdsk /r ?


    --
    Monday, April 12, 2010 5:08 PM
  • Here's the output....  Doesn't look like there was anything that would be preventing the server from accessing my hard drive.

    Windows will now check the disk.                        
    Cleaning up minor inconsistencies on the drive.
    Cleaning up 2285 unused index entries from index $SII of file 0x9.
    Cleaning up 2285 unused index entries from index $SDH of file 0x9.
    Cleaning up 2285 unused security descriptors.
    CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    Free space verification is complete.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    Windows has made corrections to the file system.

     156280288 KB total disk space.
      79503612 KB in 125976 files.
         85180 KB in 19560 indexes.
             0 KB in bad sectors.
        315676 KB in use by the system.
          4096 KB occupied by the log file.
      76375820 KB available on disk.

          4096 bytes in each allocation unit.
      39070072 total allocation units on disk.
      19093955 allocation units available on disk.
    Monday, April 12, 2010 5:19 PM
  • Internal Info:
    00 02 03 00 8c 38 02 00 1f 34 03 00 00 00 00 00  .....8...4......
    9e 5f 00 00 02 00 00 00 bf 10 00 00 00 00 00 00  ._..............
    0e bc c1 0a 00 00 00 00 a4 ff cd ba 00 00 00 00  ................
    02 f6 87 20 00 00 00 00 78 3c e6 e5 06 00 00 00  ... ....x<......
    52 8b 1b d6 03 00 00 00 3c e6 91 ae 0b 00 00 00  R.......<.......
    99 9e 36 00 00 00 00 00 98 38 07 00 18 ec 01 00  ..6......8......
    00 00 00 00 00 f0 83 f4 12 00 00 00 68 4c 00 00  ............hL..

    Windows has finished checking your disk.
    Please wait while your computer restarts.


    Missed that part on the copy/paste.
    Monday, April 12, 2010 5:20 PM
  • Note that chkdsk found errors. Please try backing up again.
    I'm not on the WHS team, I just post a lot. :)
    Monday, April 12, 2010 5:44 PM
    Moderator
  • I tried backing up again, it got to about 17% and then I got the error saying that it could not find the volume. I also tried doing the  "Configure Backup" from the console window and I am still getting the same error that it cannot find the volume.
    Monday, April 12, 2010 6:11 PM
  • Also you may need to run chkdsk /r a few times to correct the errors - keep running it until it comes back 'clean' i.e. no errors.  It may be time to consider a new hard drive.
    --
    Monday, April 12, 2010 7:06 PM
  • Alright. I'll try that later on after work. Thanks for the help. I'll reply with some results later or tomorrow.
    Monday, April 12, 2010 7:09 PM
  • What security software are you running? Firewalls, virus scanners, and/or cloning software?
    Monday, April 12, 2010 10:20 PM
  • I have the Iolo System Mechanic Professional running on all the computers, and this is the only one that isn't connecting to the server and backing up. I know it sucks, I'm switching them all to  something new next week when I get my refund.
    Tuesday, April 13, 2010 1:20 AM
  • So I ran a chkdsk again last night and then tried to configure that backup again this morning and it started to scan the hard drive like normal, the progress bar moving slow at first, then it makes a couple big leaps and fills up and then I get the error message saying that the drive can't be accessed. So I tried a manual backup and it slowly climbed up to about 18% then jumped to 23 to 32 to 45% and then failed.  So it seems to me that either the hard drive is screwed up or that something is disrupting the connection between the server and my hard drive... Here's the output of chkdsk

    A disk check has been scheduled.
    Windows will now check the disk.                        
    Cleaning up minor inconsistencies on the drive.
    Cleaning up 3 unused index entries from index $SII of file 0x9.
    Cleaning up 3 unused index entries from index $SDH of file 0x9.
    Cleaning up 3 unused security descriptors.
    CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    Free space verification is complete.

     156280288 KB total disk space.
      79599304 KB in 126665 files.
         85376 KB in 19583 indexes.
             0 KB in bad sectors.
        316188 KB in use by the system.
          4096 KB occupied by the log file.
      76279420 KB available on disk.

          4096 bytes in each allocation unit.
      39070072 total allocation units on disk.
      19069855 allocation units available on disk.

    Internal Info:
    00 02 03 00 54 3b 02 00 93 39 03 00 00 00 00 00  ....T;...9......
    a2 5f 00 00 02 00 00 00 d6 07 00 00 00 00 00 00  ._..............
    0e bc c1 0a 00 00 00 00 12 01 af ba 00 00 00 00  ................
    38 3f fe 11 00 00 00 00 20 79 c5 ef 06 00 00 00  8?...... y......
    da 1c 1f d2 03 00 00 00 40 ec b8 a5 0b 00 00 00  ........@.......
    99 9e 36 00 00 00 00 00 98 38 07 00 c9 ee 01 00  ..6......8......
    00 00 00 00 00 20 5b fa 12 00 00 00 7f 4c 00 00  ..... [......L..

    Windows has finished checking your disk.
    Please wait while your computer restarts.
    Tuesday, April 13, 2010 1:51 PM
  • Every time you have posted chkdsk results there have been problems.  I would say your disk is faulty.
    --
    Tuesday, April 13, 2010 2:06 PM
  • Even "minor inconsistencies" can cause a backup to fail. Run chkdsk /r again, on all drives in your client computer.

    I assume, by the way, that you're still having no problems with other clients? They back up fine? You can open backups? When you boot the Restore CD from one of your clients, or run C:\Program Files\Windows Home Server\ClientRestoreWizard.exe on it, you're able to choose a backup? (Don't proceed too far with the Restore CD or ClientRestoreWizard; you don't want to actually restore a drive.)


    I'm not on the WHS team, I just post a lot. :)
    Tuesday, April 13, 2010 2:13 PM
    Moderator
  • I ran chkdsk /r a couple more times and still couldn't get it to back up. So I just assumed the hard drive was going the way of the buffalo and gave up on it. (But yes Ken, I could back up no problem with the other clients and use the restore CD too without a hitch). So I went out to do a few things for work yesterday afternoon and came back and System Mechanic was defragmenting the hard drive. So I just let it do that, and called it a day.

    Came in this morning and checked the server, low and behold the back up successful ran and completed last night. I guess the defrag fixed whatever was wrong.  Haha. So I guess if anyone else is having a problem like mine maybe all they need to do is defragment their hard drive.

    Just to double check I did do the "Configure Backup" and that is also working just fine. So it looks like everything is back to normal.

    Thanks for all the help though! I appreciate it. :)
    Wednesday, April 14, 2010 2:57 PM
  • I would still replace that disk when you can before you lose it totally.   A disk defrag would probably have moved the cluster that was causing problems to another location.  It's only a matter of time before that troublesome cluster becomes occupied again.  You have to weigh up if it's worth losing all your backups over it or not.
    --
    Wednesday, April 14, 2010 4:13 PM
  • Yea, I was thinking the same thing. I was just hoping to get it to back up so it'd be easier to transfer everything to the new drive.  Thanks again for the help.
    Thursday, April 15, 2010 3:39 PM