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>Search

Reminder

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

upgrade

Huawei Server Maintenance Manual 09

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Installation Problems

Installation Problems

Specific Settings for Installing the SUSE OS in an RH5485

Problem Description
Table 5-290 Basic information

Item

Information

Source of the Problem

RH5485

Intended Product

RH5485

Release Date

2011-11-18

Keyword

RH5485, UEFI, Legacy Only

Author

Han Yao (employee ID: 171887)

Symptom

Hardware configuration

RH5485 server

Symptom

During SUSE operating system (OS) installation, the system reports errors, and the installation is not complete. Alternatively, the system restarts after the installation, the server is hung in the power on self-test (POST) phase, and only the cursor is blinking on the black screen.

Key Process and Cause Analysis

Key process

Restart the server, and add Legacy Only.

  1. When the server starts, press F1 to display the Setup interface of the Unified Extensible Firmware Interface (UEFI) based on the screen prompt.
  2. Select Boot Manager and press Enter.

  3. Select Boot Manager and press Enter.

  4. Select Legacy Only and press Enter.

  5. Press ESC to return to the Boot Manager interface, select Change Boot Order, and press Enter.

  6. Set Legacy Only as the first boot item.

  7. Select Commit Changes and press Enter. After saving the modification, restart the server.

Cause analysis

Compared with the traditional (Legacy) BIOS, the UEFI is a new-generation BIOS. The SUSE OS does not support the UEFI mode. When installing the SUSE OS in the RH5485, set Legacy Only as the first boot item of the server.

Conclusion and Solution

Conclusion

The SUSE OS supports only the Legacy mode.

Solution

Before installing the SUSE OS in the RH5485, access Setup of the UEFI. On the Boot Manager interface, set Legacy Only as the first boot item.

Experience

Before installing Windows Server 2008 and the RHEL system in the RH5485, do not require specific settings. Before installing the SUSE OS, set Legacy Only as the first boot item.

Note

None

Error Occurs During CentOS/RHEL 6 Installation

Problem Description
Table 5-291 Basic information

Item

Information

Source of the Problem

V2 servers

Intended Product

V2 servers

Release Date

2013-12-15

Keyword

CentOS/RHEL 6, install

Symptom

Symptom

CentOS/RHEL 6 cannot be installed on a V2 server, and the following message is displayed (see Figure 5-336):

Disk sda contains BIOS RAID metadata, but it is not part of any recognized BIOS RAID sets. Ignoring disk sda.

Figure 5-336 CentOS/RHEL 6 installation failure

Key Process and Cause Analysis

Cause analysis

The hard drive contains remaining RAID information, for example, after a drive managed by a RAID controller card is used by a RAID controller card of another model on another device. When a user installs CentOS/RHEL 6, the system checks the hard drive for remaining RAID information. If remaining RAID information is detected on the hard drive, the hard drive cannot be used.

Conclusion and Solution

Solution

  1. Workaround

    On the installation screen, edit the kernel file to add the nodmraid parameter to mask RAID arrays.

    Figure 5-337 Adding the nodmraid parameter to mask RAID arrays

  2. You can use either of the following solutions:
    • Use dd if=/dev/zero of=/dev/sda bs=8192 to erase remaining RAID metadata.
    • Use a RAID controller card or OS to perform low-level formatting on the hard drive.
Experience

None

Note

None

Many System Devices Exist in the System Manager Due to the Absence of the Chipset Driver in Windows Server 2008

Problem Description
Table 5-292 Basic information

Item

Information

Source of the Problem

V2 servers

Intended Product

V2 servers

Release Date

2013-12-15

Keyword

Windows Server 2008, chipset driver

Symptom

Symptom

When Windows Server 2008 R2 is installed on a V2 server, a large number of basic system devices are displayed in the device manager.

Key Process and Cause Analysis

Cause analysis

Windows Server 2008 R2 is installed in OS image+RAID controller card driver mode, and the chipset driver is not installed after Windows Server 2008 R2 is installed.

Conclusion and Solution

Solution

Install the chipset driver. If the OSs of other components such as MEI, SCU&AHCI, and NICs do not provide a driver, you also need to install them.

Experience

Use the ServiceCD to install the OS to avoid the need to manually install drivers.

Note

None

Failed to Install Red Hat Enterprise Linux 6.3 on Servers Using IvyBridge E7-4830 V2 CPUs

Problem Description
Table 5-293 Basic information

Item

Information

Source of the Problem

RH5885 V3

Intended Product

Servers using IvyBridge CPUs

Release Date

2014-12-22

Keyword

RHEL6.3, installation failure

Symptom

Hardware configuration

RH5885 V3 with four IvyBridge E7-4830 v2 CPUs.

Software configuration

RHEL6.3

Symptom

The error message shown in Figure 5-338 is displayed when the RHEL6.3 installation begins.

Figure 5-338 Installation error

If you press Enter when the error message is displayed, the installation can be continued and successfully finished. On the two environment servers in the lab, this problem can be recurred if the servers use IvyBridge E7-4830 V2 CPUs, but this problem cannot be recurred if the servers use IvyBridge E7-4870 V2 CPUs. In other words, this problem will 100% occur on certain models of the IvyBridge EX series but does not occur on all models of the series.

Key Process and Cause Analysis

Key process

  1. Recur this problem in the same environment in the lab.
  2. Contact Red Hat FAE to consult about the problem and find out that this problem occurs because the RHEL6.3 does not support all IvyBridge CPU models. This problem does not affect the CPU usage. The following is the official explanation of this problem at Red Hat website.

    https://access.redhat.com/solutions/722773

Figure 5-339 Explanation at Red Hat website (1)

The same also applies to virtual machines.

https://access.redhat.com/solutions/785833

Figure 5-340 Explanation at Red Hat website (2)

Cause analysis

RHEL6.3 and earlier RHEL6 versions are not compatible with IvyBridge CPUs. Only RHEL6.4 and later versions can support IvyBridge CPUs.

Conclusion and Solution

Conclusion

This problem is caused by OS version compatibility. RHEL6.3 does not support all IvyBridge CPUs.

Solution

This problem does not affect RHEL6.3 installation. However, it is recommended that RHEL6.4 or later RHEL6 series OSs be installed on servers using IvyBridge CPUs. RHEL5 series OSs are RHEL5.9 and later versions.

Experience

Select an OS version that is compatible with the current server based on the compatibility list.

Note

For details about Red Hat's official explanation of the earliest OS versions supported by all Intel CPU models, go to the following website:

https://access.redhat.com/support/policy/intel

Figure 5-341 lists the IvyBridge E7V2 versions supported by Intel CPU models.

Figure 5-341 IvyBridge E7V2 versions supported by Intel CPUs

Solaris 10U9 Installation Failure

Problem Description
Table 5-294 Basic information

Item

Information

Source of the Problem

RH2485 V2 (SandyBridge CPU)

Intended Product

All servers

Release Date

2014-12-22

Keyword

Solaris 10U9, installation failure

Symptom

Hardware configuration

RH2485 V2 with SandyBridge E5 CPUs

Software configuration

Solaris 10U9

Symptom

The system breaks down during the installation of Solaris 10U9 on a drive partition. At the breakdown, a blank screen is displayed, and the following information is displayed:

boot: cannot find misc/amd64/krtld 
boot: error loading interpreter (misc/amd64/krtld) 
Elf64 read error. 
panic: no entry point in kernel/amd64/unix 
Press any key to reboot
Key Process and Cause Analysis

Key process

  1. After search on the Internet, it was found that a post at an Oracle technical forum stated that the problem was caused by data damage in a hard drive.
  2. Onsite personnel canceled RAID relationships, performed low-level formatting on each hard drive, rebuilt RAID arrays, and installed Solaris 10U9 again. The problem persisted.
  3. Onsite personnel re-downloaded the DVD-ROM image file, burnt an installation DVD-ROM, and used the DVD-ROM to install Solaris 10U9. The installation was successful and the problem was resolved.

Cause analysis

The Solaris 10U9 installation failure is caused by DVD-ROM image file damage.

Conclusion and Solution

Conclusion

The Solaris 10U9 installation problem is caused by DVD-ROM image damage.

Solution

Re-burn the installation DVD-ROM.

Experience

Check the installation DVD-ROM image prior to other items when locating an OS installation problem.

Note

Huawei iMana virtual image function does not support Solaris 10 series. A DVD-ROM must be burnt for installation.

ESXi 5.1 Installation Failure

Problem Description
Table 5-295 Basic information

Item

Information

Source of the Problem

RH5885 V3

Intended Product

All servers

Release Date

2014-12-18

Keyword

VMware ESXi 5.1, installation failure

Symptom

Hardware configuration

RH5885 V3 with four 15-core E7-4890 v2 processors

Software configuration

ESXi 5.1

Symptom

A customer operator reported that VMware ESXi 5.1.0 could not be installed on the RH5885H V3 server, and the purple screen shown in Figure 5-342 was displayed.

Figure 5-342 Installation error

Key Process and Cause Analysis

Key process

  1. The earliest OS version that VMware claimed to support IvyBridge platforms is ESXi 5.1 U2. However, VMware ESXi 5.0 U1 can be successfully installed on a large number of RH5885 V3 servers. Therefore, the ESXi 5.1 installation problem is not caused by incompatibility.
  2. The forum on the VMware official website provides the cause and solution to this problem. For details, visit the link:

    https://communities.vmware.com/message/2187459

    This link leads to a post that provides the cause of and solution to this problem:

     . Re: Error - Could not load multiboot modules:bad parameter  
            Thank you! 
    
    
            CD Image was broken. 
    
    
            With new CD install was completed without errors.
  3. After the customer re-burned the installation DVD-ROM and used it to install ESXi 5.1 again, the installation is successful.

Cause analysis

The installation failure is caused by installation DVD-ROM damage.

Conclusion and Solution

Conclusion

The installation failure is caused by installation DVD-ROM damage.

Solution

Re-burn the installation DVD-ROM and install ESXi 5.1 again.

Experience

Though ESXi 5.0, ESXi 5.1, and earlier versions of VMware OSs can be successfully installed on RH5885 V3 and RH5885H V3 servers, their long-term steady operating and performance cannot be guaranteed, and RAS features are unavailable. In addition, VMware claims that its ESXi 5.0, ESXi 5.1, or earlier OS versions do not support Intel E7 v2 CPUs, and these OSs cannot be certified. If a problem occurs in such a VMware OS, VMware does not help to locate the problem. It is recommended that customers use only OS versions on servers that the OS vendors claim to support.

Note
  1. VMware ESXi 5.1 U2 and later versions support Intel E7 v2 CPUs. For details, see the VMware official statement at the following link:

    http://www.vmware.com/files/pdf/techpaper/Whats-New-VMware-vSphere-51-Platform-Technical-Whitepaper.pdf

    Figure 5-343 VMware official statement

  2. Intel also released a statement to specify that the minimum versions of virtualization platforms such as VMware ESXi that support Intel E7 v2 CPUs are ESXi 5.1 and ESXi 5.5. This is consistent with that in the VMware official statement.

    Link: https://software.intel.com/en-us/articles/intel-xeon-processor-e7-v2-family-technical-overview

    Figure 5-344 Intel statement

  3. In the preceding two official statements, the earliest VMware OS version that support E7 v2 CPUs is ESXi 5.1. However, when we used ESXi 5.1 for RH5885 V3 or 5885H V3 certification, the certification application is rejected by the VMware official certification team. They required us to use ESXi 5.1 U2 for re-certification. The reason is that the earliest version that supports Intel E7 v2 CPUs is ESXi 5.1 U2.

An Error Was Reported During CentOS/RHEL Installation

Problem Description
Table 5-296 Basic information

Item

Information

Source of the Problem

V2 servers

Intended Product

All servers

Release Date

2013-11-28

Keyword

CentOS/RHEL, system installation, error reporting

Symptom

Symptom

During RHEL 5.5 installation, an error message is reported, as shown in Figure 5-345.

Figure 5-345 RHEL 5.5 installation error

Key Process and Cause Analysis

Cause analysis

In the boot state, the OS automatically scans for a drive where the OS can be installed. If no suitable drive is found, the OS reports an error.

No drive can be found because the LSI2208 controller card driver is not loaded on RHEL 5.5.

Conclusion and Solution

Solution

  1. If the RAID controller card is LSI SAS1078 or LSI SAS2208, only drives that have been added to RAID arrays can be used.
  2. Check whether the problem is caused by the failure to load the RAID controller card driver.
  3. The capacity of a hard drive or RAID array is greater than 2 TB. The OS may not support auto switching to the GUID partition table (GPT).
  4. Check whether the problem is caused by hardware faults such as SAS cable disconnection or mis-connection, SAS cable faults, hardware backplane faults, RAID controller card faults, or mainboard faults.
  5. Check whether the problem is caused by the OS image or physical DVD-ROM driver.
Experience

None

Note

None

OS Graphical Installation Failure in VNC Mode

Problem Description
Table 5-297 Basic information

Item

Information

Source of the Problem

V2 servers

Intended Product

All servers

Release Date

2013-12-15

Keyword

Virtual Network Computing (VNC) mode, graphical installation

Symptom

Symptom

The screen shown in Figure 5-346 is displayed during the OS installation. It seems that the device stops responding, and the OS installation cannot proceed.

Figure 5-346 Device not respond during OS installation

Key Process and Cause Analysis

Cause analysis

The screen shown in Figure 5-346 indicates that the current installation mode is NVC. You need to use the VNCViewer client to continue the OS installation after the screen is displayed.

Experience

None

Note

None

Drive D Space Reduces After the Server Restart Upon Windows Server 2008 R2 Installation

Problem Description
Table 5-298 Basic information

Item

Information

Source of the Problem

BH622 V2

Intended Product

All servers

Release Date

2013-07-17

Keyword

Windows, virtual memory

Symptom

Hardware configuration

BH622 V2, 64 GB DIMM

Software configuration

Windows Server 2008 R2

Symptom

Windows Server 2008 R2 is installed on the BH622 V2 server. 50 GB is used as the system partition. After installation, the remaining space (more than 500 GB) is used to create drive D. After the system restart, 64 GB of drive D is used, and the used space of drive C is changed from more than 20 GB to 7 GB.

Key Process and Cause Analysis

Cause analysis

A virtual memory whose size is the same as that of the physical memory is configured for Windows Server OS by default. The available space of drive C is less than 64 GB. Therefore, the virtual memory is allocated to drive D.

Conclusion and Solution

Conclusion

The space of drive C is insufficient for the virtual memory. Therefore, Windows Server OS automatically allocates the virtual memory to drive D.

Solution

Change the size of the virtual memory.

Right-click My Computer, choose Properties > Advanced system settings > Advanced, and click Settings under Performance. On the page that is displayed, manually modify the virtual memory configuration.

Experience

None

Note

None

Failed to Install VMWare 6.5 on CH242 V3 DDR4 Equipped with the LSI SAS3108

Problem Description
Table 5-299 Basic information

Item

Information

Source of the Problem

Live network

Intended Product

E9000

Release Date

2018

Keyword

OS installation, VMware, error

Symptom

Symptom

"Unable to read partition table for device" is displayed during the installation of VMWare 6.5 on a CH242 V3 DDR4 equipped with the LSI SAS3108 RAID controller card.

Key Process and Cause Analysis

Problem analysis

The system disk is not initialized. As a result, the system disk cannot be read. You can initialize the system disk on the BIOS to solve the problem.

Conclusion and Solution

Solution

The preliminary check shows that the system disk is not initialized. Perform the initialization as follows:

Rebuild RAID 10.

Move the cursor to RAID ID, press F2, choose Initialization > Fast Init, and press Enter.

After a message is displayed, asking you whether to perform the initialization operation, select Yes.

After the system displays a message indicating that the initialization is complete, select OK.

After the initialization is complete, restart the server and reinstall the OS.

Translation
Download
Updated: 2019-02-25

Document ID: EDOC1000041338

Views: 83430

Downloads: 3893

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next