Explore may fail with "Invalid value '/dev/xvdp' for unixDevice"
ERROR: recover_volume(.\cpmserver\cpm\recovery.py:<line_number>)
Volume <volume_id> created (original: vol-0d746a37a79a611fe). However
attach to instance <instance_id> (device: <path>) failed. Reason:
Invalid value '<path>' for unixDevice. Attachment point <path> is
already in use
please check how many Explore
sessions are open since CPM cannot attach more than 10 mounting points.
If CPM has 10 volumes connected to it, please close some of them and
retry exploring the volume.
You may also close these sessions via the General Settings screen.
In the General Settings screen, go to the Cleanup tab and click
on the Clear Explore Sessions as seen in the screenshot below:
Upgrading to 2.3.0e will not resolve the issue but the error
message received will be more informative- Can't attach more volumes. No
more available device names.
Please upgrade to latest 2.X.X version
Reference defect number – N2WS-2587, fixed in v2.3.0e
Related Articles
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 ..."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 ...CPM may fail to clear “Explore” sessions which are not properly closed
When exploring a volume via CPM, if the session is not properly closed by using the Close button, the volume may remain attached to the CPM. If you notice that the volume remains attached to the CPM (EC2 console shows more than 2 volumes attached to ...Backups may fail due to the "Value (None) for parameter snapshotId is invalid" error
If backups are failing, please download the CPM logs and search for the string: <Code>InvalidParameterValue</Code><Message>Value (None) for parameter snapshotId is invalid. Expected: 'snap-...'.</Message> If you found the above string please update ...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: ...