No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Fail to Install Hypervisor Image for RHV 4.0.6 on RH2288 V3

Publication Date:  2017-10-27 Views:  147 Downloads:  0
Issue Description

Customer want to install Hypervisor Image for RHV 4.0.6 on RH2288 V3. During installation there is an error as shown below :-

 

 

Alarm Information

There is no alarm in iBMC.

Handling Process

Analysis on the two symptoms is as follows:

Symptom 1: A partitioning error occurred during the OS installation.

Conclusion:
According to Red Hat engineers, the error was caused by incorrect configuration in automatic partitioning by the OS. This problem can be resolved by manually configuring partitions during the OS installation.


Analysis Process:
1. The same error was reported during the RHVH 4.0 installation in the lab, and the installation failed too.
2. According to Red Hat engineers, the root partition of RHVH 4.0 must adopt LVM Thin Provisioning. 

 

 https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html-single/installation_guide/#Advanced_RHVH_Install


3. After LVM Thin Provisioning was selected during the installation, RHVH 4.0 was installed properly.
4. An installation guide will be provided for the customer to install RHVH 4.0 without any partitioning error.

 

 

Symptom 2: The OS could not start properly after connecting to the FC storage and mapping a LUN.

Conclusion:
A VG named rhvh existed in the LUN that was mapped to the server, but the RHVH system created another VG named rhvh during the installation by default. The two VGs with same name resulted in abnormal OS installation and startup.


Analysis Process:
1. In addition to local storage, a LUN was mapped to the OS from an FC HBA card. After the FC HBA card was disabled in the BIOS, the OS was installed properly. After the installation, all the results of imgbase check were OK.

 

 

2. After the installation was successful, if the FC HBA card was enabled in the BIOS, the OS could be accessed properly. The log indicated that the system partition could not be found, as shown in the following figure.

 

After the FC cable was removed, the OS could be accessed properly. 

 
After the OS was started and the cable was reconnected, the output of the vgdisplay command run in the OS contained two VGs with the same name rhvh.

 

The two VGs existed in the local storage and the FC LUN. In this case, the OS could not properly mount a system partition during the startup, and the OS startup failed.


The customer removed the current LUN and mapped a new LUN to the server. The server OS then started properly.

Root Cause

A VG named rhvh existed in the LUN that was mapped to the server, but the RHVH system created another VG named rhvh during the installation by default. The two VGs with same name resulted in abnormal OS installation and startup.

Solution
An installation guide provided for the customer to install RHVH 4.0 without any partitioning error. Please refer to attachment for the installation guide.
Suggestions

Install the OS first, than mapped the LUN to OS.

END