RDP 3.50 and E200 Array

[Ed Cox]

Hello
Well I have tried everything I know and so here I am, where there is much love in this forum.

I did a fresh install of RDP 3.50 and am doing a full scripted Win 2003 Ent install to a BL460c. Several errors occurred during the scripting process that are disk related:

First - As the job tried to create the 8GB NTFS partition, I got this:
"RDeploy - Not enough space to add or resize the partition" - Error 152
So I went into the BIOS and did a Restore Default settings\Erase Boot disk. Still no luck.

Modified the initial NTFS partition from 8192GB to 100% of disk. Got past the error above.
Then...
"XCopy initialization failed - Return Code = 4."
SO...I went into the Server Deployment Toolbox and ran an Array Erase (WinPE).
Funny thing: Wipe.exe stopped to prompt me for which disk I wanted to wipe - Disk 1 or Disk 2. Disk 1 or Disk2? How did there get to be two disks on there anyway?!?!? Disk 1 is 922MB (yes...MB) and Disk 2 is 63GB. So I chose Disk 1 and then the follow up script in the RDP job erases the array configuration.
SO...I got past the XCopy problem. Then the Proliant files, the Altiris files and the OS Distribution files were copied over successfully. And I thought I was home free... Until...

Windows Setup stopped and indicated (See attachement).

Everything is brand new in this environment. I think the OS installation is still being copied down to that 922MB disk 1 and I can't figure out how the heck it got there and why it won't go away.
Any ideas are warmly welcomed.

Thank you!
Ed

[Gordon Leonard]

Strange things happen when you have bad bits.

Did you check the MD5 sum value?

[Ed Cox]

Well..it turns out that the 922MB drive was being detected because the QLogic card had an SSP connection to a LUN on an MSA. So the OS scripted installation was using the QLogic connection to the LUN as it's boot drive. Strange that it would do that since the BIOS has the E200i as the primary boot controller and the QLogic BIOS is not enabled, nor was it set for any Selectable Boot settings to even point to the MSA.
So...after shutting down the MSA during the scripting process, all is well. And wouldn't you know it...the same thing occurred this week at a customer site this week.
Ed

[Ole Thomsen_1]

I got the same error 152 "Rdeploy: There is not enough space to add or resize the partition" on a BL460c.

The server is connected to an EVA4000 but no LUNs presented. I could not shut down the SAN, but i tried to just disable the server ports on the SAN-switch.

And the error disappeared :-)

Thanks for the hint!

Ole Thomsen

[pasquino bocci_1]

Hi,

the installation will default to the SAN disk, so you have two choices:
1) disable the HBA
2) remove the FC cables.
Pasquino