Cannot boot into LXPM after several reboots with RHEL7.3 image mounted - Lenovo ThinkSystem
Cannot boot into LXPM after several reboots with RHEL7.3 image mounted - Lenovo ThinkSystem
Cannot boot into LXPM after several reboots with RHEL7.3 image mounted - Lenovo ThinkSystem
Symptom
Users cannot boot into LXPM after several reboots with RHEL7.3 image mounted.
The issue occurs when users perform the following:
1. Boot into LXPM and change the boot mode to UEFI.
2. Install RHEL7.3 by manual installation and after reboot, press F1 to boot into LXPM again.
2. Repeat the above steps for about five (5) times.
3. After pressing F1 to go into UEFI and click "Launch Graphical System Setup", the system will not respond.
(where LXPM = Lenovo XClarity Provisioning Manager)
Affected Configurations
The system may be any of the following Lenovo servers:
- ThinkSystem SN550, any model 7X16
- ThinkSystem SN850, any model 7X15
- ThinkSystem SR850, any model 7X18, 7X19
- ThinkSystem SR950, any model 7X11, 7X12
- ThinkSystem SR950 (SAP HANA), any model 7X13
- ThinkSystem SD530, any model 7X20
- ThinkSystem SR530, any model 7X07, 7X08
- ThinkSystem SR550, any model 7X03, 7X04
- ThinkSystem SR630, any model 7X01, 7X02
- ThinkSystem SR650, any model 7X05, 7X06
- ThinkSystem ST550, any model 7X09, 7X10
This tip is not software specific.
This tip is not option specific.
The system has the symptom described above.
Solution
This behavior will be corrected in a future release of XCC.
The target date for this release is scheduled for First Quarter 2018.
The file is or will be available by selecting the appropriate Product Group, type of System, Product name, Product machine type, and Operating system on Lenovo Support web page, at the following URL:
http://datacentersupport.lenovo.com/
Workaround
Restart XCC to resolve the issue.
(where XCC = Lenovo XClarity Controller)
Additional Information
This issue can occur when the host system is rebooted while a transfer is in process. Restarting XCC can reset this un-handled condition.
The root cause of this issue is an un-handling condition that occurs when the host is shut down (VDD goes to zero) while the USB device is using DMA to transfer data.
(where VDD = Virtual Disk Drive, DMA = Direct Memory Access)