locked
Volume with name SYS is failing - Not RRS feed

  • Question

  • Since RC2 I've been getting this message on a fairly regular basis. I thought when I reformatted the drive and installed the released version it would go away but it didn't. I run repair and then chkdsk but no errors are ever found. Looking through the event logs finds no issues. I did a deep scan using the manufacture's tools and no errors found. I came across this thread but it didn't seem to come to any conclusions. I have serious doubts there is anything actually wrong with the drive. Is this a bug?
    Friday, December 28, 2007 1:45 AM

All replies

  • Give us details on your hardware configuration. It's possible that it's the drive, or the host bus adapter (motherboard chipset?) that's failing. Or it's possible that you have a driver issue. Or any of a number of other things.
    Friday, December 28, 2007 4:15 AM
    Moderator
  • The mobo is an ASUS K8V SE Deluxe which has a VIA K8T800 chipset. The CPU is an athlon XP 3000+. The drive is a Seagate ST3500830A 500GB IDE connected to the primary IDE on the board. The driver is out of the box from Microsoft. I have the same model of drive attached to the secondary IDE with no issues. There are also 3x 200GB and one 300GB drive connected to an Adaptec 2410SA controller. There is one Maxtor 300GB and 2x Maxtor 500GB SATA drives attached as well. I put a brand new 600W power supply in over X-Mas thinking maybe it was browning out. I also scanned the drive with SpinRite and it came through clean.
    Friday, December 28, 2007 2:56 PM
  • Do you have a DVD-ROM drive installed? Where is it connected?
    Friday, December 28, 2007 8:06 PM
    Moderator
  • Yes there is a DVD-ROM installed as the master on the secondary IDE. The slave on the secondary IDE is unused. Reading my specs post I guess I should clarify that the 2 500GB drives are on the master and slave of the primary IDE, not the secondary IDE I posted before.
    Saturday, December 29, 2007 2:23 AM
  • Anyone know where I can tell what is causing this error? Event viewer yields nothing. I've given up fixing the supposed failing drive and just ignore the pop-ups. If there are no logs anywhere that say why this error is generated I going to submit a bug report I think.
    Saturday, January 5, 2008 2:23 AM
  • Have you had a look in C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs
    at the following files:

    1) chkdsk.log
    2) q_de.log

    Can you see if anything out of the ordinary appears in one of those logs?
    Saturday, January 5, 2008 12:08 PM
  • The chkdsk.log shows no errors. The q_de.log looks normal but the failing message showed up in the time frame of these messages.

    Code Block

    MIGR:  01/05/2008 12:00:18:906: Beginning full migration pass. LazyPass is False.
    MIGR:  01/05/2008 12:06:29:718: Ended full migration pass.



    Earlier in the log there are entries like this.

    Code Block

    MIGR:  01/05/2008 02:42:09:671: Beginning full migration pass. LazyPass is False.
    MIGR:  01/05/2008 02:42:15:296: *** Can not get OPLOCK on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\GlobalCluster.4096.dat in HandleOneFile with error -2
    MIGR:  01/05/2008 02:42:15:312: *** Can not get OPLOCK on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\GlobalClusterLatest.4096.dat in HandleOneFile with error -2
    MIGR:  01/05/2008 02:42:15:421: *** Can not get OPLOCK on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\NABOO.C.FileRecordHash.4096.dat in HandleOneFile with error -2
    MIGR:  01/05/2008 02:42:15:437: *** Can not get OPLOCK on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\NABOO.C.VolumeCluster.4096.dat in HandleOneFile with error -2
    MIGR:  01/05/2008 02:42:15:859: *** Can not get OPLOCK on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\NABOO.C.VolumeClusterLatest1.4096.dat in HandleOneFile with error 300
    MIGR:  01/05/2008 02:42:16:265: *** Can not get OPLOCK on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\NABOO.C.VolumeClusterLatest2.4096.dat in HandleOneFile with error 300
    MIGR:  01/05/2008 02:42:16:671: *** Can not get OPLOCK on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\NABOO.C.VolumeClusterLatest3.4096.dat in HandleOneFile with error 300
    MIGR:  01/05/2008 02:42:17:218: *** Can not get OPLOCK on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\{2368B1FE-9B0A-49BE-8C98-26BC189FEA7A}.tmp in HandleOneFile with error -2
    MIGR:  01/05/2008 02:43:17:296: Ended full migration pass.




    Saturday, January 5, 2008 5:13 PM
  • Here's some interesting entries from qsm.010508.log. What do they mean exactly ?

    Code Block

    [1/5/2008 12:01:01 PM  bb4] Fix volume snapshots
    [1/5/2008 12:01:01 PM  bb4] Monitoring thread Calculating sizes
    [1/5/2008 12:01:27 PM  a84] Chkdsk done

    [1/5/2008 12:01:27 PM  a84] Monitoring thread is checking disk @ D:
    [1/5/2008 12:01:27 PM  a84] Executing C:\WINDOWS\system32\cmd.exe /C chkdsk.exe D: >"C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk.log"
    [1/5/2008 12:02:05 PM  a84] Chkdsk done

    [1/5/2008 12:02:05 PM  a84] Monitoring thread is checking disk @ c:\fs\R
    [1/5/2008 12:02:05 PM  a84] Executing C:\WINDOWS\system32\cmd.exe /C chkdsk.exe c:\fs\R >"C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk.log"
    [1/5/2008 12:02:12 PM  a84] Chkdsk done

    [1/5/2008 12:02:12 PM  a84] Monitoring thread is checking disk @ c:\fs\9
    [1/5/2008 12:02:12 PM  a84] Executing C:\WINDOWS\system32\cmd.exe /C chkdsk.exe c:\fs\9 >"C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk.log"
    [1/5/2008 12:02:27 PM  bb4] Fix volume snapshots
    [1/5/2008 12:02:27 PM  bb4] Monitoring thread Calculating sizes
    [1/5/2008 12:02:29 PM  a84] Chkdsk done

    [1/5/2008 12:02:29 PM  a84] Monitoring thread is checking disk @ c:\fs\8
    [1/5/2008 12:02:29 PM  a84] Executing C:\WINDOWS\system32\cmd.exe /C chkdsk.exe c:\fs\8 >"C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk.log"
    [1/5/2008 12:03:29 PM  a84] Chkdsk done

    [1/5/2008 12:03:29 PM  a84] Monitoring thread is checking disk @ C:
    [1/5/2008 12:03:29 PM  a84] Executing C:\WINDOWS\system32\cmd.exe /C chkdsk.exe C: >"C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk.log"
    [1/5/2008 12:03:59 PM  a84] Chkdsk done

    [1/5/2008 12:03:59 PM  a84] SetObjectSelfHealth (SYS) QSM_OS_HEALTHY => QSM_OS_FAILING
    [1/5/2008 12:03:59 PM  a84] Monitoring thread is checking disk @ c:\fs\P
    [1/5/2008 12:03:59 PM  a84] Executing C:\WINDOWS\system32\cmd.exe /C chkdsk.exe c:\fs\P >"C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk.log"
    [1/5/2008 12:04:08 PM  a84] Chkdsk done

    [1/5/2008 12:04:08 PM  a84] Monitoring thread is checking disk @ c:\fs\C
    [1/5/2008 12:04:08 PM  a84] Executing C:\WINDOWS\system32\cmd.exe /C chkdsk.exe c:\fs\C >"C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk.log"
    [1/5/2008 12:04:17 PM  a84] Chkdsk done

    [1/5/2008 12:04:17 PM  a84] Monitoring thread is checking disk @ c:\fs\B
    [1/5/2008 12:04:17 PM  a84] Executing C:\WINDOWS\system32\cmd.exe /C chkdsk.exe c:\fs\B >"C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk.log"
    [1/5/2008 12:04:26 PM  a84] Chkdsk done

    [1/5/2008 12:04:26 PM  a84] SetObjectHealth (SYS) QSM_OS_HEALTHY => QSM_OS_FAILING
    VolumeEvent started
    ComputeAdviseArray started
    ComputeAdviseArray ended (2)
    VolumeEvent ended
    [1/5/2008 12:04:26 PM  a84] All disks checked


    Saturday, January 5, 2008 7:41 PM
  • Hi AtariJeff,

     

    I have been running the Eval version of WHS for some time now (and will be buying the full version) and find that after being on for about 10 to 14 days I get the same message. I too have throroughly checked the drives themselves and find no problems however the message is rather alarming isn't it? My system is a rather old platform (Single PIII @733 Mhz with 512 MB RAM and a Silicon Image RAID controlling 2 x 500 GB Seagate SATA drives). On looking through the System Event logs I get an item VolSNAP ID 21 "The flush and hold operation for Volume C: was aborted because of low available system memory". I am assuming that the 512 MB RAM is a little on the low side and will need some more RAM when I do actually build my final system. At the moment I reboot the box every other week or so and that seems to have eliminated the message.

     

    With kind regards,

     

    Neal

    Saturday, January 5, 2008 9:12 PM
  •  Akroama wrote:

    Hi AtariJeff,

     

    I have been running the Eval version of WHS for some time now (and will be buying the full version) and find that after being on for about 10 to 14 days I get the same message. I too have throroughly checked the drives themselves and find no problems however the message is rather alarming isn't it? My system is a rather old platform (Single PIII @733 Mhz with 512 MB RAM and a Silicon Image RAID controlling 2 x 500 GB Seagate SATA drives). On looking through the System Event logs I get an item VolSNAP ID 21 "The flush and hold operation for Volume C: was aborted because of low available system memory". I am assuming that the 512 MB RAM is a little on the low side and will need some more RAM when I do actually build my final system. At the moment I reboot the box every other week or so and that seems to have eliminated the message.

     

    With kind regards,

     

    Neal

    I just want to add that I have seen this from time to time (12 times in 100 days on 3 different drives).  I run repair rather than reboot.  Other than that I ignore it, I don't believe it is anything other than an 'erroneous error message'. 

    Sunday, January 6, 2008 6:53 AM
  • I'm having the same problems listed here.

     

    My config is as follows:

     

    M/B: ECS GeForce6100SM-M, nForce405+6100, Socket-AM2, m-ATX, LAN, DDR2, PCI-Ex8
    CPU: AMD Sempron 3000+ 1.6GHz
    RAM: Corsair Value PC4200 DDR2 512MB
    System HDD: Samsung SpinPoint S166 160GB SATA2 8MB 7200RPM
    Extra HDD: Seagate Barracuda 7200.10 250GB SATA2 16MB 7200RPM
    PSU: 420W

    DVD-ROM: Samsung SH-162C DVD player

     

    I got the notice that my SYS volume was failing and tried to repair it in the WHS console, but the whole thing froze up on me at about 10% into the Hard Drive Repair Wizard. Rebooted and ran chkdsk /f /r without any reported issues. When logging back into the server there were no errors listed - Network Healthy.

     

    I just received the first error, so I haven't been able to reproduce it yet. However, here's what I found in the Event Viewer's System log:

     

    Event Type: Error
    Event Source: VolSnap
    Event Category: None
    Event ID: 21
    Date:  14.01.2008
    Time:  18:00:49
    User:  N/A
    Computer: WHS
    Description:
    The flush and hold operation for volume D: was aborted because of low available system memory

     

    The above error goes for both the C: and D: drive.

     

    Event Type: Warning
    Event Source: PlugPlayManager
    Event Category: None
    Event ID: 260
    Date:  14.01.2008
    Time:  18:00:52
    User:  N/A
    Computer: WHS
    Description:
    The service "WMConnectCDS" vetoed a target device change request.

    Monday, January 14, 2008 9:48 PM
  • Well I'm officially calling this a bug. I replaced the mobo (ASUS M2N-E), CPU (Athlon x2 4400), RAM (2x1024Mb DDR2), all 6 HD's (Seagate 500Gb SATA2), and all cables. The only carry over parts are the PS, case, and DVD-ROM drive. It ran fine for about a week then as soon as I started backing up PC's the message reappeared.
    Wednesday, January 30, 2008 10:19 PM
  • Dear all,

     

    I can confirm that this bug is on the HP MediaSmart server as well. I have 3x 500GB HDs (all Seagates) and I can confirm these disks are rock solid.

     

    The question for Microsoft (and HP as well - as I could eventually have deal with their tech support people) is (get ready for some rambling):

     

    Will they be mature enough to recognize a possible (and yet another) bug in the WHS product, or will they patronize us, the enthusiasts, will silly first/second line support scripted questions?

     

    We all been there, done that (got the t-shirt, etc). I mean, I am sure I am not the only guy here who is tired of seeing a computer's gut and checking on hard drives. Recently I had to swap the logic-board of an IBM deathstar and had the plates of a Maxtor disk 'cleaner' in my kitchen. Last thing I need is some rep telling me to run chkdsk on my system YET AGAIN.

     

    The point is, the product is having quite a bad publicity about the data corruption issue, and now this. We, as the enthusiasts and early adopters, are willing to try harder and invest in the product and in the end, our opinions will count for other consumers. Can Microsoft work with us on this one? I would be happy to help with tests (and I am sure lots of other people would as well). But please consider: THIS IS VERY LIKELY TO BE A BUG.

    Monday, March 10, 2008 10:37 PM
  •  PMDCI wrote:

    We, as the enthusiasts and early adopters, are willing to try harder and invest in the product an din the end, our opinions will count for other consumers. Can Microsoft work with us on this one? I would be happy to help with tests (and I am sure lots of other people would as well). But please consider: THIS IS VERY LIKELY TO BE A BUG.

    +1

    I am willing to anything I can to help sort it out, provided the suggestions make sense.  Just like you can't fix bad hardware with software, you shouldn't try to fix faulty software with hardware.

    Monday, March 10, 2008 11:13 PM
  •  Akroama wrote:

    Hi AtariJeff,

     

    I have been running the Eval version of WHS for some time now (and will be buying the full version) and find that after being on for about 10 to 14 days I get the same message. I too have throroughly checked the drives themselves and find no problems however the message is rather alarming isn't it? My system is a rather old platform (Single PIII @733 Mhz with 512 MB RAM and a Silicon Image RAID controlling 2 x 500 GB Seagate SATA drives). On looking through the System Event logs I get an item VolSNAP ID 21 "The flush and hold operation for Volume C: was aborted because of low available system memory". I am assuming that the 512 MB RAM is a little on the low side and will need some more RAM when I do actually build my final system. At the moment I reboot the box every other week or so and that seems to have eliminated the message.

     

    With kind regards,

     

    Neal

    Sounds like a memory leak doesn't it.

    Monday, March 10, 2008 11:17 PM
  •  

    Funny you mentioned the possibility of a memory leak.

     

    As per other users, I have also noticed the error on Windows Event Viewer related to low system memory. Moreover, I have also noticed that portfwd.exe takes a monstrous amount of system memory. When I checked last time it was about 140MB, and I read users complaining the service got about 640MB.

     

    Perhaps we have a culprit sucking's system memory, which are affecting the performance of the server and hence the error that *might* be causing the SYS failing message.

     

    I'm only guessing of course... Perhaps one error has nothing to do with the other

    Monday, March 10, 2008 11:35 PM
  •  PMDCI wrote:

     

    Funny you mentioned the possibility of a memory leak.

     

    As per other users, I have also noticed the error on Windows Event Viewer related to low system memory. Moreover, I have also noticed that portfwd.exe takes a monstrous amount of system memory. When I checked last time it was about 140MB, and I read users complaining the service got about 640MB.

     

    Perhaps we have a culprit sucking's system memory, which are affecting the performance of the server and hence the error that *might* be causing the SYS failing message.

     

    I'm only guessing of course... Perhaps one error has nothing to do with the other

    I voting for our old friend chkdsk, it is old, trusted, tried and true.  When chkdsk found errors it used to be meaningful but that was DOS 3.2, it is not a program you run 2-4 times a day for days on end. 

    Tuesday, March 11, 2008 1:28 AM
  •  Jeshimon wrote:

    I voting for our old friend chkdsk, it is old, trusted, tried and true.  When chkdsk found errors it used to be meaningful but that was DOS 3.2, it is not a program you run 2-4 times a day for days on end. 

     

    You have a very good point. I was wondering about this just the other day... I mean, come on running chkdsk every 15 min? How can this be good? The problem as well is the nature of the NTFS filesys. Should a journaling filesystem realy depend of such tool for maintaining its integrity? Perhaps I am lacking the right words here, but what I am trying to say is that chkdsk is a one-off tool.

     

    I just hope someone at Microsoft is paying attention to this thread/issue.
    Tuesday, March 11, 2008 2:07 AM
  •  PMDCI wrote:

    I just hope someone at Microsoft is paying attention to this thread/issue.

    It appears not!  I think some of the people seeing the problem post once and go away thinking the problem will get handled.  It is not getting handled, it is being ignored.

    Tuesday, March 11, 2008 9:22 PM
  •  Jeshimon wrote:

    It appears not!  I think some of the people seeing the problem post once and go away thinking the problem will get handled.  It is not getting handled, it is being ignored.

     

    Well, I am making sure I am giving my 2 cents. In a way or another

     

    Tuesday, March 11, 2008 10:16 PM
  •  PMDCI wrote:

     Jeshimon wrote:

    It appears not!  I think some of the people seeing the problem post once and go away thinking the problem will get handled.  It is not getting handled, it is being ignored.

     

    Well, I am making sure I am giving my 2 cents. In a way or another

     

    I checked it out pretty well written.  You do know there is an older thread here that deals with the same bug...

    Tuesday, March 11, 2008 11:01 PM
  • Just want to get this thread going again.  I have run whs for two months now on new hardware.  My first set up 1 320 gig WD hardrive.  After about 1 month of service I got the Volume with name SYS failing error about every other day.  I decided to upgrade my drive to a 750 gig WD, note still only using one drive due to corruption bug.  I rebuilt server and it ran smooth for about 4 weeks and wouldn't you know the Volume with name SYS is failing is back.  I run the repair option and this seems to buy me about 2 days and the error keeps coming back.  I find it hard to beleave that two brand new disks would fail in a months time.  After reading so many posts of people seeing this problem I beleave there is a bug here.  Just want to make sure Microsoft is seeing this so they will look into the issue.  For now I am just going to ignore the warning.  I don't have anything on my server that can't be replaced, the only loss would be the time to put it back together.

    Wednesday, April 16, 2008 2:31 PM
  • Does anyone here get a nagging feeling that this software could have been tested a little bit better than it was before release? 


    I sure do.

     

    I was hoping that memory leaks in Windows was a thing of the past but I guess that's not the case.

     

     

     

     Jeshimon wrote:

     Akroama wrote:

    Hi AtariJeff,

     

    I have been running the Eval version of WHS for some time now (and will be buying the full version) and find that after being on for about 10 to 14 days I get the same message. I too have throroughly checked the drives themselves and find no problems however the message is rather alarming isn't it? My system is a rather old platform (Single PIII @733 Mhz with 512 MB RAM and a Silicon Image RAID controlling 2 x 500 GB Seagate SATA drives). On looking through the System Event logs I get an item VolSNAP ID 21 "The flush and hold operation for Volume C: was aborted because of low available system memory". I am assuming that the 512 MB RAM is a little on the low side and will need some more RAM when I do actually build my final system. At the moment I reboot the box every other week or so and that seems to have eliminated the message.

     

    With kind regards,

     

    Neal

    Sounds like a memory leak doesn't it.

    Wednesday, April 16, 2008 4:02 PM
  • Just wanted to post this error that I see in the logs

     

    Chkdsk was executed in read-only mode on a voulme snapshot.  It seems when it logs this error is when I get the SYS is failing warning. 

     

    What does this mean? Anyone have any ideas if this is causing my warning?

    Thursday, April 17, 2008 2:13 AM
  •  

    I am seeing the same errors, and they are driving me nuts. I found this article, but am not sure if it will help..

     

    http://support.microsoft.com/kb/933653

     

    Tuesday, May 13, 2008 7:37 PM
  • I have been having SYS failing every week or two since I set up WHS in December.

     

    In order to identify the problem I have been doing a chkdsk /f on the drives (C, D and DATA) and then rebooting.

    I have then gone to the System log and copy/pasted the text from the first entry after reboot (this is the chkdsk result) .

    I have pasted these results into three text files (I would attach them if I knew how....)

     

    A sample ( for C: ) is as follows:

     

    Event Type: Information
    Event Source: Winlogon
    Event Category: None
    Event ID: 1001
    Date:  15/05/2008
    Time:  12:40:45 a.m.
    User:  N/A
    Computer: SERVER
    Description:
    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is SYS.


    One of your disks needs to be checked for consistency. You
    may cancel the disk check, but it is strongly recommended
    that you continue.
    Windows will now check the disk.                        
    Cleaning up instance tags for file 0x449c.
    Cleaning up minor inconsistencies on the drive.
    Cleaning up 6 unused index entries from index $SII of file 0x9.
    Cleaning up 6 unused index entries from index $SDH of file 0x9.
    Cleaning up 6 unused security descriptors.
    ...

     

    The results for all three drives are (almost) identical every time.

    This can not be a hard drive fault.

    My guess is that there is a problem with the file system.

    Something like file locking > access contention > race condition > index corruption.

     

    My hardware is 2 x WD10EACS 1TB HDD (purchased in December and March) in a Shuttle SN21G5 with 1G memory.

    I intend to upgrade the memory to 2G soon.

     

     

    Additional infromation:

    - The same error is generally occuring on both drives, all three volumes (C:, D: and c/fs/o).
    Since I started recording, I have 8 for C:, 7 for D: and 4 for C:\fs\O.

    - The IDE ATA/ATAPI controller driver is Microsoft 5.2.3790.3959 and disk drive Microsoft 5.2.3790.0

    - I have started running Diskeeper WHS last month (no difference to the SYS errors)

    - WHS is running from a UPS.

     

    After the same reboot, abreviated logs for the other two volumes are as follows:

     

    Date:  15/05/2008
    Time:  12:40:45 a.m.
    Checking file system on D:
    Cleaning up minor inconsistencies on the drive.
    Cleaning up 5 unused index entries from index $SII of file 0x9.
    Cleaning up 5 unused index entries from index $SDH of file 0x9.
    Cleaning up 5 unused security descriptors.

    Date:  15/05/2008
    Time:  12:40:45 a.m.
    Checking file system on [c:\fs\O:]
    Cleaning up minor inconsistencies on the drive.
    Cleaning up 6 unused index entries from index $SII of file 0x9.
    Cleaning up 6 unused index entries from index $SDH of file 0x9.
    Cleaning up 6 unused security descriptors.

    Saturday, May 17, 2008 1:26 PM
  • Chris, the error message stating that a volume is failing can have many causes. It's my understanding that a certain number of those messages are "false positives" but I don't have additional information I could share with you on that, I'm afraid.

    But even the minor inconsistencies you list are probably enough for Windows Home Server to consider the drive suspect. The physical hard drive may not be failing, but something is causing those inconsistencies. It could be something about Windows Home Server, it could be bad storage drivers (are you using drivers for Windows Server 2003? I don't see them available on the Shuttle web site...), ir could be third party software you've installed, etc... What software have you installed on your home server?
    Saturday, May 17, 2008 4:49 PM
    Moderator
  •  Ken Warren wrote:
    Chris, the error message stating that a volume is failing can have many causes. It's my understanding that a certain number of those messages are "false positives" but I don't have additional information I could share with you on that, I'm afraid.

    But even the minor inconsistencies you list are probably enough for Windows Home Server to consider the drive suspect. The physical hard drive may not be failing, but something is causing those inconsistencies. It could be something about Windows Home Server, it could be bad storage drivers (are you using drivers for Windows Server 2003? I don't see them available on the Shuttle web site...), ir could be third party software you've installed, etc... What software have you installed on your home server?

    Ken,

    You know that I've long been a proponent of this not being a hardware problem; but I must admit openly after moving everything but SYS off the motherboard controller that I've not seen any of these errors since 30 May, 2008.  I have seen:

     

    Source: ESENT

    TimeGenerated: 5/16/2008 9:59:50 PM

    InstanceId: 474

    Catagory: Database Page Cache

    CatagoryNumber: 2

    EntryType: Error

    Message: wuaueng.dll (840) SUS20ClientDataStore: The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 577536 (0x000000000008d000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch.  The expected checksum was 272468049 (0x103d8851) and the actual checksum was 272468053 (0x103d8855).  The read operation will fail with error -1018 (0xfffffc06).  If this condition persists then please restore the database from a previous backup.  This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    ----

     

    Which I think probably would have set that flag in the past.  The last time I saw the error was Jan 19, 2008 and the volume failing error was Jan 18, so I'm not sure.
    Saturday, May 17, 2008 7:32 PM
  • Same issue here - happens about once per week...  chkdsk /f then logs the following type of result:

    chkdsk /f on C:, Event log showed in the Winlogon event:

    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is SYS.


    A disk check has been scheduled.
    Windows will now check the disk.                        
    Cleaning up instance tags for file 0x3797.
    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.
    Windows has made corrections to the file system.

      20972825 KB total disk space.
       5224908 KB in 15595 files.
          4536 KB in 1832 indexes.
             0 KB in bad sectors.
        119253 KB in use by the system.
         65536 KB occupied by the log file.
      15624128 KB available on disk.

          4096 bytes in each allocation unit.
       5243206 total allocation units on disk.
       3906032 allocation units available on disk.


    All updates and patches applied... drivers updated etc, I'm hopeful that somewhere in PP1
    there is a fix that addresses this, as it really drains confidence in WHS to be a reliable store for my data.  After 6+ years of using basic NAS boxes flawlessly, I was hoping for better than this out of WHS!
    Friday, June 20, 2008 4:11 AM