none
Windows Home Server Could Not Start RRS feed

  • Question

  • I was unable to connect to WHS so I attached a monitor to the server and saw "Windows could not start because the following file is missing or corrupt: <Windows Root>\system32\hal.dll

    I believe this issue is further complicated by the fact that I have applied SP1 and don't have a slipstreamed disk.  My question is how do I recover from this and still preserve my backup and shared folders.  I have a total of three separate disk drives on the server.  Any help would be appreciated.
    Monday, January 5, 2009 3:04 AM

Answers

  • JacobsDG said:

    I was unable to connect to WHS so I attached a monitor to the server and saw "Windows could not start because the following file is missing or corrupt: <Windows Root>\system32\hal.dll

    I believe this issue is further complicated by the fact that I have applied SP1 and don't have a slipstreamed disk.  My question is how do I recover from this and still preserve my backup and shared folders.  I have a total of three separate disk drives on the server.  Any help would be appreciated.


    First, my guess is your primary hard drive is failing.  The first thing I would do is pull the primary drive out of the server, connect it to another computer and run chkdsk /r on that drive.  If it finds and corrects any errors, you could try putting it back in the server and starting it up to see if it works.  However, I would start looking for a new drive to replace that one ASAP.

    In any event, to answer your question, you want to boot from the WHS DVD.  When you get to the installation selection screen, you should see 2 options:  New Installation and Server Reinstallation.  You want Server Reinstallation.  It will wipe the OS partition but leave the rest of the data in tact.  Once the reinstallation is complete, all you need to do is re-create any users and re-install any add-ins.  (NOTE:  If you don't get Server Reinstallation as an option, don't go any further.  Please post back here for suggestions on how to get the reinstallation mode to appear.)
    Monday, January 5, 2009 3:33 AM
    Moderator
  • So the immediate boot problem has been caused by the Bios, which had changed the sequence of the disks.
    But as mentioned in your other thread - the DATA volume on your primary disk is unreadable and may point to a failing drive indeed.
    Best greetings from Germany
    Olaf
    Saturday, January 10, 2009 10:05 PM
    Moderator

All replies

  • JacobsDG said:

    I was unable to connect to WHS so I attached a monitor to the server and saw "Windows could not start because the following file is missing or corrupt: <Windows Root>\system32\hal.dll

    I believe this issue is further complicated by the fact that I have applied SP1 and don't have a slipstreamed disk.  My question is how do I recover from this and still preserve my backup and shared folders.  I have a total of three separate disk drives on the server.  Any help would be appreciated.


    First, my guess is your primary hard drive is failing.  The first thing I would do is pull the primary drive out of the server, connect it to another computer and run chkdsk /r on that drive.  If it finds and corrects any errors, you could try putting it back in the server and starting it up to see if it works.  However, I would start looking for a new drive to replace that one ASAP.

    In any event, to answer your question, you want to boot from the WHS DVD.  When you get to the installation selection screen, you should see 2 options:  New Installation and Server Reinstallation.  You want Server Reinstallation.  It will wipe the OS partition but leave the rest of the data in tact.  Once the reinstallation is complete, all you need to do is re-create any users and re-install any add-ins.  (NOTE:  If you don't get Server Reinstallation as an option, don't go any further.  Please post back here for suggestions on how to get the reinstallation mode to appear.)
    Monday, January 5, 2009 3:33 AM
    Moderator
  • I will check out the drive with chkdsk.  In the mean time I booted with the WHS DVD and it immeadiatly took me to a Welcome to Windows Home Server Setup.  I take it I shouldn't be here, so now what?
    Monday, January 5, 2009 4:06 AM
  • JacobsDG said:

    I will check out the drive with chkdsk.  In the mean time I booted with the WHS DVD and it immeadiatly took me to a Welcome to Windows Home Server Setup.  I take it I shouldn't be here, so now what?


    No, that's fine.  That's the first screen you get.  Next will be Load Additional Storage Drivers.  (You should see all of the drives on this screen.)  After that is the one with the installation options.
    Monday, January 5, 2009 4:11 AM
    Moderator
  • Thank you for all your help.   I continued with the install.  I had to load a SATA driver for the third drive.  It loaded and all drives were visable.  Next screen with Select an Installation Type only offers me New Installation so I have stopped there.  Now what?
    Wednesday, January 7, 2009 3:46 AM
  • JacobsDG said:

    Thank you for all your help.   I continued with the install.  I had to load a SATA driver for the third drive.  It loaded and all drives were visable.  Next screen with Select an Installation Type only offers me New Installation so I have stopped there.  Now what?


    Which drive is listed as disk 0 in the drive listing screen?
    Saturday, January 10, 2009 6:13 PM
    Moderator
  • Drive 0 has one volume 189GB NTFS named DATA

    Drive 1 has two volumes 20GB NTFS named SYS and 169GB RAW

    Drive 2 has one volume 698GB NTFS named DATA
    Saturday, January 10, 2009 9:06 PM
  • So the immediate boot problem has been caused by the Bios, which had changed the sequence of the disks.
    But as mentioned in your other thread - the DATA volume on your primary disk is unreadable and may point to a failing drive indeed.
    Best greetings from Germany
    Olaf
    Saturday, January 10, 2009 10:05 PM
    Moderator