"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 codes as the instance
'i-abcdef0123456789' is not in the 'stopped' state.
This error means that you have chosen the wrong volume when selecting the "use existing data volume" option in step 3 of N2WS configuration wizard.
The most common mistake is trying to attach the "root" volume (default size 30GB) of the old instance instead of the "cpmdata" volume (default size 5GB)
The correct volume can be identified by locating a snapshot with both of the tags "cpm_server_id" or "cpm_policy_name"
To resolve this problem, please follow the upgrade instructions at https://docs.n2ws.com/user-guide/2-configuring-n2ws#id-2.2-upgrading-n2ws
Or raise a ticket with out support team and we will gladly arrange a remote session to help you upgrade.
Related Articles
"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 ...Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error
Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error: Error - snapshot of independent volume vol-0123456789abcdef failed to start. Reason: The volume 'vol-0123456789abcdef' does not exist This error may ...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 ...Upgrade may fail with the "Failed labeling and mounting after 10 retries, giving up" and "Could not mount the new volume, returned: 256" errors
Upgrade using AMI may fail with the following error in the file config_shell_commands.log: 2021-02-08 18:07:06,610: perform_shell_commands(:339) Could not mount the new volume, returned: 256 2021-02-08 18:07:06,610: perform_shell_commands(:349) ...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 ...