- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- raid fails when bad blocks are present.
ProLiant Servers (ML,DL,SL)
1753626
Members
5289
Online
108797
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
09-10-2008 11:39 AM
09-10-2008 11:39 AM
raid fails when bad blocks are present.
I have found a problem with our standard logical thinking (and HP training) regarding HP raid.
Scenario as follows:-
Standard raid 1 no hot spare.
Drive showed standard failed light (orange)
Replaced drive rebuild started.
Rebuild failed stating bad block on read.
The solution was as follows (after a lot of detective work).
Shut down machine fit original orange light failed drive ONLY
Power on machine and accept the default F2 option, this will self initiate after 30 seconds.
Let machine boot and check all okay (O/S boots as normal etc)
Put in new blank drive.
Open hp system management and check logical drive(s) is/are re-building.
You should now be okay.
The reason for this is the drive originally failed as HP Raid could not mirror a bad block, and the system reports incorrectly a failed drive.
I know this is unusual situation but i have now seen it twice,
I have no idea what would happen with raid 1 with Hotspare or raid 5. Only suspicions
has anyone had this on a raid 1 with hot spare or raid 5 system?
what was the resoloution?
cheers
Scenario as follows:-
Standard raid 1 no hot spare.
Drive showed standard failed light (orange)
Replaced drive rebuild started.
Rebuild failed stating bad block on read.
The solution was as follows (after a lot of detective work).
Shut down machine fit original orange light failed drive ONLY
Power on machine and accept the default F2 option, this will self initiate after 30 seconds.
Let machine boot and check all okay (O/S boots as normal etc)
Put in new blank drive.
Open hp system management and check logical drive(s) is/are re-building.
You should now be okay.
The reason for this is the drive originally failed as HP Raid could not mirror a bad block, and the system reports incorrectly a failed drive.
I know this is unusual situation but i have now seen it twice,
I have no idea what would happen with raid 1 with Hotspare or raid 5. Only suspicions
has anyone had this on a raid 1 with hot spare or raid 5 system?
what was the resoloution?
cheers
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