Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS Server Problems RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have been running the original WHS based on Windows Server 2003 for many years now without a hitch. Last week, I started getting messages that there were file conflicts. Since I am using the server for multiple users, I decided to wait until early Monday (4am) to bring down the server and run the repairs. When I went to bring it back up, one of the drives (there are 5) did not show up in CMOS and WHS reported it as missing. I cleaned out the computer and reseated the connectors for the drive that was missing. To my surprise, it came up and WHS booted. I was afraid that there may be corruption so I used the method of running chkdsk on each of the drives in a batch file. The only difference was that I added the /R parameter to have it also check the free space on the drives for errors.

    This is a fairly large system with many folders duplicated. It has 5 drives one 512GB and the rest (four) 1TB drives. Before it failed I had planned on adding another 1TB drive as my free space had fallen to less than 160GB. I started the chkdsk batch yesterday evening around 8pm. It has made it through 3 stages but is stuck on stage 4 of 5. It is currently at 161842 of 430096 files and is taking about an hour for 1000 files. At this rate, it will not finish for another 9 days. 

    I picked up another 2TB drive yesterday.

    The question I have is should I be patient and wait until it is done with the chkdsk, stop the chkdsk and add the new 2TB drive and then do a removal of the drive that was causing the failure or should I remove the /R parameter and rerun the chkdsk batch file. 

    Unfortunately, I have all of my Quickbook files on the server and was in the process of doing my taxes before this started. Right now I can't get to anything on the server as I booted it in Safe mode for the chkdsk. 

    I would appreciate any help.

    Thanks.

    Wednesday, February 15, 2012 11:03 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    If you can identify the drive having trouble, I would probably try forcing the issue, after reading this faq about what data may be at risk:

    • Shut the server down.
    • Physically remove the drive having issues. (Optionally, install the new drive now.)
    • Boot the server.
    • Use the console to remove the "missing" drive.
    • If you didn't already install the new drive, shut down and do so now, then boot your server.
    • Add the new drive to server storage.

    I'm not on the WHS team, I just post a lot. :)

    Thursday, February 16, 2012 2:35 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Ken!

    I did stop the chkdsk and rebooted the machine. I am not able to bring up the WHS Console. I get the following in my event log:

    EventType clr20r3, P1 homeserverconsole.exe, P2 6.0.0.0, P3 4acceb5f, P4 whscommon, P5 6.0.0.0, P6 4accead8, P7 334, P8 1b, P9 system.io.ioexception, P10 NIL.



    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    I did a chkdsk without the /R on drive c: (sys) and it comes back clean. I have no add ins for WHS. Any ideas on how to fix this?

    Thanks

    Steve Mayo

    Thursday, February 16, 2012 7:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This makes me think you have a failing HDD. Can you identify it? If so (and if it's not the system drive), read the FAQ I linked previously so you'll understand what's at risk, then follow the step by step instructions in my previous post. If it's the system drive (though I don't believe it is), you'll have to replace the drive, then use your ogirinal installation media to perform a server recovery.

    I'm not on the WHS team, I just post a lot. :)

    Thursday, February 16, 2012 8:49 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I do/did have a failing drive. I downloaded Seatools for DOS and ran a check on all the drives. Only one came back as bad. I then tried to clone that drive to another Seagate of the same size, but after two hours the errors had grown to over 50% of the drive. I gave up. That drive is toast.  

    So now I have the drive removed and the new 2TB drive installed, but am still getting the error when I try to bring up the console. 

    How do I go about performing a server recovery?

    Thanks.

    Steve Mayo

    Friday, February 17, 2012 10:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This has been the worst disaster that I have had since installing WHS in 2009. I did the server recovery and lost all of my backups and many folders that were not duplicated. 

    The main problem that I am having now is that the High Definition Audio device drivers by Realtek will not install. I downloaded the latest drivers for the motherboard, downloaded the generic drivers from Realtek, reinstalled WHS again with no success. This is on the motherboard and was working prior to doing the crash. 

    Any ideas on what can be done?

    Steve Mayo

    Thursday, February 23, 2012 7:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Since Windows Home Server isn't designed to be used as a media playback device, I'd honestly have to say you should ignore the HD audio drivers and move on. Failing that, I presume you struggled with installing them the first time; did you document the solution?

    I'm not on the WHS team, I just post a lot. :)

    Friday, February 24, 2012 1:34 AM
    Moderator