Install openEuler 22.03 LTS SP3 on an IEI Server
This guide preserves the archived OEM procedure and its example values. Original English screens are retained; translated bitmap labels are English instructional illustrations, not captures from an official English installer. Official English replacement figures can show different example settings, noted beside each image. No operating-system installation or disk operation was performed while preparing this article.
1, Optical Disc Boot
1) Connect the installation drive to the server. Upon powering on, see <F11> to Boot Menu. The feedback shown in the red box of the image below indicates success; wait for the boot menu.
2) Select the USB drive or optical drive to boot (usually displays the brand name of the USB drive or optical drive), then press Enter.
3) After successfully booting the system, the following interface will appear,
4) Press Enter directly on the first item to start installing the system.
2, Basic Settings
1) Select Language: Chinese - Simplified (China) or English, then click the Continue button.
Language selection. This official English example selects English (United States); the OEM source selected Simplified Chinese. Language autonyms in the list are retained as interface data.
2) Click "Continue" to enter the Installation Summary page.
Installation Summary. Official example: root disabled, Minimal Install, automatic partitioning, no network; it does not show a completed installation.
3) Time Zone selection. Once configured, click the "Done (D)" button.
Time & Date. Official example uses Asia/Shanghai, 10:34, 2022-09-22 with network time off; configure the actual date/time and reachable NTP source.
4) Keyboard selection. Click the "+" button to add a new keyboard layout, select the language to add, then click the "Add (A)" button. After adding, click the "Done (D)" button.
Keyboard Layout. Official English example has English (US); the OEM original has Chinese. Use + to add the required layout.
5) Select Installation Source
The Verify button below can check if the disc or image is complete (note that this may take a long time and verification can be skipped).
Installation Source. The official image uses local sr0 and redacts its release label. Use the actual 22.03-LTS-SP3 medium; no proxy credentials are filled.
6) Additional repositories are optional. Use trusted repositories matching openEuler 22.03 LTS SP3 and the intended architecture. The source New_Repository entry has a blank URL, so it is not a working repository definition or proof of an updated installation. Configure only required repositories and choose Done.
, Software Selection
1) Software Selection.
Choose the base environment required for the workload. The shown 22.03 LTS SP3 screen offers Minimal Install, Server and Virtualization Host; it does not show Server with GUI. One source figure selects Server and another selects Minimal Install, each with Development Tools checked. These are alternatives. The source’s all-development-packages and right-click instructions are not mandatory installation requirements. Use only the toolchain and matching development prerequisites needed for a particular source-built driver or application.
4, Partition Settings
1) Automatic partitioning. After selecting automatic, click Done.
Automatic partitioning. Official English example uses a selected 30 GiB ATA VBOX HARDDISK, replacing the OEM example with a 557.75 GiB AVAGO virtual drive and separate USB medium. Identify the actual target; sizes are not recommendations.
A. Manual Partitioning in UEFI Mode
Select the supported partition scheme and create the mount points required for the actual firmware mode and workload. The source prose says Standard Partition and a 200 MB ESP, but its empty editor uses LVM and its later example shows /home 482.16 GiB, / 70 GiB, /boot 1024 MiB, /boot/efi 600 MiB and swap 4 GiB on a 557.75 GiB AVAGO drive. The official replacement illustrates a separate 30 GiB layout, described in its caption. These are examples, not fixed sizing rules. For UEFI use an appropriate EFI System Partition and supported boot layout. Review filesystem types and destructive flags, then Done and Accept Changes as appropriate. Changes are applied after returning to the summary and beginning installation.
After partition creation is complete, click "Done".
Manual partitioning. This official English example uses a 30 GiB virtual disk: /home 4.66 GiB, / 10 GiB, /boot 512 MiB, /boot/efi 512 MiB and swap 14.34 GiB. The OEM example instead shows /home 482.16 GiB, / 70 GiB, /boot 1024 MiB, /boot/efi 600 MiB and swap 4 GiB. These are different illustrative layouts, not one continuous installation or fixed sizing rules.
The Summary of Changes displays the actual proposed destroy/create/format operations; it does not prove that a previous OS existed. The source includes Destroy Format: Unknown and creation of a GPT, EFI System Partition and LVM objects. Cancel if the target or required data is wrong, protect needed data, and confirm only the intended plan. Accept Changes does not mean formatting or installation has completed.
B. The required boot partitions depend on the actual Legacy/UEFI mode and disk partition table. UEFI uses an appropriate ESP mounted at /boot/efi; a BIOS/GPT installation can need a BIOS boot partition instead. Verify the complete supported layout rather than only adding or omitting /boot/efi. The empty source editor also displays an unrelated iso9660 USB label CentOS_7_x86_64 on sdc; that retained source inconsistency does not identify valid openEuler installation media.
5, Network Settings
1) Select the intended connected NIC and configure the actual hostname and addressing. The OEM port list is unplugged and its final summary says Not connected. DHCP needs a working link and reachable DHCP service; merely enabling Ethernet does not guarantee an address. The official enp0s3 illustration is a separate disconnected example.
Network & Host Name. Official example shows a disconnected enp0s3 interface and localhost.localdomain; the OEM example lists ens10f0 and several other ports. Use the actual connected NIC and planned hostname.
2) The OEM IPv4 example uses ens10f0, 192.168.21.11, netmask 255.255.255.0 and gateway 192.168.21.1, with DNS blank. Use values assigned for the actual network and verify link, routing and name resolution.
6, User Settings
Configure the root user password. Here you can choose whether to enable or disable the root user; select according to your needs.
1) Apply the actual installer and organizational password policy. The OEM source lists the following complexity rules; policy enforcement and any override behavior depend on the actual image/settings. The official root form discusses a weak-password confirmation, so the source’s blanket claim that every weak password is impossible to set is too broad. Use an appropriate strong secret locally.
a) Password length must be at least 8 characters.
b) Password must contain at least 3 of the following character types: uppercase letters, lowercase letters, digits, and special characters.
c) Password cannot be the same as the username.
d) Password cannot be a dictionary word.
Root Account. Official English form shows Enable root account selected but an empty password; the OEM original has a masked entered password. Set a compliant secret locally, never copy credentials from a guide.
2) Create a standard user. Password requirements are the same as those for the root user regarding complexity.
Create User. Official example uses openeuler with wheel membership and a masked password rated Good; the OEM source uses ieisystem. Choose an actual intended account and privileges.
7, Start Installation
1) After all configurations are complete as shown below, click Start Installation to begin system installation.
Installation Progress. Official image shows Creating disklabel on /dev/sda, replacing the OEM Setting up installation environment stage; neither is a completion result.
8, Complete Installation
1) Configuration after installation completion
2) Enter the boot interface
3) Log in at the console with the intended account. The supplied example ends at a text login prompt; it does not demonstrate a GUI installation. This does not establish that openEuler can never provide a desktop through another supported package selection or configuration.
English reference and source scope
No corresponding complete English edition of this OEM QA was verified. The official references supply release-specific terminology and suitable English illustrations; they do not certify the pictured OEM hardware/driver combinations. All original sections and working image references are retained, with material source differences explained.