- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- 641 Raid Controller on ML370 Boot issues
ProLiant Servers (ML,DL,SL)
1753969
Members
7439
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-10-2004 04:10 AM
05-10-2004 04:10 AM
641 Raid Controller on ML370 Boot issues
I discovered an interesting issue.
I have a ML-370 with a 641 Raid controller and is setup as follows.
2 arrays both are Raid 1+0
The C drive (array A)is comprized of 2 18.4Gb 10k hotswap drives. This drive System Software/OS (Win 2003 or 2000)
Drive E (Array B) is comprized of 2 36.4Gb 10k drives. Contains user profiles, data and installed programs.
We found this configuration to be an ideal configuration for many of our clients, until recently.
There is a scenario in which the system will no longer boot and it really bothers us and it seems on the surface to be a firmware issue on the 641 controller.
Recently we had a need to boot the backed up/mirrored drives on another system (identical configuration ML 370). Much to our suprize it did not boot.
We took one drive from each mirror C and E; inserted them into the test system. The 641 found the arrays and asked the F1 to fail or F2 for interim recovery. It only asked this question once. The system continued to boot. Upon booting Windows I get a BSOD (Blue Screen) "Bootable device not accessable"
After much trial an error I found this little bit of info.
IF you use 1 drive from each mirrored array, you will get the F1/F2 message only for the first array in error. The controller then automaticly fails the second one which is what causes our bluescreen.
If we use a complete mirror set on either array and minus one on the other then normal boot up happens just fine.
Our procedures with our customers is: IF we make changes or weekly we will swap a mirror to have a complete backup of the system. This way we supposedly have a complete copy of the systems off site.
Now with this issue we will need to buy more drives to take a complete mirror. Which is a pain because you must shutdown the systems to make this happen. Other than buying one large drive to merge the 2 arrays into 1 is there any workarounds?
Why does the 641 fail the second array when hitting F2? This is NOT the way mirroring should work. Note: This is not an issue on single array configurations.
I have a ML-370 with a 641 Raid controller and is setup as follows.
2 arrays both are Raid 1+0
The C drive (array A)is comprized of 2 18.4Gb 10k hotswap drives. This drive System Software/OS (Win 2003 or 2000)
Drive E (Array B) is comprized of 2 36.4Gb 10k drives. Contains user profiles, data and installed programs.
We found this configuration to be an ideal configuration for many of our clients, until recently.
There is a scenario in which the system will no longer boot and it really bothers us and it seems on the surface to be a firmware issue on the 641 controller.
Recently we had a need to boot the backed up/mirrored drives on another system (identical configuration ML 370). Much to our suprize it did not boot.
We took one drive from each mirror C and E; inserted them into the test system. The 641 found the arrays and asked the F1 to fail or F2 for interim recovery. It only asked this question once. The system continued to boot. Upon booting Windows I get a BSOD (Blue Screen) "Bootable device not accessable"
After much trial an error I found this little bit of info.
IF you use 1 drive from each mirrored array, you will get the F1/F2 message only for the first array in error. The controller then automaticly fails the second one which is what causes our bluescreen.
If we use a complete mirror set on either array and minus one on the other then normal boot up happens just fine.
Our procedures with our customers is: IF we make changes or weekly we will swap a mirror to have a complete backup of the system. This way we supposedly have a complete copy of the systems off site.
Now with this issue we will need to buy more drives to take a complete mirror. Which is a pain because you must shutdown the systems to make this happen. Other than buying one large drive to merge the 2 arrays into 1 is there any workarounds?
Why does the 641 fail the second array when hitting F2? This is NOT the way mirroring should work. Note: This is not an issue on single array configurations.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2004 04:25 AM
05-10-2004 04:25 AM
Re: 641 Raid Controller on ML370 Boot issues
Steven,
you are trying to abuse the controllers. It has nothing to do with how mirroring works. You are trying to do drive roaming with reduced arrays and the SmartArray controllers are not designed to do that. You have just been lucky if it worked for you in single array configurations.
you are trying to abuse the controllers. It has nothing to do with how mirroring works. You are trying to do drive roaming with reduced arrays and the SmartArray controllers are not designed to do that. You have just been lucky if it worked for you in single array configurations.
.
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