09-29-2004 12:54 PM
I recently acquired a Proliant 8000 with 4GB RAM and 10 x 18GB SCSI2 hard disks. Two questions so far:
1) I've grabbed 8 x 900MHz processors from a Proliant 8500 and installed them in the 8000 (complete with VRM's). On boot up, the 8000 states that a physical ROM upgrade is required, yet the machine continues to boot fine. Is this a problem?
2) I'm trying to install Windows Server 2003, with a drive configuration of:
Array A: 2 x 18GB RAID 1 (Slot 3)
Array B: 2 x 18GB RAID 1 (Slot 3)
Array C: 2 x 18GB RAID 0 (Slot 3)
Array D: 4 x 18GB RAID 0 (Slot 2)
1 logical drives created to maximum possible in each of these.
However, when I install, I get 2 problems. Part way through copying 'D:\I386\DRIVER.CAB', the setup process complains that it can't copy the file. Repeated retrys give the same message and so does trying it from the recovery console. (It doesn't seem to get beyond 3MB.) It's not the CD, because I've copied the file onto another server. Secondly, when I skip the file and complete the setup, the machine reboots, only to come up with 'Invalid system disk'. Do I need to somehow set the partition active or something?
Any help on these issues would be greatly appreciated.
09-30-2004 10:00 AM
First Update the Bios so that it should fix the error your getting about physical ROM requirred aswell the bios will have the correct microcode for the Newly added processors
Secondly During Install of W2003 are you specifing the driver for your array controller. If not Hit F6 when prompted and install the Driver from diskette.
If your Proliant 8000 is using the Integrated array controller
09-30-2004 10:56 AM
Thanks for taking the time to respond. I had already upgraded the BIOS - originally it came up with 'unsupported processors'. I think it needs a boot-block chip change or something. Not quite sure there.
On the controller side, it's using a 4250ES RAID controller which it seems to detect OK. However, it can't be configured correctly if it's failing to copy a large file (DRIVER.CAB - 75MB), plus failing to prepare the disk for reboot.
Since the most pressing issues are disk related, I guess it's worth downloading the Compaq driver and using this at set up time. I'll post when I have an update.
09-30-2004 11:04 AM
HP ProLiant 32-Bit SCSI Controller Driver for Windows 2000/Windows Server 2003 Â» 220.127.116.11 B
23 Apr 03 Â» 18.104.22.168
12 Feb 03
HP ProLiant 64-Bit/66-Mhz Dual Channel Wide Ultra3 SCSI Controller Driver for Windows 2000 Â» 6.1.550.100 E
23 Apr 03 Â» 6.1.550.100 D
12 Feb 03
HP ProLiant 64-Bit/66-Mhz Dual Channel Wide Ultra3 SCSI Controller Driver for Windows Server 2003 Â» 6.4.645.100
17 Dec 03 Â» 6.3.6300.100
1 Jul 03
HP ProLiant Drive Array Driver for Windows 2000/Windows Server 2003 Â» 22.214.171.124 C
23 Apr 03 Â» 126.96.36.199 B
12 Feb 03
HP ProLiant Drive Array Notification for Windows 2000/Windows Server 2003 Â» 188.8.131.52 B
17 Dec 03 Â» 184.108.40.206
1 Jul 03
HP ProLiant Smart Array 5x and 6x Controller Driver for Windows 2000/Windows Server 2003 Â» 220.127.116.11
18 Aug 04 Â» 18.104.22.168
18 Jun 04
HP ProLiant Smart Array-2 Controllers Driver for Windows Server 2003 Â» 22.214.171.124 F
1 Jul 03 Â» 126.96.36.199 E
23 Apr 03
HP ProLiant Storage System Driver for Windows 2000/Server 2003 Â» 188.8.131.52 C
10-04-2004 06:03 AM
I'm still getting the message that a physical upgrade is required, even though Windows Server 2003 fully detects the 8 x 900MHz processors. I don't know if that's a marketing effort by Compaq to get more money ;-) If anyone can help me there, I'd appreciate a reply.
Thanks for your time Ryan.