Netserver LH4 and Windows Server 2003

[Alain Tuor]

Hello,
We've tried to install Windows 2003 on 3 different LH4 (D6973A) with the latest BIOS and NetRaid FirmWare, but all of them gave the following error when doing a Shut Down : after the message 'Windows Shutting Down', a window opens saying 'Delayed Write Failed, Windows was unable to write all the Data...', mentioning the name of the file; when we press OK, we get the same message for another file (about 10 of them), and then it shuts down.

Does anyone know if there is a specific issue with LH4 Servers and Windows 2003 ? Thanks

[amhakassa]

Hi Tuor,

Actualy windows 2003 is not certified on this server by HP yet, even though it seems to work for many people. However, have you tried to have the latest serive pack on windows 2003?

regards
Amha Kassa

[Alain Tuor]

Thanks Amha for your reply. We've tried all latest patches, but haven't found anything yet. It's just weird that Microsoft Windows 2003 gives no more information than this eror messags, stating that the HardWaree may be faulty

[e4services]

Doesn't make me feel to comfortable about the RAID. Have you been to the LSI Logic site and see what they have to say about the Mylex controllers and Windows 2003? Could be issues with the driver. Of course you did not mention your configuration so may be you are attached to the Adaptec SCSI

[John Birkett]

I had the same issue with 2003 and an LH3. I found that a clean install caused this to appear, but an upgrade from 2000 Advanced Server would not give the message. I also tried an install to an internal hard drive, not one from the Raid controller and do not get the message. After some research and talking to our techs at work, it appears that W2003 is shutting down the raid services before completing the write to the log files. I have sent Microsoft a message but have not heard back as yet. I have it installed on an internal 9gb and use the raid for data and all other things.
Regards,
John

[Alain Tuor]

Well It seems that my collegue found the solution to our problem. Windows 2003 has compatibility problems with HP NetRaid assistant. By installing the latest Windows 2000 NetRaid Drivers from HP (replacing the Microsoft driver version) it now works fine. Hopefully this will stay that way :-)

[John Birkett]

Glad to hear that worked. As I said, I have installed on an internal non raid drive for the system and boot partition and use the raid controller. Another thing I found that is quite disturbing is:
When using the Netraid Assist software and creating a Raid configuration other than Raid 0, Windows does not recognize the Raid level dynamically. Now that I think about it, even when creating a Raid configuration using the boot cntl-M process Windows did not recognize the Raid 5 configuration. When initialization runs it fails and recognizes all the space as if it was looking at Raid 0. Has anybody else found this anomaly also?
Regards,
John

[Terri Harris]

I just wanted to clarify something Amhakassa said "not certified yet". Sorry but Windows 2003 will not be certified or supported by HP on any of the Netservers. Glad you are able to get this working!

[clausw]

we have had the same problem, now we do not install netraid assistent and no HP drivers for the netraid (the build in controller is not realy a netraid, it is a symbios clone). Just use Microsoft drivers and the server works, but you dont have any onlinefeatures and no monitoring.
It don't really looks like a good customersupport to say "not certified/supportet and finish", have to buy a proliant and thats it.

[Ted Eggleton]

I am experiencing simmilar problems with a Netserver E800 using a standard HDD except I do not get any error messages, it just hangs. Switching off does not appear to create any problems restarting, well not so far anyway.
I have got the same response from HP which I regard as pretty pathetic coming from a Company that claims to be a leader in the field. Maybe if enough people complain they will do somthing about it (Ha Ha).
Has anybody else had the same problem?
Whoops, it has just restarted! It took over five minutes to shutdown, still not good.