Missing Windows Data Disks

Important! The information provided in this section is for general Troubleshooting guidance only. The information is provided on "AS IS" basis, with no guarantee of completeness, accuracy or timeliness, and without warranty or representations of any kind, expressed or implied. In no event will CloudEndure and/or its subsidiaries and/or their employees or service providers be liable to you or anyone else for any decision made or action taken in reliance on the information provided above or for any direct, indirect, consequential, special or similar damages (including any kind of loss), even if advised of the possibility of such damages. CloudEndure is not responsible for the update, validation or support of troubleshooting information.

Follow these steps if no disks are visible in Windows disk management other than the C: drive.

1. Ensure that the volumes are attached to the ec2 instance.
   Wait 40 minutes, reboot the Target machineThe Machine created during Test, Cutover or Recovery. and see if the disks appear.

2. Verify if the PV drivers were installed by reviewing the DriversMSI log file: C:\Program Files\Amazon\XenTools\AWSPVDriverMSI.log
   If the drivers are missing, install the PV drivers manually on the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). as described in this AWS guide. Check to see if the disks appear.

3. Check if there are any pending Windows Update on the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine.. If so, install the pending updates on the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine., wait for replication to resyncWhen the initial synchronization was stopped before completion (due to a reboot, for example), the re-synchronization process compares the data on the Source and the Target to determine which data still needs to be replicate. Then, only the data that exists solely on the Source is copied to the Target., and then launch a new Target machineThe Machine created during Test, Cutover or Recovery.. Check to see if the disks appear.