Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
755 questions
Facing errors while installing Mobility agent on CentOS Physical machine(ASR)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 28.999999999999996%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
shashank pissay
61
Reputation points
I am trying to install ASR Mobility agent manually on Centos 6.10 (Kernel-2.6.32-754.23.1.el6.x86_64). Facing errors as shown below. Made sure there is sufficient space on the volumes. Also made sure to give 777 permissions to /usr/local/ASR/Vx
11/21/2023 11:58:01: Contents of /etc/vxagent/orig_initrd_images/ before generating the initrd images.
total 0
11/21/2023 11:58:01: Backed up existing initrd images successfully.
11/21/2023 11:58:01 : Generating initrd images.
11/21/2023 11:58:01: /usr/local/ASR/Vx/scripts/initrd/install.sh install /usr/local/ASR/Vx vmware
- dracut_dir=/usr/lib/dracut/modules.d
- '[' '!' -d /usr/lib/dracut/modules.d ']'
- dracut_dir=/usr/share/dracut/modules.d
- '[' '!' -d /usr/share/dracut/modules.d ']'
- dracut_dir=/usr/share/dracut/modules.d/95involflt
- cmd=install
- shift
- install /usr/local/ASR/Vx vmware
- set -x
- ret=0
- '[' '!' -x /usr/local/ASR/Vx/scripts/initrd/involflt_install_lib.sh ']'
- . /usr/local/ASR/Vx/scripts/initrd/involflt_install_lib.sh /usr/local/ASR/Vx
++ set -x
++ V2A_MODULES='hv_storvsc mptspi mptsas'
++ INSTALL_DIR=/usr/local/ASR/Vx
++ INITRD_DIR=/usr/local/ASR/Vx/scripts/initrd
++ _LIB=/usr/local/ASR/Vx/scripts/initrd/involflt_init_lib.sh
++ _CFG=/usr/local/ASR/Vx/scripts/initrd/involflt_init_lib.sh.cfg
++ _OS=
- for ret in 1
- install_init vmware
- set -x
++ /usr/local/ASR/Vx/scripts/vCon/OS_details.sh print
- _OS=RHEL6-64
- echo 'Generating initrd for RHEL6-64'
Generating initrd for RHEL6-64
- '[' -f /usr/local/ASR/Vx/scripts/initrd/involflt_init_lib.sh.cfg ']'
- cp /usr/local/ASR/Vx/scripts/initrd/involflt_init_lib.sh /usr/local/ASR/Vx/scripts/initrd/involflt_init_lib.sh.cfg
- is_distro SLES
- set -x
- echo RHEL6-64
- grep -qi SLES
- return 1
- regenerate_initrd_dracut /usr/local/ASR/Vx vmware
- set -x
- local vxdir=
- rm -rf /usr/share/dracut/modules.d/95involflt
- mkdir -p /usr/share/dracut/modules.d/95involflt
- cp /usr/local/ASR/Vx/scripts/initrd/95involflt/99_involflt.rules /usr/local/ASR/Vx/scripts/initrd/95involflt/install /usr/local/ASR/Vx/scripts/initrd/95involflt/installkernel /usr/local/ASR/Vx/scripts/initrd/95involflt/involflt_init.sh /usr/local/ASR/Vx/scripts/initrd/95involflt/module-setup.sh /usr/share/dracut/modules.d/95involflt/
- cp /usr/local/ASR/Vx/scripts/initrd/involflt_init_lib.sh.cfg /usr/share/dracut/modules.d/95involflt/involflt_init_lib.sh
- cp /usr/local/ASR/Vx/bin/inm_dmit /usr/share/dracut/modules.d/95involflt/
++ echo /usr/local/ASR/Vx
++ sed 's///\//g'
- vxdir='/usr/local/ASR/Vx'
- echo 'Setting vxdir = /usr/local/ASR/Vx (/usr/local/ASR/Vx)'
Setting vxdir = /usr/local/ASR/Vx (/usr/local/ASR/Vx)
- sed -i 's/_vxdir=""/_vxdir="/usr/local/ASR/Vx"/' /usr/share/dracut/modules.d/95involflt/installkernel
- is_distro OL8
- set -x
- echo RHEL6-64
- grep -qi OL8
- return 1
- is_distro OL9
- set -x
- echo RHEL6-64
- grep -qi OL9
- return 1
- is_distro RHEL8
- set -x
- echo RHEL6-64
- grep -qi RHEL8
- return 1
- is_distro RHEL9
- set -x
- echo RHEL6-64
- grep -qi RHEL9
- return 1
- is_distro RHEL7
- set -x
- echo RHEL6-64
- grep -qi RHEL7
- return 1
- is_distro SLES15
- set -x
- echo RHEL6-64
- grep -qi SLES15
- return 1
- regenerate_all
- dracut -h
- grep -q -- --kver
- regenerate_foreach
- local retval=0
- local kernel=
++ ls /lib/modules
- for kernel in '
ls /lib/modules' - echo 2.6.32-504.23.4.el6.x86_64
- grep -q '^[1-9]'
- test -f /lib/modules/2.6.32-504.23.4.el6.x86_64/modules.dep
- test -f /boot/vmlinuz-2.6.32-504.23.4.el6.x86_64
- regenerate 2.6.32-504.23.4.el6.x86_64
- local opt=
- local ifile=
- dracut -h
- grep -q -- --kver
- is_distro OL6
- set -x
- echo RHEL6-64
- grep -qi OL6
- return 1
- dracut -f '' 2.6.32-504.23.4.el6.x86_64
pigz: abort: write error on <stdout> (No space left on device)
E: dracut: creation of /boot/initramfs-2.6.32-504.23.4.el6.x86_64.img failed
- echo 'Cannot generate initrd for '
Cannot generate initrd for
- return 1
- retval=1
- for kernel in '
ls /lib/modules' - echo 2.6.32-754.23.1.el6.x86_64
- grep -q '^[1-9]'
- test -f /lib/modules/2.6.32-754.23.1.el6.x86_64/modules.dep
- test -f /boot/vmlinuz-2.6.32-754.23.1.el6.x86_64
- regenerate 2.6.32-754.23.1.el6.x86_64
- local opt=
- local ifile=
- dracut -h
- grep -q -- --kver
- is_distro OL6
- set -x
- echo RHEL6-64
- grep -qi OL6
- return 1
- dracut -f '' 2.6.32-754.23.1.el6.x86_64
- is_distro OL6
- set -x
- echo RHEL6-64
- grep -qi OL6
- return 1
- return 0
- for kernel in '
ls /lib/modules' - echo 2.6.32-754.35.1.el6.x86_64
- grep -q '^[1-9]'
- test -f /lib/modules/2.6.32-754.35.1.el6.x86_64/modules.dep
- test -f /boot/vmlinuz-2.6.32-754.35.1.el6.x86_64
- regenerate 2.6.32-754.35.1.el6.x86_64
- local opt=
- local ifile=
- dracut -h
- grep -q -- --kver
- is_distro OL6
- set -x
- echo RHEL6-64
- grep -qi OL6
- return 1
- dracut -f '' 2.6.32-754.35.1.el6.x86_64
- is_distro OL6
- set -x
- echo RHEL6-64
- grep -qi OL6
- return 1
- return 0
- return 1
- return 1
- return 1
- break
- install_cleanup
- set -x
- echo Cleanup
Cleanup
- return 1
11/21/2023 12:03:58: Contents of /boot after generating the initrd images.
total 80712
-rw-r--r-- 1 root root 2545975 Jun 9 2015 System.map-2.6.32-504.23.4.el6.x86_64
-rw-r--r-- 1 root root 2658899 Sep 26 2019 System.map-2.6.32-754.23.1.el6.x86_64
-rw-r--r-- 1 root root 2660415 Nov 7 2020 System.map-2.6.32-754.35.1.el6.x86_64
-rw-r--r-- 1 root root 106371 Jun 9 2015 config-2.6.32-504.23.4.el6.x86_64
-rw-r--r-- 1 root root 108308 Sep 26 2019 config-2.6.32-754.23.1.el6.x86_64
-rw-r--r-- 1 root root 108308 Nov 7 2020 config-2.6.32-754.35.1.el6.x86_64
drwxr-xr-x. 3 root root 1024 Oct 25 2013 efi
drwxr-xr-x. 2 root root 1024 Sep 2 2021 grub
-rw------- 1 root root 30486030 Nov 21 12:01 initramfs-2.6.32-754.23.1.el6.x86_64.img
-rw------- 1 root root 30489192 Nov 21 12:03 initramfs-2.6.32-754.35.1.el6.x86_64.img
drwx------. 2 root root 12288 Oct 25 2013 lost+found
-rw-r--r-- 1 root root 200210 Jun 9 2015 symvers-2.6.32-504.23.4.el6.x86_64.gz
-rw-r--r-- 1 root root 216292 Sep 26 2019 symvers-2.6.32-754.23.1.el6.x86_64.gz
-rw-r--r-- 1 root root 216357 Nov 7 2020 symvers-2.6.32-754.35.1.el6.x86_64.gz
-rwxr-xr-x 1 root root 4152720 Jun 9 2015 vmlinuz-2.6.32-504.23.4.el6.x86_64
-rwxr-xr-x 1 root root 4335888 Sep 26 2019 vmlinuz-2.6.32-754.23.1.el6.x86_64
-rwxr-xr-x 1 root root 4336848 Nov 7 2020 vmlinuz-2.6.32-754.35.1.el6.x86_64
11/21/2023 12:03:58: Failed to generate initrd images. Restoring original initrd images.
11/21/2023 12:03:58: Contents of /etc/vxagent/orig_initrd_images/ after generating the initrd images.
total 58848
-rw------- 1 root root 30127465 Nov 21 11:58 initramfs-2.6.32-754.23.1.el6.x86_64.img
-rw------- 1 root root 30129651 Nov 21 11:58 initramfs-2.6.32-754.35.1.el6.x86_64.img
11/21/2023 12:03:58: Contents of /boot after restoring the initrd images.
total 80011
-rw-r--r-- 1 root root 2545975 Jun 9 2015 System.map-2.6.32-504.23.4.el6.x86_64
-rw-r--r-- 1 root root 2658899 Sep 26 2019 System.map-2.6.32-754.23.1.el6.x86_64
-rw-r--r-- 1 root root 2660415 Nov 7 2020 System.map-2.6.32-754.35.1.el6.x86_64
-rw-r--r-- 1 root root 106371 Jun 9 2015 config-2.6.32-504.23.4.el6.x86_64
-rw-r--r-- 1 root root 108308 Sep 26 2019 config-2.6.32-754.23.1.el6.x86_64
-rw-r--r-- 1 root root 108308 Nov 7 2020 config-2.6.32-754.35.1.el6.x86_64
drwxr-xr-x. 3 root root 1024 Oct 25 2013 efi
drwxr-xr-x. 2 root root 1024 Sep 2 2021 grub
-rw------- 1 root root 30127465 Nov 21 12:03 initramfs-2.6.32-754.23.1.el6.x86_64.img
-rw------- 1 root root 30129651 Nov 21 12:03 initramfs-2.6.32-754.35.1.el6.x86_64.img
drwx------. 2 root root 12288 Oct 25 2013 lost+found
-rw-r--r-- 1 root root 200210 Jun 9 2015 symvers-2.6.32-504.23.4.el6.x86_64.gz
-rw-r--r-- 1 root root 216292 Sep 26 2019 symvers-2.6.32-754.23.1.el6.x86_64.gz
-rw-r--r-- 1 root root 216357 Nov 7 2020 symvers-2.6.32-754.35.1.el6.x86_64.gz
-rwxr-xr-x 1 root root 4152720 Jun 9 2015 vmlinuz-2.6.32-504.23.4.el6.x86_64
-rwxr-xr-x 1 root root 4335888 Sep 26 2019 vmlinuz-2.6.32-754.23.1.el6.x86_64
-rwxr-xr-x 1 root root 4336848 Nov 7 2020 vmlinuz-2.6.32-754.35.1.el6.x86_64
11/21/2023 12:03:58: Contents of /etc/vxagent/orig_initrd_images/ after restoring the initrd images.
total 0
11/21/2023 12:03:58: Restored original initrd images successfully.
11/21/2023 12:03:58 : Failed to generate initrd image. Rolling back agent installation.
11/21/2023 12:03:58 : Re-try installation and contact support if issue persists.
11/21/2023 12:03:58: Give 770 permissions to /usr/local/ASR/Vx/
{count} votes
-
SadiqhAhmed-MSFT 48,351 Reputation points Microsoft Employee2023-11-23T14:05:55.7466667+00:00 Hello @Anonymous Thank you for contacting us through Microsoft Q&A platform. Happy to help!
I see that you are trying to install ASR Mobility agent manually on Centos 6.10 and being faced an error.
As per details, it seems like space requirement issue. The error "pigz: abort: write error on <stdout> (No space left on device)". There are free space requirements mentioned for asr install. Please check free space on device and make enough space available and then retry.
Also, check the supported versions of CentOS and kernel versions - https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview
Hope this helps!
-
SadiqhAhmed-MSFT 48,351 Reputation points Microsoft Employee
2023-11-28T07:22:16.62+00:00 @Anonymous Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
-
SadiqhAhmed-MSFT 48,351 Reputation points Microsoft Employee
2023-11-29T07:29:35.2866667+00:00 @Anonymous We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Sign in to comment
Sign in to answer