SMS.1913 Failed to Check I/O Monitoring Disks

Symptom

An error occurs during server migration, and the error message "SMS.1913 Failed to check the I/O monitoring disks" is displayed.

Possible Causes

The source Windows server was migrated using SMS, and the I/O monitoring driver is active. If a new disk is added to the source server after migration begins, its incremental data will not be monitored or synchronized.

Solution

Select a solution as required.

• If a disk is added to the source server and the data on the disk needs to be synchronized, perform the following steps:
  1. Restart the source server.
     

     Check whether the source server can be restarted to avoid affecting services.

  2. Uninstall the migration Agent from the source server. For details, see How Do I Uninstall the SMS-Agent from the Source and Target Servers After the Migration Is Complete?.
  3. Reinstall the Agent on the source server. For details, see Installing the SMS-Agent on Windows.
  4. Perform the following operations again: configure the target server, start a full replication, launch the target server, and synchronize the incremental data.
• If no disk is added to the source server or the data on the new disk does not need to be synchronized, you can modify the configuration file to skip the I/O monitoring disk detection. Specifically:
  1. Modify the g-property.cfg configuration file.
     • For Python 3, go to the C:\SMS-Agent-Py3\config directory and set enable_check_monitor_disk in the g-property.cfg file to False.
     • For Python 2, go to the C:\SMS-Agent-Py2\config directory and set enable_check_monitor_disk in the g-property.cfg file to False.

     

     

     If a new disk is added, the data on the new disk cannot be synchronized after the value of enable_check_monitor_disk is set to False.

  2. Save the configuration file.
  3. Return to the SMS console, delete the created migration task, and create and start a new migration task.