locked
Troubleshoot WHS freezing -once a week at same time RRS feed

  • Question

  • My home built WHS freezes every weekend (around 2:40 am this week - seems to be 2-4am each Sunday morning) - I can see the login screen via a directly attached monitor but a local mouse doesn't work and I can't connect via client software. 

    The only thing that is really close to the time of shutdown in the logs this week is this error:
    The master browser has received a server announcement from the computer UBUNTU that believes that it is the master browser for the domain on transport NetBT_Tcpip_{CB1655EB-C202-4757-9A. The master browser is stopping or an election is being forced.

    I have a laptop with dual boot Vista and Ubuntu - I suspect it was on overnight last night. However we don't run it on linux much and other freezes would have happened when the laptop wasn't on. 

    Looking at last week I see this error just before the time of the freeze: 
    The driver has detected that device \Device\Ide\IdePort0 has old or out-of-date firmware. Reduced performance may result.

    Any ideas? What else should I be looking for in the logs? Right now the server seems to be working well and this freeze seems to happen like clockwork each weekend. 

    In terms of software, I'm running 3-4 different bits of media serving software and that's about it.  Each time the error occurs was at times that I was fast asleep in bed so it wasn't something I did directly (for a change!!).

    Thanks
     
     
    Monday, January 18, 2010 1:49 AM

All replies

  • It sounds like your server is having issues at about the time it would normally be doing it's regular weekly maintenance. Have you tried running chkdsk on all the drives in your server ?
    I'm not on the WHS team, I just post a lot. :)
    Monday, January 18, 2010 3:26 AM
    Moderator
  • Not for some time - will give that a shot and see what comes out. 
    Thanks
    Monday, January 18, 2010 6:40 PM
  • Ok, did that last week and finally got a chance to dig out the results - any clues here?  Will see if the server freezes again tonight.... :-( 

    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 minor inconsistencies on the drive.
    Cleaning up 1878 unused index entries from index $SII of file 0x9.
    Cleaning up 1878 unused index entries from index $SDH of file 0x9.
    Cleaning up 1878 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.

      20972825 KB total disk space.
      11344308 KB in 78075 files.
         88888 KB in 12276 indexes.
             0 KB in bad sectors.
        225689 KB in use by the system.
         65536 KB occupied by the log file.
       9313940 KB available on disk.

          4096 bytes in each allocation unit.
       5243206 total allocation units on disk.
       2328485 allocation units available on disk.
    Sunday, January 24, 2010 4:41 AM
  • You certainly have at least one partition (D:) that you didn't show. Please let us know all the results, not just the C: partition.
    I'm not on the WHS team, I just post a lot. :)
    Sunday, January 24, 2010 4:44 PM
    Moderator
  • I need to look into that - I ran the command from your previous link and thought it ran on all partitions, but there was only one winlogin value in the log - nothing relating to d:

    I also saw this week that the last entry in the log before the machine hung was this: 

    Event Type: Error
    Event Source: atapi
    Event Category: None
    Event ID: 9
    Date: 1/24/2010
    Time: 3:17:21 AM
    User: N/A
    Computer: SHUTTLESERVER
    Description:
    The device, \Device\Ide\IdePort0, did not respond within the timeout period.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Sunday, January 24, 2010 7:26 PM
  • That device is probably your system drive, or the disk controller on your motherboard it's connected to. You can always run chkdsk /r manually on D:; that would be a good first step.

    Do you hibernate your server?
    I'm not on the WHS team, I just post a lot. :)
    Sunday, January 24, 2010 7:48 PM
    Moderator
  • No - I don't use any hibernation. From troubleshooting previous issues I'm pretty sure all the power settings are set to avoid shutting down devices, etc.

    thanks for the tips - running chkdsk on d: right now - but looks like it's going to take a while...
    Sunday, January 24, 2010 8:29 PM
  • Here are the results of chkdsk on D: - nothing jumps out at me - any thoughts?

    C:\Documents and Settings\Administrator>chkdsk d: /R
    The type of the file system is NTFS.

    Chkdsk cannot run because the volume is in use by another
    process.  Chkdsk may run if this volume is dismounted first.
    ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
    Would you like to force a dismount on this volume? (Y/N) y
    Volume dismounted.  All opened handles to this volume are now invalid.
    Volume label is DATA.

    CHKDSK is verifying files (stage 1 of 5)...
    328560 file records processed.
    File verification completed.
    53 large file records processed.
    0 bad file records processed.
    0 EA records processed.
    167480 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 5)...
    1205653 index entries processed.
    Index verification completed.
    5 unindexed files processed.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
    328560 security descriptors processed.
    Security descriptor verification completed.
    39195 data files processed.
    CHKDSK is verifying Usn Journal...
    34067952 USN bytes processed.
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    328544 files processed.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    22901044 free clusters processed.
    Free space verification is complete.

     467403142 KB total disk space.
     375233336 KB in 288074 files.
        123468 KB in 39196 indexes.
             0 KB in bad sectors.
        442162 KB in use by the system.
         65536 KB occupied by the log file.
      91604176 KB available on disk.

          4096 bytes in each allocation unit.
     116850785 total allocation units on disk.
      22901044 allocation units available on disk.
    Monday, January 25, 2010 3:41 AM
  • bump - server hung again this weekend - any other ideas?
    Sunday, January 31, 2010 9:58 PM
  • bump - server hung again this weekend - any other ideas?
    Maybe there is some issue with your backup database (which is part of the Sunday cleanup process).  Did you try repairing the backup database manually?  How about deleting the entire backup database, then starting a new one?

    Also, in terms of hardware possibilities, maybe it's a problem with the data cable for that IDE port 0 drive being loose, or with the power supply not supplying enough power for all of your hardware (although I would tend to believe it would much more random than the once-a-week scenario you're describing).
    Sunday, January 31, 2010 10:20 PM
    Moderator
  • Thanks - no I hadn't tried that - will give the backup idea a try. 

    Is there an easy way to link the port 0 drive to the physical drive so I know which once it's referring to? I poked around but couldn't see anything. (Edit - never mind - found it)
    Tuesday, February 2, 2010 2:35 AM
  • tried repairing the database - no luck - it still crashed this weekend. Seemed to take about 3-4 attempts for it to start up again without freezing afterwards - been running fine since Sunday with no issues. AARGH. 
    Thursday, February 11, 2010 3:59 AM
  • my WHS does the exact same thing and has been for some time now.  since i have the HP MediaSmart WHS, i don't have a monitor so i need to hard reboot the system each week (scary).  the Database Repair does not cause the freeze, but i can now readily reproduce the freeze by running Backup Cleanup.  i haven't been able figure out how to fix this yet, but at least i now figured out what is causing it.
    Sunday, February 14, 2010 5:43 AM
  • Ok, did that last week and finally got a chance to dig out the results - any clues here?  Will see if the server freezes again tonight.... :-( 

    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 minor inconsistencies on the drive.
    Cleaning up 1878 unused index entries from index $SII of file 0x9.
    Cleaning up 1878 unused index entries from index $SDH of file 0x9.
    Cleaning up 1878 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.

      20972825 KB total disk space.
      11344308 KB in 78075 files.
         88888 KB in 12276 indexes.
             0 KB in bad sectors.
        225689 KB in use by the system.
         65536 KB occupied by the log file.
       9313940 KB available on disk.

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

    Can I ask if you ran chkdsk from a consol or on the server itsself (i.e. monitor & keyboard attached to server)
    Wednesday, October 6, 2010 4:43 PM
  • my WHS does the exact same thing and has been for some time now.  since i have the HP MediaSmart WHS, i don't have a monitor so i need to hard reboot the system each week (scary).  the Database Repair does not cause the freeze, but i can now readily reproduce the freeze by running Backup Cleanup.  i haven't been able figure out how to fix this yet, but at least i now figured out what is causing it.

    Mine freezes too, but only when the Server either connects to Microsoft for Updates or if I transfer files accross the network. Which makes it a useless server!
    Wednesday, October 6, 2010 4:45 PM