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)  Failed labeling and mounting after 10 retries, giving up

This file is part of the configuration wizard logs, available for download in the UI:

This error usually occurs when users specify  a wrong volume during the upgrade - instead of the cpmdata volume (or its copy created from a snapshot), it's any other volume.

In order to verify that the wrong volume is being used, you can attach it to any Linux instance and mount under any name.

Then you can run the "ll" command. If the list of folders doesn't match the screenshot below, it is not a cpmdata volume.

 

Often, users would create a copy of old root volume instead of cpmdata.

Please terminate the new instance and repeat the upgrade procedure using the correct volume.

• Related Articles

• 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 ...

• Upgrade fails with error "Could not mount the new volume, returned: 8192"

  If you get this error message during an upgrade, it is very likely that the filesystem is corrupted on the CPMData Volume. Please perform these steps: 1) Connect to N2WS EC2 instance where the upgrade failed using user "cpmuser" and your Key 2) ...

• "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 ...

• cpmdata policy might fail with error volume does not exist

  Issue: If the volumeID of the CPMDATA volume(EBS) changes (due to restoring CPM from snapshot for example),  This might cause the cpmdata policy to fail, still showing the old VolumeID: Solution: try to run cpmdata policy ASAP

• Volume Snapshot may fail with error "The maximum per volume CreateSnapshot request rate has been exceeded"

  Volume Snapshots may fail with the following errors in the log files. backup log 02-12-20 11:07:22 - Error - create snapshot of instance volume vol-xxxxxxxxxxxxx failed. 02-12-19 11:07:22 - Error - snapshot of instance ec2-xxxxxxxxx-xxxx-xx, volume ...