Dell recommends that you refer to the material in this and other related topics:
|
Non certified disk drive detected. Disk needs to be pulled out for the system to become operational. |
Disk needs to be pulled out for the system to become operational. |
|
Some of the network cards are not part of the bond configuration. |
|
|
Use "maintenance --configuration --restore" to recover from backup configuration. | |
|
No valid system configuration file(s) found in configuration database. |
Use "maintenance --configuration --restore" to restore from backup configuration. |
|
Use "maintenance --configuration --restore" to restore configuration from backup. | |
|
Use "maintenance --configuration --restore" to restore configuration from backup. | |
|
If NVRAM device was replaced use "maintenance --hardware --reinit_nvram" to initialize NVRAM. | |
|
Windows Server module is down. Windows client access will be disrupted. |
|
|
Windows Server module has been disabled because of multiple crashes. |
|
|
Filesystem server is not healthy. Client access will be interrupted. |
|
|
Filesystem checker crashing multiple times, entering support mode. |
|
|
Reboot the system to recover. If problem persists contact Dell Support. | |
|
Reboot the system to recover. If problem persists contact Dell Support. | |
|
Use "maintenance --configuration --reinit_dictionary" to re-init. | |
|
Capacitor is disconnected from NVRAM. If problem persist after reboot, replace NVRAM card. |
|
|
SSD is disconnected from NVRAM device. If problem persist after reboot, replace NVRAM card. |
|
|
NVRAM has failed to backup or restore data during the last boot. |
|
|
Filesystem server is crashing repeatedly. Entering Maintenance mode to run filesystem scan utility. |
|
|
If this is a newly replaced NVRAM, use "maintenance --hardware --reinit_nvram" to initialize. | |
|
Filesystem server is crashing repeatedly in Maintenance Mode. |
|
|
One or more software package is incompatible, please upgrade the appliance to rectify the issue. |
Please upgrade the system appliance to rectify the issue. Upgrade the DR Series system appliance (in the Software Upgrade page, click Start Upgrade). |
|
NVRAM Health check in progress, please wait for it to complete before using the system. |
|
|
NVRAM Health check is required, system will perform a quick health check |
|
|
Failed to start NVRAM Health check, please reboot the appliance to recover from this state |
|
|
Appliance encountered O/S issues. Please reboot the appliance to recover from this condition. |
|
|
High system memory usage detected, system performance will be sluggish. |
|
|
The next NVRAM capacitor health check is scheduled for <variable>. |
|
|
Windows Active Directory client is unable to contact the Active Directory domain server. |
|
|
Storage enclosure <variable> is authorized. |
|
|
Storage enclosure <variable> is de-commissioned. |
|
|
The system IP address has changed from <variable> to <variable>. |
|
|
Namespace Volume has become in-accessible, please call Dell support. |
|
|
Storage Enclosure with Service Tag <variable> added successfully. |
|
|
Power-off the appliance, fix the connectivity issues and power-on the appliance. | |
|
Retry to upgrade. If the problem persists, contact Dell Support. | |
|
Filesystem scan completed, restarting filesystem for normal operation. |
|
|
If Restore Manager (RM) recovery was performed recently, please re-apply the license(s) and reboot. | |
|
System clock has drifted more than 24 hours, from the last filesystem start. |
|
|
Please contact your DR4x00 Sales representative to get the Hardware Version. | |
|
This DR4x00 Virtual Machine is for evaluation purpose only. Evaluation period ends on <variable>. |
|
|
This DR4x00 Virtual Machine is designed to work only with 4 CPU(s) and 8GB of memory. |
|
|
This DR2000v is unable to contact the license server to validate the license usage. |
Please rectify the connectivity issues and reboot the system. |
|
This DR2000v Virtual appliance usage time limit has expired. |
Contact your Dell DR Series Sales representative to get a permanent license. |
|
This DR2000v Virtual appliance usage time limit will expire on <variable>. |
|
|
Register using the CLI command "virtual_machine --register" again. | |
|
This DR4300e requires a license to operate, please install storage usage license. |
You need to install a capacity license. Contact Dell Support for assistance. |
|
Re-add the old capacity license(s) after recovering the system. Contact Dell Support for assistance. | |
|
Filesystem scan requested. Switching to Maintenance Mode. Filesystem has read-only access. |
|
|
Data volume is not present. Check that all drives are inserted and powered up. |
|
|
Filesystem server crashed multiple times. System is now entering Maintenance mode. |
|
|
Insufficient disk space. Filesystem switched to read-only mode. |
|
|
If this is a newly replaced NVRAM device, use the CLI maintenance --hardware --reinit_nvram command. For more information, see the Dell DR Series System Command Line Reference Guide. | |
|
Replication re-sync cannot proceed because the Namespace depth has reached its maximum. |
|
|
Run filesystem scan as soon as possible. ("maintenance --filesystem --start_scan") | |
|
Filesystem Name Space partition has reached its maximum allowable limit. |
|
|
Filesystem Name Space partition is reaching its maximum allowable limit. |
|
|
Please check whether the storage enclosure(s) are powered-up and connected to the appliance. | |
|
If Restore Manager (RM) recovery was performed recently, please re-apply the license(s) and reboot. | |
|
System clock has drifted more than 24 hours, from the last filesystem start. |
|
|
One or more replication target systems are running low in space. |
|
|
Filesystem scan completed with no inconsistencies. Switching back to operational mode. |
|
|
System has reached space full condition, seeding will be stopped. |
|
|
Seeding device metadata info file missing, unable to import. |
|
|
Seeding export paused as the device contains data from another seeding job. |
|
|
Please check that the "password" and "encryption type" matches the Seeding export job. | |
|
Please copy out the old diagnostics bundles and delete for future auto diagnostics collection. | |
|
Appliance available storage level is below the set threshold. |
|
|
Successfully <variable> system marker. |
|
|
<variable> OPDUP encryption updated to <variable> |
|
|
Successfully <variable> container <variable> with the following marker(s) "<markers>". |
|
|
Container <name> created successfully. |
|
|
Container <name> marked for deletion. |
For more information, see Deleting Containers. Use the DR Series system CLI maintenance --filesystem --reclaim_space command to recover this storage space. |
|
Container <name> has been deleted. |
|
|
Successfully renamed container <name> as <name>. |
|
|
Container <name> is configured to access over <variable> by the following clients: <clients> ('*' means access for everyone). |
|
|
Container <name> is updated to access over <variable> by the following clients: <clients> ('*' means access for everyone). |
|
|
Disabled access for Container <name> over <variable> for the following clients: <clients> ('*' means disabled access for everyone). |
|
|
Successfully added connection entry for container <name>: type <variable> clients <variable>. |
|
|
Successfully updated connection entry for container <name>: type <variable> clients <variable>. |
|
|
Successfully deleted connection entry for container <name>: type <variable> clients <variable>. |
|
|
Replication entry created successfully for container <name>: role <variable> peer <variable> peer container <variable>. |
|
|
Replication configuration updated successfully for container <name>: role <variable> peer <variable>. |
|
|
Replication marked for deletion for Container <name>: peer <variable> peer container <name>. |
|
|
Successfully initiated replication re-sync on Container <name>. |
|
|
Replication <variable> defaults successfully updated: role <variable> peer <variable>. |
|
|
Successfully updated replication bandwidth limit for <variable> to <variable>. |
|
|
Successfully removed replication bandwidth limit for <variable>. |
|
|
Successfully set <variable> replication bandwidth limit. |
|
|
Replication enabled for container <name> with role <role>. |
|
|
Replication disabled for container <name> with role <role>. |
|
|
Snapshot <variable> → <variable> created successfully. |
|
|
Snapshot <variable> → <variable> successfully updated. |
|
|
Snapshot <variable> → <variable> successfully deleted. |
|
|
Client <client> authorized to access NDMP Tape Server. |
|
|
De-authorized NDMP client - <client>. |
|
|
OST client <variable> with mode <variable> added successfully |
|
|
OST client <variable> deleted successfully. |
|
|
OST client <variable> with mode <variable> updated successfully. |
|
|
OST client <variable> deleted successfully. |
|
|
OST client <variable> with mode <variable> updated successfully. |
|
|
Successfully updated <variable> schedule. |
|
|
System compression level set to <variable>. |
|
|
Rapid Data Access (RDA) client <variable> with mode <variable> added successfully. |
|
|
Rapid Data Access (RDA) client <variable> deleted successfully. |
|
|
Rapid Data Access (RDA) client <variable> with mode <variable> updated successfully. |
|
|
DR2000v with UUID <variable> IP Address <variable> Hostname <variable> registered successfully. |
|
|
DR2000v with UUID <variable> IP Address <variable> Hostname <variable> unregistered successfully. |
|
|
Internal failure—mtab initialization failure for container <variable>. |
|
|
Internal failure retrieving configuration for container ID <variable>. |
|
|
Internal failure deleting container ID <variable>. |
|
|
Internal failure stopping container ID <variable>. |
|
|
Internal failure adding connection <variable> for container ID <variable>. |
|
|
Internal failure deleting connection <variable> for container ID <variable>. |
|
|
Name space volume nearing low space condition. To prevent faster exhaustion of space, snapshot required for replication seeding for container <variable> will be paused until Name space volume recovers from low space conditions. |
|
|
Replication started as per schedule, will be active until <variable>. |
|
|
Replication stopped as per schedule, will restart at <variable>. |
|
|
Container replay failed for container <variable>. |
|
|
Internal failure—Name Space subsystem initialization failed. |
|
|
Please schedule a filesystem consistency check using the DR Series system CLI maintenance --filesystem --start_scan command. | |
|
System entering Maintenance mode—Name Space log replay failed. |
|
|
System entering Maintenance Mode—Name Space transaction failure. |
|
|
Filesystem has reached the maximum supported number of Name Space entries. |
|
|
Filesystem has recovered from a lack of available Name Space entries. |
|
|
To find all files with corrupt attributes and to clear the state, please perform a maintenance scan using the DR Series system CLI maintenance --filesystem --start_scan command. Contact Dell Support for assistance or intervention. | |
|
System entering maintenance mode - Name Space Log Rotation failed |
|
|
File/Directory Statistics table out of sync. Switching to maintenance mode. |
|
|
Root inode of container, id <variable>, was found to be inconsistent. Fixed the attribute, ACL on root inode needs to be manually verified and fixed. |
|
|
Replication internal re-sync started for container <variable>. |
|
|
Replication internal re-sync completed for container <variable>. |
|
|
Internal failure creating replication snapshot for container <variable>. |
|
|
Internal failure deleting replication snapshot for container <variable>. |
|
|
Replication switching to re-sync due to corrupt replication Name Space oplog for container <variable>. |
|
|
Replication data operations log (oplog) full for container <variable>. |
|
|
Replication switching to re-sync due to corrupt replication data oplog for container <variable>. |
|
|
Replication transmit log (txlog) full for container <variable>. |
|
|
System entering Maintenance mode due to corrupt replication txlog for container <variable>. |
Collect a diagnostics log file, and open a Support record with Dell Support for assistance. |
|
System entering Maintenance mode due to replication txlog commit error <variable> for container <variable>. |
Collect a diagnostics log file, and open a Support record with Dell Support for assistance. |
|
Unable to make progress on filesystem replication for container <variable>. |
Collect a diagnostics log file, and open a Support record with Dell Support for assistance. |
|
Replication syncmgr exited for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Dell Support for assistance. |
|
Replication syncmgr event for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Dell Support for assistance. |
|
Name Space replicator exited for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Dell Support for assistance. |
|
Replication data replicator exited for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Dell Support for assistance. |
|
Replication protocol version mismatch for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Dell Support for assistance. |
|
Replication protocol version mismatch detected for container <variable>. Replication will continue with downgraded source protocol version. |
|
|
Replication delete cleanup failed for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Dell Support for assistance. |
|
Replication target system <variable> is running low on space. Replication cannot proceed further on container <variable>. |
Informational message. Contact Dell Support for assistance or intervention. |
|
Replication misconfiguration detected for container <variable>. Replication relationship might have been deleted forcibly on target system <variable>. |
Informational message. Contact Dell Support for assistance or intervention. |
|
Replication failed for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Dell Support for assistance. |
|
Replication server failed to commit blockmap for container <variable>. System is entering Maintenance mode. |
|
|
Container <variable> replication is paused, cleaner on replica is reclaiming space. |
|
|
Found mismatch in system software version with peer <variable>. Replication on source container <variable> would be stalled. |
|
|
Replication stalled on source container <variable> due to a mismatch in system software version or network issue with peer <variable>. |
|
|
Found mismatch in system software version with peer <variable>. Backup or replication on some or all target containers would be stalled. |
|
|
Received a garbled message from peer <variable>. Connection would be dropped. |
|
|
Container <variable> replication encountered encryption setup error. |
|
|
NFS client successfully mounted <variable>. |
|
|
Maximum NFS connection limit <variable> reached, active NFS connections <variable>. |
You have reached the threshold limit. Reduce the number of connections. |
|
NFS client <variable> successfully unmounted <variable>. |
|
|
NFS client <variable> successfully unmounted all containers. |
|
|
CIFS client <variable> session successfully disconnected from container <variable> . |
|
|
Maximum <variable> connection limit <variable> reached. |
You have reached the threshold limit for the specified protocol. Reduce the number of connections. |
|
CIFS server failed to start <variable>. |
Reboot the DR Series system. If issue persists, contact Dell Support for assistance or intervention. |
|
CIFS client connected <variable> times to container <variable>. |
Reboot the DR Series system. If issue persists, contact Dell Support for assistance or intervention. |
|
Informational message. If issue persists, contact Dell Support for assistance or intervention. | |
|
Informational message. If issue persists, contact Dell Support for assistance or intervention. | |
|
Informational message. If issue persists, contact Dell Support for assistance or intervention. | |
|
Informational message. If issue persists, contact Dell Support for assistance or intervention. | |
|
Online data verification (DataCheck) detected <variable> corruption. |
Informational message. If issue persists, contact Dell Support for assistance or intervention. |
|
Online data verification (DataCheck) detected <variable> corruptions. |
Informational message. If issue persists, contact Dell Support for assistance or intervention. |
|
Informational message. If issue persists, contact Dell Support for assistance or intervention. | |
|
System has reached space full condition, seeding will be stopped. |
|
|
Seeding device metadata info file missing, unable to import. |
|
|
Seeding export paused as the device contains data from another seeding job. |
|
|
Please check that the "password" and "encryption type" matches the Seeding export job. | |
|
Container <variable> added to seeding. |
|
|
Container <variable> is removed while seeding is in progress. |
|
|
Container <variable> removed from seeding. |
|
|
Unable to read bmap scid. Retry seeding after running filesystem scan. |
|
|
Unable to read DS scid. Retry seeding after running filesystem scan. |
|
|
Seeding device mount not accessible. Check the CIFS mount and re-add the device to continue. |
|
|
Internal Error. Unable to load deduplication dictionary <variable>. |
Use the DR Series system CLI maintenance --configuration --reinit_dictionary command. If this issue persists, contact Dell Support for assistance or intervention. |
|
Internal Error. Unable to locate deduplication dictionary <variable>. |
Use the DR Series system CLI maintenance --configuration --reinit_dictionary command. If issue persists, contact Dell Support for assistance or intervention. |
|
Filesystem cleaner run <variable> started. |
|
|
Filesystem cleaner run <variable> completed in <variable> milliseconds (ms). |
|
|
Filesystem cleaner process encountered input/output (I/O) errors. |
|
|
Failure to sync NVRAM <variable>. |
|
|
Failure reading from NVRAM <variable>. |
|
|
Failure writing to NVRAM <variable>. |
|
|
Failure to write sync NVRAM <variable>. |
|
|
Internal Error. Datastore <variable> length mismatch <variable>. |
|
|
Out of space. Rollback of updates on object <variable> failed. Restarting file server. |
|
|
Contact Dell Support for assistance or repair the filesystem. For repairs, see About The DR Series Maintenance Mode. | |
|
Contact Dell Support for assistance or repair the filesystem. For repairs, see About The DR Series Maintenance Mode. | |
|
Decompression of datastore failed <variable>. |
|
|
Internal Error. Failed to clean active datastore <variable>. |
|
|
Internal Error. Negative reference on datastore <variable>. Record type: <variable>. Count: <variable>. |
|
|
Internal Error. Data store <variable> contains negative stream reference count. Record type: <variable>. Count: <variable>. |
|
|
Internal Error. Data store <variable> total reference count reached threshold. Record type: <variable>. Count: <variable>. |
|
|
Internal Error. Entering Maintenance mode due to failure in processing logs. |
|
|
Internal Error. Failed to acquire optimizer pipeline. Error: <variable>. |
|
|
Internal Error. Failed to create optimizer event. Type: <variable>, Error: <variable>. |
|
|
Internal Error. Task execution in fiber <variable> timed out after <variable> milliseconds (ms). Restarting file server. |
|
|
Optimization initialized on container <variable>. |
|
|
Optimization terminated on container <variable>. |
|
|
Cleaner aborted at <variable>. |
The DR Series system should enter Maintenance mode, and Cleaner process will restart. |
|
Internal Error. Moving data from NVRAM to disk failed. System is entering its Maintenance mode. |
|
|
System entering Maintenance Mode due to corrupt encryption keystore. Triggering key import. |
|
|
Filesystem Cleaner process started as per schedule (will be active until <variable>). |
|
|
Filesystem Cleaner process stopped as per schedule (will restart at <variable>). |
|
|
Start system upgrade to version <variable>. |
|
|
System name changed to <variable>. |
|
|
System date changed to <variable>. |
|
|
System time zone changed to <variable>. |
|
|
NTP server <variable> added. |
|
|
NTP server <variable> deleted. |
|
|
User <variable> enabled. |
|
|
User <variable> disabled. |
|
|
Static IP address <variable> assigned. |
|
|
Network interface bonding mode set to <variable>. |
|
|
Network MTU size set to <variable>. |
|
|
System name set to <variable>. |
|
|
Email relay host set to <variable> for email alerts. |
|
|
Recipients for email alerts set to <variable>. |
|
|
Recipient <variable> added to receive email alerts. |
|
|
Recipient <variable> is no longer receiving email alerts. |
Check whether email recipient still exists, or if mailbox is full. |
|
Administrator information set to <variable> for email alerts. |
|
|
System diagnostics package <variable> deleted. |
|
|
System diagnostic package <variable> is copied off the system. |
|
|
System diagnostic package <variable> is collected. |
|
|
System diagnostics space usage exceeded threshold. Auto cleaning oldest package: <variable>. |
|
|
Host <variable> added to SNMP alert recipient list. |
|
|
Host <variable> deleted from SNMP alert recipient list. |
|
|
Host <variable> enabled for SNMP alerts. |
|
|
Host <variable> disabled for SNMP alerts. |
|
|
User <variable> logged into the system. |
|
|
CIFS user <variable> added. |
|
|
CIFS user <variable> deleted. |
|
|
Password changed for CIFS user <variable>. |
|
|
System upgrade completed <variable>. |
|
|
Cleared foreign configuration on disk <variable>. |
|
|
User <variable> logged into the system. |
|
|
Disk <variable> configured as hot spare. |
|
|
DNS settings updated with primary <variable>, secondary <variable>, and suffix <variable>. |
|
|
<variable> added with entitlement id <variable>. |
|
|
Security privilege(s) changed for <variable>. |
|
|
User <variable> logged into the administrative web interface. |
|
|
Network interface(s) <variable> enabled. |
|
|
Network interface(s) <variable> disabled. |
|
|
SMBD backup traffic interface(s) <variable> do not have an IP. |
|
|
File system check completed successfully. No inconsistencies were found. |
|
|
One (or more) file(s) were deleted as part of the repair process. |
Informational message. No user intervention is required. To verify, please use the DR Series system CLI maintenance --filesystem --repair_history verbose command. |
|
One or more file(s) were deleted as part of the repair process for container <variable>. Replication will be stopped for this container. |
|
|
One or more file(s) were deleted as part of the repair process for container <variable>. Re-sync has been initiated for this container. |
|
|
Restart the RDA server. If issue persists, contact Dell Support for assistance or intervention. | |
|
<Variable> client authentication failed. |
|
|
<Variable> Logical Storage Unit (LSU) quota exceeded <variable>. |
|
|
<Variable> backup failed <variable>. |
|
|
<Variable> Opdup failed <variable>. |
|
|
<Variable> Restore failed <variable>. |
|
|
RDA connections exceeded the maximum limit; count: <variable>, maximum limit: <variable>. |
|
|
Connection from the <variable> client <variable> aborted. |
|
|
Informational message. No user intervention is required. Check for the supported OST client versions in the Dell DR Series System Interoperability Guide. | |
|
System is entering the Maintenance mode: <variable> LSU information file is corrupted. |
|
|
System is entering the Maintenance mode: <variable> image information is corrupted. |
|
|
<variable> client connection was reset. |
|
|
System is entering the Maintenance mode: RDA meta directory is corrupted. |
|
|
System entering Maintenance Mode - RDA txlog full, LSU <variable>. |
|
|
System entering Maintenance Mode - RDA txlog operation error <variable>, LSU <variable>. |
|
|
System entering Maintenance Mode - RDA txlog roll-forward error <variable>, LSU <variable>. |
|
The Diagnostics service in the DR Series system lets you display, collect, and manage your system’s diagnostic log file bundles. Each diagnostic log file bundle provides:
To access this functionality, use the following DR Series system navigation panel GUI option:
|
• |
Support > Diagnostics |
The Diagnostics service works by collecting all the system-related information that could help when diagnosing a problem or error condition in the system.
For more information about diagnostics log file bundles, see Diagnostics Page and Options.
|
• |
Admin-Generated mode: when a DR Series system CLI or DR Series system GUI request is made by the administrator (and the default reason that is listed is admin-generated). |
|
• |
Auto-Generated mode: when a process or service failure is reported, the DR Series system starts collecting system-related information. After it completes the auto-generated collection, it generates a system event. |
For more information, see Diagnostics Page and Options, Generating a Diagnostics Log File, Downloading Diagnostics Log Files. and Deleting a Diagnostics Log File.
The diagnostics log file bundle collects the same type of hardware, storage, and operating system information that is collected when using the Dell System E-Support Tool (DSET) and the DR Series system CLI commands (diagnostics --collect --dset). For more information about DR Series system command line interface commands, see the Dell DR Series Command Line Reference Guide.
The Diagnostics service collection tool process observes the following guidelines:
|
• |
|
• |
The DR Series system CLI also provides the means for managing, generating, or downloading the diagnostics log files. For more information, see the Dell DR Series System Command Line Reference Guide. |
In general, the DR Series system enters the Maintenance mode whenever the file system has encountered an issue that prevents it from operating normally.
|
NOTE: You can use the Reason code information available in the Maintenance mode to call Dell Support. All maintenance must be conducted using the DR Series systems Command Line Interface. |
When in its Maintenance mode, the filesystem is in a read-only state, and the system runs the following maintenance-based operations:
|
NOTE: Whenever the DR Series systems enters or exits from the Maintenance mode state, all communication via protocols is lost. |
|
• |
Generates a filesystem status report (if the filesystem check finds no issues, the DR Series system switches back to Operational mode without user intervention). |
If the filesystem check finds issues, you can choose to make repairs (using Confirm Repair Filesystem) or ignore the detected issue (using Skip Repair Filesystem), at which point the system switches back to Operational mode.
The Maintenance mode process displays a number of stages, indicated on the Maintenance Mode progress bar, which include:
|
NOTE: If the Filesystem Check detects any repairable files, it generates a Repair Report that identifies these reported files. The Maintenance Mode progress bar halts at the Completed Generating Repair stage, and remains in Maintenance mode until you click Confirm Repair Filesystem. The DR Series system does not advance to the Switching to Operation Mode stage until the filesystem repair is completed. |
The Maintenance Mode page provides the following information:
|
◦ |
Displays the five stages of Maintenance mode |
|
◦ |
Provides a search capability that allows you to click prev or next to display the previous or next page in the Repair Report, or lets you display a specific page number of the Repair Report by entering this number in the Goto page and click go. |
|
After the DR Series system enters Maintenance mode, there can only be two possible outcome states:
|
• |
Operational mode (Normal State): where the filesystem check was successful, and no system files need to be repaired (Filesystem Check: successful). |
|
• |
Maintenance mode has halted: where the filesystem check detected one or more repairable files (Filesystem Check: unsuccessful). |
Filesystem Check — Successful: when the Maintenance mode successfully completes all of its stages, the DR Series system displays its status as having entered Operational mode (Normal State). Only after the Maintenance mode has successfully completed its internal check can it return to an Operational mode.
To return to the Operational mode, click Go to Dashboard on the Maintenance Mode page options bar. Go to Dashboard is only active when all of the internal system checks have completed and the progress bar indicates that all stages have been completed.
|
NOTE: When in Maintenance mode, image expiration fails because the DR Series system is in a read-only state. If this occurs, the DMA assumes that the backup images have expired. However, the DR Series system administrator may be unaware that the backup data images still reside on the DR Series system. |
Filesystem Check — Unsuccessful: when the Maintenance mode halts at the Completed Generating Report stage, this indicates that the filesystem check detected some repairable files, and listed them in the Repair Report pane on the Maintenance Mode page.
To return to the Operational mode, click Confirm Repair Filesystem on the Maintenance Mode page options bar to repair the files listed in the Repair Report. Confirm Repair Filesystem is the only active option you can select when the progress bar indicates that some filesystem files are in need of repair.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
