Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- ProLiant
- >
- ProLiant Servers - Netservers
- >
- Re: Win2003SP1 Unattended via WinPE2005 on DL380G5...
ProLiant Servers - Netservers
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-16-2007 12:48 AM
05-16-2007 12:48 AM
Win2003SP1 Unattended via WinPE2005 on DL380G5 with MSA60. Incorrect Boot Order; WinSetup uses array
Does anyone know of any boot order issues when calling WINNT32.exe via Windows PE 2005?
The BIOS boot order is set to P400 and drivers are both in WinPE and the Win2003SP1 unattended setup.
The attached MSA60 Smart Array is in PCIe slot 3 and is P800 controller. Again drivers in both.
The boot order is as follows:
P400
IDE
P800
The BIOS will not allow changing the IDE position.
This is what happens. WinPE detects the P800 as being the boot controller or detects the P400 as being it, but Windows Setup then uses the biggest disk available as the boot partition.
Upon reboot a blue screen happens, but if you then go into BIOS and switch boot order to being P800 instead of P400, Windows setup then appears and continues which proves that the BIOS is reporting P800 as boot partition to WinPE OR Windows Setup is using wrong drive. I suspect its WINPE as the first thing it does is format a C: partition succesfully - just C: on wrong disk set hence why proper boot partiton would state "Non System Disk..."
Anyone any thoughts on this ?
The BIOS boot order is set to P400 and drivers are both in WinPE and the Win2003SP1 unattended setup.
The attached MSA60 Smart Array is in PCIe slot 3 and is P800 controller. Again drivers in both.
The boot order is as follows:
P400
IDE
P800
The BIOS will not allow changing the IDE position.
This is what happens. WinPE detects the P800 as being the boot controller or detects the P400 as being it, but Windows Setup then uses the biggest disk available as the boot partition.
Upon reboot a blue screen happens, but if you then go into BIOS and switch boot order to being P800 instead of P400, Windows setup then appears and continues which proves that the BIOS is reporting P800 as boot partition to WinPE OR Windows Setup is using wrong drive. I suspect its WINPE as the first thing it does is format a C: partition succesfully - just C: on wrong disk set hence why proper boot partiton would state "Non System Disk..."
Anyone any thoughts on this ?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-16-2007 09:38 PM
05-16-2007 09:38 PM
Re: Win2003SP1 Unattended via WinPE2005 on DL380G5 with MSA60. Incorrect Boot Order; WinSetup uses array
Hello,
I would start with no partitions defined. This way you can only define one partition on the P400 controller where Windows should be installed.
Maybe you can force Windows this way to install on your defined partition.
Regards,
Arian!
I would start with no partitions defined. This way you can only define one partition on the P400 controller where Windows should be installed.
Maybe you can force Windows this way to install on your defined partition.
Regards,
Arian!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-17-2007 01:11 AM
05-17-2007 01:11 AM
Re: Win2003SP1 Unattended via WinPE2005 on DL380G5 with MSA60. Incorrect Boot Order; WinSetup uses array
While I agree with Arian, start with a simple machine, install Windows, add peripherals, I doubt customers would be satisfied with that workaround.
With that being said, I don't call Winnt32.exe from within WinPE 2005, but I can confirm that at least on an ML570 G3 with multiple SA-6400's, that the POST drive order, the Windows Server drive ordering, and WinPE 2005's drive ordering are different. This appears to be regardless of how the boot order is set in the ORCA and system RBSU or manual IRQ assignments for the SA-6400's.
What is particularly puzzling is why with the same system configuration that WinPE 2005 (generated from Windows Server 2003 SP1) and Windows Server 2003 SP1 do not always show the same drive ordering.
Sorry that this probably doesn't help much, but I just wanted to confirm what you're seeing.
With that being said, I don't call Winnt32.exe from within WinPE 2005, but I can confirm that at least on an ML570 G3 with multiple SA-6400's, that the POST drive order, the Windows Server drive ordering, and WinPE 2005's drive ordering are different. This appears to be regardless of how the boot order is set in the ORCA and system RBSU or manual IRQ assignments for the SA-6400's.
What is particularly puzzling is why with the same system configuration that WinPE 2005 (generated from Windows Server 2003 SP1) and Windows Server 2003 SP1 do not always show the same drive ordering.
Sorry that this probably doesn't help much, but I just wanted to confirm what you're seeing.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP