PowerFlex Alerts and Events Reference Guide File Services Core Alerts
Summary: All alerts in this article apply to the file subsystem. These alerts do not have SCG symptom IDs, except where noted.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Instructions
PowerFlex Alerts and Events for File services core alerts
For the full list See Dell PowerFlex 4.6.x Alerts and Events Reference Guide
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101b03 | CEPP_ALL_SER VERS_UNREAC HABLE |
All the publishing pools of the {{nasServer}} NAS server are unavailable. | MAJOR | Events on the publishing pools of the {{nasServer}} NAS server may not be available for the CEPA server. | Check the NAS server network connectivity.
Check NAS server publishing pool and CEPA server configuration. |
file-events- publisher.cepp- all-servers- unreachable |
| 50101601 | CLUSTER_FS_F REESPACE_LO W |
The root file system in the NAS cluster object (fsid {{fsid}}) is low on free space. | MINOR | The file system is running low on free space. Creations and modifications of NAS objects may start failing. | Contact your service provider. | nas-cluster- config.cluster- fs-freespace- low |
| 50101701 | CLUSTER_FS_ STORAGE_DEVI CE_POTENTIAL LY_IMPACTED |
Recovery is recommended on the root file system in the NAS cluster object (fsid {{fsid}}). | CRITICAL | The file system's backing storage LUN has reported a potential impact; recovery is recommended on the FS. | Contact your service provider. | nas-cluster- config.cluster- fs-storage- device- potentially- impacted |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50103703 | CLUSTER_DAT A_SERVICE_CL USTER_DATA_ SERVICE_ENAB LED_NO_RECO VERY |
Cluster data service state enabled but automatic recovery is disabled. | MAJOR | Cluster data service state is enabled but automatic NAS server recovery is disabled for service procedure. NAS servers which go completely down will not be recovered automatically to prevent rolling panic. | Enable data service recovery after all issues are resolved. | nas-cluster- config.cluster- data-service- enabled-no- recovery |
| 50103704 | CLUSTER_DAT A_SERVICE_CL USTER_DATA_ SERVICE_ENAB LED_VERIFY_D ATA_LOSS |
Cluster is in state when block storage reports potential data loss for all user NAS servers. | MAJOR | Restore from data loss procedure is in progress. Data service is enabled cluster- wide but all user NAS servers reports potential data loss on mount. | After recovery is complete clear the cluster-wide flag which enables data loss verification. | nas-cluster- config.cluster- data-service- enabled-verify- data-loss |
| 50103c01 | CLUSTER_SQL_CACHE_CLUS TER_SQLCACH E_DISABLED |
The SQL cache has been disabled due to DB internal issue. | MAJOR | The SQL cache is disabled due to internal issue. The REST-API server is working now in degraded mode, filtering and paging are unavailable, slow response could be expected. | Check the Filesystem or the LUN hosting the SQL database using svc_recover service command. | nas-cluster- config.cluster- sql-cache- cluster- sqlcache- disabled |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50100103 | DNS_SERVICE_ ALL_SERVERS_ UNREACHABLE |
The DNS client of the {{nasServer}} NAS server is unable to connect to all configured DNS servers. | MAJOR | The DNS client is unable to contact any DNS server and so is not operational. This may happen when the NAS server cannot reach the peer DNS server because of network problems. | Check the NAS server network interface and the router configuration. Or check the availability of the configured DNS server running the 'svc_cifssupport-checkup' or 'svc_nas -dns' command from the NAS container. | file-dns- servers.dns- service-all- servers- unreachable |
| 50101815 | IMPORT_SESSI ON_ERROR_INI TIAL_PROVISIO NING |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed to complete initial provisioning. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has failed to complete the initial provisioning stage. The error occurred while preparing the target NAS server and the source system for the import (error {{errorCode}}). The import process is suspended. See the report on the import session for details. | Use Resume action to retry initial provisioning and continue the import process. The import process can be canceled at any moment using Cancel action. | file-import- sessions.import- session-error- initial- provisioning |
| 50101816 | IMPORT_SESSI ON_ERROR_INI TIAL_COPY |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed to complete the initial data copy. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has failed during the initial (baseline) data copy stage. The data transfer may be suspended for some of the file systems (error {{errorCode}}). See the report on the import session for details. | Use Resume action to retry and continue with the initial data copy for failed file systems. The operation is attempted automatically if possible. The import process can be canceled at any moment using Cancel action. | file-import- sessions.import- session-error- initial-copy |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101817 | IMPORT_SESSI ON_ERROR_IM PORTING_CON FIG |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed to import the configuration. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has failed during the configuration import stage.
The error occurred while retrieving settings from the source system and applying them to the target NAS server (error {{errorCode}}). The import process is suspended. See the report on the import session for details. |
Use Resume action to retry importing the configuration and continue the process. Skip Failed Step option allows to ignore the failed operation and continue to the next import step if possible. This option can cause an inconsistency in the configuration and even data unavailability after cutover.
The import process can be canceled at any moment using Cancel action. |
file-import- sessions.import- session-error- importing-config |
| 50101818 | IMPORT_SESSI ON_ERROR_CU TTING_OVER |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed to cutover. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has failed during the cutover stage. The error occurred while trying to reconnect clients from the source to the target NAS server (error {{errorCode}}). Clients may experience data unavailability.
See the report on the import session for details. |
Use Cutover action again to retry. Manual intervention may be required to restore the client data access. The import process can be canceled at any moment using Cancel action. | file-import- sessions.import- session-error- cutting-over |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101822 | IMPORT_SESSI ON_ERROR_CL USTER_CONTR OLLER_FAILOV ER |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed due to a restart of the cluster controller. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has been interrupted because the cluster controller was restarted on the target system. This may be due to a node failure or an intentional role transfer.
The import session will be recovered and resumed once the cluster controller is fully operational. |
Wait until the import session is recovered.
Retry the last operation if it is not resumed automatically. The import process can be canceled at any moment using Cancel action. |
file-import- sessions.import- session-error- cluster- controller- failover |
| 50101823 | IMPORT_SESSI ON_ERROR_C ONNECTING_D ATA_NODE |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed to connect to the target NAS server's node. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has failed due to unavailability of the target NAS server's node.
The system health status may provide more details. |
Check the system health status, ensure that the target NAS server's node is operational and try to repeat the last operation. The import process can be canceled at any moment using Cancel action. | file-import- sessions.import- session-error- connecting- data-node |
| 50101824 | IMPORT_SESSI ON_ERROR_C ONNECTING_C LUSTER_CONT ROLLER |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed to connect to the cluster controller. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has failed due to unavailability of the cluster controller on the target system. The system health status may provide more details. | Check the system health status, ensure that the cluster controller is operational and try to repeat the last operation. The import process can be canceled at any moment using Cancel action. | file-import- sessions.import- session-error- connecting- cluster- controller |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101825 | IMPORT_SESSI ON_ERROR_SA VE_CHANGES |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed to save changes to the persistent storage. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has failed when saving changes to the persistent storage on the target system. The import state may be inconsistent.
The system health status may provide more details. |
Check the system health status, ensure that the issues with the storage are resolved and try to repeat the last operation. The import process can be canceled at any moment using Cancel action. | file-import- sessions.import- session-error- save-changes |
| 50101826 | IMPORT_SESSI ON_ERROR_INI TIAL_COPY_FAI LED_TO_PING_ SOURCE_SYST EM |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed to complete the initial data copy. Failed to ping the source system. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has failed to proceed with the initial (baseline) data copy from source NAS server '{{sourceNasSer verName}}'. The error occurred while trying to ping the source system. The data transfer is suspended. | Check connection to the source system. Ensure that ICMP traffic is not blocked. Use Resume action to retry and continue with the initial data copy for failed file systems.
The operation is attempted automatically if possible. The import process can be canceled at any moment using Cancel action. |
file-import- sessions.import- session-error- initial-copy- failed-to-ping- source-system |
| 50101827 | IMPORT_SESSI ON_ERROR_IN CREMENTAL_C OPY_FAILED_T O_PING_SOUR CE_SYSTEM |
Import session '{{importSession Name}}' ({{importSessio nId}}) failed to resume the incremental data copy. Failed to ping the source system. | MAJOR | Import session '{{importSession Name}}' ({{importSessio nId}}) has failed during the incremental data copy from source NAS server '{{sourceNasSer verName}}'. The error occurred while trying to ping the source system. The data transfer is suspended.
Clients may experience data unavailability. |
Check connection to the source system. Ensure that ICMP traffic is not blocked. Use Resume action to retry and continue with the incremental data copy for failed file systems. The operation is attempted automatically if possible. The import process can be canceled at any moment using Cancel action. | file-import- sessions.import- session-error- incremental- copy-failed-to- ping-source- system |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d09 | FS_IMPORT_E RROR_UNREC OVERABLE |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed due to a general error. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) encountered a general error. It is not possible to continue the data copy.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Use Resume action to restart the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- unrecoverable |
| 50101d0a | FS_IMPORT_E RROR_UNREC OVERABLE_DE ST_FSCKED |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because the file system recovery process has modified the target file system. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because the file system recovery process has modified the target file system. It is not possible to continue the data copy.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Use Resume action to restart the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- unrecoverable- dest-fscked |
| 50101d0b | FS_IMPORT_E RROR_UNREC OVERABLE_AP P_LOG_FAIL |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed due to an unsuccessful failover recovery. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed due to an unsuccessful failover recovery. There was an unsuccessful attempt to restart the import after a failure. It is not possible to continue the data copy.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Use Resume action to restart the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- unrecoverable- app-log-fail |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d0c | FS_IMPORT_E RROR_CONNE CTION |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because the data connection to the source system was terminated. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed. The data connection between the source and the target system was terminated. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the network connectivity between the target system and the source system, and resolve potential issues that might prevent establishing a connection.
Then, use Resume action to resume the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. |
file-systems.fs- import-error- connection |
| 50101d0d | FS_IMPORT_E RROR_DHSM_ AUTH |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because DHSM HTTP connection encountered an authentication error. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed. DHSM HTTP connection encountered an authentication error. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the provided source DHSM username and password. Then, use Resume action to continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- dhsm-auth |
| 50101d0e | FS_IMPORT_E RROR_DHSM_ SSL_CONNECT ION |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because DHSM HTTP connection encountered an SSL error. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed. DHSM HTTP connection encountered an SSL error.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Check the connectivity between the target system and the source system, and resolve potential issues that might prevent establishing an SSL connection. Then, use Resume action to continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- dhsm-ssl- connection |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d0f | FS_IMPORT_E RROR_DHSM_ BAD_REQUEST_RESPONSE |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because a bad request or response was transferred over the DHSM HTTP connection. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed. A bad request or response was transferred over the DHSM HTTP connection. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the status of the DHSM server on the source system and resolve any issues. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- dhsm-bad- request- response |
| 50101d10 | FS_IMPORT_E RROR_DESTIN ATION_IO |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed due to an I/O error on the target system. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) encountered an I/O error on the target system. Import session '{{importSession Name}}' ({{importSessio nId}}). | Use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- destination-io |
| 50101d11 | FS_IMPORT_E RROR_DESTIN ATION_QUOTA_EXCEEDED |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because a quota of the target file system was exceeded. file system was exceeded. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed. A quota of the file system was exceeded on the target system. Import session '{{importSession Name}}' exceeded on the source system. Write mirroring is required to ensure the data consistency on the source side in case a rollback is performed.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Increase the quota of file system '' on the target system. Then, use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- destination- quota-exceeded |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d17 | FS_IMPORT_E RROR_SOURCE_NO_SPACE |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because there was no free space available on the source file system. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed. There was no free space available on the source system. Write mirroring is required to ensure the data consistency on the source side in case a rollback is performed.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Increase the size of the source file system. Then, use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- source-no- space |
| 50101d18 | FS_IMPORT_E RROR_SOURCE_NAME_TOO_L ONG |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because a file path on the source file system is too long. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed. A file path on the source file system exceeds the permitted length and cannot be imported.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Cancel this import session, ensure that file path on source file system '' do not exceed 1023 UTF-16 code units, and then create another import session. Alternatively, contact your service provider. | file-systems.fs- import-error- source-name- too-long |
| 50101d19 | FS_IMPORT_E RROR_INTERN AL_ERROR |
The import of file system '{{targetFilesyst get the status from the target NAS server's node. | MAJOR | The import of file system '{{targetFilesyst get the status from the target NAS server.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Check the system health status and the action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- internal-error |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d1d | FS_IMPORT_E RROR_STARTI NG_BUSY |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because a previous attempt did not complete gracefully. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because a previous attempt to import this file system did not complete gracefully.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Use Resume action to resume the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-busy |
| 50101d1e | FS_IMPORT_E RROR_STARTI NG_DHSM_AU TH |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start due to a DHSM HTTP authentication error. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start. The DHSM HTTP connection encountered an authentication error. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the provided source DHSM username and password. Then, use Resume action to continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-dhsm- auth |
| 50101d1f | FS_IMPORT_E RROR_STARTI NG_DHSM_SSL_NEGOTIATE |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because the DHSM SSL negotiation was unsuccessful. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start. SSL negotiation was unsuccessful while establishing a secure DHSM connection. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the connectivity between the target system and the source system, ensure that SSL is enabled for DHSM server on the source system, and resolve potential issues that might prevent establishing an SSL connection. Then, use Resume action to resume the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-dhsm- ssl-negotiate |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d20 | FS_IMPORT_E RROR_STARTI NG_DHSM_SE ND_REQUEST |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because there was a problem sending a DHSM HTTP request. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start. There was a problem sending a DHSM HTTP request. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the connectivity between the target system and the source system, and resolve potential issues. Then, use Resume action to continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-dhsm- send-request |
| 50101d21 | FS_IMPORT_E RROR_STARTI NG_DHSM_CLI ENT |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because the DHSM HTTP client is not available. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start. The DHSM HTTP client is not available. Import session '{{importSession Name}}' ({{importSessio nId}}). | Reduce the system load and memory usage on the target system. Then, use Resume action to resume the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-dhsm- client |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d22 | FS_IMPORT_E RROR_STARTI NG_DHSM_CN X_INIT |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because the DHSM HTTP client was not initialized properly. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start. The DHSM HTTP client was not initialized properly. Import session '{{importSession Name}}' ({{importSessio nId}}). | Verify that the system parameter 'imt.remoteDhs mPort' is set to a nonzero value. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-dhsm- cnx-init |
| 50101d23 | FS_IMPORT_E RROR_STARTI NG_LOCAL_FIL E_SYSTEM_NO T_FOUND |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because the target file system could not be found. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because the file system could not be found on the target system. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the health status of the target system. Use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-local- file-system-not- found |
| 50101d24 | FS_IMPORT_E RROR_STARTI NG_LOCAL_FIL E_SYSTEM_TH AW |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because the access to the target file system could not be restored. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start. The access to the file system could not be restored on the target system.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Check the health status of the target system. Use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-local- file-system- thaw |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d2b | FS_IMPORT_E RROR_STOPPI NG_LOCAL_FIL E_SYSTEM_TH AW |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to stop because the access to the target file system could not be restored. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to stop. The access to the file system could not be restored on the target system.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Check the health status of the target system. Then, retry the action to continue. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- stopping-local- file-system- thaw |
| 50101d2c | FS_IMPORT_E RROR_STOPPI NG_LOCAL_FIL E_SYSTEM_NO T_FOUND |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to stop because the target file system could not be found. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to stop. The file system could not be found on the target system. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the health status of the target system. Then, retry the action to continue. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- stopping-local- file-system-not- found |
| 50101d2d | FS_IMPORT_E RROR_STARTI NG_DESTINATI ON_IS_READ_ ONLY |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because the target file system became read-only. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start. The file system became read-only on the target system. Import session '{{importSession Name}}' ({{importSessio nId}}). | Make target file system '' writable. Then, use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting- destination-is- read-only |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d2e | FS_IMPORT_E RROR_STOPPI NG_DESTINATI ON_IS_READ_ ONLY |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to stop because the target file system became read-only. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to stop. The file system became read-only on the target system. Cleaning up the migration database is not possible. Import session '{{importSession Name}}' ({{importSessio nId}}). | Make target file system '' writable. Then, retry the action to continue. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- stopping- destination-is- read-only |
| 50101d2f | FS_IMPORT_E RROR_STARTI NG_DESTINATI ON_LOW_SPA CE |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because the target file system was low on space. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed. The file system on the target system was low on space.
Import session '{{importSession Name}}' ({{importSessio nId}}). |
Increase the size of the target file system to avoid the low-on- space condition. Then, use Resume action to retry and continue the data copy. Extra space may be required on the target file system to complete the import due to metadata differences between the source and the target file systems. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting- destination-low- space |
| 50101d30 | FS_IMPORT_E RROR_STARTI NG_FAILED_TO_MIGRATE_DH SM_CONNECTI ONS |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because an error occurred while importing the DHSM connections. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start due to an unsuccessful attempt to import the DHSM connections of the file system. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the health status of the target system. Use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-failed- to-migrate- dhsm- connections |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101d31 | FS_IMPORT_E RROR_STARTI NG_DHSM_BA D_REQUEST_R ESPONSE |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start because a bad request or response was transferred over the DHSM HTTP connection. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed to start. A bad request or response was transferred over the DHSM HTTP connection. Import session '{{importSession Name}}' ({{importSessio nId}}). | Check the status of the DHSM server on the source system and resolve any issues. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- starting-dhsm- bad-request- response |
| 50101d32 | FS_IMPORT_E RROR_LOW_O N_RESOURCES |
The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because the target system is low on resources. | MAJOR | The import of file system '{{targetFilesyst emName}}' ({{targetFilesyst emId}}) failed because of excessive load on the target system. Import session '{{importSession Name}}' ({{importSessio nId}}). | Reduce the system load and memory usage on the target system. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs- import-error- low-on- resources |
| 50100501 | LDAP_SERVICE_CONFIG_FAIL ED |
The LDAP service configuration of the NAS server {{nasServer}} for domain {{domain}} failed. | MAJOR | The LDAP service configuration of the NAS server {{nasServer}} for domain {{domain}} failed. The LDAP client is not operational. | Run the 'svc_cifssupport-checkup' or 'svc_nas -ldap' command from the NAS container for diagnostics. | file-ldap- servers.ldap- service-config- failed |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50100502 | LDAP_SERVICE_IS_BADLY_CO NFIGURED |
LDAP client settings on NAS server {{nasServer}} are not valid within domain {{domain}}. | MAJOR | You have configured a LDAP service in server {{nasServer}} for the domain {{domain}}. But the LDAP service encounters some configuration issue. So you could get some unexpected issue using this name resolver. | On NAS server check LDAP configuration for domain.
Check binding and access rights to this LDAP server, in particular the username and password used to connect to the server. Run the 'svc_cifssupport-checkup' or 'svc_nas -ldap' command from the NAS container for diagnostics. |
file-ldap- servers.ldap- service-is-badly- configured |
| 50100505 | LDAP_SERVICE_ALL_SERVERS_UNREACHABL E |
No LDAP servers configured for NAS server {{nasServer}} are responding. | MAJOR | In the NAS server {{nasServer}}, LDAP service could not provide mapping anymore. All configured LDAP servers for domain {{domain}} are now out of order. | In the NAS server, check the availability of LDAP servers configured for domain . At least one of the configured LDAP server need to be operational.
Check for LDAP service status or for connectivity issue. It is recommended to configure at least two LDAP servers per domain. Or check the availability of the configured LDAP server running the 'svc_cifssupport-checkup' command from the NAS container. |
file-ldap- servers.ldap- service-all- servers- unreachable |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50100c01 | NAS_SERVER_ OUT_OF_SERVI CE |
NAS server {{vdmname}} is down. | CRITICAL | NAS server {{vdmname}} doesn't provide service on any of NAS cluster nodes. | Contact your service provider in case the NAS server will not be up in a near future. | nas-servers.nas- server-out-of- service |
| 50100c02 | NAS_SERVER_ DEGRADED |
NAS server {{vdmname}} fault tolerance is degraded. | MAJOR | NAS server {{vdmname}} is serving, but its fault tolerance is degraded. The service might be disrupted in case of unexpected failure. | Contact your service provider in case the NAS server will not become fault tolerant in a near future. | nas-servers.nas- server-degraded |
| 50100c05 | NAS_SERVER_I N_MAINTENAN CE |
NAS server {{vdmname}} is in maintenance mode. | CRITICAL | NAS server {{vdmname}} is in maintenance mode for recovery. | Contact your service provider. | nas-servers.nas- server-in- maintenance |
| 50100c06 | NAS_SERVER_ NAS_SERVER_ CLUSTER_DAT A_SERVICE_ST OPPED |
NAS server {{vdmname}} is down due to stopped service. | MAJOR | NAS server {{vdmname}} is stopped because administrator has requested to stop all data services on the NAS cluster. | N/A | nas-servers.nas- server-cluster- data-service- stopped |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50100c09 | NAS_SERVER_ NAS_SERVER_ UNRECOVERAB LE |
The NAS server {{vdmname}} is in an unrecoverable state after its deletion that have failed. | CRITICAL | Deletion of the NAS server failed, some resouces are left in the system, manual intervention is likely needed. | Contact your service provider. | nas-servers.nas- server- unrecoverable |
| 50101202 | NAS_SERVER_ FS_STATE_UN MOUNTED_IO_ ERROR |
The {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}) is offline due to receiving an I/O error. | CRITICAL | The file system has received an I/O error and is unmounted.
There may be a problem with the storage device. |
Please contact support. | nas-servers.nas- server-fs-state- unmounted-io- error |
| 50101203 | NAS_SERVER_ FS_STATE_UN MOUNTED_CO RRUPTION_DE TECTED |
The {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}) is offline after discovering corruption. | CRITICAL | The file system has discovered internal corruption and is unmounted. The NAS server is offline. | Contact your service provider. | nas-servers.nas- server-fs-state- unmounted- corruption- detected |
| 50101204 | NAS_SERVER_ FS_STATE_SER VICE_UNMOUN TED |
The {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}) has been taken offline for service. | MAJOR | The file system has been taken offline for service. | Complete the planned service procedure and remount the FS with 'svc_recover-action mount' service command. | nas-servers.nas- server-fs-state- service- unmounted |
| 50101205 | NAS_SERVER_ FS_STATE_REC OVERED_OK |
The {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}) has completed recovery and is waiting to be restarted. | MAJOR | The file system has completed recovery and is waiting to be restarted. | Contact your service provider. | nas-servers.nas- server-fs-state- recovered-ok |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101206 | NAS_SERVER_ FS_STATE_REC OVERY_FAILED |
Recovery failed on the {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}. | CRITICAL | Recovery failed on the file system, manual intervention is likely needed. | Contact your service provider. | nas-servers.nas- server-fs-state- recovery-failed |
| 50101301 | NAS_SERVER_ FS_STORAGE_ DEVICE_POTEN TIALLY_IMPAC TED |
Recovery is recommended on the {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}). | CRITICAL | The file system's backing storage LUN has reported a potential impact; recovery is recommended on the FS. | Run recovery on the FS with 'svc_recover-action recover' and remount it with 'svc_recover-action mount'. | nas-servers.nas- server-fs- storage-device- potentially- impacted |
| 50104001 | NAS_SERVER_ CONFIG_SNAP_NAS_SERVER_CONFIG_SNA P_REFRESH_F AILED |
The configuration filesystem snap refresh on the NAS server {{vdmname}} has failed with the following error {{error}}. | MAJOR | While starting the NAS server in destination mode, the refresh of the configuration filesystem snap has failed. This may be due to an issue with the configuration filesystem which might be corrupted. If the NAS server is still up in non production mode, the configuration information might be stale. | The refresh snap issue must first be fixed. If the problem happened during a switchover, you must complete it with svc_dataprotect ion service command from the former source side: - svc_dataprotect ion nasServer-vdmoid xxxx-action switchoversessi on -fsoid xxxx for each user file system replication switchoversessi on - svc_dataprotect ion nasServer-vdmoid xxxx-action switchtodestina tionmode to start the NAS server in destination mode | nas-servers.nas- server-config- snap-refresh- failed |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50104102 | NAS_SERVER_ FILE_INTERFAC E_SOME_NAS_ SERVER_INTER FACES_IN_FAIL URE |
One or more file interfaces on the NAS server {{vdmname}} are in failure. | MAJOR | One or more file interfaces on the NAS server {{vdmname}} are wrongly configured. | Get the file interfaces list for the NAS server and modify their configuration accordingly to the network environment. | nas-servers.nas- server-file- interface-some- nas-server- interfaces-in- failure |
| 50104103 | NAS_SERVER_ FILE_INTERFAC E_ALL_NAS_SE RVER_INTERFA CES_IN_FAILU RE |
All file interfaces on the NAS server {{vdmname}} are in failure. | MAJOR | All file interfaces on the NAS server {{vdmname}} are wrongly configured. | Get the file interfaces list for the NAS server and modify their configuration accordingly to the network environment. | nas-servers.nas- server-file- interface-all- nas-server- interfaces-in- failure |
| 50100403 | NIS_SERVICE_ ALL_SERVERS_ UNREACHABLE |
The NIS client is unable to connect to all configured NIS servers. | MAJOR | The NIS client is unable to contact any NIS server and so is not operational. This may happen when the NAS server cannot reach the peer NIS server because of network problems. | Check the NAS server network interface and the router configuration. Or check the availability of the configured NIS server running the 'svc_cifssupport-checkup' or 'svc_nas -nis' command from the NAS conainter. | file-nis- servers.nis- service-all- servers- unreachable |
| 50101901 | NFS_SERVER_ JOINED_NO |
The NFS server of the NAS server {{nasServer}} is configured with nfs secure using the SMB configuration, but is currently not registered in SMB AD KDC. | MAJOR | In order to work, a NFS server which is configured with nfs secure using the SMB configurqtion must be registered into the KDC of the windows domain. No user can actually connect. | Register the NFS server in the SMB KDC with join rest api call. | nfs-servers.nfs- server-joined-no |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50100d01 | NODE_DOWN |
NAS node {{node}} is temporarily down. | MAJOR | NAS node {{node}} is temporarily down, but should be back up shortly. | Contact your service provider in case the failed node will not be recovered in a near future. | nas- nodes.node- down |
| 50100d03 | NODE_RECOVE RY_FAILED |
NAS node {{node}} is down and its automatic recovery has failed. | CRITICAL | NAS node {{node}} is down and its automatic recovery has failed. | Contact your service provider in case the failed node will not be recovered in a near future. | nas- nodes.node- recovery-failed |
| 50101501 | NODE_FS_STO RAGE_DEVICE_ POTENTIALLY_I MPACTED |
Recovery is recommended on the root file system in NAS node {{node}} (fsid {{fsid}}). | CRITICAL | The file system's backing storage LUN has reported a potential impact; recovery is recommended on the FS. | Contact your service provider. | nas- nodes.node-fs- storage-device- potentially- impacted |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 5010280a | NON_RECOVE RABLE_ERROR S_PRI_POSTEV T_FAILED |
File system replication session (id:{{fsReplicationS essionId}}) transfer failed. Session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication- sessions.non- recoverable- errors-pri- postevt-failed |
| 50102801 | NON_RECOVE RABLE_ERROR S_PRISCH_REC OVER_FAILED |
File system replication session (id:{{fsReplicationS essionId}}) recovery failed and session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication- sessions.non- recoverable- errors-prisch- recover-failed |
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50100906 | FS_STATE_REC OVERY_FAILED |
Recovery failed on file system {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}. | CRITICAL | Recovery failed on the file system, manual intervention is likely needed. | Contact your service provider. | file-systems.fs- state-recovery- failed |
| 50100907 | FS_STATE_CRE ATE_FAILED_C OULD_NOT_CL EANUP |
File system {{fsname}} in NAS server {{vdmname}} failed creation but could not cleanup the object completely. The object is not usable and can only be deleted. | CRITICAL | The file system create has failed, the object is not usable. | Attempt to delete the file system object at a later time. | file-systems.fs- state-create- failed-could- not-cleanup |
| 50100908 | FS_STATE_SN AP_CREATE_F AILED_COULD_ NOT_CLEANUP |
Snap {{fsname}} in NAS server {{vdmname}} failed creation but could not cleanup the object completely. The object is not usable and can only be deleted. | CRITICAL | The snap create has failed, the object is not usable. | Attempt to delete the snap object at a later time. | file-systems.fs- state-snap- create-failed- could-not- cleanup |
| 50100909 | FS_STATE_CL ONE_CREATE_ FAILED_COULD_NOT_CLEANU P |
Clone {{fsname}} in NAS server {{vdmname}} failed creation but could not cleanup the object completely. The object is not usable and can only be deleted. | CRITICAL | The clone create has failed, the object is not usable. | Attempt to delete resulting file system object at a later time. | file-systems.fs- state-clone- create-failed- could-not- cleanup |
| 5010090a | FS_STATE_FS_ DELETE_PARTI ALLY_FAILED |
File system {{fsname}} in NAS server {{vdmname}} partially failed delete. The object is likely no longer fully usable and can only be deleted. | CRITICAL | The file system delete has partially failed, the object is not usable. | Attempt to delete the file system object again at a later time. | file-systems.fs- state-fs-delete- partially-failed |
| 5010090b | FS_STATE_SN AP_DELETE_PARTIALLY_FAILED |
Snap {{fsname}} in NAS server {{vdmname}} partially failed delete. The object is likely no longer fully usable and can only be deleted. | CRITICAL | The snap delete has partially failed, the object is not usable. | Attempt to delete the snap object again at a later time. | file-systems.fs- state-snap-delete-partiallyfailed |
Affected Products
PowerFlex rack, ScaleIOArticle Properties
Article Number: 000270649
Article Type: How To
Last Modified: 24 Jun 2026
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.