Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS Installation crashes at first reboot - driver issue? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    When installing WHS, HDD was recognised (SATA WD Caviar Green 1TB), files were copied over OK but, on first reboot for installation, got blue screen with the message 'STOP: 0x0000007B'.  I think this means that the boot drive is not accessible.  I tried a second drive with the same effect (only one drive connected at a time).  Dell diagnostics showed HDD was fine.  As a test, I loaded Windows 7 onto the machine without any issues.  Assume I may have a WHS driver issue.  What does Win 7 support that WHS does not?  How do I get the driver if this is the problem?
    PC is Dell Vostro 420 with latest BIOS. Standard AHC1 1.0 Serial ATA Controller shown under Win 7.

    Friday, December 4, 2009 6:56 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    Performance drop? Yes, but it's not huge and will almost certainly be masked by other bottlenecks in the overall system.

    As for the absence of SATA drivers, Windows Home Server is based on Windows Server 2003. There are no SATA drivers in-box in Windows Server 2003, and it would take an Act of Congress to add them at this late date, due to stability and testing requirements.

    System drives: If you didn't complete setup you shouldn't have a problem. If you did finish setup, wipe the drive in another PC before you add it to your server.
    I'm not on the WHS team, I just post a lot. :)
    Friday, December 4, 2009 7:59 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Windows Home Server is based on Windows Server 2003, which has no SATA or AHCI drivers inbox. You can configure your server to use "Legacy IDE" mode for the drives, or prepare and use an "F6 floppy" (USB flash drives will usually not work, so it will really have to be a floppy) following the instructions in your motherboard manual.
    I'm not on the WHS team, I just post a lot. :)
    Friday, December 4, 2009 7:18 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for prompt reply.
    Just tried switching BIOS to ATA and set up has resumed - looks promising.  Assume there's a performance drop in not using SATA?
    PC doesn't have a FDD so I guess I don't have any options.
    I did try using the PP3 beta in case it had better support.  Seems strange not to support SATA.
    I saw one of your replies about the danger of putting a WHS system disk into a functional WHS machine.  Will this still apply to a disk that didn't have a complete installation - I tried to load WHS onto two disks in case one had failed.
    Friday, December 4, 2009 7:47 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Performance drop? Yes, but it's not huge and will almost certainly be masked by other bottlenecks in the overall system.

    As for the absence of SATA drivers, Windows Home Server is based on Windows Server 2003. There are no SATA drivers in-box in Windows Server 2003, and it would take an Act of Congress to add them at this late date, due to stability and testing requirements.

    System drives: If you didn't complete setup you shouldn't have a problem. If you did finish setup, wipe the drive in another PC before you add it to your server.
    I'm not on the WHS team, I just post a lot. :)
    Friday, December 4, 2009 7:59 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Ken - your help's appreciated
    Steve
    Friday, December 4, 2009 8:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    thanks for this post.  had the same issue.  configured dell bios to see hard drive as ATA, and install is moving forward.  Great Job.  saved me who knosw how much time. Thanks!
    Monday, February 15, 2010 6:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I was also getting BSOD issues whilst trying to install 'Windows Server 2003 - Enterprise Edition'. Followed your advise and changed to 'ATA' in BIOS. Worked like a dream :)

    Thank you for this thread

    Monday, June 28, 2010 8:24 AM