ACR : kickstart installation failed and got alarm partitioning error

Doc ID		SOLN268296
Version:		3.0
Status:		Published
Published date:		04 Oct 2018
Created Date:		11 May 2015

Author:

chengdongzhao

Details

**Updated ACR15.1 on RHEL 7.X** **Updated: Customer advising provided "Kickstart" file will not run and just returns to the command prompt.***

The ACR kickstert file fails to install on new RedHat 6.3 build on IBM x3650 server. Partition designed like below:
/boot Bootstrap RAID 1 A 1 GB
/ Linux and ACR RAID 1 A 10 GB
Swap Virtual Memory RAID 1 A 8 GB
/var Linux .var and the DB RAID 1 A 20 GB
/calls The Recordings RAID 5 B 672 GB – Unit Size of 64k
Got alarm like below:
The following errors occurred with your partitioning:
You have not created a /boot/efi partition.
This can happen if there is not enough space on your hard drive(s) for the installation.

Problem Clarification

***Updated: After emailing Verint the KS file that was being used there were some issues Identified***

Exact issue happening:Kickstart OS install Failed: After the kickstart file has been loaded, the OS gives an error about "Partitioning error; No UEFI partition defined or not enough free space"

Cause

***Updated: It was identified by Verint to ensure that the kickstart guide be followed. The identified issues were with the Network settings as well as to ensure the disk settings did not exceed the actual physical space.***

With RedHat 6.3 build on IBM x3650 server with Raid 1 & Raid 5 configured, it need efi partition configured for kickstart installation.

Solution

***Updated: Kickstart Guide need for creating the file needs to be followed.

edit kickstart script (in Linux environment) and add below line for efi partition, then perform kickstart installation:
part /boot/efi --fstype=efi --size=100 --ondisk=sda

Attachment File

acr_12.1_15.1_kickstart-v2.docx
514K • 2 minute(s) @ 56k, < 1 minute @ broadband

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy