You must reconfigure Disk 1 on the vRealize Automation version you are upgrading from before beginning the upgrade.

About this task

Perform this procedure for each replica appliance node sequentially, and then for the master node.

Note:

When you perform this procedure, you might see these warning messages:

  • WARNING: Re-reading the partition table failed with error 16:
    Device or resource busy. The kernel still uses the old table. The
    new table will be used at the next reboot or after you run
    partprobe(8) or kpartx(8) Syncing disks.
    
  • Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. 

Ignore this message: You should reboot now before making further changes. If you reboot your system before step 10, you will corrupt the upgrade process.

Procedure

  1. Power on and SSH login to the vRealize Automation appliance.
  2. Stop all vRealize Automation services.
    1. service vcac-server stop
    2. service vco-server stop
    3. service vpostgres stop
  3. Unmount the swap partition:

    swapoff -a

  4. Delete the existing Disk 1 partitions and create a 44 GB root partition and a 6 GB swap partition:

    (echo d; echo 2; echo d; echo 1; echo n; echo p; echo ; echo ; echo '+44G'; echo n; echo p; echo ; echo ; echo ; echo w; echo p; echo q) | fdisk /dev/sda

  5. Change the swap partition type.

    (echo t; echo 2; echo 82; echo w; echo p; echo q) | fdisk /dev/sda

  6. Set the Disk 1 bootable flag:

    (echo a; echo 1; echo w; echo p; echo q) | fdisk /dev/sda

  7. Register the partition changes with the Linux kernel.

    partprobe

    Note:

    If you see a message telling you to reboot before you make further changes, ignore the message. Rebooting the system before step 10 corrupts the upgrade process.

  8. Format the new swap partition.

    mkswap /dev/sda2

  9. Mount the swap partition.

    swapon -a

  10. Reboot the vRealize Automation appliance.
  11. After the appliance reboots, resize the Disk 1 partition table.

    resize2fs /dev/sda1

  12. Verify that the disk expansion is successful by running df -h and checking that the available disk space on /dev/sda1 is greater than 3 GB.
  13. Repeat steps 1-11 on all other vRealize Automation appliances.
  14. Shut down all replica vRealize Automation appliance nodes.

What to do next

Install the Update on the vRealize Automation Appliance