<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Extend HardDisks/Partitions on the vIDM Appliance in VMware Aria Suite Lifecycle Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Extend-HardDisks-Partitions-on-the-vIDM-Appliance/m-p/2982819#M280</link>
    <description>&lt;P&gt;It's great when a community contribution is upgraded to an official KB article &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@90D223CDF4C4491D7DFF693BB5C76865/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 18 Aug 2023 08:25:37 GMT</pubDate>
    <dc:creator>rwk1982</dc:creator>
    <dc:date>2023-08-18T08:25:37Z</dc:date>
    <item>
      <title>Extend HardDisks/Partitions on the vIDM Appliance</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Extend-HardDisks-Partitions-on-the-vIDM-Appliance/m-p/2850270#M197</link>
      <description>&lt;P&gt;Our vIDM appliance is now at 3.3.4, was updated several times and still has the disk layout from the initial 3.3.2 installation:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rwk1982_1-1622553423963.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89246i45ACD95435C46F19/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="rwk1982_1-1622553423963.png" alt="rwk1982_1-1622553423963.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The pre check to 3.3.5 now fails complaining:&amp;nbsp;Disk space on /opt/vmware/horizon should be at least 7 GB for upgrade bundle upload. Current available space on /opt/vmware/horizon is 2 GB in node. So i decided to extend the disks and partitions to match the 3.3.5 vIDM disk settings:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rwk1982_2-1622555689247.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89251i1B00F280B1F60A93/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="rwk1982_2-1622555689247.png" alt="rwk1982_2-1622555689247.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The steps are quite simple and can be done online:&lt;/P&gt;&lt;P&gt;Extend Hard disk 1 to 60GB and Hard disk 2 and 3 to 20GB in vCenter (Hard disk 4 can be ignored)&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rwk1982_0-1622556788397.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89253i67878CAD4EEF29DC/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="rwk1982_0-1622556788397.png" alt="rwk1982_0-1622556788397.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;After that is a good time to take a snapshot of the VM.&lt;/P&gt;&lt;P&gt;Login as "root" to your appliance let linux rescan for the disk changes:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;echo 1 &amp;gt; /sys/class/block/sda/device/rescan
echo 1 &amp;gt; /sys/class/block/sdb/device/rescan
echo 1 &amp;gt; /sys/class/block/sdc/device/rescan&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Check if the new disk sizes are recognized with dmesg:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;dmesg -T | grep "detected capacity change"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now you can extend the root partition with:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;cfdisk /dev/sda&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Select /dev/sda4, [ Resize ], type 12G (12G are used in the 3.3.5 appliance), than [ Write ] and finally type "yes" and quit cfdisk&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rwk1982_1-1622558473434.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89254i9D338560D5DAA4A8/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="rwk1982_1-1622558473434.png" alt="rwk1982_1-1622558473434.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Now you must resize the file system with "resize2fs" to use the new space:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[before resize2fs]
df -h | grep "sda4"
/dev/sda4 8.8G 3.9G 4.5G 47% /

[run resize2fs]
resize2fs /dev/sda4

[after resize2fs]
df -h | grep "sda4"
/dev/sda4 12G 3.9G 7.3G 35% /&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Next is to resize the two data partitions which are LVMs and the steps are different in this case:&lt;/P&gt;&lt;P&gt;Use "pvresize" to let LVM know that the physical disk size has changed:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[before pvresize]
pvdisplay /dev/sdc /dev/sdb
  --- Physical volume ---
  PV Name               /dev/sdc
  VG Name               tomcat_vg
  PV Size               10.00 GiB / not usable 4.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              2559
  Free PE               0
  Allocated PE          2559
  PV UUID               546IZ8-0PYE-AAKg-f2WP-VGeG-L9ep-OTasC3

  --- Physical volume ---
  PV Name               /dev/sdb
  VG Name               db_vg
  PV Size               10.00 GiB / not usable 4.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              2559
  Free PE               0
  Allocated PE          2559
  PV UUID               ue30Dt-bPWI-JlYG-DktR-5mGT-AZ66-4KEK03

[run pvresize]
pvresize /dev/sdb /dev/sdc

[after pvresize]
pvdisplay /dev/sdc /dev/sdb
  --- Physical volume ---
  PV Name               /dev/sdc
  VG Name               tomcat_vg
  PV Size               &amp;lt;20.00 GiB / not usable 0
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              5119
  Free PE               2560
  Allocated PE          2559
  PV UUID               546IZ8-0PYE-AAKg-f2WP-VGeG-L9ep-OTasC3

  --- Physical volume ---
  PV Name               /dev/sdb
  VG Name               db_vg
  PV Size               &amp;lt;20.00 GiB / not usable 0
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              5119
  Free PE               2560
  Allocated PE          2559
  PV UUID               ue30Dt-bPWI-JlYG-DktR-5mGT-AZ66-4KEK03&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Next step is to&amp;nbsp;&lt;SPAN&gt;extend the logical volumes with "lvextend" to use the new space:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[before lvextend]
lvdisplay /dev/tomcat_vg/horizon /dev/db_vg/db
  --- Logical volume ---
  LV Path                /dev/tomcat_vg/horizon
  LV Name                horizon
  VG Name                tomcat_vg
  LV UUID                gw2MpR-PZgs-ehmA-Ebpc-vg52-97Nd-9t5YVW
  LV Write Access        read/write
  LV Creation host, time sc-a01-049-209, 2019-09-12 15:55:24 +0000
  LV Status              available
  # open                 1
  LV Size                &amp;lt;10.00 GiB
  Current LE             2559
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1

  --- Logical volume ---
  LV Path                /dev/db_vg/db
  LV Name                db
  VG Name                db_vg
  LV UUID                WzGOjU-z4Qw-FI0u-aOVO-AWlB-AO1O-2fwSkN
  LV Write Access        read/write
  LV Creation host, time sc-a01-049-209, 2019-09-12 15:55:23 +0000
  LV Status              available
  # open                 1
  LV Size                &amp;lt;10.00 GiB
  Current LE             2559
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

[run lvextend]
lvextend -l +100%FREE /dev/tomcat_vg/horizon
lvextend -l +100%FREE /dev/db_vg/db

[after lvextend]
lvdisplay /dev/tomcat_vg/horizon /dev/db_vg/db
  --- Logical volume ---
  LV Path                /dev/tomcat_vg/horizon
  LV Name                horizon
  VG Name                tomcat_vg
  LV UUID                gw2MpR-PZgs-ehmA-Ebpc-vg52-97Nd-9t5YVW
  LV Write Access        read/write
  LV Creation host, time sc-a01-049-209, 2019-09-12 15:55:24 +0000
  LV Status              available
  # open                 1
  LV Size                &amp;lt;20.00 GiB
  Current LE             5119
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1

  --- Logical volume ---
  LV Path                /dev/db_vg/db
  LV Name                db
  VG Name                db_vg
  LV UUID                WzGOjU-z4Qw-FI0u-aOVO-AWlB-AO1O-2fwSkN
  LV Write Access        read/write
  LV Creation host, time sc-a01-049-209, 2019-09-12 15:55:23 +0000
  LV Status              available
  # open                 1
  LV Size                &amp;lt;20.00 GiB
  Current LE             5119
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And finally use "resize2fs" to extend the file system on the two LVs:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[before resize2fs]
df -h | grep "mapper"
/dev/mapper/db_vg-db           9.8G 1014M  8.3G  11% /db
/dev/mapper/tomcat_vg-horizon  9.8G  7.1G  2.2G  78% /opt/vmware/horizon

[run resize2fs]
resize2fs /dev/tomcat_vg/horizon
resize2fs /dev/db_vg/db

[after resize2fs]
df -h | grep "mapper"
/dev/mapper/db_vg-db            20G 1019M   18G   6% /db
/dev/mapper/tomcat_vg-horizon   20G  7.2G   12G  39% /opt/vmware/horizon&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's all... and I think not supported from VMware &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@175698D61412968B624AD0FDF51E2E6D/emoticons/1f604.png" alt=":grinning_face_with_smiling_eyes:" title=":grinning_face_with_smiling_eyes:" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jun 2021 15:32:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Extend-HardDisks-Partitions-on-the-vIDM-Appliance/m-p/2850270#M197</guid>
      <dc:creator>rwk1982</dc:creator>
      <dc:date>2021-06-01T15:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: Extend HardDisks/Partitions on the vIDM Appliance</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Extend-HardDisks-Partitions-on-the-vIDM-Appliance/m-p/2982733#M279</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's all... and I think not supported from VMware &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@175698D61412968B624AD0FDF51E2E6D/emoticons/1f604.png" alt=":grinning_face_with_smiling_eyes:" title=":grinning_face_with_smiling_eyes:" /&gt;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Welp if it wasn't it sure is now, I stumbled upon both of these articles and realized one was just like the other, haha.&lt;/P&gt;&lt;P&gt;Thanks, this is helping me alot!&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/85425#:~:text=How%20to%20Increase%20vIDM%20appliance%20disk%20space%20%2885425%29,tab%20key%20select%20%5B%20Write%20%5D%20type%20%22yes%22" target="_blank"&gt;How to Increase vIDM appliance disk space (85425) (vmware.com)&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Aug 2023 15:42:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Extend-HardDisks-Partitions-on-the-vIDM-Appliance/m-p/2982733#M279</guid>
      <dc:creator>NewGuy9</dc:creator>
      <dc:date>2023-08-17T15:42:16Z</dc:date>
    </item>
    <item>
      <title>Re: Extend HardDisks/Partitions on the vIDM Appliance</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Extend-HardDisks-Partitions-on-the-vIDM-Appliance/m-p/2982819#M280</link>
      <description>&lt;P&gt;It's great when a community contribution is upgraded to an official KB article &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@90D223CDF4C4491D7DFF693BB5C76865/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Aug 2023 08:25:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Extend-HardDisks-Partitions-on-the-vIDM-Appliance/m-p/2982819#M280</guid>
      <dc:creator>rwk1982</dc:creator>
      <dc:date>2023-08-18T08:25:37Z</dc:date>
    </item>
  </channel>
</rss>

