Dears,
I am facing an issue while preparing Failback client. I am following this blog
https://aws.amazon.com/blogs/storage/building-a-disaster-recovery-site-on-aws-for-workloads-on-microsoft-azure/
to configure Failback client.
https://github.com/aws-samples/aws-drs-failback-client-azure-gcp
Following steps i have completed:
1- Set Up VMware Workstation
2- Download Amazon Linux 2 ISO
3- Create New VM
4- Prepare Additional Storage:
5- Partition the /dev/xvdb device and format
6- Download the Convertor Script
7- Grant executable permissions (Convertor-GCP.sh)
After executing the script downloaded "aws-failback-livecd-64bit.iso" successfully.
Getting an error message while script mount "aws-failback-livecd-64bit.iso" file to /mnt folder.
Mounting the Downloaded Failback Client ISO to /mnt
mount: /mnt: failed to setup loop device for /root/aws-failback-livecd-64bit.iso.
/root/aws-failback-livecd-64bit.iso is not mounted
Please advise the solution of this issue.
Regards.
Complete logs:
root@ip-10-2-0-181 data]# ./Convertor-GCP.sh
Enter the region name:
us-east-2
Enter the Disk name i.e /dev/sda :
/dev/xvdc
Enter the Partition name i.e /dev/sda1 :
/dev/xvdc1
Downloading Failback Client ISO
--2024-04-07 09:20:36-- https://aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com/latest/failback_livecd/aws-failback-livecd-64bit.iso
Resolving aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com (aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com)...
Connecting to aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com (aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com)|52.219.111.84|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 959285248 (915M) [binary/octet-stream]
Saving to: ‘aws-failback-livecd-64bit.iso’
aws-failback-livecd-64bit.iso 100%[==============================================================================================>] 914.85M 45.7MB/s in 20s
2024-04-07 09:20:56 (46.4 MB/s) - ‘aws-failback-livecd-64bit.iso’ saved [959285248/959285248]
Mounting the Downloaded Failback Client ISO to /mnt
mount: /mnt: failed to setup loop device for /root/aws-failback-livecd-64bit.iso.
/root/aws-failback-livecd-64bit.iso is not mounted
AWS OFFICIALUpdated 8 months ago
Hi Matt,
I have changed Disk name and partition name as per the instructions. However getting same error message.
Enter the region name: us-east-2 Enter the Disk name i.e /dev/sda : /dev/xvdb Enter the Partition name i.e /dev/sda1 : /dev/xvdb1 Downloading Failback Client ISO --2024-04-07 18:56:35-- https://aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com/latest/failback_livecd/aws-failback-livecd-64bit.iso Resolving aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com (aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com)... , ... Connecting to aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com (aws-elastic-disaster-recovery-us-east-2.s3.amazonaws.com)|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 959285248 (915M) [binary/octet-stream] Saving to: ‘aws-failback-livecd-64bit.iso’
aws-failback-livecd-64bit.iso 100%[===================================================================================>] 914.85M 45.0MB/s in 18s
2024-04-07 18:56:54 (49.5 MB/s) - ‘aws-failback-livecd-64bit.iso’ saved [959285248/959285248]
Mounting the Downloaded Failback Client ISO to /mnt mount: /mnt: failed to setup loop device for /root/aws-failback-livecd-64bit.iso. /root/aws-failback-livecd-64bit.iso is not mounted
what is the output of the
lsblkcommand?I have created new VM. Added new disk named xvdb and added a partition named xvdb1 and mount a directory named /mnt
Now the output of lsblk command is: xvda xvda1 xvda127 xvda128 xvdb disk xvdb1 part /mnt
dears any feedback, please