- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Disk Group Quarantine Issue After Replacing a Disk...
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
Forums
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
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
01-21-2025 02:02 AM
01-21-2025 02:02 AM
Hi everyone! Here’s the situation: There are two MSA2060-ENCL-SFF storage systems with MSA-12G-ENCL-LFF expansion shelves, one is old and the other is new. The old one is currently turned off. Both storage systems have Pool B with Disk Groups dgB01. On the expansion shelf of the old storage system, we needed to replace the fifth disk, so we replaced it with a disk from the old expansion shelf of the old system. The disk appeared in the system, but it is listed as an Unassociated Disk in Disk Groups (dgB01).
Here is the output from the CLI:
# show disk-groups
Name Size Free Pool Tier % of Pool Own RAID Disks Chk Status Current Job Job% Sec Fmt Health
----------------------------------------------------------------------------------------------------------------------------------
dgA01 30.6TB 18.4TB A Performance 100 A MSA-DP+ 22 512k FTOL VRSC 48% 512e OK
dgB01 63.9TB 30.0TB B Archive 100 B MSA-DP+ 12 512k FTOL VRSC 87% 512e Degraded
Reason
Action
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The spare capacity available to the MSA-DP+ disk group is not sufficient to meet the required configured spare capacity that is needed to provide full fault tolerance. Spare capacity availability can be influenced by operations that require available space in the system, such as reconstructing data from a failed disk.
- Add disks to the disk group, or replace any disks that may have failed. The system will automatically increase the spare capacity to meet the requirements placed on the system by the target spare capacity.
rcB01 3817.5GB 1481.8GB B Read Cache 0 B RAID0 2 512k UP 512e OK
dgB01 63.9TB 0B N/A 100 B MSA-DP+ 12 512k QTOF 512e Fault
Reason Action
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
The disk group is quarantined. - Look for events in the event log related to quarantine (172, 485, or 590), and follow the recommended actions for those events.
----------------------------------------------------------------------------------------------------------------------------------
Success: Command completed successfully. (2025-01-21 14:55:27)
#
As I understand it, it has read the metadata from the disk that was replaced from the old storage system with the same Disk Groups, and now it shows this Disk Group as quarantined. What can be done here?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2025 07:48 AM
01-21-2025 07:48 AM
Solution@abzalsoltankhan
If you can return the drive to the other system and remove the disk-group metadata on the disk, that would be the easiest way to clear the disk.
If you are unable to complete that task then you will need to contact HPE support and request an escalation. Clearing disk-metadata can be a very dangerous task, while this case seems to be straight forward, the initial levels of support are not supposed to be able to clear the metadata as a wrong step could permanently remove all data from the system.
FYI - more than likely the other system will also have problems that may require escalated support to recover, so it would be good to get both systems in a usable state sooner rather than later.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
