locked
Volume Failing Notices Continue......but RRS feed

  • Question

  • I still get a volume failing error every two weeks or so. I installed the addin Home Server Smart and it reports all is OK.  See the screenshot http://prntscr.com/40z1

    Has this ever been linked to a bug? My server is fairly new.
    Thursday, February 18, 2010 2:08 PM

All replies

  • Do you run chkdsk when you get the warning? What does it report?
    I'm not on the WHS team, I just post a lot. :)
    Thursday, February 18, 2010 2:43 PM
    Moderator
  • Yes.  It showed no bad sectors.  I will run chkdsk again the next time it appears.  I've read a number of people have been seeing this recently.  What is likely the cause?
    Thursday, February 18, 2010 2:57 PM
  • I said I would post results of CHKDSK of WHS when I recieved the volume failing issue.  Here it is http://prntscr.com/49v8  Any ideas why this issue is continuing?
    Monday, February 22, 2010 1:15 PM
  • You need to do a check disk with repair - you have errors on your D: drive:
    http://social.microsoft.com/Forums/en-US/whsfaq/thread/b5372407-1f24-4eff-9092-069c4b4f0cee

    If you read the logs you posted you will see it says "Windows founds problems with the file system" - you need to use the parameters exactly as given in the referenced post to fix these errors.


    --
    Monday, February 22, 2010 3:44 PM
  • Since I already know what the logs say and what drive the errors are on do I still use the command below or just use CHKDSK /F?

    net stop pdl

    net stop whsbackup

    chkdsk D: /x /r 

    chkdsk C: /x /r

    for /d %%1 in (C:\fs\*) do start chkdsk /x /r %%1
    Monday, February 22, 2010 4:12 PM
  • As you only ave one disk you might as well do a chkdsk /r on D:

    Personally I prefer to have the system reboot and check the disk rather than dismount and remount the volume.  Also I tend to prefer the /r option which tests the whole disk.
    --
    Monday, February 22, 2010 4:30 PM
  • I am running the command above.  It finshed D and now goes to C but states "CHKDSK cannot run because the volume is in use by another process.  Do you want to schedule this volume to be checked the next time the system restarts?"

    Should I say yes or kill some process so it can run?  I am not sure what process is running.     
    Monday, February 22, 2010 8:08 PM
  • I am running the command above.  It finshed D and now goes to C but states "CHKDSK cannot run because the volume is in use by another process.  Do you want to schedule this volume to be checked the next time the system restarts?"

    Should I say yes or kill some process so it can run?  I am not sure what process is running.     
    It's the OS that's running.  :)

    Although your previous chkdsk showed no signs of problems on the C partition, I would hit yes, reboot your server and let it run anyway...
    Monday, February 22, 2010 8:28 PM
    Moderator
  • OK. How do errors get on a drive that I access vary rarely unless through the console?

    Monday, February 22, 2010 8:51 PM
  • Here is the 2nd CHKDSK run of D drive.  http://prntscr.com/4b3m
    Tuesday, February 23, 2010 12:17 AM
  • Can you please, please run chkdsk /r on that drive, as you were asked previously? Your screen shots repeatedly show you running chkdsk with no parameters, which won't fix a darned thing.
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, February 23, 2010 2:29 AM
    Moderator
  • Here's the chkdsk /r on D drive http://prntscr.com/4bed
    Tuesday, February 23, 2010 6:16 AM
  • The 3rd last line reads:
    "Windows has made corrections to the file system"

    This means the errors have probably been fixed.  If you run chkdsk /r again it should come back with words to the effect of everything is fine - you don't need to post us the screen shot again - just the information that is important.  Now you shouldn't get a warning of a failing volume.  If you do then perhaps you should look into replacing the disk.


    Also it's probably easier and gives users here some traceability (once your prntscr images have expired) if you just copy and paste the logs here rather than provide screen shots of text files.  Though in the case of chkdsk output there are online a few lines of interest.


    --
    Tuesday, February 23, 2010 1:33 PM
  • OK. How do errors get on a drive that I access vary rarely unless through the console?


    Basically, Hard Drives wear out over time.  Even a new hard drive can fail in a short space of time.  Also you may not be accessing the drive but Windows Home Server is using it for storing your backups and file duplication.
    --
    Tuesday, February 23, 2010 1:37 PM
  • So far no more errors (albeit a little to early to tell) but it does seem to perform a little better.
    Thursday, February 25, 2010 2:16 AM
  • This happened again today http://prntscr.com/4xsn .  Anyone know WHY?  My server doesn't show any bad sectors.

    Sunday, March 7, 2010 12:20 AM
  • Hi,

    Again you need to run a chkdsk /r on all your drives according to this FAQ:
    http://social.microsoft.com/Forums/en-US/whsfaq/thread/b5372407-1f24-4eff-9092-069c4b4f0cee

    If it were me, I would remove the drive from your Windows Home Server and replace it with another unit.

    Cheers,
    Al
    --
    Monday, March 8, 2010 2:31 PM
  • ...  My server doesn't show any bad sectors.

    What tool are you using that tells you that?
    I'm not on the WHS team, I just post a lot. :)
    Monday, March 8, 2010 3:26 PM
    Moderator
  • Doesn't chkdsk report this?  If not what tool can you use? Also I use the addin Home Server Smart.  It doesn't show any bad sectors either.

    Friday, March 12, 2010 7:56 PM