locked
Home Server Installation Problems - with SI 3112/4 controller / SATA Drives RRS feed

  • Question

  • Dear Support Team, I have attempted a number of times to install Home server on my Tyan Transport GT24 B2891 server. On Installation WHS requested a driver for SATA Controller SI3114 to be installed - it accepted only a 32 bit driver, refusing to install the 64bit driver. After installing the driver for SATA drives, it began installing the system after partitioning and formating disk 0 on the system (the system has 4 drives - drive 0 500gb, drive 1-3 1,5 tb all drives were new or ntfs patitioned and formated).
     
    The installation continued extremely slowly to the point just before installing the WHS console and then broke off with an ERROR ... cannot initiate Volume. 4 Attempts were made each time with the same result. The faulty home server could be accessed, mmc called up with its basic server services etc - it recognized all drives in the system and all clients in the network - copying to and from clients was possible - but the network / client connector refused to install manually. Internet and MS Update was accessible - all updates available on the MS Update site could be downloaded and updated without error.  The WHS console refused installation manually with a host of further error messages. 
    An attempt was then made to install HS on a 110 GB PATA/IDE drive. This installation was completed without a hitch. This drive was attached to the system provisionally (externally) via an IDE Cable connected directly to the motherboard. There is no way this drive can be permanently installed on the hardware in this way. Therefore a clone was made of this disk to the original hardware System SATA drive. WHS started on this disk without a hitch. The WHS console connected perfectly and clients could be linked to the home server system via the network and client connector. all worked fine except for a small major FLAW:
     
    The WHS console did not want to release the original 110 GB PATA/IDE Drive that was used for the basic HS installation, eventhough the system booted from the cloned SATA drive. The HWS Console listed the Pata disk under storage disks - as unattached - the function remove, repair, install disk are greyed out. It could therefore not be removed from the console. When the disk is physically removed (by disconnnecting) or logically removed via MMC, the WHS console comes up with critical errors and refuses to work normally until the (now empty voided/ or /empty partitioned and formated 110gb) disk is reinstalled or connected, When reconnected and rebooted the system works fine - does backups and restores etc as required. some other minor errors still occur and are listed in the incident logs below - one or more services refused to start . see attached incident logs.

    Problem: how can i fix the errors listed / and / or / do a proper error free installation straight to the Sata drive after controller driver installation or release the PATA/IDE drive. (during the update phase from MS the original Sata contoller driver for the si3114 (silicon image controller) was replaced with a signed MS controller driver.) -
     
    Why was this driver not includen in the WHS package? - Tyan and Silicon Image sre Brandnames and were in MS's Hardware-driver pool.
    Furthermore, i could not locate the location the controller driver was copied to for use in a possible new WHS installation test. 
    Please help - I've been trying to get this system working for 3 weeks now and have been thro the multitude of information sources on your WHS site without avail. PS . Even removing the drive from the registry did not help - neither did deinstalling and reinstalling the WHS console help and only led to more serious and new error sources.  The attached incident error lists show a relatively clean and working system except for the above listed problem of the still attached PATA Drive.
     
    I thank you in advance for your kind and urgent assistance - yours sincerely  - win - (germany, Munich)
     
    PS I have activated this system at least 4 times already due to all the failed installations.  
    Here some details of the main errors found and listed in the incident logs: DTC error - transaction manager could not be started ....
    Der Transaktions-Manager von MS DTC konnte nicht gestartet werden. Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter
    http://go.microsoft.com/fwlink/events.asp.
     
    Net 2.0 runtime error - EventType clr20r3, P1 demigrator.exe, P2 6.0.0.0, P3 4acceb1f, P4 decore, P5 6.0.0.0, P6 4acceb1d, P7 1b2, P8 c, P9 system.io.filenotfoundexception, P10 NIL.
    Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.
     
    Home server Incident Log:
     
    Fehler des Clientsicherungsservers bei d:\wssg_src\whs_pp3\qhs\src\backup\server\service\qsminterface.cpp(80)
    Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.
     
    Windows Home-Speicherverwaltungsdienst wurde gestartet.
    Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.
     
    System incident log:
    Could initialize XPS Docu writer as XPS document writer driver could not be found.
    Der Drucker Microsoft XPS Document Writer konnte nicht initialisiert werden, da der Treiber Microsoft XPS Document Writer nicht gefunden wurde.
    Redirection service could not recognize the type of connection Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter
    http://go.microsoft.com/fwlink/events.asp.



    Wednesday, May 18, 2011 5:33 AM