N2WS-22420 - Copy to S3 failing with local device /dev//dev/xvdf (/dev/xvdf) does not exist

N2WS-22420 - Copy to S3 failing with local device /dev//dev/xvdf (/dev/xvdf) does not exist


Copy To S3 is failing with the following error:

Patch for v4.1.1a is available and attached to this KB. 

Click here to go back to the Release notes: Release notes for the latest v4.1.x CPM release

    • Related Articles

    • N2WS-21963 - Copy to S3 fails with Failed to stop processor(s)

      Issue: Copy to S3 is failing with following error ERROR: add_error(segment_handler.py:322) copy of md table of segment 1 of volume vol-12345678, instance i-0987654321, backup 123 fail : Failed to stop processor(s): not all blocks were processed ...
    • Patch installation fails with Internal Server Error

      Issue: Patch installation fails with this error in the UI Solution: 1. Connect to the N2WS server via SSH, username is cpmuser and your selected keyPair 2. Run the following command sudo grep PrivateTmp /lib/systemd/system/apache2.service 3. If ...
    • CLI "recover-instance" command may fail when "root-device-source" parameter is set to "image"

      When using the CPM CLI to run the” recover-instance” command and the parameter "root-device-source” is set to “image”, instance recovery may fail with the following error: {"message": "Failed getting snapshot of root device /<path>. Error: ...
    • N2WS-22811 - Backup fails with error "internal agent error"

      Issue: Backup fails with internal agent error in UI, because it fails to auto-remove terminated instances There is this error in UI Error - Backup is aborted due to an internal agent error and this error in server logs WARNING: ...
    • N2WS-21940 - S3 Cleanup failing to start

      Issue: cleanup process is showing as not started for a long long time in S3 cleanup log 9/10/2022 22:12 Info ===== Cleanup of policy xyz (account: MyAccount, user: MyUser) ===== And error is shown in the logs Traceback (most recent call last): File ...