CPM configuration may fail with the error: "Could not attach volume %vol-id% to instance %Id% Reason: Invalid value '/dev/sdf' for unixDevice. Attachment point /dev/sdf is already in use"
Issue:
CPM configuration may fail with the error: "Could not attach volume %vol-id% to instance %Id% Reason: Invalid value '/dev/sdf' for unixDevice. Attachment point /dev/sdf is already in use"
ERROR: done(views.py:181) Could not attach volume vol-%id% to instance %id%. Reason: Invalid value '/dev/sdf' for unixDevice. Attachment point /dev/sdf is already in use
Root cause:
When the CPM configuration wizard starts there should be no volumes attached to the instance other than the root volume.
How To Fix:
Terminate the instance and before starting CPM configuration, please go to EC2 console and make sure that there are no non-root volumes attached.
Related Articles
"Cannot attach volume 'vol-xxxx' with Marketplace codes" error may be displayed during CPM upgrade
The following error message may be displayed when trying to upgrade the CPM instance using a new AMI: Could not attach volume vol-1234567890abcdef to instance i-abcdef0123456789. Reason: Cannot attach volume 'vol-1234567890abcdef' with Marketplace ..."Cannot attach volume 'vol-xxxx' with Marketplace codes" error may be displayed during the Explore operation
The following error message may be displayed when trying to explore a root volume of an instance that belongs to an AWS Marketplace product: Explore failed: 1. Volume vol-1234567890abcdef created (original: vol-0abcdef123456789). However attach to ...Empty tag value may result in the error "Instance (or Volume) <ID> wasn't scanned properly"
The error "Instance (or Volume) <ID> wasn't scanned properly" may appear in resource scan log and CPM server log if an instance, or volume is configured with the cpm backup tag key, and the tag value is empty. This message will appear only if the tag ...Login to the CPM using an IDP may fail with the "Invalid issuer" error message
If you're using an IDP, login to the CPM may fail with the following error message: login failed. reason: Invalid issuer in the Assertion/Response (invalid_response): It also may be found in the cpm_server.log: ERROR: ...File-level recovery may fail with "Reason: In order to use this AWS Marketplace product you need to accept terms and subscribe"
File-level recovery may fail with the following error printed in the CPM logs: ERROR: explore_backup_init(.\cpmserver\cpm\filemanager\views.py:368) File Level Recovery - failed exploring snapshot snap-0123456789abcdef. Reason: Volume ...