Skip to main content
NetApp Knowledge Base

How to prepare a VM for RHEL Classification Installation

  1. Last updated
  2. Save as PDF
Views:
159
Visibility:
Public
Votes:
0
Category:
netapp_console
Specialty:
ds_dc
Last Updated:

Applies to

  • Cloud Data Sense
  • BlueXP
  • Classification
  • Red Hat (RHEL)
  • Podman

Description

The steps in this KB are intended to assist with preparing a Virtual Machine (VM) for Data Sense (Classification) installation manually on Red Hat (RHEL) using Podman.

Procedure

  1. Ensure the VM is running a supported version of RHEL and meets the minimum CPU/RAM requirements 
  2. Confirm the appropriate space is allotted to the required directories:
    • [user@ClassificationVM ~]$ lsblk
      NAME              MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
      sda                 8:0    0  512G  0 disk 
      ├─sda1              8:1    0  200M  0 part /boot/efi
      ├─sda2              8:2    0  500M  0 part /boot
      ├─sda3              8:3    0    1M  0 part 
      └─sda4              8:4    0 63.3G  0 part 
        ├─rootvg-tmplv  253:0    0    2G  0 lvm  /tmp
        ├─rootvg-usrlv  253:1    0   10G  0 lvm  /usr
        ├─rootvg-homelv 253:2    0    1G  0 lvm  /home
        ├─rootvg-varlv  253:3    0    8G  0 lvm  /var
        └─rootvg-rootlv 253:4    0    2G  0 lvm  /
      sdb                 8:16   0  128G  0 disk 
      └─sdb1              8:17   0  128G  0 part /mnt
      sr0                11:0    1  628K  0 rom         
  3. ​​​​​​In the above output the minimum required allocation is not met. To meet these space requirements on /tmp and /var first it is necessary to allocate more space to the sda4 partition from the sda disk:Use the fdisk command to delete the sda4 partition and recreate it using the needed capacity: 
  • [user@ClassificationVM ~]$ sudo -s

  • Enter the fdisk utility:

    • [root@ClassificationVM ~]# fdisk /dev/sda

      Welcome to fdisk (util-linux 2.37.4).
      Changes will remain in memory only, until you decide to write them.
      Be careful before using the write command.

      GPT PMBR size mismatch (134217727 != 1073741823) will be corrected by write.
      The backup GPT table is not on the end of the device. This problem will be corrected by write.
      This disk is currently in use - repartitioning is probably a bad idea.
      It's recommended to umount all file systems, and swapoff all swap
      partitions on this disk.

      Command (m for help):

  • List the current partitions:

    • Command (m for help): p

      Disk /dev/sda: 512 GiB, 549755813888 bytes, 1073741824 sectors
      Disk model: Virtual Disk    
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disklabel type: gpt
      Disk identifier: 4B52AC4D-7B36-44C7-AE6D-9B1B01A86752

      Device       Start       End   Sectors  Size Type
      /dev/sda1     2048    411647    409600  200M EFI System
      /dev/sda2   411648   1435647   1024000  500M Linux filesystem
      /dev/sda3  1435648   1437695      2048    1M BIOS boot
      /dev/sda4  1437696 134215679 132777984 63.3G Linux LVM

  • Delete the existing sda4 partition:

    • Command (m for help): d
      Partition number (1-4, default 4): 4

      Partition 4 has been deleted.

  • Recreate the sda4 partition at the correct size (make sure the first sector matches the first sector of the previous sda4 partition:

    • Command (m for help): n
      Partition number (4-128, default 4): 4
      First sector (1437696-1073741790, default 1437696): 1437696
      Last sector, +/-sectors or +/-size{K,M,G,T,P} (1437696-1073741790, default 1073741790): +500G

      Created a new partition 4 of type 'Linux filesystem' and of size 500 GiB.
      Partition #4 contains a LVM2_member signature.

      Do you want to remove the signature? [Y]es/[N]o: n

  • List the new partition table:

    • Command (m for help): p

      Disk /dev/sda: 512 GiB, 549755813888 bytes, 1073741824 sectors
      Disk model: Virtual Disk    
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disklabel type: gpt
      Disk identifier: 4B52AC4D-7B36-44C7-AE6D-9B1B01A86752

      Device       Start        End    Sectors  Size Type
      /dev/sda1     2048     411647     409600  200M EFI System
      /dev/sda2   411648    1435647    1024000  500M Linux filesystem
      /dev/sda3  1435648    1437695       2048    1M BIOS boot
      /dev/sda4  1437696 1050013695 1048576000  500G Linux filesystem

  • Commit and write the changes:

    • Command (m for help): w
      The partition table has been altered.
      Syncing disks.

  • Check the new file system layout:

    • [root@ClassificationVM ~]# lsblk
      NAME              MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
      sda                 8:0    0  512G  0 disk 
      ├─sda1              8:1    0  200M  0 part /boot/efi
      ├─sda2              8:2    0  500M  0 part /boot
      ├─sda3              8:3    0    1M  0 part 
      └─sda4              8:4    0  500G  0 part 
        ├─rootvg-tmplv  253:0    0    2G  0 lvm  /tmp
        ├─rootvg-usrlv  253:1    0   10G  0 lvm  /usr
        ├─rootvg-homelv 253:2    0    1G  0 lvm  /home
        ├─rootvg-varlv  253:3    0    8G  0 lvm  /var
        └─rootvg-rootlv 253:4    0    2G  0 lvm  /
      sdb                 8:16   0  128G  0 disk 
      └─sdb1              8:17   0  128G  0 part /mnt
      sr0                11:0    1  628K  0 rom  
       

  • Restart the Virtual Machine to ensure ​​​​​​the Operating System recognizes the new partition table changes.

  • Add the new space in the partition to the PV (Physical Volume):

    • [root@ClassificationVM ~]# growpart /dev/sda 4
      CHANGED: partition=4 start=1437696 old: size=1048576000 end=1050013695 new: size=1072304095 end=1073741790
      [root@ryanuClassification0215 ryanu]# lsblk
      NAME              MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
      sda                 8:0    0   512G  0 disk 
      ├─sda1              8:1    0   200M  0 part /boot/efi
      ├─sda2              8:2    0   500M  0 part /boot
      ├─sda3              8:3    0     1M  0 part 
      └─sda4              8:4    0 511.3G  0 part 
        ├─rootvg-tmplv  253:0    0     5G  0 lvm  /tmp
        ├─rootvg-usrlv  253:1    0    10G  0 lvm  /usr
        ├─rootvg-homelv 253:2    0     1G  0 lvm  /home
        ├─rootvg-varlv  253:3    0    30G  0 lvm  /var
        └─rootvg-rootlv 253:4    0     2G  0 lvm  /
      sdb                 8:16   0   128G  0 disk 
      └─sdb1              8:17   0   128G  0 part /mnt
      sr0                11:0    1  1024M  0 rom  
      [root@ClassificationVM ~]# pvscan
        PV /dev/sda4   VG rootvg   lvm2 [511.31 GiB / 463.31 GiB free]
        Total: 1 [511.31 GiB] / in use: 1 [511.31 GiB] / in no VG: 0 [0   ]

  • Now that the needed space is allocated to the partition use this space to increase the size of the required Logical Volumes (LV):

    • [root@ClassificationVM ~]# lvresize -r -L +3G /dev/mapper/rootvg-tmplv
        Size of logical volume rootvg/tmplv changed from 2.00 GiB (512 extents) to 5.00 GiB (1280 extents).
        File system xfs found on rootvg/tmplv mounted at /tmp.
        Extending file system xfs to 5.00 GiB (5368709120 bytes) on rootvg/tmplv...
      xfs_growfs /dev/rootvg/tmplv
      meta-data=/dev/mapper/rootvg-tmplv isize=512    agcount=4, agsize=131072 blks
               =                       sectsz=4096  attr=2, projid32bit=1
               =                       crc=1        finobt=1, sparse=1, rmapbt=0
               =                       reflink=1    bigtime=1 inobtcount=1 nrext64=0
      data     =                       bsize=4096   blocks=524288, imaxpct=25
               =                       sunit=0      swidth=0 blks
      naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
      log      =internal log           bsize=4096   blocks=16384, version=2
               =                       sectsz=4096  sunit=1 blks, lazy-count=1
      realtime =none                   extsz=4096   blocks=0, rtextents=0
      data blocks changed from 524288 to 1310720
      xfs_growfs done
        Extended file system xfs on rootvg/tmplv.
        Logical volume rootvg/tmplv successfully resized.

    • [root@ClassificationVM ~]# lvresize -r -L +387G /dev/mapper/rootvg-varlv

    • Size of logical volume rootvg/varlv changed from 8.00 GiB (2048 extents) to 395.00 GiB (101120 extents).
        File system xfs found on rootvg/varlv mounted at /var.
        Extending file system xfs to 395.00 GiB (424128020480 bytes) on rootvg/varlv...
      xfs_growfs /dev/rootvg/varlv
      meta-data=/dev/mapper/rootvg-varlv isize=512    agcount=4, agsize=524288 blks
               =                       sectsz=4096  attr=2, projid32bit=1
               =                       crc=1        finobt=1, sparse=1, rmapbt=0
               =                       reflink=1    bigtime=1 inobtcount=1 nrext64=0
      data     =                       bsize=4096   blocks=2097152, imaxpct=25
               =                       sunit=0      swidth=0 blks
      naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
      log      =internal log           bsize=4096   blocks=16384, version=2
               =                       sectsz=4096  sunit=1 blks, lazy-count=1
      realtime =none                   extsz=4096   blocks=0, rtextents=0
      data blocks changed from 2097152 to 103546880
      xfs_growfs done
        Extended file system xfs on rootvg/varlv.
        Logical volume rootvg/varlv successfully resized.

    • [root@ClassificationVM ~]# lvresize -r -L +98G /dev/mapper/rootvg-rootlv 

    • Size of logical volume rootvg/rootlv changed from 2.00 GiB (512 extents) to 100.00 GiB (25600 extents).
        File system xfs found on rootvg/rootlv mounted at /.
        Extending file system xfs to 100.00 GiB (107374182400 bytes) on rootvg/rootlv...
      xfs_growfs /dev/rootvg/rootlv
      meta-data=/dev/mapper/rootvg-rootlv isize=512    agcount=4, agsize=131072 blks
               =                       sectsz=4096  attr=2, projid32bit=1
               =                       crc=1        finobt=1, sparse=1, rmapbt=0
               =                       reflink=1    bigtime=1 inobtcount=1 nrext64=0
      data     =                       bsize=4096   blocks=524288, imaxpct=25
               =                       sunit=0      swidth=0 blks
      naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
      log      =internal log           bsize=4096   blocks=16384, version=2
               =                       sectsz=4096  sunit=1 blks, lazy-count=1
      realtime =none                   extsz=4096   blocks=0, rtextents=0
      data blocks changed from 524288 to 26214400
      xfs_growfs done
        Extended file system xfs on rootvg/rootlv.
        Logical volume rootvg/rootlv successfully resized.

    • [root@ryanuClassification0215 ryanu]# lsblk
      NAME              MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
      sda                 8:0    0   512G  0 disk 
      ├─sda1              8:1    0   200M  0 part /boot/efi
      ├─sda2              8:2    0   500M  0 part /boot
      ├─sda3              8:3    0     1M  0 part 
      └─sda4              8:4    0 511.3G  0 part 
        ├─rootvg-tmplv  253:0    0     5G  0 lvm  /tmp
        ├─rootvg-usrlv  253:1    0    10G  0 lvm  /usr
        ├─rootvg-homelv 253:2    0     1G  0 lvm  /home
        ├─rootvg-varlv  253:3    0    30G  0 lvm  /var
        └─rootvg-rootlv 253:4    0   452G  0 lvm  /
      sdb                 8:16   0   128G  0 disk 
      └─sdb1              8:17   0   128G  0 part /mnt
      sr0                11:0    1  1024M  0 rom  

 

 


 

Partner Notes

partnerNotes_text
 

Additional Information

additionalInformation_text

Internal Notes

internalNotes_text

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.