locked
I cannot reinstall RRS feed

  • Question

  • I have placed myself in a rather precarious situation, and even if the issue is discussed elsewhere in the forum I ask kindly for good advice. Previous threads are not 100% clear to me, and what I need now is clarity in order not to mess up things further.

    My installation is self made with standard componenents, ASUS P5K, Intel Dual Core, 4 GB, Corsair 620W and Promise SATA controller. System disc 500 GB WD and 8 additional units varying from 1 to 2 TB storing documents, pictures, music, videos and movies. Have had some glitches and slowdowns recently which I assumed was a consequence of adding/removing add-ins, replacing discs, some non-supported SW (uTorrent) etc. So I decide to tidy up things with a reinstallation.

    Reinstallation process is interrupted with BSOD twice. I replace SATA cables as a first resort and the reinstallation restarts and comes to an end. Starting up WHS it is obvious that the reinstallation was a mess - endless error messages, internet connection unavailable.

    The original instability appears to be caused by bad cables on my system disk, so that out of the way I repeat the reinstallation. Now I get the following error messages:

    "The signature for Windows Setup is invalid. The error code is 80096001"

    "The application in DLL C:\WINDOWS\system32\AUTH.dll is not a valid Windows image. Please check this against your installation diskette."

    So I try reinstalling from the start for the third time just in case I had a read error from the installation DVD. This time the reinstallation option is not available, and I know all too well what happens if I press on with a new installation. I have read some threads about this issue, but I need some reassurance before I move forward.

    The crisis scenario is petrifying - losing 5-6 TB of data!



    Sunday, November 8, 2009 10:22 AM

Answers

  • ...
    Or is there sometning else I should try?
    Load storage drivers during the hardware detection phase so that all of your drives are detected correctly. This is how server reinstallation/recovery is designed to work. If some disks are missing from the storage pool, you may not be offered the reinstallation/recovery option in setup, just the new installation option.
    I'm not on the WHS team, I just post a lot. :)
    Monday, November 9, 2009 6:02 PM
    Moderator
  • Windows Server 2003 as the basic of WHS has no native support for SATA disks - therefore it doesn't see them.
    So you need to provide the appropriate mass storage controller drivers one time during initial stage of installation, the second time during the bluescreened stage of setup after pressing F6 if written on a floppy drive. The post is only about initializing the hardware, while the drivers determine, what the software gets to see from this hardware.
    Best greetings from Germany
    Olaf
    Monday, November 9, 2009 10:53 PM
    Moderator

All replies

  • Since you still get this kind of errors, it is definitively not the cable itself.
    It could be faulty memory or a faulty mass storage controller or something else like overheating. Also the DVD could not be compatible with the medium, the medium has scratches or something like that. Is it a self burned DVD or from an OEM package?

    For yor data you can read the FAQ How to recover data after server failure, which covers such situations.

    To get another installation attempt, you will have to clean out (reformat) the system volume on the system disk, which can be done with the cmd prompt in the system repair options you get booting of a Vista DVD.

    Best greetings from Germany
    Olaf
    Sunday, November 8, 2009 11:44 AM
    Moderator
  • Olaf,

    reformatting SYS partition done, but still no reinstall option - only new install. I note in your FAQ that the system volume should be detected as drive 0. It is detected on drive 1. In my BIOS the disc is lined up as first drive and changing that position has no effect on the WHS installer number. It stays as system volume on drive 1.

    Is an option to disable/disconnect all the other drives to get to the reinstall?

    Finn
    Sunday, November 8, 2009 9:22 PM
  • Hi Finn,
    I only spoke about the system volume, not the system disk for cleaning out.
    The system volume is in the server drive C: with 20 GByte size.

    If you perform a fresh install on the system disk, all data potentially stored on drive D: is lost. This can include parts of the backup database and files from non duplicated shared folders.
    After Power Pack 1 new data is stored on other drives first, if possible, so the system disk is kept free often. But there is no guarantee that this is the case. Also data from older installations or stored there due to full disks will not move away automatically, once there is enough space.
    So you should check the D: drive of that disk for data according to above FAQ.

    Best greetings from Germany
    Olaf
    Sunday, November 8, 2009 9:23 PM
    Moderator
  • Olaf,

    reformatting SYS partition done, but still no reinstall option - only new install. I note in your FAQ that the system volume should be detected as drive 0. It is detected on drive 1. In my BIOS the disc is lined up as first drive and changing that position has no effect on the WHS installer number. It stays as system volume on drive 1.

    Is an option to disable/disconnect all the other drives to get to the reinstall?

    Finn

    When you get to the Load Additional Storage Drivers screen, do you see all of your hard drives in the list?  Do you have to add your own drivers in order for all of them to show up on that list?  If so, what is the disk number shown for your primary drive (the one with 2 partitions)?  What about the other drives (what number are those in that list)?
    Sunday, November 8, 2009 11:16 PM
    Moderator
  • No, in fact not. I get the Intel attached disks (4), but not the disk attached to the on-board disk controller (Jmicron) or the four disks attached to a PSI SATA controller (Promise). My system disk is lined up as no 2 (disk 1) in the screen in question, with the SYS and DATA partitions shown. I had hoped that as WHS is up and running I could load the drivers (as was done when I first built the WHS). And WHS would recognize the drives from the tombstone info. Perhaps hoping for too much?

    I am now inclined to disconnect all drives, put the system disk on a client PC to capture the DATA part, make a new installation on a new disk and manually get the DATA from the other 8 disks into the WHS, according to Olaf's scheme. Or is there sometning else I should try?
    Monday, November 9, 2009 5:20 PM
  • ...
    Or is there sometning else I should try?
    Load storage drivers during the hardware detection phase so that all of your drives are detected correctly. This is how server reinstallation/recovery is designed to work. If some disks are missing from the storage pool, you may not be offered the reinstallation/recovery option in setup, just the new installation option.
    I'm not on the WHS team, I just post a lot. :)
    Monday, November 9, 2009 6:02 PM
    Moderator
  •  Loud and clear.
    To be sure: drivers are added in the WHS reinstallation phase, not during POST?
    Monday, November 9, 2009 10:14 PM
  • Windows Server 2003 as the basic of WHS has no native support for SATA disks - therefore it doesn't see them.
    So you need to provide the appropriate mass storage controller drivers one time during initial stage of installation, the second time during the bluescreened stage of setup after pressing F6 if written on a floppy drive. The post is only about initializing the hardware, while the drivers determine, what the software gets to see from this hardware.
    Best greetings from Germany
    Olaf
    Monday, November 9, 2009 10:53 PM
    Moderator
  • I have placed myself in a rather precarious situation, and even if the issue is discussed elsewhere in the forum I ask kindly for good advice. Previous threads are not 100% clear to me, and what I need now is clarity in order not to mess up things further.

    My installation is self made with standard componenents, ASUS P5K, Intel Dual Core, 4 GB, Corsair 620W and Promise SATA controller. System disc 500 GB WD and 8 additional units varying from 1 to 2 TB storing documents, pictures, music, videos and movies. Have had some glitches and slowdowns recently which I assumed was a consequence of adding/removing add-ins, replacing discs, some non-supported SW (uTorrent) etc. So I decide to tidy up things with a reinstallation.

    Reinstallation process is interrupted with BSOD twice. I replace SATA cables as a first resort and the reinstallation restarts and comes to an end. Starting up WHS it is obvious that the reinstallation was a mess - endless error messages, internet connection unavailable.

    The original instability appears to be caused by bad cables on my system disk, so that out of the way I repeat the reinstallation. Now I get the following error messages:

    "The signature for Windows Setup is invalid. The error code is 80096001"

    "The application in DLL C:\WINDOWS\system32\AUTH.dll is not a valid Windows image. Please check this against your installation diskette."

    So I try reinstalling from the start for the third time just in case I had a read error from the installation DVD. This time the reinstallation option is not available, and I know all too well what happens if I press on with a new installation. I have read some threads about this issue, but I need some reassurance before I move forward.

    The crisis scenario is petrifying - losing 5-6 TB of data!




    I recently had to reinstall WHS on a client’s machine used for small business.  They could not access the console via RDP on their network or Remote Access. Soon they could not access folders or sign-in on the web portal.  I attempted to adjust their Firewall settings, No success.  I went into IIS to make sure client access and RDP is accepted.  No luck.  So, I had to perform a reinstall. I believe an update to their system about three weeks ago caused the malfunction.  Their error logs where just to numerous to examine.

     

    I backed up the “Users” folder via a USB External Drive just incase I would need it.

     

    Thanks to threads on the forum experience a successful reinstall by NOT selecting automatic update.  It is important to select reinstall if you plan to save your data.  I did not do that on a system.  Luckily it was a test unit and nothing was really lost.  The Microsoft .NetFrame 3.5 is a problem item not only for WHS but for any other versions of operation system.  They need to take it out of service because it causes errors.  I will continue to do customized updates. All folders were kept intact.

     

    WHS supports only Windows/XP Drivers for hardware. If you have purchased or built a new super dual-core, quad core type system, WHS gets confused.  Don’t even try to use anything new when downloading hardware drivers unless it was XP approved.  Your installation will go very quickly.

     

    Full reinstall took about 3-hours adding SP2 & SP3.

     

    I used the connector software from the newly updated WHS Folder under the C:/Drive.  All units installed without a hitch.

     

    Now if there was only a way to capture the “Console” prior to installation.  I’m sure if I kept looking the info is in the system somewhere.   Setting up users  worked well and matching up folders was no problem

    Saturday, April 10, 2010 11:48 PM