- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Rebooting with a failed drive
Disk Enclosures
1753290
Members
5391
Online
108792
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
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
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
тАО11-27-2000 04:00 PM
тАО11-27-2000 04:00 PM
Rebooting with a failed drive
We have built a Server Farm that consists of 13 Compaq Proliant DL380 Servers. These Servers all have Integrated Smart Array Controllers v1.34 and two Mirrored disks.
To resolve a number of Printing Problems under Terminal Server we have written KixStart scripts to reboot the servers overnight . If a disk fails during the boot sequence though the BIOS generates a "1790 ... Drive array not responding" error and stops until the F1 or F2 is pressed.
Is there anyway to configure the BIOS or the Array controller so the failed device is automatically failed and the boot sequence continues using the remaining disk?
Thanks in advance.
To resolve a number of Printing Problems under Terminal Server we have written KixStart scripts to reboot the servers overnight . If a disk fails during the boot sequence though the BIOS generates a "1790 ... Drive array not responding" error and stops until the F1 or F2 is pressed.
Is there anyway to configure the BIOS or the Array controller so the failed device is automatically failed and the boot sequence continues using the remaining disk?
Thanks in advance.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2000 04:00 PM
тАО12-03-2000 04:00 PM
Re: Rebooting with a failed drive
You have to enter the Advanced EISA Setup by pressing "Ctrl.+A" instead of "Enter" on the first screen. Then you can change the setting "Stop at F1 prompt on error" to no. This should solve your problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2000 04:00 PM
тАО12-19-2000 04:00 PM
Re: Rebooting with a failed drive
Thanks , Taylor for your help . The F1 prompt on boot can be disabled , via the Advanced Mode (ctrl A) of the System Configuration Utility .
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