- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- ILO issue B: drive NOT A: drive in ML 370 G4
Server Management - Remote Server Management
1753974
Members
7128
Online
108811
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
- Report Inappropriate Content
05-02-2008 12:19 PM
05-02-2008 12:19 PM
ILO issue B: drive NOT A: drive in ML 370 G4
This was annoying. I needed to run the Windows 2003 install and at first it said that it detected no hard drives so I tried again with the F6 option and the 641 driver files in my A: drive with the Virtual Media set on this server.
This got me way into the install (install running on an existing Windows server that needs repair), it detected and read my A: drive just fine until later in the install it needed to read it again and no luck.
I checked while logged into Windows that the Virtual Drive I had defined for A: was actually being read as drive B:! So the Windows setup either lost connection to the Virtual device altogether OR for some reason it changed over to be drive B:
Any thoughts on how to overcome this issue would be greatly appreciated. I upgraded from 1.82 to 1.91 for the ILO firmware but same issue.
Thanks.
MJ
This got me way into the install (install running on an existing Windows server that needs repair), it detected and read my A: drive just fine until later in the install it needed to read it again and no luck.
I checked while logged into Windows that the Virtual Drive I had defined for A: was actually being read as drive B:! So the Windows setup either lost connection to the Virtual device altogether OR for some reason it changed over to be drive B:
Any thoughts on how to overcome this issue would be greatly appreciated. I upgraded from 1.82 to 1.91 for the ILO firmware but same issue.
Thanks.
MJ
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP