- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- "Background Parity Initialization is queued or in ...
Disk Enclosures
1752492
Members
5446
Online
108788
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
12-19-2006 04:14 AM
12-19-2006 04:14 AM
"Background Parity Initialization is queued or in progress..." on SA Clustered Storage controller
We have a DL380 G2 packaged cluster with a few arrays configured on it. One in particular, made up of 3 x 73Gb drives, we are looking to upgrade with 3 x 146Gb drives by swapping one disk out at a time, letting the array rebuild itself and ultimately expanding the logical drive into the unused space.
However, we have the above message on it when viewed through ACU although I'm not sure how long it's been there, but it's been at least a couple of weeks.
It /may/ have been there since the array was built within the cluster (judging by at least one similar such post I've read whilst researching the issue) as this array hosts the Quorum resource.
The only thing that makes me second-guess this is that we also have another packaged cluster (DL380 G3 with MSA500) which doesn't exhibit this issue, although the former is Win2k and the later is Win2k3.
So, is it safe for me to replace the drives? It should be clear that the array is being rebuilt shouldn't it (i.e. to work out when it's safe to replace the next drive).
Any assistance appreciated.
Regards,
Paul
However, we have the above message on it when viewed through ACU although I'm not sure how long it's been there, but it's been at least a couple of weeks.
It /may/ have been there since the array was built within the cluster (judging by at least one similar such post I've read whilst researching the issue) as this array hosts the Quorum resource.
The only thing that makes me second-guess this is that we also have another packaged cluster (DL380 G3 with MSA500) which doesn't exhibit this issue, although the former is Win2k and the later is Win2k3.
So, is it safe for me to replace the drives? It should be clear that the array is being rebuilt shouldn't it (i.e. to work out when it's safe to replace the next drive).
Any assistance appreciated.
Regards,
Paul
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