Loading...
Loading...
Lost two disks on separate SDSs simultaneously that caused data failed. Multiple attempts to exit maintenance mode fail. server@node-2-2 ~ $ scli --clear_sds_device_error --sds_ip 1X.2X.1X.1 --device_id 2c2zz93a01f30000 --clear_all Successfully cleared all SDS with IP 1X.2X.1X.1 (port 7072) devicesserver@node-2-2 ~ $ scli --query_all_sds | grep 1X.1X.1X.1 SDS ID: ce87bbdc000001cd Name: sds1X.1X.1X.1 State: Connected, Joined IP: 1X.1X.1X.1 Port: 7072 EXIT_MAINTENANCE_IN_PROGRESS Version: 2.0.5014server@node-2-2 ~ $ scli --exit_maintenance_mode --sds_ip 1X.1X.1X.1 --protection_domain_name PD3 --force_failed_device_id 2c2zz92401cb0000 Exit Maintenance Mode Results: SDS sds1X.9.1X.1: The specified SDS is in a process of exiting maintenance-mode.server@node-2-2 ~ $ scli --exit_maintenance_mode --sds_ip 1X.1X.1X.1 --protection_domain_name PD3 --force_failed_sds Exit Maintenance Mode Results: SDS sds10.11.10.1: The specified SDS is in a process of exiting maintenance-mode. Error: MDM failed command. Status: The specified SDS is in a process of exiting maintenance-mode. If you look at scli --query_all, you see we are. SDS Summary: Total 276 SDS Nodes 276 SDS nodes have membership state 'Joined' 276 SDS nodes have connection state 'Connected' 1 SDS nodes have maintenance state 'Exiting-Maintenance-Mode' 469.6 TB (480836 GB) total capacity 357.5 TB (366093 GB) unused capacity 0 Bytes snapshots capacity 45.1 TB (46192 GB) in-use capacity 0 Bytes thin capacity 45.1 TB (46168 GB) protected capacity 24.0 GB (24571 MB) failed capacity 0 Bytes degraded-failed capacity 0 Bytes degraded-healthy capacity 3.5 TB (3556 GB) unreachable-unused capacity
The system will not allow exiting Maintenance mode while there is failed capacity to protect the data.
User need to address the failed capacity, replace failed HW and allow rebuild to happen
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.