Why am I getting RAID Group De-activation event?

Problem/Symptom

Why am I getting RAID Group De-activation event?

Solution

1. Thin Provisioning pool -> 95% -> Deactivate.
When the used capacity of the thin provisioning pool reaches 60%, the system will send an event with information level to inform users.
This is the same as 70% and 80%. To 85%, in addition to the system issued an event with warning level, but also began to implement space reclamation.
After reaching 90%, it starts deleting the snapshot to keep the incoming data space.
If it reaches 95%, the pool will be deactivated to avoid any data error incurring from the OS side.
Please always watch the system logs of thin provisioning pool. If the used capacity of the thin provisioning pool reaches 95%, the system will deactivate the pool to avoid data loss.
So the host cannot access the pool at this time.
You have to expand the pool capacity, and then activate the pool to resolve the issue.

2. During the boot process, where member disk does not recognize
This is one of the reasons for the RAID Group Deactivate event.
When you boot, the system will detect all member hard disks, and when one of the member hard disks is not detected, the RAID Group Deactivate event will occur.

3. Manually set Deactivate -> Disk roaming -> another unit
Disk Roaming
Disks can be re-sequenced in the same system or move all member disks in the same pool from system-1 to system-2. This is called disk roaming.
System can execute disk roaming online.
Please follow these steps.
(1) Select the Pools function submenu, selects a pool. And then click ▼ -> Deactivate.
(2) Click the OK button to apply. The Status changes to Offline.
(3) Move all member disks of the pool to another system.
(4) In Volumes tab, select the pool. And then click ▼ -> Activate.
(5) Click the OK button to apply. The Status changes to Online.
Disk roaming has some constraints as described in the following.
(1) Check the firmware version of two systems first. It is better for both systems to have the same
firmware version or the firmware version of the system-2 is newer.
(2) All physical disks of the pool should be moved from system-1 to system-2 together. The configuration of both pool and volume will be kept but LUN configuration will be cleared in order to avoid conflict with the current setting of the system-2.
INFORMATION:
XCubeSAN series does NOT support disk roaming from AegisSAN LX, AegisSAN Q500, nor AegisSAN V100.

Apply to

All XCubeSAN module.