- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Parity Initialization Status
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
10-31-2011 01:50 AM
10-31-2011 01:50 AM
Parity Initialization Status
We have a smart array 5i in embedded slot running from a DL380 G2 to a disk sub system (Old I know) configured as a 450 GB raid 5 array the server went down over the weekend for some unknow reason and the controller disabled the logical drive due to errors, we dont have much hope for the data but started an Initialization on the logical drive as the array config utility can still see them in the hope we may be able to recover something, problem is the has now been running for about 72 hours. Does anyone know how long this could pottentially take?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2011 05:21 AM
10-31-2011 05:21 AM
Re: Parity Initialization Status
The 5i is an embedded SCSI. The largest SCSI drive I recall HP delivering was a 300GB. I doubt the smart array card firmware knows how to handle the extra blocks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2011 05:26 AM
10-31-2011 05:26 AM
Re: Parity Initialization Status
Never mind, you said, 450GB Raid 5 LUN. Not enough coffee.
If you are doing a inititialization again? You deleted the LUN? If you deleted the LUN, the LUN device ID changed, the HOST will see it as a different volume.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2011 05:52 AM
10-31-2011 05:52 AM
Re: Parity Initialization Status
We didnt delete the LUN when the server came back up we had the option to re enable the disabled logical drive to recover some data which forced the array to initialize, its been stuck here since.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2011 04:29 AM
11-07-2011 04:29 AM
Re: Parity Initialization Status
It sounds like the Raidset has hit a URE, unrecoverable read error on one of the members. This will cause the init to stop. You could look at a ADU report and look at the Hard Read Errors, since reset for each member. But in the end, I think you will have backup data, delete the volume and replace a few drives. And recreate everything.