locked
CHKDSK on WHS RRS feed

  • Question

  • A few days ago, I started to get problems after installing february updates. I tought the updates were the problems. So, after a bit of testing, I decided to uninstall the updates until I find the real problem. In the meantime, I submitted a bug on Connect. Lara Jones from Microsoft examinate the cab file I provided. There is always some errors. All my drives are WD SATA and 1 IDE. I ran the diagnostic tool on my drives and no errors were found. So, this morning, I checked the event log again and CHKDSK ran around midnight. Because the /F parameter was not specified, it did not corrected the errors.

    Getting tired of always having errors, I then decided to run CHKDSK manually with specifying the /F parameter, which is suppose to fix the errors. I did the following command:

    chkdsk /f /r
    for /d %%1 in (C:\fs\*) do start chkdsk /f /r %%1

    After a while, the connector icon turned to yellow, saying I have file conflicts. Checking the file conflicts message, it says it can't find the drive.

    A little bit later, the icon turned red, saying the backup service is not running.

    I'm now a little scared with that happening, to lose some files. Is this a normal behavior (not me being scared!) the icon turning yellow and then red when running CHKDSK.

    Thanks for your answers,

    Klode
    Thursday, March 5, 2009 2:53 PM
    Moderator

Answers

  • Klode said:

    I just want to point to you the following:

    1- Errors started on february 27th, shortly after installing the updates.

    2- I lost the entire backup database on sunday morning march 1st after the scheduled weekly clean-up.

    3- I've never had problems about opening backup at 79% for which the update was for.

    4- I've always been able to restore any of my computers when needed.

    My WHS software is in french. I don't know if it can make any difference, but just mention it in case.

    When using the toolkit, it can never find the software share, because in french it's called "Logiciel".

    Thanks,

    Klode



    Here are the comments back from the developer:

    The errors which seem to be going on here would probably not be caught by CHKDSK, even with /R.  It appears that as we read data from certain files, sometimes we get correct data, other times we’re getting corrupted data.  In both cases, no error is being reported, as if everything was OK.

     

    The most evil disk errors are those which are not reported, where incorrect data is returned with no indication of failure.  In this particular case, we’re reading through a file which should be full of sorted numbers, but some numbers arrive out of order.  Next time we see errors, but in a different place.

     

    All this suggests that something in this server’s disk system -- either drives, cables, controllers, drivers -- is unreliable and shouldn’t be trusted with the user’s data.

     

    Has there been any change in this server’s hardware recently?


    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Friday, March 6, 2009 5:38 PM
    Moderator
  • It turned out to be a faulty SATA cable worn at one end, showing wires. Just finishing reinstallation and installing all updates from the update button in the console. So far so good until now.

    Klode

    Monday, March 9, 2009 4:12 PM
    Moderator

All replies

  • Yes, it is normal. Anytime you unmount a volume, the backup service will stop running and file conflicts will appear.

    Please see this post: http://social.microsoft.com/Forums/en-US/whsfaq/thread/7ef4db6c-4a73-42e7-b79e-cacd41365442 which cautions you that this may happen.

    A Note: If you have physical errors on the disk due to a bad disk, you may lose data.

    Thank you
     

    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Thursday, March 5, 2009 3:02 PM
    Moderator
  • Thank you Lara for your quick answer. That makes me a little more confident. I know if you have physical error on a disk, you may lose data. I don't believe I have that on one of my drives. After running the diagnostic tool on all the drives, it all came back with no errors. May be you can confirm that after looking to the answer sent to my e-mail.

     Hi, This has been resolved external as this is an issue with your HDD. Every time we read the Index.4096.dat file, we get different bytes. [result from searching for Finished on all the backup logs] backup-022209.log:[2009-02-22 00:02:02 b84] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022209.log:[2009-02-22 01:03:01 b84] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022209.log:[2009-02-22 21:18:57 ba8] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022309.log:[2009-02-23 14:38:06 bcc] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022309.log:[2009-02-23 15:05:52 ba8] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022409.log:[2009-02-24 19:03:44 bbc] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022709.log:[2009-02-27 14:04:12 b98] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022709.log:[2009-02-27 16:50:30 b90] Checker: Finished checking backup database consistency, 3 error(s) found. backup-022709.log:[2009-02-27 17:23:22 b98] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022709.log:[2009-02-27 17:32:20 bc0] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 00:00:31 bc0] Checker: Finished checking backup database consistency, 5 error(s) found. backup-030109.log:[2009-03-01 00:00:31 bc0] CleanupScheduler: Finished cleanup backup-030109.log:[2009-03-01 09:16:58 bb8] Checker: Finished checking backup database consistency, 2 error(s) found. backup-030109.log:[2009-03-01 09:20:29 13cc] Checker: Finished checking backup database consistency, 2 error(s) found. backup-030109.log:[2009-03-01 09:42:16 13cc] Checker: Finished repairing backup database. backup-030109.log:[2009-03-01 09:42:17 13cc] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 09:42:17 1594] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 09:44:29 1594] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 09:44:31 1594] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 09:44:31 1594] CleanupScheduler: Finished cleanup backup-030109.log:[2009-03-01 13:19:59 bcc] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030209.log:[2009-03-02 07:59:15 bb4] Checker: Finished checking backup database consistency, 0 error(s) found. The errors seem to vary from 3 to 0 to 5 and then 2 before repair is run at 2009-03-01 09:20:29. Comment from developer: "Interestingly the errors found are different every time consistency checker is run. They all are related to Index.4096.dat file (order errors or data.dat file missing because of a random dataoffset in the index file)." Thank you Lara Jones [MS]

    Hopefully, I hope running CHKDSK will fix these errors for good now.

    Klode
    Thursday, March 5, 2009 3:16 PM
    Moderator
  • Klode said:

    Thank you Lara for your quick answer. That makes me a little more confident. I know if you have physical error on a disk, you may lose data. I don't believe I have that on one of my drives. After running the diagnostic tool on all the drives, it all came back with no errors. May be you can confirm that after looking to the answer sent to my e-mail.

     Hi, This has been resolved external as this is an issue with your HDD. Every time we read the Index.4096.dat file, we get different bytes. [result from searching for Finished on all the backup logs] backup-022209.log:[2009-02-22 00:02:02 b84] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022209.log:[2009-02-22 01:03:01 b84] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022209.log:[2009-02-22 21:18:57 ba8] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022309.log:[2009-02-23 14:38:06 bcc] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022309.log:[2009-02-23 15:05:52 ba8] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022409.log:[2009-02-24 19:03:44 bbc] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022709.log:[2009-02-27 14:04:12 b98] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022709.log:[2009-02-27 16:50:30 b90] Checker: Finished checking backup database consistency, 3 error(s) found. backup-022709.log:[2009-02-27 17:23:22 b98] Checker: Finished checking backup database consistency, 0 error(s) found. backup-022709.log:[2009-02-27 17:32:20 bc0] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 00:00:31 bc0] Checker: Finished checking backup database consistency, 5 error(s) found. backup-030109.log:[2009-03-01 00:00:31 bc0] CleanupScheduler: Finished cleanup backup-030109.log:[2009-03-01 09:16:58 bb8] Checker: Finished checking backup database consistency, 2 error(s) found. backup-030109.log:[2009-03-01 09:20:29 13cc] Checker: Finished checking backup database consistency, 2 error(s) found. backup-030109.log:[2009-03-01 09:42:16 13cc] Checker: Finished repairing backup database. backup-030109.log:[2009-03-01 09:42:17 13cc] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 09:42:17 1594] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 09:44:29 1594] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 09:44:31 1594] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030109.log:[2009-03-01 09:44:31 1594] CleanupScheduler: Finished cleanup backup-030109.log:[2009-03-01 13:19:59 bcc] Checker: Finished checking backup database consistency, 0 error(s) found. backup-030209.log:[2009-03-02 07:59:15 bb4] Checker: Finished checking backup database consistency, 0 error(s) found. The errors seem to vary from 3 to 0 to 5 and then 2 before repair is run at 2009-03-01 09:20:29. Comment from developer: "Interestingly the errors found are different every time consistency checker is run. They all are related to Index.4096.dat file (order errors or data.dat file missing because of a random dataoffset in the index file)." Thank you Lara Jones [MS]

    Hopefully, I hope running CHKDSK will fix these errors for good now.

    Klode



    Hi,

    I'm requesting assistance with this answer as a developer actually approached me about this bug in person and  I'd like to confirm the expected results before I answer you.

    Thanks!
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Thursday, March 5, 2009 5:37 PM
    Moderator
  • I just want to point to you the following:

    1- Errors started on february 27th, shortly after installing the updates.

    2- I lost the entire backup database on sunday morning march 1st after the scheduled weekly clean-up.

    3- I've never had problems about opening backup at 79% for which the update was for.

    4- I've always been able to restore any of my computers when needed.

    My WHS software is in french. I don't know if it can make any difference, but just mention it in case.

    When using the toolkit, it can never find the software share, because in french it's called "Logiciel".

    Thanks,

    Klode
    Thursday, March 5, 2009 5:55 PM
    Moderator
  • Klode said:

    I just want to point to you the following:

    1- Errors started on february 27th, shortly after installing the updates.

    2- I lost the entire backup database on sunday morning march 1st after the scheduled weekly clean-up.

    3- I've never had problems about opening backup at 79% for which the update was for.

    4- I've always been able to restore any of my computers when needed.

    My WHS software is in french. I don't know if it can make any difference, but just mention it in case.

    When using the toolkit, it can never find the software share, because in french it's called "Logiciel".

    Thanks,

    Klode



    Here are the comments back from the developer:

    The errors which seem to be going on here would probably not be caught by CHKDSK, even with /R.  It appears that as we read data from certain files, sometimes we get correct data, other times we’re getting corrupted data.  In both cases, no error is being reported, as if everything was OK.

     

    The most evil disk errors are those which are not reported, where incorrect data is returned with no indication of failure.  In this particular case, we’re reading through a file which should be full of sorted numbers, but some numbers arrive out of order.  Next time we see errors, but in a different place.

     

    All this suggests that something in this server’s disk system -- either drives, cables, controllers, drivers -- is unreliable and shouldn’t be trusted with the user’s data.

     

    Has there been any change in this server’s hardware recently?


    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Friday, March 6, 2009 5:38 PM
    Moderator
  • In addition to changes in the disk subsystem, you should also look to external causes. A power supply issue can have a trickle-down effect on other systems in the server, for example, or a power surge or loss of power may have caused a problem.

    I'm not on the WHS team, I just post a lot. :)
    Saturday, March 7, 2009 3:44 PM
    Moderator
  • Yes, there has been some changes. I added a controller card to add more sata ports and added 1 Tb drive which was connected on the new controller. After all issues arise, I removed the 1 Tb drive and the controller card as well.

    About running CHKDSK, there is always some errors found on the C drive  and 1 particular drive. CHKDSK ran for about 2 days checking all disks. I was able to see the results in the event viewer. Other drives came back with no errors. If I can copy the logs containing the errors, this might help to finally see what the exact problem is. I'll be back soon with the exact result of CHKDSK on the drives.

    This result is for both drives, system drive and 1 data drive. It translate like this:

    "Cleaning up minor inconsistencies on the drive."

    And it's not the first time I see this message. I didn't pay much attention since it was cleaning them. But never had on the other drives. This is what caught my attention this time because I check all events related to chkdsk.

    Ken, aout the power surge or power loss, I have a UPS connected to the server. As for the power supply, it's CoolerMaster 650 Watts.

    Thank you very much for your help,

    Klode
    Saturday, March 7, 2009 4:30 PM
    Moderator
  • It turned out to be a faulty SATA cable worn at one end, showing wires. Just finishing reinstallation and installing all updates from the update button in the console. So far so good until now.

    Klode

    Monday, March 9, 2009 4:12 PM
    Moderator