diff --git a/content/en/docs/Installation/Installation.md b/content/en/docs/Installation/Installation.md index e8ba003d1fec68027108f9d76f0f6d8f2204b4c3..6ce6f6b20da525a6077f0bef45ef3dc0e9700266 100644 --- a/content/en/docs/Installation/Installation.md +++ b/content/en/docs/Installation/Installation.md @@ -1 +1,6 @@ -This document describes how to obtain the openEuler installation package and install openEuler using different methods. \ No newline at end of file +# Installation Guide + +This guide describes how to install Huawei openEuler. + +This guide is intended for openEuler users with a basic understanding of Linux system management, and is also recommended for administrators, system engineers, and maintenance personnel. + diff --git a/content/en/docs/Installation/an-exception-occurs-during-the-selection-of-the-installation-source.md b/content/en/docs/Installation/an-exception-occurs-during-the-selection-of-the-installation-source.md deleted file mode 100644 index 328815ef3c7082b3c470946e61e860632404fb66..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/an-exception-occurs-during-the-selection-of-the-installation-source.md +++ /dev/null @@ -1,14 +0,0 @@ -# An Exception Occurs During the Selection of the Installation Source - -## Symptom - -After the selection of the installation source, the message "Error checking software selection" is displayed. - -## Possible Cause - -This is because the software package dependency in the installation source is abnormal. - -## Solution - -Check whether the installation source is abnormal. Use the new installation source. - diff --git a/content/en/docs/Installation/completing-the-installation.md b/content/en/docs/Installation/completing-the-installation.md deleted file mode 100644 index cfcc1e3682e0c64284d900a96b4e51b48772dcf0..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/completing-the-installation.md +++ /dev/null @@ -1,10 +0,0 @@ -# Completing the Installation - -openEuler has been installed, as shown in [Figure 1](#en-us_topic_0186390267_en-us_topic_0122145917_fig1429512116338). Click **Reboot** to restart the system. - -**Figure 1** Completing the installation -![](figures/completing-the-installation.png "completing-the-installation") - -- If the physical DVD-ROM is used to install the OS and the DVD-ROM drive is not automatically ejected during the restart, manually remove the DVD-ROM. Then, the openEuler CLI login page is displayed. -- If the virtual DVD-ROM drive is used to install the OS, change the server boot option to **Hard Disk** and restart the server. Then, the openEuler CLI login page is displayed. - diff --git a/content/en/docs/Installation/configurations-during-installation.md b/content/en/docs/Installation/configurations-during-installation.md deleted file mode 100644 index f62b1c27634cd62fbaf3f2b9b9c469ab17191271..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/configurations-during-installation.md +++ /dev/null @@ -1,69 +0,0 @@ -# Configurations During Installation - -After the installation starts, the overall installation progress and the progress of writing the software package to the system are displayed. - -**Figure 1** Installation process -![](figures/installation-process.png "installation-process") - -During the process of installing software packages, you need to configure the root password and create users. - -## Password Complexity - -The password of the **root** user or the password of the new user must meet the password complexity requirements. Otherwise, the password configuration or user creation will fail. The password complexity requirements are as follows: - -1. A password must contain at least eight characters. -2. A password must contain at least three of the following types: uppercase letters, lowercase letters, digits, and special characters. -3. A password must be different from the account name. -4. A password cannot contain words in the dictionary. - - Querying a dictionary - - In the installed openEuler environment, you can run the following command to export the dictionary library file **dictionary.txt**, and then check whether the password is in the dictionary. - - ``` - cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt - ``` - - - Modifying a dictionary - 1. Modify the exported dictionary library file, and then run the following command to update the dictionary library: - - ``` - # create-cracklib-dict dictionary.txt - ``` - - 2. Run the following command to add another dictionary file **custom.txt** to the original dictionary library. - - ``` - # create-cracklib-dict dictionary.txt custom.txt - ``` - - - - -## Setting the Root User Password - -Click **Root Password**. In the displayed dialog box, as shown in [Figure 2](#en-us_topic_0186390266_en-us_topic_0122145909_fig1323165793018), enter a password and re-enter to confirm. - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->The root password is required to be configured at the same time of installing software packages. Otherwise, the installation will fail. A **root** account is used for performing critical system administration tasks. It is not recommended to use this account for daily work or system access. - -**Figure 2** Password of the **root** account -![](figures/password-of-the-root-account.png "password-of-the-root-account") - -After configuration, click **Done** in the left-upper corner to switch back to the installation process page. - -## Creating a User - -Click **User Creation**. [Figure 3](#en-us_topic_0186390266_en-us_topic_0122145909_fig1237715313319) shows the page for creating a user. Enter a username and set a password. By clicking **Advanced**, you can also configure a home directory and a user group, as shown in [Figure 4](#en-us_topic_0186390266_en-us_topic_0122145909_fig128716531312). - -**Figure 3** Creating a user -![](figures/creating-a-user.png "creating-a-user") - -**Figure 4** Advanced user configuration -![](figures/advanced-user-configuration.png "advanced-user-configuration") - -After configuration, click **Done** in the left-upper corner to switch back to the installation process page. - -Click **Finish**. The configuration of openEuler is complete. - -![](figures/completing-the-configuration.png) - diff --git a/content/en/docs/Installation/configuring-an-installation-program-language.md b/content/en/docs/Installation/configuring-an-installation-program-language.md deleted file mode 100644 index 3572a51bd3f2625ef226fd5e5d560632f0082cc0..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/configuring-an-installation-program-language.md +++ /dev/null @@ -1,11 +0,0 @@ -# Configuring an Installation Program Language - -After the installation starts, the system will prompt the language that is used during the configuration installation process. English is configured by default, as shown in [Figure 1](#en-us_topic_0186390093_en-us_topic_0122145864_fig144630179151). Configure another language as required. - -**Figure 1** Selecting a language -![](figures/selecting-a-language.png "selecting-a-language") - -After configurations, click **Continue**. The main installation configuration page is displayed. - -If you want to exit the installation, click **Exit**. The message "Are you sure you want to exit the installation program?" is displayed. Click **Yes** in the dialog box to go back to the installation wizard page. - diff --git a/content/en/docs/Installation/en-us_bookmap_0229291255.md b/content/en/docs/Installation/en-us_bookmap_0229291255.md deleted file mode 100644 index 108d1397af810dedf7cb952e3a62eadeb86eebeb..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/en-us_bookmap_0229291255.md +++ /dev/null @@ -1,58 +0,0 @@ -# Installation Guide - -- [Terms of Use](terms-of-use.md) -- [Preface](preface.md) -- [Installation Preparations](installation-preparations.md) - - [Obtaining the Installation Source](obtaining-the-installation-source.md) - - [Release Package Integrity Check](release-package-integrity-check.md) - - [Installation Requirements for PMs](installation-requirements-for-pms.md) - - [Hardware Compatibility](hardware-compatibility.md) - - [Minimum Hardware Specifications](minimum-hardware-specifications.md) - - - [Installation Requirements for VMs](installation-requirements-for-vms.md) - - [Virtualization Platform Compatibility](virtualization-platform-compatibility.md) - - [Minimum Virtualization Space](minimum-virtualization-space.md) - - -- [Installation Mode](installation-mode.md) - - [Installation Through a CD/DVD-ROM](installation-through-a-cd-dvd-rom.md) - - [Installation Through a USB Flash Drive](installation-through-a-usb-flash-drive.md) - - [Installation Through the Network Using PXE](installation-through-the-network-using-pxe.md) - - [Installation Through a QCOW2 Image](installation-through-a-qcow2-image.md) - - [Installation Through a Private Image](installation-through-a-private-image.md) - -- [Installation Guideline](installation-guideline.md) - - [Starting the Installation](starting-the-installation.md) - - [Installation in GUI Mode](installation-in-gui-mode.md) - - [Configuring an Installation Program Language](configuring-an-installation-program-language.md) - - [Entering the Installation Page](entering-the-installation-page.md) - - [Setting Installation Parameters](setting-installation-parameters.md) - - [Setting the Keyboard Layout](setting-the-keyboard-layout.md) - - [Setting a System Language](setting-a-system-language.md) - - [Setting Date and Time](setting-date-and-time.md) - - [Setting the Installation Source](setting-the-installation-source.md) - - [Selecting Installation Software](selecting-installation-software.md) - - [Setting the Installation Destination](setting-the-installation-destination.md) - - [Setting the Network and Host Name](setting-the-network-and-host-name.md) - - - [Starting Installation](starting-installation.md) - - [Configurations During Installation](configurations-during-installation.md) - - [Completing the Installation](completing-the-installation.md) - - -- [Using Kickstart for Automatic Installation](using-kickstart-for-automatic-installation.md) - - [Introduction](introduction.md) - - [Semi-automatic Installation Guide](semi-automatic-installation-guide.md) - - [Full-automatic Installation Guide](full-automatic-installation-guide.md) - -- [FAQs](faqs.md) - - [Why Does openEuler Fail to Start After I Install It to the Second Disk?](why-does-openeuler-fail-to-start-after-i-install-it-to-the-second-disk.md) - - [What Are the Constraints on Network Configurations?](what-are-the-constraints-on-network-configurations.md) - - [Why Does openEuler Enter Emergency Mode After It Is Powered On?](why-does-openeuler-enter-emergency-mode-after-it-is-powered-on.md) - - [Failed to Reinstall openEuler When a Logical Volume Group That Cannot Be Activated Has Existed in openEuler](failed-to-reinstall-openeuler-when-a-logical-volume-group-that-cannot-be-activated-has-existed-in-op.md) - - [An Exception Occurs During the Selection of the Installation Source](an-exception-occurs-during-the-selection-of-the-installation-source.md) - - [How Do I Manually Enable the kdump Service?](how-do-i-manually-enable-the-kdump-service.md) - - [Failed to Selected Only One Disk for Reinstallation When openEuler Was Installed on a Logical Volume Consisting of Multiple Disks](failed-to-selected-only-one-disk-for-reinstallation-when-openeuler-was-installed-on-a-logical-volume.md) - - [Failed to Install openEuler on an x86 PM in UEFI Mode due to Secure Boot Option Setting](failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting.md) - - diff --git a/content/en/docs/Installation/entering-the-installation-page.md b/content/en/docs/Installation/entering-the-installation-page.md deleted file mode 100644 index 0461747a546148e7b48e8a122425f3442a1e3193..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/entering-the-installation-page.md +++ /dev/null @@ -1,11 +0,0 @@ -# Entering the Installation Page - -After the installation program starts, the main installation configuration page is displayed, as shown in [Figure 1](#en-us_topic_0186390094_en-us_topic_0122145883_fig5969171592212). On the page, you can configure the time, language, installation source, network, and storage device. - -Some configuration items are matched with safety symbols. A safety symbol will disappear after the item is configured. Start the installation only when all the safety symbols disappear from the page. - -If you want to exit the installation, click **Exit**. The message "Are you sure you want to exit the installation program?" is displayed. Click **Yes** in the dialog box to go back to the installation wizard page. - -**Figure 1** Installation summary -![](figures/installation-summary.png "installation-summary") - diff --git a/content/en/docs/Installation/failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting.md b/content/en/docs/Installation/failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting.md deleted file mode 100644 index 387bc660e6a9dc4a0c39aa452a7efc8e03ca91bc..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting.md +++ /dev/null @@ -1,33 +0,0 @@ -# Failed to Install openEuler on an x86 PM in UEFI Mode due to Secure Boot Option Setting - -## Symptom - -During the installation of openEuler on an x86 PM in UEFI mode, the system stays at the "No bootable device" page and the installation cannot continue because **secure boot** is set to **enabled** \(by default, it is set to **disabled**\), as shown in [Figure 1](#fig115949762617). - -**Figure 1** Dialog box showing "No bootable device" -![](figures/dialog-box-showing-no-bootable-device.png "dialog-box-showing-no-bootable-device") - -## Possible Cause - -After **secure boot** is set to **enabled**, the mainboard verifies the boot program and OS. If the boot program and OS are not signed using the corresponding private key, the boot program and OS cannot pass the authentication of the built-in public key on the mainboard. - -## Solution - -Access the BIOS, set **secure boot** to **disabled**, and reinstall the openEuler. - -1. During the system startup, press **F11** and enter the password **Admin@9000** to access the BIOS. - - ![](figures/bios.png) - -2. Choose **Administer Secure Boot**. - - ![](figures/security.png) - -3. Set **Enforce Secure Boot** to **Disabled**. - - ![](figures/enforce-secure-boot.png) - - >![](public_sys-resources/icon-note.gif) **NOTE:** - >After **Enforce Secure Boot** is set to **Disabled**, save the settings, and exit. Then, reinstall the system. - - diff --git a/content/en/docs/Installation/failed-to-reinstall-openeuler-when-a-logical-volume-group-that-cannot-be-activated-has-existed-in-op.md b/content/en/docs/Installation/failed-to-reinstall-openeuler-when-a-logical-volume-group-that-cannot-be-activated-has-existed-in-op.md deleted file mode 100644 index 53a2970276e05fec79e4c09c15a11ae1e1f81a48..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/failed-to-reinstall-openeuler-when-a-logical-volume-group-that-cannot-be-activated-has-existed-in-op.md +++ /dev/null @@ -1,48 +0,0 @@ -# Failed to Reinstall openEuler When a Logical Volume Group That Cannot Be Activated Has Existed in openEuler - -## Symptom - -After a disk fails, openEuler fails to be reinstalled because a logical volume group that cannot be activated has existed in openEuler. - -## Possible Cause - -During the installation of openEuler, a logical volume group cannot be activated. - -## Solution - -Before reinstalling openEuler, restore the abnormal logical volume group to the normal status or clear it. The following uses an example: - -- Restore the logical volume group. - 1. Run the following command to clear the active status of the abnormal logical volume group to ensure that the error message "Can't open /dev/sdc exclusively mounted filesystem" is not displayed: - - ``` - vgchange -a n testvg32947 - ``` - - 2. Run the following command to recreate a physical volume based on the backup file: - - ``` - pvcreate --uuid JT7zlL-K5G4-izjB-3i5L-e94f-7yuX-rhkLjL --restorefile /etc/lvm/backup/testvg32947 /dev/sdc - ``` - - 3. Run the following command to restore the logical volume group information: - - ``` - vgcfgrestore testvg32947 - ``` - - 4. Run the following command to reactivate the logical volume group: - - ``` - vgchange -ay testvg32947 - ``` - - -- Run the following commands to clear the logical volume group: - - ``` - vgchange -a n testvg32947 - vgremove -y testvg32947 - ``` - - diff --git a/content/en/docs/Installation/failed-to-selected-only-one-disk-for-reinstallation-when-openeuler-was-installed-on-a-logical-volume.md b/content/en/docs/Installation/failed-to-selected-only-one-disk-for-reinstallation-when-openeuler-was-installed-on-a-logical-volume.md deleted file mode 100644 index 8293b806d32e2a3ecafa31b924712b1abc333dc0..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/failed-to-selected-only-one-disk-for-reinstallation-when-openeuler-was-installed-on-a-logical-volume.md +++ /dev/null @@ -1,41 +0,0 @@ -# Failed to Selected Only One Disk for Reinstallation When openEuler Was Installed on a Logical Volume Consisting of Multiple Disks - -## Symptom - -If openEuler was installed on a logical volume consisting of multiple disks, an error message will be displayed as shown in [Figure 1](#fig115949762617) when you attempt to select one of the disks for reinstallation. - -**Figure 1** Error message -![](figures/error-message.png "error-message") - -## Possible Cause - -The previous logical volume contains multiple disks. If you select one of the disks for reinstallation, the logical volume will be damaged. - -## Solution - -The logical volume formed by multiple disks is equivalent to a volume group. Therefore, you only need to delete the corresponding volume group. - -1. Press **Ctrl**+**Alt**+**F2** to switch to the CLI and run the following command to find the volume group: - - ``` - vgs - ``` - - ![](figures/en-us_image_0231657950.png) - -2. Run the following command to delete the volume group: - - ``` - vgremove euleros - ``` - -3. Run the following command to restart the installation program for the modification to take effect: - - ``` - systemctl restart anaconda - ``` - - >![](public_sys-resources/icon-note.gif) **NOTE:** - >You can also press **Ctrl**+**Alt**+**F6** to return to the GUI and click **Refresh** in the lower right corner to refresh the storage configuration. - - diff --git a/content/en/docs/Installation/faqs.md b/content/en/docs/Installation/faqs.md index 0427b4be98990a3fd2153eccdfcb484d41dd4cb2..d32e37f7997bdc2821539ed1c98d300d5b99545a 100644 --- a/content/en/docs/Installation/faqs.md +++ b/content/en/docs/Installation/faqs.md @@ -1,3 +1,324 @@ -# FAQs +# FAQs + +- [FAQs](#faqs) + - [Why Does openEuler Fail to Start After I Install It to the Second Disk?](#why-does-openeuler-fail-to-start-after-i-install-it-to-the-second-disk) + - [What Are the Constraints on Network Configurations?](#what-are-the-constraints-on-network-configurations) + - [Why Does openEuler Enter Emergency Mode After It Is Powered On?](#why-does-openeuler-enter-emergency-mode-after-it-is-powered-on) + - [Failed to Reinstall openEuler When a Logical Volume Group That Cannot Be Activated Has Existed in openEuler](#failed-to-reinstall-openeuler-when-a-logical-volume-group-that-cannot-be-activated-has-existed-in-openeuler) + - [An Exception Occurs During the Selection of the Installation Source](#an-exception-occurs-during-the-selection-of-the-installation-source) + - [How Do I Manually Enable the kdump Service?](#how-do-i-manually-enable-the-kdump-service) + - [Failed to Selected Only One Disk for Reinstallation When openEuler Was Installed on a Logical Volume Consisting of Multiple Disks](#failed-to-selected-only-one-disk-for-reinstallation-when-openeuler-was-installed-on-a-logical-volume-consisting-of-multiple-disks) + - [Failed to Install openEuler on an x86 PM in UEFI Mode due to Secure Boot Option Setting](#failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting) + + +## Why Does openEuler Fail to Start After I Install It to the Second Disk? + +### Symptom + +The OS is installed on the second disk **sdb** during the installation. The openEuler fails to be started. + +### Possible Cause + +When openEuler is installed to the second disk, MBR and GRUB are installed to the second disk **sdb** by default. The following two situations may occur: + +1. openEuler installed on the first disk is loaded and started if it is complete. +2. openEuler installed on the first disk fails to be started from hard disks if it is incomplete. + +The preceding two situations occur because the first disk **sda** is booted by default to start openEuler on the BIOS window. If openEuler is not installed on the **sda** disk, system restart fails. + +### Solution + +This problem can be solved using either of the following two methods: + +- During the installation of openEuler, select the first disk or both disks, and install the boot loader on the first disk **sda**. +- After installing openEuler, restart it by modifying the boot option on the BIOS window. + +## What Are the Constraints on Network Configurations? + +The NetworkManager and network services are network service management tools. Some functions of the two services overlap. + +- If the NetworkManager service is used, run the **nmcli** command or modify the configuration file to configure the network \(such as the IP address and route\). Do not run the **ip**, **ifconfig**, or **route** command to configure the network. + + >![](public_sys-resources/icon-note.gif) **NOTE:** + >When the NetworkManager service is enabled and you run commands such as **ip**, **ifconfig**, and **route** to configure the network, the configurations will be overwritten by NetworkManager. + + To check whether NetworkManager is enabled, run the following command: + + ``` + systemctl status NetworkManager + ``` + + >![](public_sys-resources/icon-note.gif) **NOTE:** + >For details about the use of the **nmcli** command, see the execution result of the **nmcli --help** or **man nmcli** command. + +- If you want to run commands such as **ip**, **ifconfig**, and **route** commands to manage network information, run the following command to disable the NetworkManager service: + + ``` + systemctl stop NetworkManager + ``` + + +## Why Does openEuler Enter Emergency Mode After It Is Powered On? + +### Symptom + +openEuler enters emergency mode after it is powered on. + +![](figures/en-us_image_0229291264.jpg) + +### Possible Causes + +Damaged OS files result in disk mounting failure, or overpressured I/O results in disk mounting timeout \(threshold: 90s\). + +An unexpected system power-off, and low I/O performance of disks may also cause the problem. + +### Solution + +1. Enter the password of the **root** account to log in to openEuler. +2. Check and restore files by using the file system check \(fsck\) tool, and restart openEuler. + + >![](public_sys-resources/icon-note.gif) **NOTE:** + >The fsck tool checks and maintains inconsistent file systems. If the system is powered off or a disk is faulty, run the **fsck** command to check file systems. Run the **fsck.ext3 -h** and **fsck.ext4 -h** commands to view the usage method of the fsck tool. + + +If you want to disable the timeout mechanism of disk mounting, add **x-systemd.device-timeout=0** to the **etc/fstab** file. For example: + +``` +# +# /etc/fstab +# Created by anaconda on Mon Sep 14 17:25:48 2015 +# +# Accessible filesystems, by reference, are maintained under '/dev/disk' +# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info +# +/dev/mapper/openEuler-root / ext4 defaults,x-systemd.device-timeout=0 0 0 +UUID=afcc811f-4b20-42fc-9d31-7307a8cfe0df /boot ext4 defaults,x-systemd.device-timeout=0 0 0 +/dev/mapper/openEuler-home /home ext4 defaults 0 0 +/dev/mapper/openEuler-swap swap swap defaults 0 0 +``` + +## Failed to Reinstall openEuler When a Logical Volume Group That Cannot Be Activated Has Existed in openEuler + +### Symptom + +After a disk fails, openEuler fails to be reinstalled because a logical volume group that cannot be activated has existed in openEuler. + +### Possible Cause + +During the installation of openEuler, a logical volume group cannot be activated. + +### Solution + +Before reinstalling openEuler, restore the abnormal logical volume group to the normal status or clear it. The following uses an example: + +- Restore the logical volume group. + 1. Run the following command to clear the active status of the abnormal logical volume group to ensure that the error message "Can't open /dev/sdc exclusively mounted filesystem" is not displayed: + + ``` + vgchange -a n testvg32947 + ``` + + 2. Run the following command to recreate a physical volume based on the backup file: + + ``` + pvcreate --uuid JT7zlL-K5G4-izjB-3i5L-e94f-7yuX-rhkLjL --restorefile /etc/lvm/backup/testvg32947 /dev/sdc + ``` + + 3. Run the following command to restore the logical volume group information: + + ``` + vgcfgrestore testvg32947 + ``` + + 4. Run the following command to reactivate the logical volume group: + + ``` + vgchange -ay testvg32947 + ``` + + +- Run the following commands to clear the logical volume group: + + ``` + vgchange -a n testvg32947 + vgremove -y testvg32947 + ``` + + +## An Exception Occurs During the Selection of the Installation Source + +### Symptom + +After the selection of the installation source, the message "Error checking software selection" is displayed. + +### Possible Cause + +This is because the software package dependency in the installation source is abnormal. + +### Solution + +Check whether the installation source is abnormal. Use the new installation source. + +## How Do I Manually Enable the kdump Service? + +### Symptom + +Run the **systemctl status kdump** command. The following information is displayed, indicating that no memory is reserved. + +![](figures/en-us_image_0229291280.png) + +### Possible Cause + +The kdump service requires the system to reserve memory for running the kdump kernel. However, the system does not reserve memory for the kdump service. As a result, the kdump service cannot be started. + +### Solution + +For the scenario where the OS has been installed + +1. Add **crashkernel=1024M,high** to **/boot/efi/EFI/openEuler/grub.cfg**. +2. Restart the system for configuration to take effect. +3. Run the following command to check the kdump status: + + ``` + systemctl status kdump + ``` + + If the following information is displayed, the kdump status is **active**, indicating that the kdump service is enabled. No further action is required. + + ![](figures/en-us_image_0229291272.png) + + +### Parameter Description + +The following table describes the parameters of the memory reserved for the kdump kernel. + +**Table 1** crashkernel parameters + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Kernel Boot Parameter

+

Description

+

Default Value

+

Remarks

+

crashkernel=X

+

Reserve X of the physical memory for kdump when the physical memory is less than 4 GB.

+

None. You can adjust the value as required.

+

This configuration method is used only when the memory is less than 4 GB. Ensure that the continuous available memory is sufficient.

+

crashkernel=X@Y

+

Reserve X of the memory at the start address Y for kdump.

+

None. You can adjust the value as required.

+

Ensure that the X of the memory at the start address Y is not reserved for other modules.

+

crashkernel=X,high

+

Reserve 256 MB of the physical memory for kdump when the physical memory is less than 4 GB, and X of the physical memory for kdump when the physical memory is greater than or equal to 4 GB.

+

None. You can adjust the value based as required. The recommended value is 1024M,high.

+

Ensure that 256 MB of the memory is reserved for continuous use when the physical memory is less than 4 GB and X of the memory is reserved when the physical memory is greater than or equal to 4 GB. The actual reserved memory size equals 256 MB plus X.

+

crashkernel=X,low

+

crashkernel=Y,high

+

Reserve X of the physical memory for kdump when the physical memory is less than 4 GB and Y of the physical memory for kdump when the physical memory is greater than or equal to 4 GB.

+

None. You can adjust the value as required.

+

Ensure that X of the memory is reserved for continuous use when the physical memory is less than 4 GB and Y of the memory is reserved when the physical memory is greater than or equal to 4 GB. The actual reserved memory size equals X plus Y.

+
+ +## Failed to Selected Only One Disk for Reinstallation When openEuler Was Installed on a Logical Volume Consisting of Multiple Disks + +### Symptom + +If openEuler was installed on a logical volume consisting of multiple disks, an error message will be displayed as shown in [Figure 1](#fig115949762617) when you attempt to select one of the disks for reinstallation. + +**Figure 1** Error message +![](figures/error-message.png "error-message") + +### Possible Cause + +The previous logical volume contains multiple disks. If you select one of the disks for reinstallation, the logical volume will be damaged. + +### Solution + +The logical volume formed by multiple disks is equivalent to a volume group. Therefore, you only need to delete the corresponding volume group. + +1. Press **Ctrl**+**Alt**+**F2** to switch to the CLI and run the following command to find the volume group: + + ``` + vgs + ``` + + ![](figures/en-us_image_0231657950.png) + +2. Run the following command to delete the volume group: + + ``` + vgremove euleros + ``` + +3. Run the following command to restart the installation program for the modification to take effect: + + ``` + systemctl restart anaconda + ``` + + >![](public_sys-resources/icon-note.gif) **NOTE:** + >You can also press **Ctrl**+**Alt**+**F6** to return to the GUI and click **Refresh** in the lower right corner to refresh the storage configuration. + + +## Failed to Install openEuler on an x86 PM in UEFI Mode due to Secure Boot Option Setting + +### Symptom + +During the installation of openEuler on an x86 PM in UEFI mode, the system stays at the "No bootable device" page and the installation cannot continue because **secure boot** is set to **enabled** \(by default, it is set to **disabled**\), as shown in [Figure 2](#fig115949762617). + +**Figure 2** Dialog box showing "No bootable device" +![](figures/dialog-box-showing-no-bootable-device.png "dialog-box-showing-no-bootable-device") + +### Possible Cause + +After **secure boot** is set to **enabled**, the mainboard verifies the boot program and OS. If the boot program and OS are not signed using the corresponding private key, the boot program and OS cannot pass the authentication of the built-in public key on the mainboard. + +### Solution + +Access the BIOS, set **secure boot** to **disabled**, and reinstall the openEuler. + +1. During the system startup, press **F11** and enter the password **Admin@9000** to access the BIOS. + + ![](figures/bios.png) + +2. Choose **Administer Secure Boot**. + + ![](figures/security.png) + +3. Set **Enforce Secure Boot** to **Disabled**. + + ![](figures/enforce-secure-boot.png) + + >![](public_sys-resources/icon-note.gif) **NOTE:** + >After **Enforce Secure Boot** is set to **Disabled**, save the settings, and exit. Then, reinstall the system. + + + \ No newline at end of file diff --git a/content/en/docs/Installation/full-automatic-installation-guide.md b/content/en/docs/Installation/full-automatic-installation-guide.md deleted file mode 100644 index 35b133041d9a1898ce5fe7850223c0ee34c82ae9..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/full-automatic-installation-guide.md +++ /dev/null @@ -1,174 +0,0 @@ -# Full-automatic Installation Guide - -## Environment Requirements - -The environment requirements for full-automatic installation of openEuler using kickstart are as follows: - -- PM/VM \(for details about how to create VMs, see the documents from corresponding vendors\): includes the computer where kickstart is used for automatic installation and the computer where the kickstart tool is installed. -- Httpd: stores the kickstart file. -- TFTP: provides vmlinuz and initrd files. -- DHCPD/PXE: provides the DHCP service. -- ISO: openEuler-20.03-LTS-aarch64-dvd.iso - -## Procedure - -To use kickstart to perform full-automatic installation of openEuler, perform the following steps: - -**Environment Preparation** - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->Before the installation, ensure that the firewall of the HTTP server is disabled. Run the following command to disable the firewall: ->``` ->iptables -F ->``` - -1. Install httpd and start the service. - - ``` - # dnf install httpd -y - # systemctl start httpd - # systemctl enable httpd - ``` - -2. Install and configure TFTP. - - ``` - # dnf install tftp-server -y - # vim /etc/xinetd.d/tftp - service tftp - { - socket_type = dgram - protocol = udp - wait = yes - user = root - server = /usr/sbin/in.tftpd - server_args = -s /var/lib/tftpboot - disable = no - per_source = 11 - cps = 100 2 - flags = IPv4 - } - # systemctl start tftp - # systemctl enable tftp - # systemctl start xinetd - # systemctl status xinetd - # systemctl enable xinetd - ``` - -3. Run the following commands to prepare the installation source: - - ``` - # mount openEuler-20.03-LTS-aarch64-dvd.iso /mnt - # cp -r /mnt/* /var/www/html/openEuler/ - ``` - -4. Set and modify the kickstart configuration file **openEuler-ks.cfg**. Select the HTTP installation source by referring to [\#EN-US\_TOPIC\_0229291289/l1692f6b9284e493683ffa2ef804bc7ca](#l1692f6b9284e493683ffa2ef804bc7ca). - - ``` - #vim /var/www/html/ks/openEuler-ks.cfg - ==================================== - ***Modify the following information as required.*** - #version=DEVEL - ignoredisk --only-use=sda - autopart --type=lvm - # Partition clearing information - clearpart --none --initlabel - # Use graphical install - graphical - # Keyboard layouts - keyboard --vckeymap=cn --xlayouts='cn' - # System language - lang zh_CN.UTF-8 - #Use http installation source - url --url=//192.168.122.1/openEuler/ - %post - #enable kdump - sed -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg - %end - ... - ``` - -5. Modify the PXE configuration file **grub.cfg** as follows: - - ``` - # cp -r /mnt/images/pxeboot/* /var/lib/tftpboot/ - # cp /mnt/EFI/BOOT/grubaa64.efi /var/lib/tftpboot/ - # cp /mnt/EFI/BOOT/grub.cfg /var/lib/tftpboot/ - # ls /var/lib/tftpboot/ - grubaa64.efi grub.cfg initrd.img TRANS.TBL vmlinuz - # vim /var/lib/tftpboot/grub.cfg - set default="1" - - function load_video { - if [ x$feature_all_video_module = xy ]; then - insmod all_video - else - insmod efi_gop - insmod efi_uga - insmod ieee1275_fb - insmod vbe - insmod vga - insmod video_bochs - insmod video_cirrus - fi - } - - load_video - set gfxpayload=keep - insmod gzio - insmod part_gpt - insmod ext2 - - set timeout=60 - - - ### BEGIN /etc/grub.d/10_linux ### - menuentry 'Install openEuler 20.03 LTS' --class red --class gnu-linux --class gnu --class os { - set root=(tftp,192.168.1.1) - linux /vmlinuz ro inst.geoloc=0 console=ttyAMA0 console=tty0 rd.iscsi.waitnet=0 inst.ks=http://192.168.122.1/ks/openEuler-ks.cfg - initrd /initrd.img - } - ``` - -6. Run the following commands to configure DHCP \(which can be replaced by DNSmasq\): - - ``` - # dnf install dhcp -y - # - # DHCP Server Configuration file. - # see /usr/share/doc/dhcp-server/dhcpd.conf.example - # see dhcpd.conf(5) man page - # - # vim /etc/dhcp/dhcpd.conf - ddns-update-style interim; - ignore client-updates; - filename "grubaa64.efi"; # pxelinux location of the startup file; - next-server 192.168.122.1; # (IMPORTANT) TFTP server IP address; - subnet 192.168.122.0 netmask 255.255.255.0 { - option routers 192.168.111.1; # Gateway address - option subnet-mask 255.255.255.0; # Subnet mask - range dynamic-bootp 192.168.122.50 192.168.122.200; # Dynamic IP address range - default-lease-time 21600; - max-lease-time 43200; - } - # systemctl start dhcpd - # systemctl enable dhcpd - ``` - - -**Installing the System** - -1. On the **Start boot option** screen, press **F2** to boot from the PXE and start automatic installation. - - ![](figures/en-us_image_0229291270.png) - - ![](figures/en-us_image_0229291286.png) - - ![](figures/en-us_image_0229291247.png) - -2. The automatic installation window is displayed. -3. Verify that the installation is complete. - - ![](figures/completing-the-automatic-installation.png) - - diff --git a/content/en/docs/Installation/hardware-compatibility.md b/content/en/docs/Installation/hardware-compatibility.md deleted file mode 100644 index fd7b18d96fc7489f4196c5bad5f6132fd76385a2..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/hardware-compatibility.md +++ /dev/null @@ -1,38 +0,0 @@ -# Hardware Compatibility - -You need to take hardware compatibility into account during openEuler installation. [Table 1](#table14948632047) describes the types of supported servers. - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->- TaiShan 200 servers are backed by Huawei Kunpeng 920 processors. ->- Currently, only Huawei TaiShan and FusionServer Pro servers are supported. More servers from other vendors will be supported in the future. - -**Table 1** Supported servers - - - - - - - - - - - - - - - - -

Server Type

-

Server Name

-

Server Model

-

Rack server

-

TaiShan 200

-

2280 balanced model

-

Rack server

-

FusionServer Pro

-

FusionServer Pro 2288H V5

-
NOTE:

The server must be configured with the Avago SAS3508 RAID controller card and the LOM-X722 NIC.

-
-
- diff --git a/content/en/docs/Installation/how-do-i-manually-enable-the-kdump-service.md b/content/en/docs/Installation/how-do-i-manually-enable-the-kdump-service.md deleted file mode 100644 index 9ff29e80c335deb12644f2da198674cfe5c11635..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/how-do-i-manually-enable-the-kdump-service.md +++ /dev/null @@ -1,86 +0,0 @@ -# How Do I Manually Enable the kdump Service? - -## Symptom - -Run the **systemctl status kdump** command. The following information is displayed, indicating that no memory is reserved. - -![](figures/en-us_image_0229291280.png) - -## Possible Cause - -The kdump service requires the system to reserve memory for running the kdump kernel. However, the system does not reserve memory for the kdump service. As a result, the kdump service cannot be started. - -## Solution - -For the scenario where the OS has been installed - -1. Add **crashkernel=1024M,high** to **/boot/efi/EFI/openEuler/grub.cfg**. -2. Restart the system for configuration to take effect. -3. Run the following command to check the kdump status: - - ``` - systemctl status kdump - ``` - - If the following information is displayed, the kdump status is **active**, indicating that the kdump service is enabled. No further action is required. - - ![](figures/en-us_image_0229291272.png) - - -## Parameter Description - -The following table describes the parameters of the memory reserved for the kdump kernel. - -**Table 1** crashkernel parameters - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Kernel Boot Parameter

-

Description

-

Default Value

-

Remarks

-

crashkernel=X

-

Reserve X of the physical memory for kdump when the physical memory is less than 4 GB.

-

None. You can adjust the value as required.

-

This configuration method is used only when the memory is less than 4 GB. Ensure that the continuous available memory is sufficient.

-

crashkernel=X@Y

-

Reserve X of the memory at the start address Y for kdump.

-

None. You can adjust the value as required.

-

Ensure that the X of the memory at the start address Y is not reserved for other modules.

-

crashkernel=X,high

-

Reserve 256 MB of the physical memory for kdump when the physical memory is less than 4 GB, and X of the physical memory for kdump when the physical memory is greater than or equal to 4 GB.

-

None. You can adjust the value based as required. The recommended value is 1024M,high.

-

Ensure that 256 MB of the memory is reserved for continuous use when the physical memory is less than 4 GB and X of the memory is reserved when the physical memory is greater than or equal to 4 GB. The actual reserved memory size equals 256 MB plus X.

-

crashkernel=X,low

-

crashkernel=Y,high

-

Reserve X of the physical memory for kdump when the physical memory is less than 4 GB and Y of the physical memory for kdump when the physical memory is greater than or equal to 4 GB.

-

None. You can adjust the value as required.

-

Ensure that X of the memory is reserved for continuous use when the physical memory is less than 4 GB and Y of the memory is reserved when the physical memory is greater than or equal to 4 GB. The actual reserved memory size equals X plus Y.

-
- diff --git a/content/en/docs/Installation/installation-guideline.md b/content/en/docs/Installation/installation-guideline.md index 7677e6c1aff35f54e759ef01346b085b83c55ce8..7f0f68ec04c1c48c29d42a408953fe9fcf1be734 100644 --- a/content/en/docs/Installation/installation-guideline.md +++ b/content/en/docs/Installation/installation-guideline.md @@ -1,5 +1,331 @@ -# Installation Guideline +# Installation Guideline This section describes how to install openEuler using a CD-ROM. The installation process is the same for other installation modes except the boot option. + +- [Installation Guideline](#installation-guideline) + - [Starting the Installation](#starting-the-installation) + - [Booting from the CD/DVD-ROM Drive](#booting-from-the-cddvd-rom-drive) + - [Installation Wizard](#installation-wizard) + - [Installation in GUI Mode](#installation-in-gui-mode) + - [Configuring an Installation Program Language](#configuring-an-installation-program-language) + - [Entering the Installation Page](#entering-the-installation-page) + - [Setting the Keyboard Layout](#setting-the-keyboard-layout) + - [Setting a System Language](#setting-a-system-language) + - [Setting Date and Time](#setting-date-and-time) + - [Setting the Installation Source](#setting-the-installation-source) + - [Selecting Installation Software](#selecting-installation-software) + - [Setting the Installation Destination](#setting-the-installation-destination) + - [Storage Configuration](#storage-configuration) + - [Setting the Network and Host Name](#setting-the-network-and-host-name) + - [Starting Installation](#starting-installation) + - [Configurations During Installation](#configurations-during-installation) + - [Password Complexity](#password-complexity) + - [Setting the Root User Password](#setting-the-root-user-password) + - [Creating a User](#creating-a-user) + - [Completing the Installation](#completing-the-installation) + + +## Starting the Installation + +### Booting from the CD/DVD-ROM Drive + +Load the ISO image of openEuler from the CD/DVD-ROM drive of the server and restart the server. The procedure is as follows: + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>Before the installation, ensure that the server boots from the CD/DVD-ROM drive preferentially. The following steps describe how to install the openEuler using the virtual CD/DVD-ROM drive on the baseboard management controller \(BMC\). Installing the openEuler from a physical drive is simple. After the installation starts, the procedure for the physical drive is the same as that of the virtual drive. + +1. On the toolbar, click the icon shown in the following figure. + + **Figure 1** Drive icon + ![](figures/drive-icon.png "drive-icon") + + An image dialog box is displayed, as shown in the following figure. + + **Figure 2** Image dialog box + ![](figures/image-dialog-box.png "image-dialog-box") + +2. Select **Image File** and then click **Browse**. The **Open** dialog box is displayed. +3. Select the image file and click **Open**. In the image dialog box, click **Connect**. If **Connect** changes to **Disconnect**, the virtual CD/DVD-ROM drive is connected to the server. +4. On the toolbar, click the restart icon shown in the following figure to restart the device. + + **Figure 3** Restart icon + ![](figures/restart-icon.png "restart-icon") + + +### Installation Wizard + +A boot menu is displayed after the system is booted using the boot medium. In addition to options for starting the installation program, some other options are available on the boot menu. During system installation, the **Test this media & install openEuler 20.03 LTS** mode is used by default. Press the arrow keys on the keyboard to change the selection, and press **Enter** when the desired option is highlighted. + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>- If you do not perform any operations within 1 minute, the system automatically selects the default option **Test this media & install openEuler 20.03 LTS** and enters the installation page. +>- During PM installation, if you cannot use the arrow keys to select boot options and the system does not respond after you press **Enter**, click ![](figures/en-us_image_0229420473.png) on the BMC page and configure **Key & Mouse Reset**. + +**Figure 4** Installation Wizard +![](figures/installation-wizard.png "installation-wizard") + +Installation wizard options are described as follows: + +- **Install openEuler 20.03 LTS**: Install openEuler on your server in GUI mode. + +- **Test this media & install openEuler 20.03 LTS**: Default option. Install openEuler on your server in GUI mode. The integrity of the installation medium is checked before the installation program is started. + +- **Troubleshooting**: Troubleshooting mode, which is used when the system cannot be installed properly. In troubleshooting mode, the following options are available: + - **Install openEuler 20.03-LTS in basic graphics mode**: Basic graphics installation mode. In this mode, the video driver is not started before the system starts and runs. + - **Rescue the openEuler system**: Rescue mode, which is used to restore the system. In rescue mode, the installation process is printed in the VNC or BMC, and the serial port is unavailable. + +On the installation wizard screen, press **e** to go to the parameter editing screen of the selected option, and press **c** to go to the command-line interface \(CLI\). + +### Installation in GUI Mode + +On the installation wizard page, select **Test this media & install openEuler 20.03 LTS** to enter the GUI installation mode. + +Perform graphical installation operations using a keyboard. + +- Press **Tab** or **Shift**+**Tab** to move between GUI controls \(such as buttons, area boxes, and check boxes\). +- Press the up or down arrow key to move a target in the list. +- Press the left or right arrow key to move between the horizontal toolbar and watch bar. +- Press the spacebar or **Enter** to select or delete highlighted options, expand or collapse a drop-down list. +- Press **Alt**+a shortcut key \(the shortcut key varies for different pages\) to select the control where the shortcut key is located. The shortcut key can be highlighted \(underlined\) by holding down Alt. + + +## Configuring an Installation Program Language + +After the installation starts, the system will prompt the language that is used during the configuration installation process. English is configured by default, as shown in [Figure 5](#en-us_topic_0186390093_en-us_topic_0122145864_fig144630179151). Configure another language as required. + +**Figure 5** Selecting a language +![](figures/selecting-a-language.png "selecting-a-language") + +After configurations, click **Continue**. The main installation configuration page is displayed. + +If you want to exit the installation, click **Exit**. The message "Are you sure you want to exit the installation program?" is displayed. Click **Yes** in the dialog box to go back to the installation wizard page. + +## Entering the Installation Page + +After the installation program starts, the main installation configuration page is displayed, as shown in [Figure 6](#en-us_topic_0186390094_en-us_topic_0122145883_fig5969171592212). On the page, you can configure the time, language, installation source, network, and storage device. + +Some configuration items are matched with safety symbols. A safety symbol will disappear after the item is configured. Start the installation only when all the safety symbols disappear from the page. + +If you want to exit the installation, click **Exit**. The message "Are you sure you want to exit the installation program?" is displayed. Click **Yes** in the dialog box to go back to the installation wizard page. + +**Figure 6** Installation summary +![](figures/installation-summary.png "installation-summary") + +## Setting the Keyboard Layout + +On the **INSTALLATION SUMMARY** page, click **KEYBOARD**. You can add or delete multiple keyboard layouts in the system. + +- On the left white box, click to select the keyboard layout and click the keyboard under the box. +- To test the keyboard layout: On the left white box, click to select the keyboard layout, click the inside of the right text box, and enter the text to ensure that the keyboard layout can work properly. + +**Figure 7** Setting the keyboard layout +![](figures/setting-the-keyboard-layout.png "setting-the-keyboard-layout") + +After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. + +## Setting a System Language + +On the **INSTALLATION SUMMARY** page, click **LANGUAGE SUPPORT** to set the system language, as shown in [Figure 8](#en-us_topic_0186390098_en-us_topic_0122145772_fig187301927172619). Set another language as required, such as Chinese. + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>- If you select Chinese, the system does not display Chinese characters after you log in to the system using VNC, because VNC does not support Chinese characters. If you log in to the system in SSH mode, Chinese characters will be displayed. +>- If you select English, there will be no impact. + +**Figure 8** Setting a system language +![](figures/setting-a-system-language.png "setting-a-system-language") + +After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. + +## Setting Date and Time + +On the **INSTALLATION SUMMARY** page, click **TIME & DATE**. On the **TIME & DATE** page, set the system time zone, date, and time. + +When setting the time zone, you can click a specific city on the map with the mouse, or select a region from the drop-down list of **Region** or a city from the drop-down list of **City** at the top of the page, as shown in [Figure 9](#en-us_topic_0186390096_en-us_topic_0122145900_fig1260162652312). + +If your city is not displayed on the map or in the drop-down list, select the nearest city in the same time zone. + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>- Before manually setting the time zone, disable the network time synchronization function in the upper right corner. +>- If you want to use the network time, ensure that the network can connect to the remote NTP server. For details about how to set the network, see [Setting the Network and Host Name](#setting-the-network-and-host-name). + +**Figure 9** Setting date and time +![](figures/setting-date-and-time.png "setting-date-and-time") + +After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. + +## Setting the Installation Source + +On the **INSTALLATION SUMMARY** page, click **INSTALLATION SOURCE** to locate the installation source. + +If you use a CD/DVD-ROM for installation, the installation program automatically detects and displays the installation source information. You can use the default settings. [Figure 10](#en-us_topic_0186390100_en-us_topic_0144427079_fig93633295132) shows an example. + +**Figure 10** Setting the installation source +![](figures/setting-the-installation-source.png "setting-the-installation-source") + +When you use the network for installation, if the HTTPS server uses a private certificate, press **e** on the installation wizard page to go to the parameter editing page and add the **inst.noverifyssl** parameter, as shown in [Figure 11](#fig113517811415). + +**Figure 11** Adding the **inst.noverifyssl** parameter +![](figures/adding-the-inst-noverifyssl-parameter.png "adding-the-inst-noverifyssl-parameter") + +After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>During the installation, if you have any questions about configuring the installation source, see [An Exception Occurs During the Selection of the Installation Source](faqs.html#an-exception-occurs-during-the-selection-of-the-installation-source). + +## Selecting Installation Software + +On the **INSTALLATION SUMMARY** page, click **SOFTWARE SELECTION** to specify the software package to be installed. + +Based on the actual requirements, select **Minimal Install** on the left box and select an add-on in the **Add-Ons for Selected Environment** area on the right, as shown in [Figure 12](#en-us_topic_0186390261_en-us_topic_0122145865_fig03031519101414). + +**Figure 12** Selecting installation software +![](figures/selecting-installation-software.png "selecting-installation-software") + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>- In **Minimal Install** mode, not all packages in the installation source will be installed. If the required package is not installed, you can mount the installation source to the local PC and configure a repo source, and use DNF to install the package. +>- If you select **Virtual Host**, the virtualization components QEMU, libvirt, and edk2 are installed by default. You can select whether to install the OVS component in the add-on area. + +After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. + +## Setting the Installation Destination + +On the **INSTALLATION SUMMARY** page, click **INSTALLATION DESTINATION** to select the OS installation disk and partition. + +You can view available local storage devices in [Figure 13](#fig1195417125015). You can also add an attached device or a network disk specified by clicking **Add a disk**. + +>![](public_sys-resources/icon-notice.gif) **NOTICE:** +>When selecting the device to be installed, you are advised not to use the NVMe SSD storage medium as the OS installation disk. + +**Figure 13** Setting the installation destination +![](figures/setting-the-installation-destination.png "setting-the-installation-destination") + +### Storage Configuration + +On the **INSTALLATION DESTINATION** page, configure storage for system partition. You can either manually configure partitions or select **Automatic** to automatically configure partitioning. + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>- During partitioning, to ensure system security and performance, you are advised to divide the device into the following partitions: **/boot**, **/var**, **/var/log**, **/var/log/audit**, **/home**, and **/tmp**. +>- If the system is configured with the swap partition, the swap partition is used when the physical memory of the system is insufficient. Although the swap partition can be used to expand the physical memory, if the swap partition is used due to insufficient memory, the system response slows and the system performance deteriorates. Therefore, you are not advised to configure the swap partition in the system with sufficient physical memory or the performance sensitive system. +>- If you need to split a logical volume group, select **Custom** to manually partition the logical volume group. On the **MANUAL PARTITIONING** page, click **Modify** in the **Volume Group** area to reconfigure the logical volume group. + +**Automatic** + +Select **Automatic** if the software is installed in a new storage device or the data in the storage device is not required. + +**Customize** + +If you need to manually partition the disk, click **Customize** and click **Done** in the upper left corner. The following page is displayed. + +**Figure 14** MANUAL PARTITIONING page +![](figures/manual-partitioning-page.png "manual-partitioning-page") + +On the **MANUAL PARTITIONING** page, you can partition the disk in either of the following ways: + +- Automatic creation: Click **Click here to create them automatically**. The system automatically assigns four mount points according to the available storage space: **/boot**, **/**, **/boot/efi**, and **swap**. +- Manual creation: Click ![](figures/en-us_image_0229291243.png) to add a mount point. It is recommended that the expected capacity of each mount point not exceed the available space. + + >![](public_sys-resources/icon-note.gif) **NOTE:** + >If the expected capacity of the mount point exceeds the available space, the system allocates the remaining available space to the mount point. + + +After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. + +## Setting the Network and Host Name + +On the **INSTALLATION SUMMARY** page, select **NETWORK & HOST NAME** to configure the system network functions. + +The installation program automatically detects a local access interface. The detected interface is listed in the left box, and the interface details are displayed in the right-hand area, as shown in [Figure 15](#en-us_topic_0186390264_en-us_topic_0122145831_fig123700157297). In the upper right corner, click the switchover button to enable or disable the network interface. You can also click **Configure** to configure the selected interface. + +In the lower left box, enter the host name. The host name can be the fully quantified domain name \(FQDN\) in the format of hostname.domainname or the brief host name in the format of hostname. + +**Figure 15** Setting the network and host name +![](figures/setting-the-network-and-host-name.png "setting-the-network-and-host-name") + +After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. + +## Starting Installation + +On the installation page, after all the mandatory items are configured, the safety symbols will disappear. Then, you can click **Begin Installation** to install the system. + +**Figure 16** Starting installation +![](figures/starting-installation.png "starting-installation") + +## Configurations During Installation + +After the installation starts, the overall installation progress and the progress of writing the software package to the system are displayed. + +**Figure 17** Installation process +![](figures/installation-process.png "installation-process") + +During the process of installing software packages, you need to configure the root password and create users. + +### Password Complexity + +The password of the **root** user or the password of the new user must meet the password complexity requirements. Otherwise, the password configuration or user creation will fail. The password complexity requirements are as follows: + +1. A password must contain at least eight characters. +2. A password must contain at least three of the following types: uppercase letters, lowercase letters, digits, and special characters. +3. A password must be different from the account name. +4. A password cannot contain words in the dictionary. + - Querying a dictionary + + In the installed openEuler environment, you can run the following command to export the dictionary library file **dictionary.txt**, and then check whether the password is in the dictionary. + + ``` + cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt + ``` + + - Modifying a dictionary + 1. Modify the exported dictionary library file, and then run the following command to update the dictionary library: + + ``` + # create-cracklib-dict dictionary.txt + ``` + + 2. Run the following command to add another dictionary file **custom.txt** to the original dictionary library. + + ``` + # create-cracklib-dict dictionary.txt custom.txt + ``` + + + + +### Setting the Root User Password + +Click **Root Password**. In the displayed dialog box, as shown in [Figure 18](#en-us_topic_0186390266_en-us_topic_0122145909_fig1323165793018), enter a password and re-enter to confirm. + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>The root password is required to be configured at the same time of installing software packages. Otherwise, the installation will fail. A **root** account is used for performing critical system administration tasks. It is not recommended to use this account for daily work or system access. + +**Figure 18** Password of the **root** account +![](figures/password-of-the-root-account.png "password-of-the-root-account") + +After configuration, click **Done** in the left-upper corner to switch back to the installation process page. + +### Creating a User + +Click **User Creation**. [Figure 19](#en-us_topic_0186390266_en-us_topic_0122145909_fig1237715313319) shows the page for creating a user. Enter a username and set a password. By clicking **Advanced**, you can also configure a home directory and a user group, as shown in [Figure 20](#en-us_topic_0186390266_en-us_topic_0122145909_fig128716531312). + +**Figure 19** Creating a user +![](figures/creating-a-user.png "creating-a-user") + +**Figure 20** Advanced user configuration +![](figures/advanced-user-configuration.png "advanced-user-configuration") + +After configuration, click **Done** in the left-upper corner to switch back to the installation process page. + +Click **Finish**. The configuration of openEuler is complete. + +![](figures/completing-the-configuration.png) + +## Completing the Installation + +openEuler has been installed, as shown in [Figure 21](#en-us_topic_0186390267_en-us_topic_0122145917_fig1429512116338). Click **Reboot** to restart the system. + +**Figure 21** Completing the installation +![](figures/completing-the-installation.png "completing-the-installation") + +- If the physical DVD-ROM is used to install the OS and the DVD-ROM drive is not automatically ejected during the restart, manually remove the DVD-ROM. Then, the openEuler CLI login page is displayed. +- If the virtual DVD-ROM drive is used to install the OS, change the server boot option to **Hard Disk** and restart the server. Then, the openEuler CLI login page is displayed. diff --git a/content/en/docs/Installation/installation-in-gui-mode.md b/content/en/docs/Installation/installation-in-gui-mode.md deleted file mode 100644 index b66996800ecbe7c040d885bc887d6e32f4d1c0b7..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/installation-in-gui-mode.md +++ /dev/null @@ -1,14 +0,0 @@ -# Installation in GUI Mode - -On the installation wizard page, select **Test this media & install openEuler 20.03 LTS** to enter the GUI installation mode. - -Perform graphical installation operations using a keyboard. - -- Press **Tab** or **Shift**+**Tab** to move between GUI controls \(such as buttons, area boxes, and check boxes\). -- Press the up or down arrow key to move a target in the list. -- Press the left or right arrow key to move between the horizontal toolbar and watch bar. -- Press the spacebar or **Enter** to select or delete highlighted options, expand or collapse a drop-down list. -- Press **Alt**+a shortcut key \(the shortcut key varies for different pages\) to select the control where the shortcut key is located. The shortcut key can be highlighted \(underlined\) by holding down Alt. - - - diff --git a/content/en/docs/Installation/installation-mode.md b/content/en/docs/Installation/installation-mode.md index c86b2e8520a56a349ed73896445b7c35e095bf0f..5ffc390d7cfff37936055c7501f89a63908270f8 100644 --- a/content/en/docs/Installation/installation-mode.md +++ b/content/en/docs/Installation/installation-mode.md @@ -1,18 +1,37 @@ -# Installation Mode +# Installation Mode >![](public_sys-resources/icon-notice.gif) **NOTICE:** ->- Only TaiShan 200 and FusionServer Pro servers are supported. For details about the supported server models, see [Installation Preparations](installation-preparations.html). Only a virtualization platform created by the virtualization components \(openEuler as the host OS and QEMU and KVM provided in the release package\) of openEuler and the x86 virtualization platform of Huawei public cloud are supported. ->- Currently, only installation modes such as CD-ROM, USB flash drive, network, QCOW2 image, and private image are supported. In addition, only the x86 virtualization platform of Huawei public cloud supports the private image installation mode. - -## Installation Through a CD/DVD-ROM +>- Only TaiShan 200 and FusionServer Pro servers are supported. For details about the supported server models, see [Hardware Compatibility](installation-preparations.html#hardware-compatibility). Only a virtualization platform created by the virtualization components \(openEuler as the host OS and QEMU and KVM provided in the release package\) of openEuler and the x86 virtualization platform of Huawei public cloud are supported. +>- Currently, only installation modes such as CD-ROM, USB flash drive, network, QCOW2 image, and private image are supported. In addition, only the x86 virtualization platform of Huawei public cloud supports the private image installation mode. + + + +- [Installation Mode](#installation-mode) + - [Installation Through a CD/DVD-ROM](#installation-through-a-cddvd-rom) + - [Preparing the Installation Source](#preparing-the-installation-source) + - [Starting the Installation](#starting-the-installation) + - [Installation Through a USB Flash Drive](#installation-through-a-usb-flash-drive) + - [Preparing the Installation Source](#preparing-the-installation-source-1) + - [Starting the Installation](#starting-the-installation-1) + - [Installation Through the Network Using PXE](#installation-through-the-network-using-pxe) + - [Installation Through a QCOW2 Image](#installation-through-a-qcow2-image) + - [Creating a QCOW2 Image](#creating-a-qcow2-image) + - [Starting the Installation](#starting-the-installation-2) + - [Installation Through a Private Image](#installation-through-a-private-image) + - [Creating a Private Image](#creating-a-private-image) + - [Starting the Installation](#starting-the-installation-3) + + + +## Installation Through a CD/DVD-ROM This section describes how to create or use a CD/DVD-ROM to install the openEuler. -### Preparing the Installation Source +### Preparing the Installation Source If you have obtained a CD/DVD-ROM, install the OS using the CD/DVD-ROM. If you have obtained an ISO file, record the ISO file to a DVD and install the OS using the obtained DVD. -### Starting the Installation +### Starting the Installation Perform the following operations to start the installation: @@ -26,11 +45,11 @@ Perform the following operations to start the installation: After a short delay, a graphical wizard page is displayed, which contains different boot options. If you do not perform any operation within one minute, the installation starts automatically with the default options. -## Installation Through a USB Flash Drive +## Installation Through a USB Flash Drive This section describes how to create or use a USB flash drive to install the openEuler. -### Preparing the Installation Source +### Preparing the Installation Source Pay attention to the capacity of the USB flash drive. The USB flash drive must have sufficient space to store the entire image. It is recommended that the USB flash drive has more than 16 GB space. @@ -90,7 +109,7 @@ Pay attention to the capacity of the USB flash drive. The USB flash drive must h No progress is displayed during the image write process. When the number sign \(\#\) appears again, the write is complete. Exit the **root** account and remove the USB flash drive. In this case, you can use the USB flash drive as the installation source of the system. -### Starting the Installation +### Starting the Installation Perform the following operations to start the installation: @@ -104,7 +123,7 @@ Perform the following operations to start the installation: After a short delay, a graphical wizard page is displayed, which contains different boot options. If you do not perform any operation within one minute, the installation program automatically starts the installation. -## Installation Through the Network Using PXE +## Installation Through the Network Using PXE To boot with PXE, you need to properly configure the server and your computer's network interface to support PXE. @@ -113,13 +132,13 @@ If the target hardware is installed with a PXE-enabled NIC, we can configure it For installation through the network using PXE, the client uses a PXE-enabled NIC to send a broadcast request for DHCP information and IP address to the network. The DHCP server provides the client with an IP address and other network information, such as the IP address or host name of the DNS and FTP server \(which provides the files required for starting the installation program\), and the location of the files on the server. >![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** ->The TFTP, DHCP, and HTTP server configurations are not described here. For details, see [Full-automatic Installation Guide](full-automatic-installation-guide.html). +>The TFTP, DHCP, and HTTP server configurations are not described here. For details, see [Full-automatic Installation Guide](using-kickstart-for-automatic-installation.html#full-automatic-installation-guide). -## Installation Through a QCOW2 Image +## Installation Through a QCOW2 Image This section describes how to create or use a QCOW2 image to install the openEuler. -### Creating a QCOW2 Image +### Creating a QCOW2 Image 1. Install the **qemu-img** software package. @@ -148,7 +167,7 @@ This section describes how to create or use a QCOW2 image to install the openEul ``` -### Starting the Installation +### Starting the Installation Perform the following operations to start the installation: @@ -161,15 +180,15 @@ Perform the following operations to start the installation: For details, see the [*openEuler 20.03 LTS Virtualization User Guide*](../Virtualization/virtualization.html). -## Installation Through a Private Image +## Installation Through a Private Image This section describes how to create or use a private image to install the openEuler. -### Creating a Private Image +### Creating a Private Image For instructions about how to create a private image, see [*Image Management Service User Guide*](https://support.huaweicloud.com/intl/en-us/usermanual-ims/en-us_topic_0013901628.html). -### Starting the Installation +### Starting the Installation For details about how to start the x86 virtualization platform of Huawei public cloud, see [Elastic Cloud Server User Guide](https://support.huaweicloud.com/intl/en-us/wtsnew-ims/index.html). diff --git a/content/en/docs/Installation/installation-preparations.md b/content/en/docs/Installation/installation-preparations.md index 60cf2b33c2605c66d54bbba43c69227f799299e9..2efbc181826ec7ad44ccdf616e47ad72fbfba334 100644 --- a/content/en/docs/Installation/installation-preparations.md +++ b/content/en/docs/Installation/installation-preparations.md @@ -1,8 +1,25 @@ -# Installation Preparations +# Installation Preparations This section describes the compatibility of the hardware and software and the related configurations and preparations required for the installation. -## Obtaining the Installation Source + + +- [Installation Preparations](#installation-preparations) + - [Obtaining the Installation Source](#obtaining-the-installation-source) + - [Release Package Integrity Check](#release-package-integrity-check) + - [Introduction](#introduction) + - [Prerequisites](#prerequisites) + - [Procedure](#procedure) + - [Installation Requirements for PMs](#installation-requirements-for-pms) + - [Hardware Compatibility](#hardware-compatibility) + - [Minimum Hardware Specifications](#minimum-hardware-specifications) + - [Installation Requirements for VMs](#installation-requirements-for-vms) + - [Virtualization Platform Compatibility](#virtualization-platform-compatibility) + - [Minimum Virtualization Space](#minimum-virtualization-space) + + + +## Obtaining the Installation Source Obtain the openEuler release package and verification file before the installation. @@ -28,18 +45,18 @@ Perform the following operations to obtain the openEuler release package: 2. Click **openEuler-20.03-LTS-x86\_64-dvd.iso** to download the openEuler release package to the local host. 3. Click **openEuler-20.03-LTS-x86\_64-dvd.iso.sha256sum** to download the openEuler verification file to the local host. -## Release Package Integrity Check +## Release Package Integrity Check >![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** >This section describes how to verify the integrity of the release package in the AArch64 architecture. The procedure for verifying the integrity of the release package in the x86\_64 architecture is the same. -### Introduction +### Introduction To prevent the software package from being incompletely downloaded due to network or storage device faults during transmission, you need to verify the integrity of the software package after obtaining it. Only the software packages that pass the verification can be installed. Compare the verification value recorded in the verification file with the .iso file verification value calculated manually to check whether the software package passes the verification. If the verification values are consistent, the .iso file is not damaged. If they are inconsistent, you can confirm that the file is damaged and you need to obtain the file again. -### Prerequisites +### Prerequisites Before verifying the integrity of the release package, you need to prepare the following files: @@ -47,7 +64,7 @@ ISO file: **openEuler-20.03-LTS-aarch64-dvd.iso** Verification file: **openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum** -### Procedure +### Procedure To verify the file integrity, perform the following operations: @@ -69,11 +86,11 @@ To verify the file integrity, perform the following operations: If the verification values are consistent, the .iso file is not damaged. If they are inconsistent, you can confirm that the file is damaged and you need to obtain the file again. -## Installation Requirements for PMs +## Installation Requirements for PMs To install the openEuler OS on a PM, the PM must meet the following hardware compatibility and minimum hardware requirements. -### Hardware Compatibility +### Hardware Compatibility You need to take hardware compatibility into account during openEuler installation. [Table 1](#table14948632047) describes the types of supported servers. @@ -113,7 +130,7 @@ You need to take hardware compatibility into account during openEuler installati -### Minimum Hardware Specifications +### Minimum Hardware Specifications [Table 2](#tff48b99c9bf24b84bb602c53229e2541) lists the minimum hardware specifications supported by openEuler. @@ -160,18 +177,18 @@ You need to take hardware compatibility into account during openEuler installati -## Installation Requirements for VMs +## Installation Requirements for VMs To install the openEuler OS on a VM, the VM must meet the following hardware compatibility and minimum hardware requirements. -### Virtualization Platform Compatibility +### Virtualization Platform Compatibility When installing openEuler, pay attention to the compatibility of the virtualization platform. Currently, the following virtualization platforms are supported: - A virtualization platform created by the virtualization components \(openEuler as the host OS and QEMU and KVM provided in the release package\) of openEuler - x86 virtualization platform of Huawei public cloud -### Minimum Virtualization Space +### Minimum Virtualization Space [Table 3](#tff48b99c9bf24b84bb602c53229e2541) lists the minimum virtualization space required by openEuler. diff --git a/content/en/docs/Installation/installation-requirements-for-pms.md b/content/en/docs/Installation/installation-requirements-for-pms.md deleted file mode 100644 index e180fa6838ed6d4b01db473f24f605235ab8af81..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/installation-requirements-for-pms.md +++ /dev/null @@ -1,5 +0,0 @@ -# Installation Requirements for PMs - -To install the openEuler OS on a PM, the PM must meet the following hardware compatibility and minimum hardware requirements. - - diff --git a/content/en/docs/Installation/installation-requirements-for-vms.md b/content/en/docs/Installation/installation-requirements-for-vms.md deleted file mode 100644 index f8de391cdd98130393da07dcbac976dc4c2bdcbe..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/installation-requirements-for-vms.md +++ /dev/null @@ -1,6 +0,0 @@ -# Installation Requirements for VMs - -To install the openEuler OS on a VM, the VM must meet the following hardware compatibility and minimum hardware requirements. - - - diff --git a/content/en/docs/Installation/installation-through-a-cd-dvd-rom.md b/content/en/docs/Installation/installation-through-a-cd-dvd-rom.md deleted file mode 100644 index 440bb8634837511789ba7e894dad6da8d885c0b5..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/installation-through-a-cd-dvd-rom.md +++ /dev/null @@ -1,22 +0,0 @@ -# Installation Through a CD/DVD-ROM - -This section describes how to create or use a CD/DVD-ROM to install the openEuler. - -## Preparing the Installation Source - -If you have obtained a CD/DVD-ROM, install the OS using the CD/DVD-ROM. If you have obtained an ISO file, record the ISO file to a DVD and install the OS using the obtained DVD. - -## Starting the Installation - -Perform the following operations to start the installation: - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->Set the system to preferentially boot from the CD/DVD-ROM drive. Take the BIOS as an example. You need to move the **CD/DVD-ROM Drive** option under **Boot Type Order** to the top. - -1. Disconnect all drives that are not required, such as USB drives. -2. Start your computer system. -3. Insert the installation CD/DVD-ROM into the CD/DVD-ROM drive. -4. Restart the computer system. - -After a short delay, a graphical wizard page is displayed, which contains different boot options. If you do not perform any operation within one minute, the installation starts automatically with the default options. - diff --git a/content/en/docs/Installation/installation-through-a-private-image.md b/content/en/docs/Installation/installation-through-a-private-image.md deleted file mode 100644 index 99f69fd172a1e4c69781b42273f58c1a455ccdd8..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/installation-through-a-private-image.md +++ /dev/null @@ -1,12 +0,0 @@ -# Installation Through a Private Image - -This section describes how to create or use a private image to install the openEuler. - -## Creating a Private Image - -For instructions about how to create a private image, see _[Image Management Service User Guide](https://support.huaweicloud.com/usermanual-ims/en-us_topic_0013901628.html)_. - -## Starting the Installation - -For details about how to start the x86 virtualization platform of Huawei public cloud, see [Elastic Cloud Server User Guide](https://support.huaweicloud.com/intl/en-us/wtsnew-ims/index.html). - diff --git a/content/en/docs/Installation/installation-through-a-qcow2-image.md b/content/en/docs/Installation/installation-through-a-qcow2-image.md deleted file mode 100644 index 520bfd78dc3b0f2ee8bdbd5cab7dd93708c2726e..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/installation-through-a-qcow2-image.md +++ /dev/null @@ -1,46 +0,0 @@ -# Installation Through a QCOW2 Image - -This section describes how to create or use a QCOW2 image to install the openEuler. - -## Creating a QCOW2 Image - -1. Install the **qemu-img** software package. - - ``` - # dnf install -y qemu-img - ``` - -2. Run the **create** command of the qemu-img tool to create an image file. The command format is as follows: - - ``` - $ qemu-img create -f -o - ``` - - The parameters are described as follows: - - - _imgFormat_: Image format. The value can be **raw** or **qcow2**. - - _fileOption_: File option, which is used to set features of an image file, such as specifying a backend image file, compression, and encryption. - - _fileName_: File name. - - _diskSize_: Disk size, which specifies the size of a block disk. The unit can be K, M, G, or T, indicating KiB, MiB, GiB, or TiB. - - For example, to create an image file **openEuler-imge.qcow2** whose disk size is 32 GB and format is qcow2, the command and output are as follows: - - ``` - $ qemu-img create -f qcow2 openEuler-image.qcow2 32G - Formatting 'openEuler-image.qcow2', fmt=qcow2 size=34359738368 cluster_size=65536 lazy_refcounts=off refcount_bits=16 - ``` - - -## Starting the Installation - -Perform the following operations to start the installation: - -1. Prepare a QCOW2 image file. -2. Prepare the VM network. -3. Prepare the UEFI boot tool set EDK II. -4. Prepare the VM XML configuration file. -5. Create a VM. -6. Start the VM. - -For details, see the _openEuler 20.03 LTS Virtualization User Guide_. - diff --git a/content/en/docs/Installation/installation-through-a-usb-flash-drive.md b/content/en/docs/Installation/installation-through-a-usb-flash-drive.md deleted file mode 100644 index 9d0e076fef29c74f0941ce75b0bc1dc973e857a0..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/installation-through-a-usb-flash-drive.md +++ /dev/null @@ -1,77 +0,0 @@ -# Installation Through a USB Flash Drive - -This section describes how to create or use a USB flash drive to install the openEuler. - -## Preparing the Installation Source - -Pay attention to the capacity of the USB flash drive. The USB flash drive must have sufficient space to store the entire image. It is recommended that the USB flash drive has more than 16 GB space. - -1. Connect the USB flash drive to the system and run the **dmesg** command to view related log. At the end of the log, you can view the information generated by the USB flash drive that is just connected. The information is similar to the following: - - ``` - [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk - ``` - - >![](public_sys-resources/icon-note.gif) **NOTE:** - >Take the **sdb** USB flash drive as an example. - -2. Switch to user **root**. When running the **su** command, you need to enter the password. - - ``` - $ su - root - ``` - -3. Ensure that the USB flash drive is not mounted. Run the following command: - - ``` - # findmnt /dev/sdb - ``` - - - If no command output is displayed, the file system is not mounted. Go to the next step. - - If the following information is displayed, the USB flash drive is automatically mounted. - - ``` - # findmnt /dev/sdb - TARGET SOURCE FSTYPE OPTIONS - /mnt/iso /dev/sdb iso9660 ro,relatime - ``` - - In this case, you need to run the **umount** command to uninstall the device. - - ``` - # umount /mnt/iso - ``` - -4. Run the **dd** command to write the ISO image to the USB flash drive. - - ``` - # dd if=/path/to/image.iso of=/dev/device bs=blocksize - ``` - - Replace **/path/to/image.iso** with the complete path of the downloaded ISO image file, replace **device** with the device name provided by the **dmesg** command, and set a proper block size \(for example, 512 KB\) to replace **blocksize** to accelerate the write progress. - - For example, if the ISO image file name is **/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso** and the detected device name is **sdb**, run the following command: - - ``` - # dd if=/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso of=/dev/sdb bs=512k - ``` - -5. After the image is written, remove the USB flash drive. - - No progress is displayed during the image write process. When the number sign \(\#\) appears again, the write is complete. Exit the **root** account and remove the USB flash drive. In this case, you can use the USB flash drive as the installation source of the system. - - -## Starting the Installation - -Perform the following operations to start the installation: - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->Set the system to preferentially boot from the USB flash drive. Take the BIOS as an example. You need to move the **USB** option under **Boot Type Order** to the top. - -1. Disconnect all drives that are not required. -2. Open your computer system. -3. Insert the USB flash drive into the computer. -4. Restart the computer system. - -After a short delay, a graphical wizard page is displayed, which contains different boot options. If you do not perform any operation within one minute, the installation program automatically starts the installation. - diff --git a/content/en/docs/Installation/installation-through-the-network-using-pxe.md b/content/en/docs/Installation/installation-through-the-network-using-pxe.md deleted file mode 100644 index 519894ed6829f6726386fe693b98ab8addc83ae2..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/installation-through-the-network-using-pxe.md +++ /dev/null @@ -1,11 +0,0 @@ -# Installation Through the Network Using PXE - -To boot with PXE, you need to properly configure the server and your computer's network interface to support PXE. - -If the target hardware is installed with a PXE-enabled NIC, we can configure it to boot the computer from network system files rather than local media \(such as CD-ROMs\) and execute the Anaconda installation program. - -For installation through the network using PXE, the client uses a PXE-enabled NIC to send a broadcast request for DHCP information and IP address to the network. The DHCP server provides the client with an IP address and other network information, such as the IP address or host name of the DNS and FTP server \(which provides the files required for starting the installation program\), and the location of the files on the server. - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->The TFTP, DHCP, and HTTP server configurations are not described here. For details, see [Full-automatic Installation Guide](full-automatic-installation-guide.md). - diff --git a/content/en/docs/Installation/introduction.md b/content/en/docs/Installation/introduction.md deleted file mode 100644 index 782fcd27c4fd1ac8744268470bddc07f792ecdef..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/introduction.md +++ /dev/null @@ -1,57 +0,0 @@ -# Introduction - -## Overview - -You can use the kickstart tool to automatically install the openEuler OS in either of the following ways: - -- Semi-automatic installation: You only need to specify the location of the kickstart file. Kickstart automatically configures OS attributes such as keyboard, language, and partitions. -- Automatic installation: The OS is automatically installed. - -## Advantages and Disadvantages - -[Table 1](#table1388812373315) lists the advantages and disadvantages of semi-automatic installation and full-automatic installation using kickstart. You can select an installation mode as required. - -**Table 1** Advantages and disadvantages - - - - - - - - - - - - - - - - -

Installation Mode

-

Advantage

-

Disadvantage

-

Semi-automatic installation

-

Services such as TFTP, PXE, and DHCP do not need to be prepared.

-

You need to manually specify the path of the kickstart file.

-

Full-automatic installation

-

The OS is installed automatically.

-

Services, such as TFTP, DHCPD, and PXE, need to be configured.

-
- -## Background - -**Kickstart** - -Kickstart is an unattended installation mode. The principle of kickstart is to record typical parameters that need to be manually entered during the installation and generate the configuration file **ks.cfg**. During the installation, the installation program searches the **ks.cfg** configuration file first for required parameters. If no matching parameters are found, you need to manually configure these parameters. If all required parameters are covered by the kickstart file, automatic installation can be achieved by only specifying the path of the kickstart file. - -Both full-automatic or semi-automatic installation can be achieved by kickstart. - -**PXE** - -Pre-boot Execution Environment \(PXE\)\) works in client/server network mode. The PXE client can obtain an IP address from the DHCP server during the startup and implement client boot and installation through the network based on protocols such as trivial file transfer protocol \(TFTP\). - -**TFTP** - -TFTP is used to transfer simple and trivial files between clients and the server. - diff --git a/content/en/docs/Installation/minimum-hardware-specifications.md b/content/en/docs/Installation/minimum-hardware-specifications.md deleted file mode 100644 index 041ca8efde420403959d0f90b0999ba2f382a28e..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/minimum-hardware-specifications.md +++ /dev/null @@ -1,46 +0,0 @@ -# Minimum Hardware Specifications - -[Table 1](#tff48b99c9bf24b84bb602c53229e2541) lists the minimum hardware specifications supported by openEuler. - -**Table 1** Minimum hardware specifications - - - - - - - - - - - - - - - - - - - - - - - - -

Component

-

Minimum Hardware Specifications

-

Description

-

Architecture

-
  • AArch64
  • x86_64
-
  • 64-bit Arm architecture
  • 64-bit Intel x86 architecture
-

CPU

-
  • Huawei Kunpeng 920 series
  • Intel ® Xeon® processor
-

-

-

Memory

-

≥ 4 GB (8 GB or higher recommended for better user experience)

-

-

-

Hard disk

-

≥ 120 GB (for better user experience)

-

The hard disk supports IDE, SATA, SAS interfaces.

-
- diff --git a/content/en/docs/Installation/minimum-virtualization-space.md b/content/en/docs/Installation/minimum-virtualization-space.md deleted file mode 100644 index e1e2c96afb3b7421f86cc0bdc76f677705bf016b..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/minimum-virtualization-space.md +++ /dev/null @@ -1,46 +0,0 @@ -# Minimum Virtualization Space - -[Table 1](#tff48b99c9bf24b84bb602c53229e2541) lists the minimum virtualization space required by openEuler. - -**Table 1** Minimum virtualization space - - - - - - - - - - - - - - - - - - - - - - - - -

Component

-

Minimum Virtualization Space

-

Description

-

Architecture

-
  • AArch64
  • x86_64
-

-

-

CPU

-

Two CPUs

-

-

-

Memory

-

≥ 4 GB (8 GB or higher recommended for better user experience)

-

-

-

Hard disk

-

≥ 32 GB (120 GB or higher recommended for better user experience)

-

-

-
- diff --git a/content/en/docs/Installation/obtaining-the-installation-source.md b/content/en/docs/Installation/obtaining-the-installation-source.md deleted file mode 100644 index e2191b1bbb21b0c99ebbcdff57c7b6fa71e91194..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/obtaining-the-installation-source.md +++ /dev/null @@ -1,28 +0,0 @@ -# Obtaining the Installation Source - -Obtain the openEuler release package and verification file before the installation. - -Perform the following operations to obtain the openEuler release package: - -1. Log in to the [openEuler Community](https://openeuler.org) website. -2. Click **Download**. -3. Click the link provided after **Download ISO**. The download list is displayed. -4. Click **openEuler-20.03-LTS**. The openEuler 20.03 LTS version download list is displayed. -5. Click **ISO**. The ISO download list is displayed. - - **aarch64**: ISO image file of the AArch64 architecture - - **x86\_64**: ISO image file of the x86\_64 architecture - - **source**: ISO image file of the openEuler source code - -6. Select the openEuler release package and verification file to be downloaded based on the architecture of the environment to be installed. - - If the AArch64 architecture is used: - 1. Click **aarch64**. - 2. Click **openEuler-20.03-LTS-aarch64-dvd.iso** to download the openEuler release package to the local host. - 3. Click **openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum** to download the openEuler verification file to the local host. - - - If the x86\_64 architecture is used: - 1. Click **x86\_64**. - 2. Click **openEuler-20.03-LTS-x86\_64-dvd.iso** to download the openEuler release package to the local host. - 3. Click **openEuler-20.03-LTS-x86\_64-dvd.iso.sha256sum** to download the openEuler verification file to the local host. - - - diff --git a/content/en/docs/Installation/preface.md b/content/en/docs/Installation/preface.md deleted file mode 100644 index 03cc2c90e93274d502d832ff5ade118ef633640b..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/preface.md +++ /dev/null @@ -1,36 +0,0 @@ -# Preface - -## Overview - -This guide describes how to install Huawei openEuler. - -## Intended Audience - -This guide is intended for openEuler users with a basic understanding of Linux system management, and is also recommended for administrators, system engineers, and maintenance personnel. - -## Symbol Conventions - -The symbols that may be found in this document are defined as follows. - - - - - - - - - - - - - -

Symbol

-

Description

-

-

Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results.

-

NOTICE is used to address practices not related to personal injury.

-

-

Supplements the important information in the main text.

-

NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.

-
- diff --git a/content/en/docs/Installation/release-package-integrity-check.md b/content/en/docs/Installation/release-package-integrity-check.md deleted file mode 100644 index 5b6050f3f8caa5fdb535ee10ea739fcfa04d0467..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/release-package-integrity-check.md +++ /dev/null @@ -1,42 +0,0 @@ -# Release Package Integrity Check - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->This section describes how to verify the integrity of the release package in the AArch64 architecture. The procedure for verifying the integrity of the release package in the x86\_64 architecture is the same. - -## Introduction - -To prevent the software package from being incompletely downloaded due to network or storage device faults during transmission, you need to verify the integrity of the software package after obtaining it. Only the software packages that pass the verification can be installed. - -Compare the verification value recorded in the verification file with the .iso file verification value calculated manually to check whether the software package passes the verification. If the verification values are consistent, the .iso file is not damaged. If they are inconsistent, you can confirm that the file is damaged and you need to obtain the file again. - -## Prerequisites - -Before verifying the integrity of the release package, you need to prepare the following files: - -ISO file: **openEuler-20.03-LTS-aarch64-dvd.iso** - -Verification file: **openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum** - -## Procedure - -To verify the file integrity, perform the following operations: - -1. Obtain the verification value in the verification file. Run the following command: - - ``` - #cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum - ``` - -2. Calculate the SHA256 verification value of the file. Run the following command: - - ``` - #sha256sum openEuler-20.03-LTS-aarch64-dvd.iso - ``` - - After the command is run, the verification value is displayed. - -3. Check whether the values calculated in step 1 and step 2 are consistent. - - If the verification values are consistent, the .iso file is not damaged. If they are inconsistent, you can confirm that the file is damaged and you need to obtain the file again. - - diff --git a/content/en/docs/Installation/selecting-installation-software.md b/content/en/docs/Installation/selecting-installation-software.md deleted file mode 100644 index 03fd96b05cf180566708183a0085a6929c3daf6b..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/selecting-installation-software.md +++ /dev/null @@ -1,15 +0,0 @@ -# Selecting Installation Software - -On the **INSTALLATION SUMMARY** page, click **SOFTWARE SELECTION** to specify the software package to be installed. - -Based on the actual requirements, select **Minimal Install** on the left box and select an add-on in the **Add-Ons for Selected Environment** area on the right, as shown in [Figure 1](#en-us_topic_0186390261_en-us_topic_0122145865_fig03031519101414). - -**Figure 1** Selecting installation software -![](figures/selecting-installation-software.png "selecting-installation-software") - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->- In **Minimal Install** mode, not all packages in the installation source will be installed. If the required package is not installed, you can mount the installation source to the local PC and configure a repo source, and use DNF to install the package. ->- If you select **Virtual Host**, the virtualization components QEMU, libvirt, and edk2 are installed by default. You can select whether to install the OVS component in the add-on area. - -After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. - diff --git a/content/en/docs/Installation/semi-automatic-installation-guide.md b/content/en/docs/Installation/semi-automatic-installation-guide.md deleted file mode 100644 index 25d61eda782b294f17a1841903582f10e5a625bb..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/semi-automatic-installation-guide.md +++ /dev/null @@ -1,117 +0,0 @@ -# Semi-automatic Installation Guide - -## Environment Requirements - -The environment requirements for semi-automatic installation of openEuler using kickstart are as follows: - -- PM/VM \(for details about how to create VMs, see the documents from corresponding vendors\): includes the computer where kickstart is used for automatic installation and the computer where the kickstart tool is installed. -- Httpd: stores the kickstart file. -- ISO: openEuler-20.03-LTS-aarch64-dvd.iso - -## Procedure - -To use kickstart to perform semi-automatic installation of openEuler, perform the following steps: - -**Environment Preparation** - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->Before the installation, ensure that the firewall of the HTTP server is disabled. Run the following command to disable the firewall: ->``` ->iptables -F ->``` - -1. Install httpd and start the service. - - ``` - # dnf install httpd -y - # systemctl start httpd - # systemctl enable httpd - ``` - -2. Run the following commands to prepare the kickstart file: - - ``` - # mkdir /var/www/html/ks - #vim /var/www/html/ks/openEuler-ks.cfg ===>The file can be obtained by modifying the anaconda-ks.cfg file automatically generated from openEuler, or can be created using the system-config-kickstart tool. - ==================================== - ***Modify the following information as required.*** - #version=DEVEL - ignoredisk --only-use=sda - autopart --type=lvm - # Partition clearing information - clearpart --none --initlabel - # Use graphical install - graphical - # Use CDROM installation media - cdrom - # Keyboard layouts - keyboard --vckeymap=cn --xlayouts='cn' - # System language - lang zh_CN.UTF-8 - - # Network information - network --bootproto=dhcp --device=enp4s0 --ipv6=auto --activate - network --hostname=openeuler.com - # Root password - rootpw --iscrypted $6$fQE83lxEZ48Or4zc$j7/PlUMHn29yTjCD4Fi44WTZL/RzVGxJ/7MGsZMl6QfE3KjIVT7M4UrhFXbafvRq2lUddAFcyWHd5WRmXfEK20 - # Run the Setup Agent on first boot - firstboot --enable - # Do not configure the X Window System - skipx - # System services - services --disabled="chronyd" - # System timezone - timezone Asia/Shanghai --isUtc--nontp - - %packages - @^minimal-environment - @standard - - %end - - %anaconda - pwpolicy root --minlen=8 --minquality=1 --notstrict --nochanges --notempty - pwpolicy user --minlen=8 --minquality=1 --notstrict --nochanges --emptyok - pwpolicy luks --minlen=8 --minquality=1 --notstrict --nochanges --notempty - %end - - %post - #enable kdump - sed -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg - %end - ===================================== - ``` - - >![](public_sys-resources/icon-note.gif) **NOTE:** - >The method of generating the password ciphertext is as follows: - >\# python3 - >Python 3.7.0 \(default, Apr 1 2019, 00:00:00\) - >\[GCC 7.3.0\] on linux - >Type "help", "copyright", "credits" or "license" for more information. - >\>\>\> import crypt - >\>\>\> passwd = crypt.crypt\("myPasswd"\) - >\>\>\> print\(passwd\) - >$6$63c4tDmQGn5SDayV$mZoZC4pa9Jdt6/ALgaaDq6mIExiOO2EjzomB.Rf6V1BkEMJDcMddZeGdp17cMyc9l9ML9ldthytBEPVcnboR/0 - -3. Mount the ISO image file to the CD-ROM drive of the computer where openEuler is to be installed. - - If you want to install openEuler through the NFS, specify the path \(which is **cdrom** by default\) of installation source in the kickstart file. - - -**Installing the System** - -1. The installation selection dialog box is displayed. - 1. On the installation wizard page in [Starting the Installation](starting-the-installation.md), select **Install openEuler 20.03 LTS** and press **e**. - 2. Add **inst.ks=http://server ip/ks/openEuler-ks.cfg** to the startup parameters. - - ![](figures/semi-automatic-installation.png) - - 3. Press **Ctrl**+**x** to start the automatic installation. - -2. Verify that the installation is complete. - - After the installation is complete, the system automatically restarts. Then, the installation page is displayed again. Shut down the computer and change startup option to start from the hard disk preferentially. - - ![](figures/completing-the-automatic-installation.png) - - diff --git a/content/en/docs/Installation/setting-a-system-language.md b/content/en/docs/Installation/setting-a-system-language.md deleted file mode 100644 index cc544d8f1e53428a8e43401cae3f6c481df899a0..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/setting-a-system-language.md +++ /dev/null @@ -1,13 +0,0 @@ -# Setting a System Language - -On the **INSTALLATION SUMMARY** page, click **LANGUAGE SUPPORT** to set the system language, as shown in [Figure 1](#en-us_topic_0186390098_en-us_topic_0122145772_fig187301927172619). Set another language as required, such as Chinese. - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->- If you select Chinese, the system does not display Chinese characters after you log in to the system using VNC, because VNC does not support Chinese characters. If you log in to the system in SSH mode, Chinese characters will be displayed. ->- If you select English, there will be no impact. - -**Figure 1** Setting a system language -![](figures/setting-a-system-language.png "setting-a-system-language") - -After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. - diff --git a/content/en/docs/Installation/setting-date-and-time.md b/content/en/docs/Installation/setting-date-and-time.md deleted file mode 100644 index 9bc313fb88e0b0be46b4128f8df49ff54532e0e1..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/setting-date-and-time.md +++ /dev/null @@ -1,17 +0,0 @@ -# Setting Date and Time - -On the **INSTALLATION SUMMARY** page, click **TIME & DATE**. On the **TIME & DATE** page, set the system time zone, date, and time. - -When setting the time zone, you can click a specific city on the map with the mouse, or select a region from the drop-down list of **Region** or a city from the drop-down list of **City** at the top of the page, as shown in [Figure 1](#en-us_topic_0186390096_en-us_topic_0122145900_fig1260162652312). - -If your city is not displayed on the map or in the drop-down list, select the nearest city in the same time zone. - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->- Before manually setting the time zone, disable the network time synchronization function in the upper right corner. ->- If you want to use the network time, ensure that the network can connect to the remote NTP server. For details about how to set the network, see [Setting the Network and Host Name](setting-the-network-and-host-name.md). - -**Figure 1** Setting date and time -![](figures/setting-date-and-time.png "setting-date-and-time") - -After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. - diff --git a/content/en/docs/Installation/setting-installation-parameters.md b/content/en/docs/Installation/setting-installation-parameters.md deleted file mode 100644 index 4f0c1398f43f6a8eefac707bd666d0b025380374..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/setting-installation-parameters.md +++ /dev/null @@ -1,4 +0,0 @@ -# Setting Installation Parameters - - - diff --git a/content/en/docs/Installation/setting-the-installation-destination.md b/content/en/docs/Installation/setting-the-installation-destination.md deleted file mode 100644 index b248d53607eaf50206786c3312dd6bd7b3e730ae..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/setting-the-installation-destination.md +++ /dev/null @@ -1,43 +0,0 @@ -# Setting the Installation Destination - -On the **INSTALLATION SUMMARY** page, click **INSTALLATION DESTINATION** to select the OS installation disk and partition. - -You can view available local storage devices in [Figure 1](#fig1195417125015). You can also add an attached device or a network disk specified by clicking **Add a disk**. - ->![](public_sys-resources/icon-notice.gif) **NOTICE:** ->When selecting the device to be installed, you are advised not to use the NVMe SSD storage medium as the OS installation disk. - -**Figure 1** Setting the installation destination -![](figures/setting-the-installation-destination.png "setting-the-installation-destination") - -## Storage Configuration - -On the **INSTALLATION DESTINATION** page, configure storage for system partition. You can either manually configure partitions or select **Automatic** to automatically configure partitioning. - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->- During partitioning, to ensure system security and performance, you are advised to divide the device into the following partitions: **/boot**, **/var**, **/var/log**, **/var/log/audit**, **/home**, and **/tmp**. ->- If the system is configured with the swap partition, the swap partition is used when the physical memory of the system is insufficient. Although the swap partition can be used to expand the physical memory, if the swap partition is used due to insufficient memory, the system response slows and the system performance deteriorates. Therefore, you are not advised to configure the swap partition in the system with sufficient physical memory or the performance sensitive system. ->- If you need to split a logical volume group, select **Custom** to manually partition the logical volume group. On the **MANUAL PARTITIONING** page, click **Modify** in the **Volume Group** area to reconfigure the logical volume group. - -**Automatic** - -Select **Automatic** if the software is installed in a new storage device or the data in the storage device is not required. - -**Customize** - -If you need to manually partition the disk, click **Customize** and click **Done** in the upper left corner. The following page is displayed. - -**Figure 2** MANUAL PARTITIONING page -![](figures/manual-partitioning-page.png "manual-partitioning-page") - -On the **MANUAL PARTITIONING** page, you can partition the disk in either of the following ways: - -- Automatic creation: Click **Click here to create them automatically**. The system automatically assigns four mount points according to the available storage space: **/boot**, **/**, **/boot/efi**, and **swap**. -- Manual creation: Click ![](figures/en-us_image_0229291243.png) to add a mount point. It is recommended that the expected capacity of each mount point not exceed the available space. - - >![](public_sys-resources/icon-note.gif) **NOTE:** - >If the expected capacity of the mount point exceeds the available space, the system allocates the remaining available space to the mount point. - - -After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. - diff --git a/content/en/docs/Installation/setting-the-installation-source.md b/content/en/docs/Installation/setting-the-installation-source.md deleted file mode 100644 index 3e9dfe3d23cf49ac0ae48b5106b27206ee1ab7b6..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/setting-the-installation-source.md +++ /dev/null @@ -1,19 +0,0 @@ -# Setting the Installation Source - -On the **INSTALLATION SUMMARY** page, click **INSTALLATION SOURCE** to locate the installation source. - -If you use a CD/DVD-ROM for installation, the installation program automatically detects and displays the installation source information. You can use the default settings. [Figure 1](#en-us_topic_0186390100_en-us_topic_0144427079_fig93633295132) shows an example. - -**Figure 1** Setting the installation source -![](figures/setting-the-installation-source.png "setting-the-installation-source") - -When you use the network for installation, if the HTTPS server uses a private certificate, press **e** on the installation wizard page to go to the parameter editing page and add the **inst.noverifyssl** parameter, as shown in [Figure 2](#fig113517811415). - -**Figure 2** Adding the **inst.noverifyssl** parameter -![](figures/adding-the-inst-noverifyssl-parameter.png "adding-the-inst-noverifyssl-parameter") - -After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->During the installation, if you have any questions about configuring the installation source, see [An Exception Occurs During the Selection of the Installation Source](an-exception-occurs-during-the-selection-of-the-installation-source.md). - diff --git a/content/en/docs/Installation/setting-the-keyboard-layout.md b/content/en/docs/Installation/setting-the-keyboard-layout.md deleted file mode 100644 index cce69f41c2e62dedf7882007922cf0d4a9e332bd..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/setting-the-keyboard-layout.md +++ /dev/null @@ -1,12 +0,0 @@ -# Setting the Keyboard Layout - -On the **INSTALLATION SUMMARY** page, click **KEYBOARD**. You can add or delete multiple keyboard layouts in the system. - -- On the left white box, click to select the keyboard layout and click the keyboard under the box. -- To test the keyboard layout: On the left white box, click to select the keyboard layout, click the inside of the right text box, and enter the text to ensure that the keyboard layout can work properly. - -**Figure 1** Setting the keyboard layout -![](figures/setting-the-keyboard-layout.png "setting-the-keyboard-layout") - -After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. - diff --git a/content/en/docs/Installation/setting-the-network-and-host-name.md b/content/en/docs/Installation/setting-the-network-and-host-name.md deleted file mode 100644 index 74e6474468eb45a7132a12a573aba03d7a5e4418..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/setting-the-network-and-host-name.md +++ /dev/null @@ -1,13 +0,0 @@ -# Setting the Network and Host Name - -On the **INSTALLATION SUMMARY** page, select **NETWORK & HOST NAME** to configure the system network functions. - -The installation program automatically detects a local access interface. The detected interface is listed in the left box, and the interface details are displayed in the right-hand area, as shown in [Figure 1](#en-us_topic_0186390264_en-us_topic_0122145831_fig123700157297). In the upper right corner, click the switchover button to enable or disable the network interface. You can also click **Configure** to configure the selected interface. - -In the lower left box, enter the host name. The host name can be the fully quantified domain name \(FQDN\) in the format of hostname.domainname or the brief host name in the format of hostname. - -**Figure 1** Setting the network and host name -![](figures/setting-the-network-and-host-name.png "setting-the-network-and-host-name") - -After the setting is complete, click **Done** in the upper left corner to go back to the **INSTALLATION SUMMARY** page. - diff --git a/content/en/docs/Installation/starting-installation.md b/content/en/docs/Installation/starting-installation.md deleted file mode 100644 index 12baf977323c432cb8013b35e9ebfeb8e7d95b60..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/starting-installation.md +++ /dev/null @@ -1,7 +0,0 @@ -# Starting Installation - -On the installation page, after all the mandatory items are configured, the safety symbols will disappear. Then, you can click **Begin Installation** to install the system. - -**Figure 1** Starting installation -![](figures/starting-installation.png "starting-installation") - diff --git a/content/en/docs/Installation/starting-the-installation.md b/content/en/docs/Installation/starting-the-installation.md deleted file mode 100644 index 2708ef2876fa3acd9feb194ece95e549ad353416..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/starting-the-installation.md +++ /dev/null @@ -1,63 +0,0 @@ -# Starting the Installation - -## Booting from the CD/DVD-ROM Drive - -Load the ISO image of openEuler from the CD/DVD-ROM drive of the server and restart the server. The procedure is as follows: - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->Before the installation, ensure that the server boots from the CD/DVD-ROM drive preferentially. The following steps describe how to install the openEuler using the virtual CD/DVD-ROM drive on the baseboard management controller \(BMC\). Installing the openEuler from a physical drive is simple. After the installation starts, the procedure for the physical drive is the same as that of the virtual drive. - -1. On the toolbar, click the icon shown in the following figure. - - **Figure 1** Drive icon - ![](figures/drive-icon.png "drive-icon") - - An image dialog box is displayed, as shown in the following figure. - - **Figure 2** Image dialog box - ![](figures/image-dialog-box.png "image-dialog-box") - -2. Select **Image File** and then click **Browse**. The **Open** dialog box is displayed. -3. Select the image file and click **Open**. In the image dialog box, click **Connect**. If **Connect** changes to **Disconnect**, the virtual CD/DVD-ROM drive is connected to the server. -4. On the toolbar, click the restart icon shown in the following figure to restart the device. - - **Figure 3** Restart icon - ![](figures/restart-icon.png "restart-icon") - - -## Installation Wizard - -A boot menu is displayed after the system is booted using the boot medium. In addition to options for starting the installation program, some other options are available on the boot menu. During system installation, the **Test this media & install openEuler 20.03 LTS** mode is used by default. Press the arrow keys on the keyboard to change the selection, and press **Enter** when the desired option is highlighted. - ->![](public_sys-resources/icon-note.gif) **NOTE:** ->- If you do not perform any operations within 1 minute, the system automatically selects the default option **Test this media & install openEuler 20.03 LTS** and enters the installation page. ->- During PM installation, if you cannot use the arrow keys to select boot options and the system does not respond after you press **Enter**, click ![](figures/en-us_image_0229420473.png) on the BMC page and configure **Key & Mouse Reset**. - -**Figure 4** Installation Wizard -![](figures/installation-wizard.png "installation-wizard") - -Installation wizard options are described as follows: - -- **Install openEuler 20.03 LTS**: Install openEuler on your server in GUI mode. - -- **Test this media & install openEuler 20.03 LTS**: Default option. Install openEuler on your server in GUI mode. The integrity of the installation medium is checked before the installation program is started. For details, see [Installation in GUI Mode](installation-in-gui-mode.md). - -- **Troubleshooting**: Troubleshooting mode, which is used when the system cannot be installed properly. In troubleshooting mode, the following options are available: - - **Install openEuler 20.03-LTS in basic graphics mode**: Basic graphics installation mode. In this mode, the video driver is not started before the system starts and runs. - - **Rescue the openEuler system**: Rescue mode, which is used to restore the system. In rescue mode, the installation process is printed in the VNC or BMC, and the serial port is unavailable. - -On the installation wizard screen, press **e** to go to the parameter editing screen of the selected option, and press **c** to go to the command-line interface \(CLI\). - -## Installation in GUI Mode - -On the installation wizard page, select **Test this media & install openEuler 20.03 LTS** to enter the GUI installation mode. - -Perform graphical installation operations using a keyboard. - -- Press **Tab** or **Shift**+**Tab** to move between GUI controls \(such as buttons, area boxes, and check boxes\). -- Press the up or down arrow key to move a target in the list. -- Press the left or right arrow key to move between the horizontal toolbar and watch bar. -- Press the spacebar or **Enter** to select or delete highlighted options, expand or collapse a drop-down list. -- Press **Alt**+a shortcut key \(the shortcut key varies for different pages\) to select the control where the shortcut key is located. The shortcut key can be highlighted \(underlined\) by holding down Alt. - - diff --git a/content/en/docs/Installation/terms-of-use.md b/content/en/docs/Installation/terms-of-use.md deleted file mode 100644 index c06728e4ff2cb79c5ece90890bd7cb684a37c88e..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/terms-of-use.md +++ /dev/null @@ -1,14 +0,0 @@ -# Terms of Use - -**Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.** - -Your replication, use, modification, and distribution of this document are governed by the Creative Commons License Attribution-ShareAlike 4.0 International Public License \(CC BY-SA 4.0\). You can visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/) to view a human-readable summary of \(and not a substitute for\) CC BY-SA 4.0. For the complete CC BY-SA 4.0, visit [https://creativecommons.org/licenses/by-sa/4.0/legalcode](https://creativecommons.org/licenses/by-sa/4.0/legalcode). - -**Trademarks and Permissions** - -openEuler is a trademark or registered trademark of Huawei Technologies Co., Ltd. All other trademarks and registered trademarks mentioned in this document are the property of their respective holders. - -**Disclaimer** - -This document is used only as a guide. Unless otherwise specified by applicable laws or agreed by both parties in written form, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, including but not limited to non-infringement, timeliness, and specific purposes. - diff --git a/content/en/docs/Installation/using-kickstart-for-automatic-installation.md b/content/en/docs/Installation/using-kickstart-for-automatic-installation.md index 4458a352ce5f4f4c9a9b712e6b1f7f7a9dc0f777..662f72b8bfd3008a7558ff50f52049c7bf896342 100644 --- a/content/en/docs/Installation/using-kickstart-for-automatic-installation.md +++ b/content/en/docs/Installation/using-kickstart-for-automatic-installation.md @@ -1,3 +1,364 @@ -# Using Kickstart for Automatic Installation +# Using Kickstart for Automatic Installation + +- [Using Kickstart for Automatic Installation](#using-kickstart-for-automatic-installation) + - [Introduction](#introduction) + - [Overview](#overview) + - [Advantages and Disadvantages](#advantages-and-disadvantages) + - [Background](#background) + - [Semi-automatic Installation Guide](#semi-automatic-installation-guide) + - [Environment Requirements](#environment-requirements) + - [Procedure](#procedure) + - [Full-automatic Installation Guide](#full-automatic-installation-guide) + - [Environment Requirements](#environment-requirements-1) + - [Procedure](#procedure-1) + + + +## Introduction + +### Overview + +You can use the kickstart tool to automatically install the openEuler OS in either of the following ways: + +- Semi-automatic installation: You only need to specify the location of the kickstart file. Kickstart automatically configures OS attributes such as keyboard, language, and partitions. +- Automatic installation: The OS is automatically installed. + +### Advantages and Disadvantages + +[Table 1](#table1388812373315) lists the advantages and disadvantages of semi-automatic installation and full-automatic installation using kickstart. You can select an installation mode as required. + +**Table 1** Advantages and disadvantages + + + + + + + + + + + + + + + + +

Installation Mode

+

Advantage

+

Disadvantage

+

Semi-automatic installation

+

Services such as TFTP, PXE, and DHCP do not need to be prepared.

+

You need to manually specify the path of the kickstart file.

+

Full-automatic installation

+

The OS is installed automatically.

+

Services, such as TFTP, DHCPD, and PXE, need to be configured.

+
+ +### Background + +**Kickstart** + +Kickstart is an unattended installation mode. The principle of kickstart is to record typical parameters that need to be manually entered during the installation and generate the configuration file **ks.cfg**. During the installation, the installation program searches the **ks.cfg** configuration file first for required parameters. If no matching parameters are found, you need to manually configure these parameters. If all required parameters are covered by the kickstart file, automatic installation can be achieved by only specifying the path of the kickstart file. + +Both full-automatic or semi-automatic installation can be achieved by kickstart. + +**PXE** + +Pre-boot Execution Environment \(PXE\)\) works in client/server network mode. The PXE client can obtain an IP address from the DHCP server during the startup and implement client boot and installation through the network based on protocols such as trivial file transfer protocol \(TFTP\). + +**TFTP** + +TFTP is used to transfer simple and trivial files between clients and the server. + +## Semi-automatic Installation Guide + +### Environment Requirements + +The environment requirements for semi-automatic installation of openEuler using kickstart are as follows: + +- PM/VM \(for details about how to create VMs, see the documents from corresponding vendors\): includes the computer where kickstart is used for automatic installation and the computer where the kickstart tool is installed. +- Httpd: stores the kickstart file. +- ISO: openEuler-20.03-LTS-aarch64-dvd.iso + +### Procedure + +To use kickstart to perform semi-automatic installation of openEuler, perform the following steps: + +**Environment Preparation** + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>Before the installation, ensure that the firewall of the HTTP server is disabled. Run the following command to disable the firewall: +>``` +>iptables -F +>``` + +1. Install httpd and start the service. + + ``` + # dnf install httpd -y + # systemctl start httpd + # systemctl enable httpd + ``` + +2. Run the following commands to prepare the kickstart file: + + ``` + # mkdir /var/www/html/ks + #vim /var/www/html/ks/openEuler-ks.cfg ===>The file can be obtained by modifying the anaconda-ks.cfg file automatically generated from openEuler, or can be created using the system-config-kickstart tool. + ==================================== + ***Modify the following information as required.*** + #version=DEVEL + ignoredisk --only-use=sda + autopart --type=lvm + # Partition clearing information + clearpart --none --initlabel + # Use graphical install + graphical + # Use CDROM installation media + cdrom + # Keyboard layouts + keyboard --vckeymap=cn --xlayouts='cn' + # System language + lang zh_CN.UTF-8 + + # Network information + network --bootproto=dhcp --device=enp4s0 --ipv6=auto --activate + network --hostname=openeuler.com + # Root password + rootpw --iscrypted $6$fQE83lxEZ48Or4zc$j7/PlUMHn29yTjCD4Fi44WTZL/RzVGxJ/7MGsZMl6QfE3KjIVT7M4UrhFXbafvRq2lUddAFcyWHd5WRmXfEK20 + # Run the Setup Agent on first boot + firstboot --enable + # Do not configure the X Window System + skipx + # System services + services --disabled="chronyd" + # System timezone + timezone Asia/Shanghai --isUtc--nontp + + %packages + @^minimal-environment + @standard + + %end + + %anaconda + pwpolicy root --minlen=8 --minquality=1 --notstrict --nochanges --notempty + pwpolicy user --minlen=8 --minquality=1 --notstrict --nochanges --emptyok + pwpolicy luks --minlen=8 --minquality=1 --notstrict --nochanges --notempty + %end + + %post + #enable kdump + sed -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg + %end + ===================================== + ``` + + >![](public_sys-resources/icon-note.gif) **NOTE:** + >The method of generating the password ciphertext is as follows: + >\# python3 + >Python 3.7.0 \(default, Apr 1 2019, 00:00:00\) + >\[GCC 7.3.0\] on linux + >Type "help", "copyright", "credits" or "license" for more information. + >\>\>\> import crypt + >\>\>\> passwd = crypt.crypt\("myPasswd"\) + >\>\>\> print\(passwd\) + >$6$63c4tDmQGn5SDayV$mZoZC4pa9Jdt6/ALgaaDq6mIExiOO2EjzomB.Rf6V1BkEMJDcMddZeGdp17cMyc9l9ML9ldthytBEPVcnboR/0 + +3. Mount the ISO image file to the CD-ROM drive of the computer where openEuler is to be installed. + + If you want to install openEuler through the NFS, specify the path \(which is **cdrom** by default\) of installation source in the kickstart file. + + +**Installing the System** + +1. The installation selection dialog box is displayed. + 1. On the installation wizard page in [Starting the Installation](installation-guideline.html#starting-the-installation), select **Install openEuler 20.03 LTS** and press **e**. + 2. Add **inst.ks=http://server ip/ks/openEuler-ks.cfg** to the startup parameters. + + ![](figures/semi-automatic-installation.png) + + 3. Press **Ctrl**+**x** to start the automatic installation. + +2. Verify that the installation is complete. + + After the installation is complete, the system automatically restarts. Then, the installation page is displayed again. Shut down the computer and change startup option to start from the hard disk preferentially. + + ![](figures/completing-the-automatic-installation.png) + + +## Full-automatic Installation Guide + +### Environment Requirements + +The environment requirements for full-automatic installation of openEuler using kickstart are as follows: + +- PM/VM \(for details about how to create VMs, see the documents from corresponding vendors\): includes the computer where kickstart is used for automatic installation and the computer where the kickstart tool is installed. +- Httpd: stores the kickstart file. +- TFTP: provides vmlinuz and initrd files. +- DHCPD/PXE: provides the DHCP service. +- ISO: openEuler-20.03-LTS-aarch64-dvd.iso + +### Procedure + +To use kickstart to perform full-automatic installation of openEuler, perform the following steps: + +**Environment Preparation** + +>![](public_sys-resources/icon-note.gif) **NOTE:** +>Before the installation, ensure that the firewall of the HTTP server is disabled. Run the following command to disable the firewall: +>``` +>iptables -F +>``` + +1. Install httpd and start the service. + + ``` + # dnf install httpd -y + # systemctl start httpd + # systemctl enable httpd + ``` + +2. Install and configure TFTP. + + ``` + # dnf install tftp-server -y + # vim /etc/xinetd.d/tftp + service tftp + { + socket_type = dgram + protocol = udp + wait = yes + user = root + server = /usr/sbin/in.tftpd + server_args = -s /var/lib/tftpboot + disable = no + per_source = 11 + cps = 100 2 + flags = IPv4 + } + # systemctl start tftp + # systemctl enable tftp + # systemctl start xinetd + # systemctl status xinetd + # systemctl enable xinetd + ``` + +3. Run the following commands to prepare the installation source: + + ``` + # mount openEuler-20.03-LTS-aarch64-dvd.iso /mnt + # cp -r /mnt/* /var/www/html/openEuler/ + ``` + +4. Set and modify the kickstart configuration file **openEuler-ks.cfg**. Select the HTTP installation source by referring to [3](#en-us_topic_0229291289_l1692f6b9284e493683ffa2ef804bc7ca). + + ``` + #vim /var/www/html/ks/openEuler-ks.cfg + ==================================== + ***Modify the following information as required.*** + #version=DEVEL + ignoredisk --only-use=sda + autopart --type=lvm + # Partition clearing information + clearpart --none --initlabel + # Use graphical install + graphical + # Keyboard layouts + keyboard --vckeymap=cn --xlayouts='cn' + # System language + lang zh_CN.UTF-8 + #Use http installation source + url --url=//192.168.122.1/openEuler/ + %post + #enable kdump + sed -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg + %end + ... + ``` + +5. Modify the PXE configuration file **grub.cfg** as follows: + + ``` + # cp -r /mnt/images/pxeboot/* /var/lib/tftpboot/ + # cp /mnt/EFI/BOOT/grubaa64.efi /var/lib/tftpboot/ + # cp /mnt/EFI/BOOT/grub.cfg /var/lib/tftpboot/ + # ls /var/lib/tftpboot/ + grubaa64.efi grub.cfg initrd.img TRANS.TBL vmlinuz + # vim /var/lib/tftpboot/grub.cfg + set default="1" + + function load_video { + if [ x$feature_all_video_module = xy ]; then + insmod all_video + else + insmod efi_gop + insmod efi_uga + insmod ieee1275_fb + insmod vbe + insmod vga + insmod video_bochs + insmod video_cirrus + fi + } + + load_video + set gfxpayload=keep + insmod gzio + insmod part_gpt + insmod ext2 + + set timeout=60 + + + ### BEGIN /etc/grub.d/10_linux ### + menuentry 'Install openEuler 20.03 LTS' --class red --class gnu-linux --class gnu --class os { + set root=(tftp,192.168.1.1) + linux /vmlinuz ro inst.geoloc=0 console=ttyAMA0 console=tty0 rd.iscsi.waitnet=0 inst.ks=http://192.168.122.1/ks/openEuler-ks.cfg + initrd /initrd.img + } + ``` + +6. Run the following commands to configure DHCP \(which can be replaced by DNSmasq\): + + ``` + # dnf install dhcp -y + # + # DHCP Server Configuration file. + # see /usr/share/doc/dhcp-server/dhcpd.conf.example + # see dhcpd.conf(5) man page + # + # vim /etc/dhcp/dhcpd.conf + ddns-update-style interim; + ignore client-updates; + filename "grubaa64.efi"; # pxelinux location of the startup file; + next-server 192.168.122.1; # (IMPORTANT) TFTP server IP address; + subnet 192.168.122.0 netmask 255.255.255.0 { + option routers 192.168.111.1; # Gateway address + option subnet-mask 255.255.255.0; # Subnet mask + range dynamic-bootp 192.168.122.50 192.168.122.200; # Dynamic IP address range + default-lease-time 21600; + max-lease-time 43200; + } + # systemctl start dhcpd + # systemctl enable dhcpd + ``` + + +**Installing the System** + +1. On the **Start boot option** screen, press **F2** to boot from the PXE and start automatic installation. + + ![](figures/en-us_image_0229291270.png) + + ![](figures/en-us_image_0229291286.png) + + ![](figures/en-us_image_0229291247.png) + +2. The automatic installation window is displayed. +3. Verify that the installation is complete. + + ![](figures/completing-the-automatic-installation.png) diff --git a/content/en/docs/Installation/virtualization-platform-compatibility.md b/content/en/docs/Installation/virtualization-platform-compatibility.md deleted file mode 100644 index 8a1dd0510685486dffd711ddab26fe1d548bc997..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/virtualization-platform-compatibility.md +++ /dev/null @@ -1,7 +0,0 @@ -# Virtualization Platform Compatibility - -When installing openEuler, pay attention to the compatibility of the virtualization platform. Currently, the following virtualization platforms are supported: - -- A virtualization platform created by the virtualization components \(openEuler as the host OS and QEMU and KVM provided in the release package\) of openEuler -- x86 virtualization platform of Huawei public cloud - diff --git a/content/en/docs/Installation/what-are-the-constraints-on-network-configurations.md b/content/en/docs/Installation/what-are-the-constraints-on-network-configurations.md deleted file mode 100644 index bf1865a24bb3f24a3ec9acac68024659ad588c6a..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/what-are-the-constraints-on-network-configurations.md +++ /dev/null @@ -1,25 +0,0 @@ -# What Are the Constraints on Network Configurations? - -The NetworkManager and network services are network service management tools. Some functions of the two services overlap. - -- If the NetworkManager service is used, run the **nmcli** command or modify the configuration file to configure the network \(such as the IP address and route\). Do not run the **ip**, **ifconfig**, or **route** command to configure the network. - - >![](public_sys-resources/icon-note.gif) **NOTE:** - >When the NetworkManager service is enabled and you run commands such as **ip**, **ifconfig**, and **route** to configure the network, the configurations will be overwritten by NetworkManager. - - To check whether NetworkManager is enabled, run the following command: - - ``` - systemctl status NetworkManager - ``` - - >![](public_sys-resources/icon-note.gif) **NOTE:** - >For details about the use of the **nmcli** command, see the execution result of the **nmcli --help** or **man nmcli** command. - -- If you want to run commands such as **ip**, **ifconfig**, and **route** commands to manage network information, run the following command to disable the NetworkManager service: - - ``` - systemctl stop NetworkManager - ``` - - diff --git a/content/en/docs/Installation/why-does-openeuler-enter-emergency-mode-after-it-is-powered-on.md b/content/en/docs/Installation/why-does-openeuler-enter-emergency-mode-after-it-is-powered-on.md deleted file mode 100644 index 10da2008daf2d95257304aefc2fbcd6d4c1dd02f..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/why-does-openeuler-enter-emergency-mode-after-it-is-powered-on.md +++ /dev/null @@ -1,39 +0,0 @@ -# Why Does openEuler Enter Emergency Mode After It Is Powered On? - -## Symptom - -openEuler enters emergency mode after it is powered on. - -![](figures/en-us_image_0229291264.jpg) - -## Possible Causes - -Damaged OS files result in disk mounting failure, or overpressured I/O results in disk mounting timeout \(threshold: 90s\). - -An unexpected system power-off, and low I/O performance of disks may also cause the problem. - -## Solution - -1. Enter the password of the **root** account to log in to openEuler. -2. Check and restore files by using the file system check \(fsck\) tool, and restart openEuler. - - >![](public_sys-resources/icon-note.gif) **NOTE:** - >The fsck tool checks and maintains inconsistent file systems. If the system is powered off or a disk is faulty, run the **fsck** command to check file systems. Run the **fsck.ext3 -h** and **fsck.ext4 -h** commands to view the usage method of the fsck tool. - - -If you want to disable the timeout mechanism of disk mounting, add **x-systemd.device-timeout=0** to the **etc/fstab** file. For example: - -``` -# -# /etc/fstab -# Created by anaconda on Mon Sep 14 17:25:48 2015 -# -# Accessible filesystems, by reference, are maintained under '/dev/disk' -# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info -# -/dev/mapper/openEuler-root / ext4 defaults,x-systemd.device-timeout=0 0 0 -UUID=afcc811f-4b20-42fc-9d31-7307a8cfe0df /boot ext4 defaults,x-systemd.device-timeout=0 0 0 -/dev/mapper/openEuler-home /home ext4 defaults 0 0 -/dev/mapper/openEuler-swap swap swap defaults 0 0 -``` - diff --git a/content/en/docs/Installation/why-does-openeuler-fail-to-start-after-i-install-it-to-the-second-disk.md b/content/en/docs/Installation/why-does-openeuler-fail-to-start-after-i-install-it-to-the-second-disk.md deleted file mode 100644 index dea11ce2209875c90c877f5e9fa5aee4995cdc92..0000000000000000000000000000000000000000 --- a/content/en/docs/Installation/why-does-openeuler-fail-to-start-after-i-install-it-to-the-second-disk.md +++ /dev/null @@ -1,22 +0,0 @@ -# Why Does openEuler Fail to Start After I Install It to the Second Disk? - -## Symptom - -The OS is installed on the second disk **sdb** during the installation. The openEuler fails to be started. - -## Possible Cause - -When openEuler is installed to the second disk, MBR and GRUB are installed to the second disk **sdb** by default. The following two situations may occur: - -1. openEuler installed on the first disk is loaded and started if it is complete. -2. openEuler installed on the first disk fails to be started from hard disks if it is incomplete. - -The preceding two situations occur because the first disk **sda** is booted by default to start openEuler on the BIOS window. If openEuler is not installed on the **sda** disk, system restart fails. - -## Solution - -This problem can be solved using either of the following two methods: - -- During the installation of openEuler, select the first disk or both disks, and install the boot loader on the first disk **sda**. -- After installing openEuler, restart it by modifying the boot option on the BIOS window. - diff --git a/content/en/docs/Quickstart/quick-start.md b/content/en/docs/Quickstart/quick-start.md index 08fa9edf75a81eda04f7f2f06ef8f43bb601b06b..59e30d621824d46d661fe989c9bf23f1b96fc66b 100644 --- a/content/en/docs/Quickstart/quick-start.md +++ b/content/en/docs/Quickstart/quick-start.md @@ -1,8 +1,19 @@ -# Quick Start +# Quick Start This document uses openEuler 20.03 LTS installed on the TaiShan 200 server as an example to describe how to quickly install and use openEuler OS. For details about the installation requirements and methods, see [openEuler 20.03 LTS Installation Guide](https://openeuler.org/en/docs/20.03_LTS/docs/Installation/Installation.html). + -## Installation Preparations +- [Quick Start](#quick-start) + - [Installation Preparations](#installation-preparations) + - [Obtaining the Installation Source](#obtaining-the-installation-source) + - [Release Package Integrity Check](#release-package-integrity-check) + - [Starting the Installation](#starting-the-installation) + - [Installation](#installation) + - [Viewing System Information](#viewing-system-information) + + + +## Installation Preparations - Hardware Compatibility @@ -85,7 +96,7 @@ This document uses openEuler 20.03 LTS installed on the TaiShan 200 server as an -## Obtaining the Installation Source +## Obtaining the Installation Source Perform the following operations to obtain the openEuler release package: @@ -111,7 +122,7 @@ Perform the following operations to obtain the openEuler release package: -## Release Package Integrity Check +## Release Package Integrity Check To prevent incomplete download of the software package due to network or storage device problems during the transmission, you can perform the following steps to check the integrity of the obtained openEuler software package: @@ -134,7 +145,7 @@ To prevent incomplete download of the software package due to network or storage If the verification values are consistent, the .iso file is not damaged. If they are inconsistent, you can confirm that the file is damaged and you need to obtain the file again. -## Starting the Installation +## Starting the Installation 1. Log in to the iBMC WebUI. @@ -179,7 +190,7 @@ To prevent incomplete download of the software package due to network or storage 9. On the installation wizard page, press **Enter** to select the default option **Test this media & install openEuler 20.03 LTS** to enter the GUI installation page. -## Installation +## Installation After entering the GUI installation page, perform the following operations to install the system: @@ -291,7 +302,7 @@ After entering the GUI installation page, perform the following operations to in -## Viewing System Information +## Viewing System Information After the system is installed and restarted, the system CLI login page is displayed. Enter the username and password set during the installation to log in to openEuler OS and view the following system information. For details about system management and configuration, see the [openEuler 20.03 LTS Administrator Guide](https://openeuler.org/en/docs/20.03_LTS/docs/Administration/administration.html). diff --git a/content/en/docs/Releasenotes/terms-of-use.md b/content/en/docs/Releasenotes/terms-of-use.md index 029d4b006ba1851a65dc70a2a4b87bd162f8fe2f..dbbef6358b01550f1c2b03252c9b254e4682b953 100644 --- a/content/en/docs/Releasenotes/terms-of-use.md +++ b/content/en/docs/Releasenotes/terms-of-use.md @@ -6,7 +6,7 @@ Your replication, use, modification, and distribution of this document are gover **Trademarks and Permissions** -A-Tune and openEuler are trademarks or registered trademarks of Huawei Technologies Co., Ltd. All other trademarks and registered trademarks mentioned in this document are the property of their respective holders. +openEuler is a trademark of Huawei Technologies Co., Ltd. All other trademarks and registered trademarks mentioned in this document are the property of their respective holders. **Disclaimer** diff --git a/content/en/menu/index.md b/content/en/menu/index.md index a517f4632336edcae5d8f5a00362a6e89e5c50b8..25082df1687b72ed37536d8c7fc5b739aa626b0a 100644 --- a/content/en/menu/index.md +++ b/content/en/menu/index.md @@ -19,38 +19,11 @@ headless: true - [Quick Start]({{< relref "./docs/Quickstart/quick-start.md" >}}) - [Installation Guide]({{< relref "./docs/Installation/Installation.md" >}}) - - [Preface]({{< relref "./docs/Installation/preface.md" >}}) - [Installation Preparations]({{< relref "./docs/Installation/installation-preparations.md" >}}) - [Installation Mode]({{< relref "./docs/Installation/installation-mode.md" >}}) - [Installation Guideline]({{< relref "./docs/Installation/installation-guideline.md" >}}) - - [Starting the Installation]({{< relref "./docs/Installation/starting-the-installation.md" >}}) - - [Configuring an Installation Program Language]({{< relref "./docs/Installation/configuring-an-installation-program-language.md" >}}) - - [Entering the Installation Page]({{< relref "./docs/Installation/entering-the-installation-page.md" >}}) - - [Setting Installation Parameters]({{< relref "./docs/Installation/setting-installation-parameters.md" >}}) - - [Setting the Keyboard Layout]({{< relref "./docs/Installation/setting-the-keyboard-layout.md" >}}) - - [Setting a System Language]({{< relref "./docs/Installation/setting-a-system-language.md" >}}) - - [Setting Date and Time]({{< relref "./docs/Installation/setting-date-and-time.md" >}}) - - [Setting the Installation Source]({{< relref "./docs/Installation/setting-the-installation-source.md" >}}) - - [Selecting Installation Software]({{< relref "./docs/Installation/selecting-installation-software.md" >}}) - - [Setting the Installation Destination]({{< relref "./docs/Installation/setting-the-installation-destination.md" >}}) - - [Setting the Network and Host Name]({{< relref "./docs/Installation/setting-the-network-and-host-name.md" >}}) - - [Starting Installation]({{< relref "./docs/Installation/starting-installation.md" >}}) - - [Configurations During Installation]({{< relref "./docs/Installation/configurations-during-installation.md" >}}) - - [Completing the Installation]({{< relref "./docs/Installation/completing-the-installation.md" >}}) - [Using Kickstart for Automatic Installation]({{< relref "./docs/Installation/using-kickstart-for-automatic-installation.md" >}}) - - [Introduction]({{< relref "./docs/Installation/introduction.md" >}}) - - [Semi-automatic Installation Guide]({{< relref "./docs/Installation/semi-automatic-installation-guide.md" >}}) - - [Full-automatic Installation Guide]({{< relref "./docs/Installation/full-automatic-installation-guide.md" >}}) - [FAQs]({{< relref "./docs/Installation/faqs.md" >}}) - - [Why Does openEuler Fail to Start After I Install It to the Second Disk?]({{< relref "./docs/Installation/why-does-openeuler-fail-to-start-after-i-install-it-to-the-second-disk.md" >}}) - - [What Are the Constraints on Network Configurations?]({{< relref "./docs/Installation/what-are-the-constraints-on-network-configurations.md" >}}) - - [Why Does openEuler Enter Emergency Mode After It Is Powered On?]({{< relref "./docs/Installation/why-does-openeuler-enter-emergency-mode-after-it-is-powered-on.md" >}}) - - [Failed to Reinstall openEuler When a Logical Volume Group That Cannot Be Activated Has Existed in openEuler]({{< relref "./docs/Installation/failed-to-reinstall-openeuler-when-a-logical-volume-group-that-cannot-be-activated-has-existed-in-op.md" >}}) - - [An Exception Occurs During the Selection of the Installation Source]({{< relref "./docs/Installation/an-exception-occurs-during-the-selection-of-the-installation-source.md" >}}) - - [How Do I Manually Enable the kdump Service?]({{< relref "./docs/Installation/how-do-i-manually-enable-the-kdump-service.md" >}}) - - [Failed to Selected Only One Disk for Reinstallation When openEuler Was Installed on a Logical Volume Consisting of Multiple Disks]({{< relref "./docs/Installation/failed-to-selected-only-one-disk-for-reinstallation-when-openeuler-was-installed-on-a-logical-volume.md" >}}) - - [Failed to Install openEuler on an x86 PM in UEFI Mode due to Secure Boot Option Setting]({{< relref "./docs/Installation/failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting.md" >}}) - - [Administrator Guide]({{< relref "./docs/Administration/administration.md" >}}) - [About This Document ]({{< relref "./docs/Administration/about-this-document.md" >}}) diff --git a/content/zh/docs/Installation/FAQ.md b/content/zh/docs/Installation/FAQ.md index 3daee532659425a1438b50bd16b2cfe4c08e04ad..1cd62301d8eab0c71e9f18f69580050535e63e57 100644 --- a/content/zh/docs/Installation/FAQ.md +++ b/content/zh/docs/Installation/FAQ.md @@ -1 +1,324 @@ -# FAQ +# FAQ + + +- [FAQ](#faq) + - [安装openEuler时选择第二盘位为安装目标，操作系统无法启动](#安装openeuler时选择第二盘位为安装目标操作系统无法启动) + - [网络配置约束限制](#网络配置约束限制) + - [openEuler开机后进入emergency模式](#openeuler开机后进入emergency模式) + - [系统中存在无法激活的逻辑卷组时，重装系统失败](#系统中存在无法激活的逻辑卷组时重装系统失败) + - [选择安装源出现异常](#选择安装源出现异常) + - [如何手动开启kdump服务](#如何手动开启kdump服务) + - [多块磁盘组成逻辑卷安装系统后，再次安装不能只选其中一块磁盘](#多块磁盘组成逻辑卷安装系统后再次安装不能只选其中一块磁盘) + - [x86物理机UEFI模式由于security boot安全选项问题无法安装](#x86物理机uefi模式由于security-boot安全选项问题无法安装) + + + +## 安装openEuler时选择第二盘位为安装目标，操作系统无法启动 + +### 问题现象 + +安装操作系统时，直接将系统安装到第二块磁盘sdb，重启系统后启动失败。 + +### 原因分析 + +当安装系统到第二块磁盘时，MBR和GRUB会默认安装到第二块磁盘sdb。这样会有下面两种情况： + +1. 如果第一块磁盘中有完整系统，则加载第一块磁盘中的系统启动。 +2. 如果第一块磁盘中没有完好的操作系统，则会导致硬盘启动失败。 + +以上两种情况都是因为BIOS默认从第一块磁盘sda中加载引导程序启动系统，如果sda没有系统，则会导致启动失败。 + +### 解决方法 + +有以下两种解决方案： + +- 当系统处于安装过程中，在选择磁盘（选择第一块或者两块都选择）后，指定引导程序安装到第一块盘sda中。 +- 当系统已经安装完成，若BIOS支持选择从哪个磁盘启动，则可以通过修改BIOS中磁盘启动顺序，尝试重新启动系统。 + +## 网络配置约束限制 + +NetworkManager、network两个服务均是网络服务管理包，两个服务之间存在部分功能重叠。 + +- 如果使用NetworkManager管理服务，则必须使用nmcli命令或修改配置文件来配置网络（如IP、路由等），而不能使用ip/ifconfig/route命令来配置。 + + >![](public_sys-resources/icon-note.gif) **说明：** + >在开启NetworkManager服务的场景下，使用ip/ifconfig/route等命令配置网络，则一段时间后配置会被NetworkManager覆盖，导致 ip/ifconfig/route配置不生效。 + + 查看NetworkManager 服务是否开启： + + ``` + systemctl status NetworkManager + ``` + + >![](public_sys-resources/icon-note.gif) **说明：** + >nmcli命令使用参考“nmcli \--help”或者“man nmcli”。 + +- 如果要使用ip/ifconfig/route等命令来管理网络，请先关闭NetworkManager服务，使用如下命令： + + ``` + systemctl stop NetworkManager + ``` + + +## openEuler开机后进入emergency模式 + +### 问题现象 + +openEuler系统开机后进入emergency模式，如下图所示： + +![](figures/zh-cn_image_0229291264.jpg) + +### 原因分析 + +操作系统文件系统损坏导致磁盘挂载失败，或者io压力过大导致磁盘挂载超时（超时时间为90秒）。 + +系统异常掉电、物理磁盘io性能低等情况都可能导致该问题。 + +### 解决方法 + +1. 用户直接输入root账号的密码，登录系统。 +2. 使用fsck工具，检测并修复文件系统，然后重启。 + + >![](public_sys-resources/icon-note.gif) **说明：** + >fsck（file system check）用来检查和维护不一致的文件系统。若系统掉电或磁盘发生问题，可利用fsck命令对文件系统进行检查。 用户可以通过“fsck.ext3 -h”、“fsck.ext4 -h”命令查看fsck的使用方法。 + + +另外，如果用户需要取消磁盘挂载超时时间，可以直接在“/etc/fstab”文件中添加“x-systemd.device-timeout=0”。如下： + +``` +# +# /etc/fstab +# Created by anaconda on Mon Sep 14 17:25:48 2015 +# +# Accessible filesystems, by reference, are maintained under '/dev/disk' +# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info +# +/dev/mapper/openEuler-root / ext4 defaults,x-systemd.device-timeout=0 0 0 +UUID=afcc811f-4b20-42fc-9d31-7307a8cfe0df /boot ext4 defaults,x-systemd.device-timeout=0 0 0 +/dev/mapper/openEuler-home /home ext4 defaults 0 0 +/dev/mapper/openEuler-swap swap swap defaults 0 0 +``` + +## 系统中存在无法激活的逻辑卷组时，重装系统失败 + +### 问题现象 + +由于磁盘故障，系统中存在无法激活的逻辑卷组，重装系统出现异常。 + +### 原因分析 + +安装时有激活逻辑卷组的操作，无法激活时会抛出异常。 + +### 解决方法 + +重装系统前如果系统中存在无法激活的逻辑卷组，为了避免重装系统过程出现异常，需在重装前将逻辑卷组恢复到正常状态或者清除这些逻辑卷组。举例如下： + +- 恢复逻辑卷组状态 + 1. 使用以下命令清除vg激活状态， 防止出现“Can't open /dev/sdc exclusively mounted filesystem”。 + + ``` + vgchange -a n testvg32947 + ``` + + 2. 根据备份文件重新创建pv。 + + ``` + pvcreate --uuid JT7zlL-K5G4-izjB-3i5L-e94f-7yuX-rhkLjL --restorefile /etc/lvm/backup/testvg32947 /dev/sdc + ``` + + 3. 恢复vg信息。 + + ``` + vgcfgrestore testvg32947 + ``` + + 4. 重新激活vg。 + + ``` + vgchange -ay testvg32947 + ``` + + +- 清除逻辑卷组 + + ``` + vgchange -a n testvg32947 + vgremove -y testvg32947 + ``` + + +## 选择安装源出现异常 + +### 问题现象 + +选择安装源后出现："Error checking software selection"。 + +### 原因分析 + +这种现象是由于安装源中的软件包依赖存在问题。 + +### 解决方法 + +检查安装源是否存在异常。使用新的安装源。 + +## 如何手动开启kdump服务 + +### 问题现象 + +执行systemctl status kdump命令，显示状态信息如下，提示无预留内存。 + +![](figures/zh-cn_image_0229291280.png) + +### 原因分析 + +kdump服务需要系统预留一段内存用于运行kdump内核，而当前系统没有为kdump服务预留内存，所以无法运行kdump服务。 + +### 解决方法 + +已安装操作系统的场景 + +1. 修改/boot/efi/EFI/openEuler/grub.cfg，添加crashkernel=1024M,high。 +2. 重启系统使配置生效。 +3. 执行如下命令，检查kdump状态： + + ``` + systemctl status kdump + ``` + + 若回显如下，即kdump的状态为active，说明kdump已使能，操作结束。 + + ![](figures/zh-cn_image_0229291272.png) + + +### 参数说明 + +kdump内核预留内存参数说明如下： + +**表 1** crashkernel参数说明 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

内核启动参数

+

描述

+

默认值

+

备注

+

crashkernel=X

+

在4G以下的物理内存预留X大小的内存给kdump使用

+

无，用户根据实际情况调整

+

该配置方法只在4G以下内存预留，必须保证4G以下连续可用内存足够预留

+

crashkernel=X@Y

+

在Y起始地址预留X大小的内存给kdump使用

+

无，用户根据实际情况调整

+

需要确保Y起始地址的X大小内存未被其他模块预留

+

crashkernel=X,high

+

在4G以下的物理内存中预留256M大小，在4G以上预留X大小内存给kdump使用

+

无，用户根据实际情况调整，推荐值为1024M,high

+

确保4G以下内存有256M连续可用内存，4G以上有连续X大小内存可预留。实际预留内存大小为256M+X

+

crashkernel=X,low

+

crashkernel=Y,high

+

在4G以下的物理内存中预留X大小，在4G以上预留Y大小内存给kdump使用

+

无，用户根据实际情况调整

+

需要确保4G以下有X大小连续可用内存，4G以上有Y大小连续可用内存。实际预留内存大小为X+Y

+
+ +## 多块磁盘组成逻辑卷安装系统后，再次安装不能只选其中一块磁盘 + +### 问题现象 + +在安装系统时，如果之前的系统选择多块磁盘组成逻辑卷进行安装，再次安装时，如果只选择了其中的一块或几块磁盘，没有全部选择，在保存配置时提示配置错误，如[图1](#fig115949762617)所示。 + +**图 1** 配置错误提示 +![](figures/配置错误提示.png "配置错误提示") + +### 原因分析 + +之前的逻辑卷包含了多块磁盘，只在一块磁盘上安装会破坏逻辑卷。 + +### 解决方法 + +因为多块磁盘组成逻辑卷相当于一个整体，所以只需要删除对应的卷组即可。 + +1. 按“Ctrl+Alt+F2”可以切换到命令行，执行如下命令找到卷组。 + + ``` + vgs + ``` + + ![](figures/zh-cn_image_0231657950.png) + +2. 执行如下命令，删除卷组。 + + ``` + vgremove euleros + ``` + +3. 执行如下命令，重启安装程序即可生效。 + + ``` + systemctl restart anaconda + ``` + + >![](public_sys-resources/icon-note.gif) **说明：** + >图形模式下也可以按“Ctrl+Alt+F6”回到图形界面，点击[图1](#fig115949762617)右下角的“Refresh”刷新存储配置生效。 + + +## x86物理机UEFI模式由于security boot安全选项问题无法安装 + +### 问题现象 + +x86物理机安装系统时，由于设置了BIOS选项security boot 为enable（默认是disable），导致系统一直停留在“No bootable device”提示界面，无法继续安装，如[图2](#fig115949762617)所示。 + +**图 2** “No bootable device”提示界面 +![](figures/No-bootable-device-提示界面.png "No-bootable-device-提示界面") + +### 原因分析 + +开启security boot后，主板会验证引导程序及操作系统 ，若没有用对应的私钥进行签名，则无法通过主板上内置公钥的认证。 + +### 解决方法 + +进入BIOS，设置security boot为disable，重新安装即可。 + +1. 系统启动时，按“F11”，输入密码“Admin@9000”进入BIOS。 + + ![](figures/BIOS.png) + +2. 选择进入Administer Secure Boot。 + + ![](figures/security.png) + +3. 设置Enforce Secure Boot为Disabled。 + + ![](figures/选择.png) + + >![](public_sys-resources/icon-note.gif) **说明：** + >设置security boot为disable之后，保存退出，重新安装即可。 + + + \ No newline at end of file diff --git a/content/zh/docs/Installation/installation.md b/content/zh/docs/Installation/installation.md index 2e11e1e7faad5bc1ddbe494b7824fa2f1c389443..27862aea1b2ec54d226260a8e459212e189e33ac 100644 --- a/content/zh/docs/Installation/installation.md +++ b/content/zh/docs/Installation/installation.md @@ -1 +1,5 @@ -本文档简要描述如何获取openEuler的安装包，并通过多种方式完成openEuler的默认安装。 \ No newline at end of file +# 安装指南 +本文档主要介绍openEuler操作系统安装方法，以指导用户顺利完成openEuler操作系统安装。 + +本文档适用于所有使用openEuler操作系统的用户，特别是初次使用或想了解openEuler的用户，包括系统工程师、管理员及维护人员等。使用本手册的用户需要具备基础的Linux系统管理知识。 + diff --git "a/content/zh/docs/Installation/openEuler\345\274\200\346\234\272\345\220\216\350\277\233\345\205\245emergency\346\250\241\345\274\217.md" "b/content/zh/docs/Installation/openEuler\345\274\200\346\234\272\345\220\216\350\277\233\345\205\245emergency\346\250\241\345\274\217.md" deleted file mode 100644 index 86f076d34552b4e81125722e5efec9a9d67ba31d..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/openEuler\345\274\200\346\234\272\345\220\216\350\277\233\345\205\245emergency\346\250\241\345\274\217.md" +++ /dev/null @@ -1,39 +0,0 @@ -# openEuler开机后进入emergency模式 - -## 问题现象 - -openEuler系统开机后进入emergency模式，如下图所示： - -![](figures/zh-cn_image_0229291264.jpg) - -## 原因分析 - -操作系统文件系统损坏导致磁盘挂载失败，或者io压力过大导致磁盘挂载超时（超时时间为90秒）。 - -系统异常掉电、物理磁盘io性能低等情况都可能导致该问题。 - -## 解决方法 - -1. 用户直接输入root账号的密码，登录系统。 -2. 使用fsck工具，检测并修复文件系统，然后重启。 - - >![](public_sys-resources/icon-note.gif) **说明：** - >fsck（file system check）用来检查和维护不一致的文件系统。若系统掉电或磁盘发生问题，可利用fsck命令对文件系统进行检查。 用户可以通过“fsck.ext3 -h”、“fsck.ext4 -h”命令查看fsck的使用方法。 - - -另外，如果用户需要取消磁盘挂载超时时间，可以直接在“/etc/fstab”文件中添加“x-systemd.device-timeout=0”。如下： - -``` -# -# /etc/fstab -# Created by anaconda on Mon Sep 14 17:25:48 2015 -# -# Accessible filesystems, by reference, are maintained under '/dev/disk' -# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info -# -/dev/mapper/openEuler-root / ext4 defaults,x-systemd.device-timeout=0 0 0 -UUID=afcc811f-4b20-42fc-9d31-7307a8cfe0df /boot ext4 defaults,x-systemd.device-timeout=0 0 0 -/dev/mapper/openEuler-home /home ext4 defaults 0 0 -/dev/mapper/openEuler-swap swap swap defaults 0 0 -``` - diff --git "a/content/zh/docs/Installation/x86\347\211\251\347\220\206\346\234\272UEFI\346\250\241\345\274\217\347\224\261\344\272\216security-boot\345\256\211\345\205\250\351\200\211\351\241\271\351\227\256\351\242\230\346\227\240\346\263\225\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/x86\347\211\251\347\220\206\346\234\272UEFI\346\250\241\345\274\217\347\224\261\344\272\216security-boot\345\256\211\345\205\250\351\200\211\351\241\271\351\227\256\351\242\230\346\227\240\346\263\225\345\256\211\350\243\205.md" deleted file mode 100644 index 49efe241acb1b0b7ba01201e536ee7526a26090d..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/x86\347\211\251\347\220\206\346\234\272UEFI\346\250\241\345\274\217\347\224\261\344\272\216security-boot\345\256\211\345\205\250\351\200\211\351\241\271\351\227\256\351\242\230\346\227\240\346\263\225\345\256\211\350\243\205.md" +++ /dev/null @@ -1,33 +0,0 @@ -# x86物理机UEFI模式由于security boot安全选项问题无法安装 - -## 问题现象 - -x86物理机安装系统时，由于设置了BIOS选项security boot 为enable（默认是disable），导致系统一直停留在“No bootable device”提示界面，无法继续安装，如[图1](#fig115949762617)所示。 - -**图 1** “No bootable device”提示界面 -![](figures/No-bootable-device-提示界面.png "No-bootable-device-提示界面") - -## 原因分析 - -开启security boot后，主板会验证引导程序及操作系统 ，若没有用对应的私钥进行签名，则无法通过主板上内置公钥的认证。 - -## 解决方法 - -进入BIOS，设置security boot为disable，重新安装即可。 - -1. 系统启动时，按“F11”，输入密码“Admin@9000”进入BIOS。 - - ![](figures/BIOS.png) - -2. 选择进入Administer Secure Boot。 - - ![](figures/security.png) - -3. 设置Enforce Secure Boot为Disabled。 - - ![](figures/选择.png) - - >![](public_sys-resources/icon-note.gif) **说明：** - >设置security boot为disable之后，保存退出，重新安装即可。 - - diff --git a/content/zh/docs/Installation/zh-cn_bookmap_0229291255.md b/content/zh/docs/Installation/zh-cn_bookmap_0229291255.md deleted file mode 100644 index 9251b8bb562141bfcf6ab5578987969f2dbda8bb..0000000000000000000000000000000000000000 --- a/content/zh/docs/Installation/zh-cn_bookmap_0229291255.md +++ /dev/null @@ -1,58 +0,0 @@ -# 安装指南 - -- [法律声明](法律声明.md) -- [前言](前言.md) -- [安装准备](安装准备.md) - - [获取安装源](获取安装源.md) - - [发布包完整性校验](发布包完整性校验.md) - - [物理机的安装要求](物理机的安装要求.md) - - [硬件兼容支持](硬件兼容支持.md) - - [最小硬件要求](最小硬件要求.md) - - - [虚拟机的安装要求](虚拟机的安装要求.md) - - [虚拟化平台兼容性](虚拟化平台兼容性.md) - - [最小虚拟化空间要求](最小虚拟化空间要求.md) - - -- [安装方式介绍](安装方式介绍.md) - - [通过光盘安装](通过光盘安装.md) - - [通过USB盘安装](通过USB盘安装.md) - - [使用PXE通过网络安装](使用PXE通过网络安装.md) - - [通过qcow2镜像安装](通过qcow2镜像安装.md) - - [通过私有镜像安装](通过私有镜像安装.md) - -- [安装指导](安装指导.md) - - [启动安装](启动安装.md) - - [通过图形化模式安装](通过图形化模式安装.md) - - [设置安装程序语言](设置安装程序语言.md) - - [进入安装界面](进入安装界面.md) - - [设置安装参数](设置安装参数.md) - - [设置键盘](设置键盘.md) - - [设置系统语言](设置系统语言.md) - - [设置时间和日期](设置时间和日期.md) - - [设置安装源](设置安装源.md) - - [选择安装软件](选择安装软件.md) - - [设置安装位置](设置安装位置.md) - - [设置网络和主机名](设置网络和主机名.md) - - - [开始安装](开始安装.md) - - [安装过程配置](安装过程配置.md) - - [安装完成](安装完成.md) - - -- [使用kickstart自动化安装](使用kickstart自动化安装.md) - - [总体介绍](总体介绍.md) - - [半自动化安装指导](半自动化安装指导.md) - - [全自动化安装指导](全自动化安装指导.md) - -- [FAQ](FAQ.md) - - [安装openEuler时选择第二盘位为安装目标，操作系统无法启动](安装openEuler时选择第二盘位为安装目标-操作系统无法启动.md) - - [网络配置约束限制](网络配置约束限制.md) - - [openEuler开机后进入emergency模式](openEuler开机后进入emergency模式.md) - - [系统中存在无法激活的逻辑卷组时，重装系统失败](系统中存在无法激活的逻辑卷组时-重装系统失败.md) - - [选择安装源出现异常](选择安装源出现异常.md) - - [如何手动开启kdump服务](如何手动开启kdump服务.md) - - [多块磁盘组成逻辑卷安装系统后，再次安装不能只选其中一块磁盘](多块磁盘组成逻辑卷安装系统后-再次安装不能只选其中一块磁盘.md) - - [x86物理机UEFI模式由于security boot安全选项问题无法安装](x86物理机UEFI模式由于security-boot安全选项问题无法安装.md) - - diff --git "a/content/zh/docs/Installation/\344\275\277\347\224\250PXE\351\200\232\350\277\207\347\275\221\347\273\234\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/\344\275\277\347\224\250PXE\351\200\232\350\277\207\347\275\221\347\273\234\345\256\211\350\243\205.md" deleted file mode 100644 index bf2ac3d3ef4e4312f61aa1b3d8a6f345eaaf45e3..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\344\275\277\347\224\250PXE\351\200\232\350\277\207\347\275\221\347\273\234\345\256\211\350\243\205.md" +++ /dev/null @@ -1,11 +0,0 @@ -# 使用PXE通过网络安装 - -要使用 PXE 引导，您需要正确配置服务器以及您的计算机需支持 PXE 的网络接口。 - -如果目标硬件安装有支持PXE的网络接口卡，我们可以配置它从其他网络系统的文件而不是本地介质（如光盘）来引导计算机并执行Anaconda安装程序。 - -对于PXE网络安装，客户机通过支持PXE的网卡，向网络发送请求DHCP信息的广播，请求IP地址等信息。DHCP服务器给客户机提供一个IP地址和其他网络信息如域名服务器、ftp服务器（它提供启动安装程序所必须的文件）的IP地址或主机名，以及服务器上文件的位置。 - ->![](public_sys-resources/icon-note.gif) **说明：** ->此处不详细讨论tftp、DHCP、http等服务器配置，相关详细配置请参考“使用kickstart自动化安装 \> 全自动化安装指导”章节。 - diff --git "a/content/zh/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md" index b102fac965b7d9bf11e08634b9122b19281084f5..619e0702e2432b5e931bbc975625d32cf4da1891 100644 --- "a/content/zh/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md" +++ "b/content/zh/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md" @@ -1,4 +1,364 @@ -# 使用kickstart自动化安装 +# 使用kickstart自动化安装 + +- [使用kickstart自动化安装](#使用kickstart自动化安装) + - [总体介绍](#总体介绍) + - [概述](#概述) + - [优缺点对比](#优缺点对比) + - [背景知识](#背景知识) + - [半自动化安装指导](#半自动化安装指导) + - [环境要求](#环境要求) + - [操作步骤](#操作步骤) + - [全自动化安装指导](#全自动化安装指导) + - [环境要求](#环境要求-1) + - [操作步骤](#操作步骤-1) + + +## 总体介绍 + +### 概述 + +用户可以使用kickstart工具进行openEuler系统的自动化安装，包括如下两种方式： + +- 半自动化安装：安装人员不需要手动设定操作系统的键盘、语言、分区等具体属性（通过kickstart实现自动化），但是需要手动指定kickstart文件的位置。 +- 全自动化安装：实现操作系统的安装过程全自动化。 + +### 优缺点对比 + +使用kickstart工具进行半自动化安装和全自动化安装的优缺点对比如[表1](#table1388812373315)所示，用户可以自行选择安装方式。 + +**表 1** 优缺点对比 + + + + + + + + + + + + + + + + +

安装方式

+

优点

+

缺点

+

半自动化安装

+

不需要准备tftp，pxe，dhcp等服务

+

需要手动指定kickstart文件的位置

+

全自动化安装

+

操作系统的全自动化安装

+

需要配置tftp，dhcpd，pxe等服务

+
+ +### 背景知识 + +**kickstart** + +kickstart是一种无人值守的安装方式。它的工作原理是在安装过程中记录典型的需要人工干预填写的各种参数，并生成一个配置文件（ks.cfg），在安装过程中，安装程序首先会去查找ks配置文件，如果找到合适的参数，就采用所找到的参数；如果没有找到合适的参数，便需要安装者手工设定。所以，如果kickstart文件涵盖了安装过程中需要设定的所有参数，安装者只需要告诉安装程序从何处取ks.cfg文件，就能实现系统安装的自动化。 + +kickstart 安装提供一个安装过程自动化的方法，可以是部分自动化，也可以是完全自动化。 + +**PXE** + +PXE（Pre-boot Execution Environment，预启动执行环境），工作于Client/Server的网络模式，支持PXE的客户端在启动过程中，能够从DHCP服务器获取IP结合TFTP（trivial file transfer protocol）等协议可以实现客户端的网络引导和安装。 + +**TFTP** + +TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议用来实现客户机与服务器之间的简单文件传输，它提供不复杂、开销不大的文件传输服务。 + +## 半自动化安装指导 + +### 环境要求 + +使用kickstart进行openEuler系统的半自动化安装的环境要求如下： + +- 物理机/虚拟机（虚拟机创建可参考对应厂商的资料）。包括使用kickstart工具进行自动化安装的计算机和被安装的计算机。 +- httpd：存放kickstart文件。 +- ISO： openEuler-20.03-LTS-aarch64-dvd.iso + +### 操作步骤 + +使用kickstart进行openEuler系统的半自动化安装的操作步骤如下： + +**环境准备** + +>![](public_sys-resources/icon-note.gif) **说明：** +>安装之前，请确保http服务器的防火墙处于关闭状态。关闭防火墙可参照如下命令： +>``` +>iptables -F +>``` + +1. httpd的安装与服务启动。 + + ``` + # dnf install httpd -y + # systemctl start httpd + # systemctl enable httpd + ``` + +2. kickstart文件的准备。 + + ``` + # mkdir /var/www/html/ks + # vim /var/www/html/ks/openEuler-ks.cfg ===>根据已安装openEuler系统自动生成的anaconda-ks.cfg修改得到，也可以使用system-config-kickstart工具做成 + ==================================== + ***以下内容需要根据实际需求进行修改*** + #version=DEVEL + ignoredisk --only-use=sda + autopart --type=lvm + # Partition clearing information + clearpart --none --initlabel + # Use graphical install + graphical + # Use CDROM installation media + cdrom + # Keyboard layouts + keyboard --vckeymap=cn --xlayouts='cn' + # System language + lang zh_CN.UTF-8 + + # Network information + network --bootproto=dhcp --device=enp4s0 --ipv6=auto --activate + network --hostname=openeuler.com + # Root password + rootpw --iscrypted $6$fQE83lxEZ48Or4zc$j7/PlUMHn29yTjCD4Fi44WTZL/RzVGxJ/7MGsZMl6QfE3KjIVT7M4UrhFXbafvRq2lUddAFcyWHd5WRmXfEK20 + # Run the Setup Agent on first boot + firstboot --enable + # Do not configure the X Window System + skipx + # System services + services --disabled="chronyd" + # System timezone + timezone Asia/Shanghai --isUtc--nontp + + %packages + @^minimal-environment + @standard + + %end + + %anaconda + pwpolicy root --minlen=8 --minquality=1 --notstrict --nochanges --notempty + pwpolicy user --minlen=8 --minquality=1 --notstrict --nochanges --emptyok + pwpolicy luks --minlen=8 --minquality=1 --notstrict --nochanges --notempty + %end + + %post + #enable kdump + sed -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg + %end + ===================================== + ``` + + >![](public_sys-resources/icon-note.gif) **说明：** + >密码密文生成方式： + >\# python3 + >Python 3.7.0 \(default, Apr 1 2019, 00:00:00\) + >\[GCC 7.3.0\] on linux + >Type "help", "copyright", "credits" or "license" for more information. + >\>\>\> import crypt + >\>\>\> passwd = crypt.crypt\("myPasswd"\) + >\>\>\> print\(passwd\) + >$6$63c4tDmQGn5SDayV$mZoZC4pa9Jdt6/ALgaaDq6mIExiOO2EjzomB.Rf6V1BkEMJDcMddZeGdp17cMyc9l9ML9ldthytBEPVcnboR/0 + +3. 将ISO镜像文件挂载到需要安装openEuler计算机的光驱上。 + + 另外，也可以选择NFS等网络安装，kickstart文件中需要指定安装源位置（默认是cdrom）。 + + +**安装系统** + +1. 启动系统进入安装选择界面。 + 1. 在“[启动安装](安装指导.html#启动安装)”中的“安装引导界面”中选择“Install openEuler 20.03 LTS”，并按下“e”键。 + 2. 启动参数中追加“inst.ks=http://server ip/ks/openEuler-ks.cfg”。 + + ![](figures/半自动-new.png) + + 3. 按“Ctrl+x”，开始系统的自动安装。 + +2. 确认系统安装完毕。 + + 系统安装完毕以后会自动重启，然后再次进入到安装界面，此时关闭计算机，调整启动顺序（优先从硬盘启动）。 + + ![](figures/自动化安装完成.png) + + +## 全自动化安装指导 + +### 环境要求 + +使用kickstart进行openEuler系统的全自动化安装的环境要求如下： + +- 物理机/虚拟机（虚拟机创建可参考对应厂商的资料）。包括使用kickstart工具进行自动化安装的计算机和被安装的计算机。 +- httpd：存放kickstart文件。 +- tftp：提供vmlinuz和initrd文件。 +- dhcpd/pxe：提供DHCP服务。 +- ISO：openEuler-20.03-LTS-aarch64-dvd.iso。 + +### 操作步骤 + +使用kickstart进行openEuler系统的全自动化安装的操作步骤如下： + +**环境准备** + +>![](public_sys-resources/icon-note.gif) **说明：** +>安装之前，请确保http服务器的防火墙处于关闭状态。关闭防火墙可参照如下命令： +>``` +>iptables -F +>``` + +1. httpd的安装与服务启动。 + + ``` + # dnf install httpd -y + # systemctl start httpd + # systemctl enable httpd + ``` + +2. tftp的安装与配置。 + + ``` + # dnf install tftp-server -y + # vim /etc/xinetd.d/tftp + service tftp + { + socket_type = dgram + protocol = udp + wait = yes + user = root + server = /usr/sbin/in.tftpd + server_args = -s /var/lib/tftpboot + disable = no + per_source = 11 + cps = 100 2 + flags = IPv4 + } + # systemctl start tftp + # systemctl enable tftp + # systemctl start xinetd + # systemctl status xinetd + # systemctl enable xinetd + ``` + +3. 安装源的制作。 + + ``` + # mount openEuler-20.03-LTS-aarch64-dvd.iso /mnt + # cp -r /mnt/* /var/www/html/openEuler/ + ``` + +4. 设置和修改kickstart配置文件 openEuler-ks.cfg，参考[3](#zh-cn_topic_0151920754_l1692f6b9284e493683ffa2ef804bc7ca)安装源的目录，此处选择http安装源。 + + ``` + #vim /var/www/html/ks/openEuler-ks.cfg + ==================================== + ***以下内容根据实际需求进行修改*** + #version=DEVEL + ignoredisk --only-use=sda + autopart --type=lvm + # Partition clearing information + clearpart --none --initlabel + # Use graphical install + graphical + # Keyboard layouts + keyboard --vckeymap=cn --xlayouts='cn' + # System language + lang zh_CN.UTF-8 + #Use http installation source + url --url=//192.168.122.1/openEuler/ + %post + #enable kdump + sed -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg + %end + ... + ``` + +5. 修改pxe配置文件grub.cfg， 可参考如下内容。 + + ``` + # cp -r /mnt/images/pxeboot/* /var/lib/tftpboot/ + # cp /mnt/EFI/BOOT/grubaa64.efi /var/lib/tftpboot/ + # cp /mnt/EFI/BOOT/grub.cfg /var/lib/tftpboot/ + # ls /var/lib/tftpboot/ + grubaa64.efi grub.cfg initrd.img TRANS.TBL vmlinuz + # vim /var/lib/tftpboot/grub.cfg + set default="1" + + function load_video { + if [ x$feature_all_video_module = xy ]; then + insmod all_video + else + insmod efi_gop + insmod efi_uga + insmod ieee1275_fb + insmod vbe + insmod vga + insmod video_bochs + insmod video_cirrus + fi + } + + load_video + set gfxpayload=keep + insmod gzio + insmod part_gpt + insmod ext2 + + set timeout=60 + + + ### BEGIN /etc/grub.d/10_linux ### + menuentry 'Install openEuler 20.03 LTS' --class red --class gnu-linux --class gnu --class os { + set root=(tftp,192.168.1.1) + linux /vmlinuz ro inst.geoloc=0 console=ttyAMA0 console=tty0 rd.iscsi.waitnet=0 inst.ks=http://192.168.122.1/ks/openEuler-ks.cfg + initrd /initrd.img + } + ``` + +6. DHCP的配置（可以使用dnsmasq代替 ）。 + + ``` + # dnf install dhcp -y + # + # DHCP Server Configuration file. + # see /usr/share/doc/dhcp-server/dhcpd.conf.example + # see dhcpd.conf(5) man page + # + # vim /etc/dhcp/dhcpd.conf + ddns-update-style interim; + ignore client-updates; + filename "grubaa64.efi"; 　　 # pxelinux 启动文件位置; + next-server 192.168.122.1;　　# (重要)TFTP Server 的IP地址; + subnet 192.168.122.0 netmask 255.255.255.0 { + option routers 192.168.111.1; # 网关地址 + option subnet-mask 255.255.255.0; # 子网掩码 + range dynamic-bootp 192.168.122.50 192.168.122.200; # 动态ip范围 + default-lease-time 21600; + max-lease-time 43200; + } + # systemctl start dhcpd + # systemctl enable dhcpd + ``` + + +**安装系统** + +1. 在“Start boot option”界面按下“F2”选择从网络pxe启动，开始自动化安装。 + + ![](figures/zh-cn_image_0229291270.png) + + ![](figures/zh-cn_image_0229291286.png) + + ![](figures/zh-cn_image_0229291247.png) + +2. 进入系统全自动化安装界面。 +3. 确认系统安装完毕。 + + ![](figures/自动化安装完成.png) diff --git "a/content/zh/docs/Installation/\345\205\250\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205\346\214\207\345\257\274.md" "b/content/zh/docs/Installation/\345\205\250\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205\346\214\207\345\257\274.md" deleted file mode 100644 index 68f6f9eaca0ba4a7e9ce1b39cefcdc4462e249d5..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\205\250\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205\346\214\207\345\257\274.md" +++ /dev/null @@ -1,174 +0,0 @@ -# 全自动化安装指导 - -## 环境要求 - -使用kickstart进行openEuler系统的全自动化安装的环境要求如下： - -- 物理机/虚拟机（虚拟机创建可参考对应厂商的资料）。包括使用kickstart工具进行自动化安装的计算机和被安装的计算机。 -- httpd：存放kickstart文件。 -- tftp：提供vmlinuz和initrd文件。 -- dhcpd/pxe：提供DHCP服务。 -- ISO：openEuler-20.03-LTS-aarch64-dvd.iso。 - -## 操作步骤 - -使用kickstart进行openEuler系统的全自动化安装的操作步骤如下： - -**环境准备** - ->![](public_sys-resources/icon-note.gif) **说明：** ->安装之前，请确保http服务器的防火墙处于关闭状态。关闭防火墙可参照如下命令： ->``` ->iptables -F ->``` - -1. httpd的安装与服务启动。 - - ``` - # dnf install httpd -y - # systemctl start httpd - # systemctl enable httpd - ``` - -2. tftp的安装与配置。 - - ``` - # dnf install tftp-server -y - # vim /etc/xinetd.d/tftp - service tftp - { - socket_type = dgram - protocol = udp - wait = yes - user = root - server = /usr/sbin/in.tftpd - server_args = -s /var/lib/tftpboot - disable = no - per_source = 11 - cps = 100 2 - flags = IPv4 - } - # systemctl start tftp - # systemctl enable tftp - # systemctl start xinetd - # systemctl status xinetd - # systemctl enable xinetd - ``` - -3. 安装源的制作。 - - ``` - # mount openEuler-20.03-LTS-aarch64-dvd.iso /mnt - # cp -r /mnt/* /var/www/html/openEuler/ - ``` - -4. 设置和修改kickstart配置文件 openEuler-ks.cfg，参考[3](#zh-cn_topic_0151920754_l1692f6b9284e493683ffa2ef804bc7ca)安装源的目录，此处选择http安装源。 - - ``` - #vim /var/www/html/ks/openEuler-ks.cfg - ==================================== - ***以下内容根据实际需求进行修改*** - #version=DEVEL - ignoredisk --only-use=sda - autopart --type=lvm - # Partition clearing information - clearpart --none --initlabel - # Use graphical install - graphical - # Keyboard layouts - keyboard --vckeymap=cn --xlayouts='cn' - # System language - lang zh_CN.UTF-8 - #Use http installation source - url --url=//192.168.122.1/openEuler/ - %post - #enable kdump - sed -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg - %end - ... - ``` - -5. 修改pxe配置文件grub.cfg， 可参考如下内容。 - - ``` - # cp -r /mnt/images/pxeboot/* /var/lib/tftpboot/ - # cp /mnt/EFI/BOOT/grubaa64.efi /var/lib/tftpboot/ - # cp /mnt/EFI/BOOT/grub.cfg /var/lib/tftpboot/ - # ls /var/lib/tftpboot/ - grubaa64.efi grub.cfg initrd.img TRANS.TBL vmlinuz - # vim /var/lib/tftpboot/grub.cfg - set default="1" - - function load_video { - if [ x$feature_all_video_module = xy ]; then - insmod all_video - else - insmod efi_gop - insmod efi_uga - insmod ieee1275_fb - insmod vbe - insmod vga - insmod video_bochs - insmod video_cirrus - fi - } - - load_video - set gfxpayload=keep - insmod gzio - insmod part_gpt - insmod ext2 - - set timeout=60 - - - ### BEGIN /etc/grub.d/10_linux ### - menuentry 'Install openEuler 20.03 LTS' --class red --class gnu-linux --class gnu --class os { - set root=(tftp,192.168.1.1) - linux /vmlinuz ro inst.geoloc=0 console=ttyAMA0 console=tty0 rd.iscsi.waitnet=0 inst.ks=http://192.168.122.1/ks/openEuler-ks.cfg - initrd /initrd.img - } - ``` - -6. DHCP的配置（可以使用dnsmasq代替 ）。 - - ``` - # dnf install dhcp -y - # - # DHCP Server Configuration file. - # see /usr/share/doc/dhcp-server/dhcpd.conf.example - # see dhcpd.conf(5) man page - # - # vim /etc/dhcp/dhcpd.conf - ddns-update-style interim; - ignore client-updates; - filename "grubaa64.efi"; 　　 # pxelinux 启动文件位置; - next-server 192.168.122.1;　　# (重要)TFTP Server 的IP地址; - subnet 192.168.122.0 netmask 255.255.255.0 { - option routers 192.168.111.1; # 网关地址 - option subnet-mask 255.255.255.0; # 子网掩码 - range dynamic-bootp 192.168.122.50 192.168.122.200; # 动态ip范围 - default-lease-time 21600; - max-lease-time 43200; - } - # systemctl start dhcpd - # systemctl enable dhcpd - ``` - - -**安装系统** - -1. 在“Start boot option”界面按下“F2”选择从网络pxe启动，开始自动化安装。 - - ![](figures/zh-cn_image_0229291270.png) - - ![](figures/zh-cn_image_0229291286.png) - - ![](figures/zh-cn_image_0229291247.png) - -2. 进入系统全自动化安装界面。 -3. 确认系统安装完毕。 - - ![](figures/自动化安装完成.png) - - diff --git "a/content/zh/docs/Installation/\345\211\215\350\250\200.md" "b/content/zh/docs/Installation/\345\211\215\350\250\200.md" deleted file mode 100644 index 63587aa05939fe80793ce82055b0c6e99a4f0a05..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\211\215\350\250\200.md" +++ /dev/null @@ -1,36 +0,0 @@ -# 前言 - -## 概述 - -本文档主要介绍openEuler操作系统安装方法，以指导用户顺利完成openEuler操作系统安装。 - -## 读者对象 - -本文档适用于所有使用openEuler操作系统的用户，特别是初次使用或想了解openEuler的用户，包括系统工程师、管理员及维护人员等。使用本手册的用户需要具备基础的Linux系统管理知识。 - -## 符号约定 - -在本文中可能出现下列标志，它们所代表的含义如下。 - - - - - - - - - - - - - -

符号

-

说明

-

-

用于传递设备或环境安全警示信息。如不避免则可能会导致设备损坏、数据丢失、设备性能降低或其它不可预知的结果。

-

“须知”不涉及人身伤害。

-

-

对正文中重点信息的补充说明。

-

“说明”不是安全警示信息，不涉及人身、设备及环境伤害信息。

-
- diff --git "a/content/zh/docs/Installation/\345\215\212\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205\346\214\207\345\257\274.md" "b/content/zh/docs/Installation/\345\215\212\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205\346\214\207\345\257\274.md" deleted file mode 100644 index d70e7f833bc13929c2cfb526a2ff0b871fcd8ab2..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\215\212\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205\346\214\207\345\257\274.md" +++ /dev/null @@ -1,117 +0,0 @@ -# 半自动化安装指导 - -## 环境要求 - -使用kickstart进行openEuler系统的半自动化安装的环境要求如下： - -- 物理机/虚拟机（虚拟机创建可参考对应厂商的资料）。包括使用kickstart工具进行自动化安装的计算机和被安装的计算机。 -- httpd：存放kickstart文件。 -- ISO： openEuler-20.03-LTS-aarch64-dvd.iso - -## 操作步骤 - -使用kickstart进行openEuler系统的半自动化安装的操作步骤如下： - -**环境准备** - ->![](public_sys-resources/icon-note.gif) **说明：** ->安装之前，请确保http服务器的防火墙处于关闭状态。关闭防火墙可参照如下命令： ->``` ->iptables -F ->``` - -1. httpd的安装与服务启动。 - - ``` - # dnf install httpd -y - # systemctl start httpd - # systemctl enable httpd - ``` - -2. kickstart文件的准备。 - - ``` - # mkdir /var/www/html/ks - # vim /var/www/html/ks/openEuler-ks.cfg ===>根据已安装openEuler系统自动生成的anaconda-ks.cfg修改得到，也可以使用system-config-kickstart工具做成 - ==================================== - ***以下内容需要根据实际需求进行修改*** - #version=DEVEL - ignoredisk --only-use=sda - autopart --type=lvm - # Partition clearing information - clearpart --none --initlabel - # Use graphical install - graphical - # Use CDROM installation media - cdrom - # Keyboard layouts - keyboard --vckeymap=cn --xlayouts='cn' - # System language - lang zh_CN.UTF-8 - - # Network information - network --bootproto=dhcp --device=enp4s0 --ipv6=auto --activate - network --hostname=openeuler.com - # Root password - rootpw --iscrypted $6$fQE83lxEZ48Or4zc$j7/PlUMHn29yTjCD4Fi44WTZL/RzVGxJ/7MGsZMl6QfE3KjIVT7M4UrhFXbafvRq2lUddAFcyWHd5WRmXfEK20 - # Run the Setup Agent on first boot - firstboot --enable - # Do not configure the X Window System - skipx - # System services - services --disabled="chronyd" - # System timezone - timezone Asia/Shanghai --isUtc--nontp - - %packages - @^minimal-environment - @standard - - %end - - %anaconda - pwpolicy root --minlen=8 --minquality=1 --notstrict --nochanges --notempty - pwpolicy user --minlen=8 --minquality=1 --notstrict --nochanges --emptyok - pwpolicy luks --minlen=8 --minquality=1 --notstrict --nochanges --notempty - %end - - %post - #enable kdump - sed -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg - %end - ===================================== - ``` - - >![](public_sys-resources/icon-note.gif) **说明：** - >密码密文生成方式： - >\# python3 - >Python 3.7.0 \(default, Apr 1 2019, 00:00:00\) - >\[GCC 7.3.0\] on linux - >Type "help", "copyright", "credits" or "license" for more information. - >\>\>\> import crypt - >\>\>\> passwd = crypt.crypt\("myPasswd"\) - >\>\>\> print\(passwd\) - >$6$63c4tDmQGn5SDayV$mZoZC4pa9Jdt6/ALgaaDq6mIExiOO2EjzomB.Rf6V1BkEMJDcMddZeGdp17cMyc9l9ML9ldthytBEPVcnboR/0 - -3. 将ISO镜像文件挂载到需要安装openEuler计算机的光驱上。 - - 另外，也可以选择NFS等网络安装，kickstart文件中需要指定安装源位置（默认是cdrom）。 - - -**安装系统** - -1. 启动系统进入安装选择界面。 - 1. 在“安装指导 \> 启动安装”章节中的“安装引导界面”中选择“Install openEuler 20.03 LTS”，并按下“e”键。 - 2. 启动参数中追加“inst.ks=http://server ip/ks/openEuler-ks.cfg”。 - - ![](figures/半自动-new.png) - - 3. 按“Ctrl+x”，开始系统的自动安装。 - -2. 确认系统安装完毕。 - - 系统安装完毕以后会自动重启，然后再次进入到安装界面，此时关闭计算机，调整启动顺序（优先从硬盘启动）。 - - ![](figures/自动化安装完成.png) - - diff --git "a/content/zh/docs/Installation/\345\217\221\345\270\203\345\214\205\345\256\214\346\225\264\346\200\247\346\240\241\351\252\214.md" "b/content/zh/docs/Installation/\345\217\221\345\270\203\345\214\205\345\256\214\346\225\264\346\200\247\346\240\241\351\252\214.md" deleted file mode 100644 index ea73c23d67a7af454bb9aec889a71e2509f410c7..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\217\221\345\270\203\345\214\205\345\256\214\346\225\264\346\200\247\346\240\241\351\252\214.md" +++ /dev/null @@ -1,41 +0,0 @@ -# 发布包完整性校验 ->![](public_sys-resources/icon-note.gif) **说明：** ->本章节以AArch64架构的发布包完整性校验为例，x86\_64架构的发布包完整性校验的操作方法相同。 - -## 简介 - -为了防止软件包在传输过程中由于网络原因或者存储设备原因出现下载不完整的问题，在获取到软件包后，需要对软件包的完整性进行校验，通过了校验的软件包才能部署。 - -这里通过对比校验文件中记录的校验值和手动方式计算的iso文件校验值，判断软件包是否完成。若两个值相同，说明iso文件完整，否则，iso完整性被破坏，请重新获取iso发布包。 - -## 前提条件 - -在校验发布包完整性之前，需要准备如下文件： - -iso文件：openEuler-20.03-LTS-aarch64-dvd.iso - -校验文件：openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum - -## 操作指导 - -文件完整性校验操作步骤如下： - -1. 获取校验文件中的校验值。执行命令如下： - - ``` - #cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum - ``` - -2. 计算文件的sha256校验值。执行命令如下： - - ``` - #sha256sum openEuler-20.03-LTS-aarch64-dvd.iso - ``` - - 命令执行完成后，输出校验值。 - -3. 对比步骤1和步骤2计算的校验值是否一致。 - - 如果校验值一致说明iso文件完整性没有破坏，如果校验值不一致则可以确认文件完整性已被破坏，需要重新获取。 - - diff --git "a/content/zh/docs/Installation/\345\220\257\345\212\250\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/\345\220\257\345\212\250\345\256\211\350\243\205.md" deleted file mode 100644 index 4b728aecaeebdc0e90b53d584e7ebc556fc620b0..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\220\257\345\212\250\345\256\211\350\243\205.md" +++ /dev/null @@ -1,66 +0,0 @@ -# 启动安装 - -## 使用光盘引导安装 - -在服务器的光驱中加载openEuler安装镜像，重启服务器，具体步骤如下。 - ->![](public_sys-resources/icon-note.gif) **说明：** ->在安装开始前，需要保证服务器启动选项为光驱优先。安装步骤以BMC挂载虚拟光驱进行光盘安装的操作举例。通过物理光驱安装的操作简单，启动安装后的流程相同，在此不再说明。 - -1. 在虚拟界面工具栏中，单击虚拟光驱工具如下图所示。 - - **图 1** 光驱图标 - ![](figures/光驱图标.png "光驱图标") - - 弹出镜像对话框，如下图所示。 - - **图 2** 镜像对话框 - ![](figures/镜像对话框.png "镜像对话框") - -2. 在镜像对话框中，选择“镜像文件”， 并单击“浏览”。弹出“打开”对话框。 -3. 选择镜像文件，单击“打开”。然后在镜像对话框中，单击“连接”。当“连接”显示为“断开”后，表示虚拟光驱已连接到服务器。 -4. 在工具栏中，单击重启工具重启设备，如下图所示。 - - **图 3** 重启图标 - ![](figures/重启图标.png "重启图标") - - -## 安装引导界面 - -系统使用引导介质完成引导后会显示引导菜单。该引导菜单除启动安装程序外还提供一些选项。安装系统时，默认采用“Test this media & install openEuler 20.03 LTS”方式进行安装。如果要选择默认选项之外的选项，请使用键盘中的“↑”和“↓”方向键进行选择，并在选项为高亮状态时按“Enter”。 - ->![](public_sys-resources/icon-note.gif) **说明：** ->- 如果60秒内未按任何键，系统将从默认选项“Test this media & install openEuler 20.03 LTS”自动进入安装界面。 ->- 安装物理机时，如果使用键盘上下键无法选择启动选项，按“Enter”键无响应，可以单击BMC界面上的鼠标控制图标“![](figures/zh-cn_image_0229420473.png)”，设置“键鼠复位”。 - -**图 4** 安装引导界面 -![](figures/安装引导界面.png "安装引导界面") - -安装引导选项说明如下： - -- Install openEuler 20.03 LTS —— 在您的服务器上使用图形用户界面模式安装。 - -- Test this media & install openEuler 20.03 LTS —— 默认选项，在您的服务器上使用图形用户界面模式安装，但在启动安装程序前会进行安装介质的完整性检查。详见“安装指导 \> 通过图形化模式安装”章节。 - -- Troubleshooting —— 问题定位模式，系统无法正常安装时使用。进入问题定位模式后，有如下两个选项。 - - Install openEuler 20.03-LTS in basic graphics mode —— 简单图形安装模式，该模式下在系统启动并运行之前不启动视频驱动程序。 - - Rescue the openEuler system —— 救援模式，用于修复系统。该模式下输出定向到VNC或BMC（Baseboard Management Controller）端，串口不可用。 - -在安装引导界面，按“e”进入已选选项的参数编辑界面，按“c”进入命令行模式。 - -## 图形化模式安装 - -在“安装引导界面”中选择“Test this media & install openEuler 20.03 LTS”进入图形化模式安装。 - -可以通过键盘操作图形化安装程序。 - -- “Tab”、“shift Tab”：界面控件（按钮、区域框、复选框等）间的移动。 -- “↑”、“↓”方向键：列表里的移动。 -- “←”、“→”方向键：水平工具条和表条间移动。 -- “空格”、“Enter”：选择或删除高亮显示的选项、展开或折叠下拉菜单。 -- “Alt”+“快捷键”：选择快捷键所在的控件，其中快捷键可通过按住Alt高亮（加下划线）显示。 - - - - - diff --git "a/content/zh/docs/Installation/\345\244\232\345\235\227\347\243\201\347\233\230\347\273\204\346\210\220\351\200\273\350\276\221\345\215\267\345\256\211\350\243\205\347\263\273\347\273\237\345\220\216-\345\206\215\346\254\241\345\256\211\350\243\205\344\270\215\350\203\275\345\217\252\351\200\211\345\205\266\344\270\255\344\270\200\345\235\227\347\243\201\347\233\230.md" "b/content/zh/docs/Installation/\345\244\232\345\235\227\347\243\201\347\233\230\347\273\204\346\210\220\351\200\273\350\276\221\345\215\267\345\256\211\350\243\205\347\263\273\347\273\237\345\220\216-\345\206\215\346\254\241\345\256\211\350\243\205\344\270\215\350\203\275\345\217\252\351\200\211\345\205\266\344\270\255\344\270\200\345\235\227\347\243\201\347\233\230.md" deleted file mode 100644 index 689d9c44876b318eaa9e4fdc866acf2657ee1f2d..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\244\232\345\235\227\347\243\201\347\233\230\347\273\204\346\210\220\351\200\273\350\276\221\345\215\267\345\256\211\350\243\205\347\263\273\347\273\237\345\220\216-\345\206\215\346\254\241\345\256\211\350\243\205\344\270\215\350\203\275\345\217\252\351\200\211\345\205\266\344\270\255\344\270\200\345\235\227\347\243\201\347\233\230.md" +++ /dev/null @@ -1,41 +0,0 @@ -# 多块磁盘组成逻辑卷安装系统后，再次安装不能只选其中一块磁盘 - -## 问题现象 - -在安装系统时，如果之前的系统选择多块磁盘组成逻辑卷进行安装，再次安装时，如果只选择了其中的一块或几块磁盘，没有全部选择，在保存配置时提示配置错误，如[图1](#fig115949762617)所示。 - -**图 1** 配置错误提示 -![](figures/配置错误提示.png "配置错误提示") - -## 原因分析 - -之前的逻辑卷包含了多块磁盘，只在一块磁盘上安装会破坏逻辑卷。 - -## 解决方法 - -因为多块磁盘组成逻辑卷相当于一个整体，所以只需要删除对应的卷组即可。 - -1. 按“Ctrl+Alt+F2”可以切换到命令行，执行如下命令找到卷组。 - - ``` - vgs - ``` - - ![](figures/zh-cn_image_0231657950.png) - -2. 执行如下命令，删除卷组。 - - ``` - vgremove euleros - ``` - -3. 执行如下命令，重启安装程序即可生效。 - - ``` - systemctl restart anaconda - ``` - - >![](public_sys-resources/icon-note.gif) **说明：** - >图形模式下也可以按“Ctrl+Alt+F6”回到图形界面，点击[图1](#fig115949762617)右下角的“Refresh”刷新存储配置生效。 - - diff --git "a/content/zh/docs/Installation/\345\246\202\344\275\225\346\211\213\345\212\250\345\274\200\345\220\257kdump\346\234\215\345\212\241.md" "b/content/zh/docs/Installation/\345\246\202\344\275\225\346\211\213\345\212\250\345\274\200\345\220\257kdump\346\234\215\345\212\241.md" deleted file mode 100644 index 3232008c0dd65db9a5b0224a0ae56697ce25c606..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\246\202\344\275\225\346\211\213\345\212\250\345\274\200\345\220\257kdump\346\234\215\345\212\241.md" +++ /dev/null @@ -1,86 +0,0 @@ -# 如何手动开启kdump服务 - -## 问题现象 - -执行systemctl status kdump命令，显示状态信息如下，提示无预留内存。 - -![](figures/zh-cn_image_0229291280.png) - -## 原因分析 - -kdump服务需要系统预留一段内存用于运行kdump内核，而当前系统没有为kdump服务预留内存，所以无法运行kdump服务。 - -## 解决方法 - -已安装操作系统的场景 - -1. 修改/boot/efi/EFI/openEuler/grub.cfg，添加crashkernel=1024M,high。 -2. 重启系统使配置生效。 -3. 执行如下命令，检查kdump状态： - - ``` - systemctl status kdump - ``` - - 若回显如下，即kdump的状态为active，说明kdump已使能，操作结束。 - - ![](figures/zh-cn_image_0229291272.png) - - -## 参数说明 - -kdump内核预留内存参数说明如下： - -**表 1** crashkernel参数说明 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

内核启动参数

-

描述

-

默认值

-

备注

-

crashkernel=X

-

在4G以下的物理内存预留X大小的内存给kdump使用

-

无，用户根据实际情况调整

-

该配置方法只在4G以下内存预留，必须保证4G以下连续可用内存足够预留

-

crashkernel=X@Y

-

在Y起始地址预留X大小的内存给kdump使用

-

无，用户根据实际情况调整

-

需要确保Y起始地址的X大小内存未被其他模块预留

-

crashkernel=X,high

-

在4G以下的物理内存中预留256M大小，在4G以上预留X大小内存给kdump使用

-

无，用户根据实际情况调整，推荐值为1024M,high

-

确保4G以下内存有256M连续可用内存，4G以上有连续X大小内存可预留。实际预留内存大小为256M+X

-

crashkernel=X,low

-

crashkernel=Y,high

-

在4G以下的物理内存中预留X大小，在4G以上预留Y大小内存给kdump使用

-

无，用户根据实际情况调整

-

需要确保4G以下有X大小连续可用内存，4G以上有Y大小连续可用内存。实际预留内存大小为X+Y

-
- diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205openEuler\346\227\266\351\200\211\346\213\251\347\254\254\344\272\214\347\233\230\344\275\215\344\270\272\345\256\211\350\243\205\347\233\256\346\240\207-\346\223\215\344\275\234\347\263\273\347\273\237\346\227\240\346\263\225\345\220\257\345\212\250.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205openEuler\346\227\266\351\200\211\346\213\251\347\254\254\344\272\214\347\233\230\344\275\215\344\270\272\345\256\211\350\243\205\347\233\256\346\240\207-\346\223\215\344\275\234\347\263\273\347\273\237\346\227\240\346\263\225\345\220\257\345\212\250.md" deleted file mode 100644 index c3807db71a5fa07b4a07c81c2e4309b5a09cd03b..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205openEuler\346\227\266\351\200\211\346\213\251\347\254\254\344\272\214\347\233\230\344\275\215\344\270\272\345\256\211\350\243\205\347\233\256\346\240\207-\346\223\215\344\275\234\347\263\273\347\273\237\346\227\240\346\263\225\345\220\257\345\212\250.md" +++ /dev/null @@ -1,22 +0,0 @@ -# 安装openEuler时选择第二盘位为安装目标，操作系统无法启动 - -## 问题现象 - -安装操作系统时，直接将系统安装到第二块磁盘sdb，重启系统后启动失败。 - -## 原因分析 - -当安装系统到第二块磁盘时，MBR和GRUB会默认安装到第二块磁盘sdb。这样会有下面两种情况： - -1. 如果第一块磁盘中有完整系统，则加载第一块磁盘中的系统启动。 -2. 如果第一块磁盘中没有完好的操作系统，则会导致硬盘启动失败。 - -以上两种情况都是因为BIOS默认从第一块磁盘sda中加载引导程序启动系统，如果sda没有系统，则会导致启动失败。 - -## 解决方法 - -有以下两种解决方案： - -- 当系统处于安装过程中，在选择磁盘（选择第一块或者两块都选择）后，指定引导程序安装到第一块盘sda中。 -- 当系统已经安装完成，若BIOS支持选择从哪个磁盘启动，则可以通过修改BIOS中磁盘启动顺序，尝试重新启动系统。 - diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md" index 506e067ca5ec133ac15493f6a3a972f31cf13a8d..31c5bfc0ca5db75346b1b9aa12b8f0409f9cf671 100644 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md" +++ "b/content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md" @@ -1,8 +1,24 @@ -# 安装准备 +# 安装准备 介绍安装前需要考虑软硬件兼容性状况，以及相关的配置和准备工作。 + -## 获取安装源 +- [安装准备](#安装准备) + - [获取安装源](#获取安装源) + - [发布包完整性校验](#发布包完整性校验) + - [简介](#简介) + - [前提条件](#前提条件) + - [操作指导](#操作指导) + - [物理机的安装要求](#物理机的安装要求) + - [硬件兼容支持](#硬件兼容支持) + - [最小硬件要求](#最小硬件要求) + - [虚拟机的安装要求](#虚拟机的安装要求) + - [虚拟化平台兼容性](#虚拟化平台兼容性) + - [最小虚拟化空间要求](#最小虚拟化空间要求) + + + +## 获取安装源 在安装开始前，您需要获取openEuler的发布包和校验文件。 @@ -28,18 +44,18 @@ 2. 单击“openEuler-20.03-LTS-x86\_64-dvd.iso”，将openEuler发布包下载到本地。 3. 单击“openEuler-20.03-LTS-x86\_64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。 -## 发布包完整性校验 +## 发布包完整性校验 >![](C:/Users/Administrator/Downloads/openDocs/docs/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** >本章节以AArch64架构的发布包完整性校验为例，x86\_64架构的发布包完整性校验的操作方法相同。 -### 简介 +### 简介 为了防止软件包在传输过程中由于网络原因或者存储设备原因出现下载不完整的问题，在获取到软件包后，需要对软件包的完整性进行校验，通过了校验的软件包才能部署。 这里通过对比校验文件中记录的校验值和手动方式计算的iso文件校验值，判断软件包是否完成。若两个值相同，说明iso文件完整，否则，iso完整性被破坏，请重新获取iso发布包。 -### 前提条件 +### 前提条件 在校验发布包完整性之前，需要准备如下文件： @@ -47,7 +63,7 @@ iso文件：openEuler-20.03-LTS-aarch64-dvd.iso 校验文件：openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum -### 操作指导 +### 操作指导 文件完整性校验操作步骤如下： @@ -69,11 +85,11 @@ iso文件：openEuler-20.03-LTS-aarch64-dvd.iso 如果校验值一致说明iso文件完整性没有破坏，如果校验值不一致则可以确认文件完整性已被破坏，需要重新获取。 -## 物理机的安装要求 +## 物理机的安装要求 若需要在物理机环境上安装openEuler操作系统，则物理机需要满足如下的硬件兼容性和最小硬件要求。 -### 硬件兼容支持 +### 硬件兼容支持 openEuler安装时，应注意硬件兼容性方面的问题，当前已支持的服务器类型如[表1](#table14948632047)所示。 @@ -113,7 +129,7 @@ openEuler安装时，应注意硬件兼容性方面的问题，当前已支持 -### 最小硬件要求 +### 最小硬件要求 openEuler所需的最小硬件要求如[表2](#tff48b99c9bf24b84bb602c53229e2541)所示。 @@ -160,18 +176,18 @@ openEuler所需的最小硬件要求如[表2](#tff48b99c9bf24b84bb602c53229e2541 -## 虚拟机的安装要求 +## 虚拟机的安装要求 若需要在虚拟机环境上安装openEuler操作系统，则虚拟机需要满足如下的虚拟化平台兼容性和最小虚拟化要求。 -### 虚拟化平台兼容性 +### 虚拟化平台兼容性 openEuler安装时，应注意虚拟化平台兼容性的问题，当前已支持的虚拟化平台为： - openEuler自有的虚拟化组件（HostOS为openEuler，虚拟化组件为发布包中的qemu、KVM）创建的虚拟化平台。 - 华为公有云的x86虚拟化平台。 -### 最小虚拟化空间要求 +### 最小虚拟化空间要求 openEuler所需的最小虚拟化空间要求如[表3](#tff48b99c9bf24b84bb602c53229e2541)所示。 diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\256\214\346\210\220.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\345\256\214\346\210\220.md" deleted file mode 100644 index fb58c8a41a42dcbae717f9bd6d0e879ce9553e4d..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\256\214\346\210\220.md" +++ /dev/null @@ -1,10 +0,0 @@ -# 安装完成 - -此刻，openEuler已完成安装，如[图1](#zh-cn_topic_0186390267_zh-cn_topic_0122145917_fig1429512116338)所示。单击“重启”后，系统将重新启动。 - -**图 1** 完成安装 -![](figures/完成安装.png "完成安装") - -- 如果当前使用物理光盘安装操作系统，且在重启过程中安装光盘没有自动弹出，请手动取出光盘，则可以直接进入openEuler命令行登录界面。 -- 如果当前使用虚拟光驱安装操作系统，则需要修改服务器的启动项为“硬盘”，然后重启服务器，则可以直接进入openEuler命令行登录界面。 - diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md" index cecc2db811bd905da4173437f37c514e1776cc31..bee6a570c1589c0e91c8ee6d6e9d2b354818a7e1 100644 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md" +++ "b/content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md" @@ -1,6 +1,329 @@ -# 安装指导 +# 安装指导 本章以光盘安装为例介绍安装openEuler，其他安装方式除在启动安装时的引导方式不同外，待启动安装后则安装流程相同，在此不再说明。 + +- [安装指导](#安装指导) + - [启动安装](#启动安装) + - [使用光盘引导安装](#使用光盘引导安装) + - [安装引导界面](#安装引导界面) + - [图形化模式安装](#图形化模式安装) + - [设置安装程序语言](#设置安装程序语言) + - [进入安装界面](#进入安装界面) + - [设置键盘](#设置键盘) + - [设置系统语言](#设置系统语言) + - [设置时间和日期](#设置时间和日期) + - [设置安装源](#设置安装源) + - [选择安装软件](#选择安装软件) + - [设置安装位置](#设置安装位置) + - [存储配置](#存储配置) + - [设置网络和主机名](#设置网络和主机名) + - [开始安装](#开始安装) + - [安装过程配置](#安装过程配置) + - [密码复杂度](#密码复杂度) + - [设置root密码](#设置root密码) + - [创建用户](#创建用户) + - [安装完成](#安装完成) + +## 启动安装 + +### 使用光盘引导安装 + +在服务器的光驱中加载openEuler安装镜像，重启服务器，具体步骤如下。 + +>![](public_sys-resources/icon-note.gif) **说明：** +>在安装开始前，需要保证服务器启动选项为光驱优先。安装步骤以BMC挂载虚拟光驱进行光盘安装的操作举例。通过物理光驱安装的操作简单，启动安装后的流程相同，在此不再说明。 + +1. 在虚拟界面工具栏中，单击虚拟光驱工具如下图所示。 + + **图 1** 光驱图标 + ![](figures/光驱图标.png "光驱图标") + + 弹出镜像对话框，如下图所示。 + + **图 2** 镜像对话框 + ![](figures/镜像对话框.png "镜像对话框") + +2. 在镜像对话框中，选择“镜像文件”， 并单击“浏览”。弹出“打开”对话框。 +3. 选择镜像文件，单击“打开”。然后在镜像对话框中，单击“连接”。当“连接”显示为“断开”后，表示虚拟光驱已连接到服务器。 +4. 在工具栏中，单击重启工具重启设备，如下图所示。 + + **图 3** 重启图标 + ![](figures/重启图标.png "重启图标") + + +### 安装引导界面 + +系统使用引导介质完成引导后会显示引导菜单。该引导菜单除启动安装程序外还提供一些选项。安装系统时，默认采用“Test this media & install openEuler 20.03 LTS”方式进行安装。如果要选择默认选项之外的选项，请使用键盘中的“↑”和“↓”方向键进行选择，并在选项为高亮状态时按“Enter”。 + +>![](public_sys-resources/icon-note.gif) **说明：** +>- 如果60秒内未按任何键，系统将从默认选项“Test this media & install openEuler 20.03 LTS”自动进入安装界面。 +>- 安装物理机时，如果使用键盘上下键无法选择启动选项，按“Enter”键无响应，可以单击BMC界面上的鼠标控制图标“![](figures/zh-cn_image_0229420473.png)”，设置“键鼠复位”。 + +**图 4** 安装引导界面 +![](figures/安装引导界面.png "安装引导界面") + +安装引导选项说明如下： + +- Install openEuler 20.03 LTS —— 在您的服务器上使用图形用户界面模式安装。 + +- Test this media & install openEuler 20.03 LTS —— 默认选项，在您的服务器上使用图形用户界面模式安装，但在启动安装程序前会进行安装介质的完整性检查。 + +- Troubleshooting —— 问题定位模式，系统无法正常安装时使用。进入问题定位模式后，有如下两个选项。 + - Install openEuler 20.03-LTS in basic graphics mode —— 简单图形安装模式，该模式下在系统启动并运行之前不启动视频驱动程序。 + - Rescue the openEuler system —— 救援模式，用于修复系统。该模式下输出定向到VNC或BMC（Baseboard Management Controller）端，串口不可用。 + +在安装引导界面，按“e”进入已选选项的参数编辑界面，按“c”进入命令行模式。 + +### 图形化模式安装 + +在“安装引导界面”中选择“Test this media & install openEuler 20.03 LTS”进入图形化模式安装。 + +可以通过键盘操作图形化安装程序。 + +- “Tab”、“shift Tab”：界面控件（按钮、区域框、复选框等）间的移动。 +- “↑”、“↓”方向键：列表里的移动。 +- “←”、“→”方向键：水平工具条和表条间移动。 +- “空格”、“Enter”：选择或删除高亮显示的选项、展开或折叠下拉菜单。 +- “Alt”+“快捷键”：选择快捷键所在的控件，其中快捷键可通过按住Alt高亮（加下划线）显示。 + +## 设置安装程序语言 + +启动安装后，在进入安装程序主界面之前，系统会提示用户设置安装过程中使用的语言。当前默认为英语，用户可根据实际情况进行调整，如[图5](#zh-cn_topic_0186390093_zh-cn_topic_0122145864_fig144630179151)所示，选择“中文”。 + +**图 5** 选择语言 +![](figures/选择语言.png "选择语言") + +完成设置后，单击“继续”，进入安装设置主界面。 + +如果您想退出安装，可以单击“退出”并在弹出的“您确定要退出安装程序吗？”对话框中单击“是”重新进入“安装引导界面”。 + +## 进入安装界面 + +系统安装程序正常启动后，会进入[图6](#zh-cn_topic_0186390094_zh-cn_topic_0122145883_fig5969171592212)所示的安装设置主界面。用户可以进行时间、语言、安装源、网络、安装位置等相关设置。 + +部分配置项会有告警符号，用户完成该选项配置后，告警符号消失。当界面上不存在告警符号时，用户才能单击“开始安装”进行系统安装。 + +如果您想退出安装，可以单击“退出”并在弹出的“您确定要退出安装程序吗？”对话框中单击“是”重新进入“安装引导界面”。 + +**图 6** 安装概览 +![](figures/安装概览.png "安装概览") + +## 设置键盘 + +在“安装概览”页面中选择“键盘”，用户可以在系统中添加或者删除多个键盘布局。 + +- 要查看键盘布局，请在左侧选框中单击选中该键盘布局，然后单击下面的“键盘”按钮。 +- 要测试键盘布局，请在左侧选框中添加键盘布局，然后在右上角键盘图标处进行点击切换为目标键盘，单击右侧文本框内部，输入文本以确认所选键盘布局可正常工作。 + +**图 7** 键盘布局 +![](figures/键盘布局.png "键盘布局") + +设置完成后，请单击左上角“完成”返回“安装概览”页面。 + +## 设置系统语言 + +在“安装概览”页面中选择“语言支持”，设置系统的语言。如[图8](#zh-cn_topic_0186390098_zh-cn_topic_0122145772_fig187301927172619)所示，用户也可根据实际情况进行调整，选择“中文”。 + +>![](public_sys-resources/icon-note.gif) **说明：** +>若选择“中文”，系统安装完成后，使用VNC登录不支持中文显示，使用串口或者SSH等方式登录支持中文显示。若选择“English”，则无影响。 + +**图 8** 语言支持 +![](figures/语言支持.png "语言支持") + +设置完成后，请单击左上角“完成”返回“安装概览”页面。 + +## 设置时间和日期 + +在“安装概览”页面中选择“时间和日期”，设置系统的时区、日期、时间等。 + +设置时区时，用户可通过鼠标在地图上单击指定的城市，也可以通过页面顶部的“地区”和“城市”下拉菜单中进行选择，如[图9](#zh-cn_topic_0186390096_zh-cn_topic_0122145900_fig1260162652312)所示。 + +如果您所在城市没有出现在地图或下拉菜单中，请选择同一时区中离您最近的城市。 + +>![](public_sys-resources/icon-note.gif) **说明：** +>- 手动设置时区时，请先关闭右上角“网络时间”同步开关。 +>- 如需使用网络时间，请保证网络能连通远程NTP服务器，设置网络具体请参见“[设置网络和主机名](#设置网络和主机名)”。 + +**图 9** 日期和时间 +![](figures/日期和时间.png "日期和时间") + +设置完成后，请单击左上角“完成”返回“安装概览”页面。 + +## 设置安装源 + +在“安装概览”页面中选择“安装源”，指定安装源的位置。 + +当使用完整光盘安装，安装程序会自动探测并显示安装源信息，用户直接使用默认配置即可，不需要进行设置，如[图10](#zh-cn_topic_0186390100_zh-cn_topic_0144427079_fig93633295132)所示。 + +**图 10** 安装源 +![](figures/安装源.png "安装源") + +当使用网络https源进行安装的时候，如果https服务器使用的是私有证书，则需要在安装引导界面按“e”进入已选选项的参数编辑界面，在参数中增加inst.noverifyssl参数，如[图11](#fig113517811415)所示。 + +**图 11** 增加inst.noverifyssl参数 +![](figures/增加inst-noverifyssl参数.png "增加inst-noverifyssl参数") + +设置完成后，请单击左上角“完成”返回“安装概览”页面。 + +>![](public_sys-resources/icon-note.gif) **说明：** +>安装过程中，如果“设置安装源”有疑问，可参考“[选择安装源出现异常](FAQ.html#选择安装源出现异常)”。 + +## 选择安装软件 + +在“安装概览”页面中选择“软件选择”，指定需要安装的软件包。 + +用户需要根据实际的业务需求，在左侧选择一个“最小安装”，在右侧选择安装环境的附加选项，如[图12](#zh-cn_topic_0186390261_zh-cn_topic_0122145865_fig03031519101414)所示。 + +**图 12** 软件选择 +![](figures/软件选择.png "软件选择") + +>![](public_sys-resources/icon-note.gif) **说明：** +>- 在最小安装的环境下，并非安装源中所有的包都会安装。如果用户需要使用的包未安装，可将安装源挂载到本地制作repo源，通过DNF工具单独安装。 +>- 选择“虚拟化主机”时会默认安装虚拟化组件qemu、libvirt、edk2，且可在附件选项处选择是否安装ovs等组件。 + +设置完成后，请单击左上角“完成”返回“安装概览”页面。 + +## 设置安装位置 + +在“安装概览”页面中选择“安装位置”，设置操作系统的安装磁盘及分区。 + +在[图13](#fig1195417125015)所示的页面中您可以看到计算机中的本地可用存储设备。您还可以通过单击“添加磁盘”，添加指定的附加设备或者网络设备。 + +>![](public_sys-resources/icon-notice.gif) **须知：** +>在选择您需要安装的设备时，建议不要选择NVMe SSD存储介质作为操作系统的安装磁盘。 + +**图 13** 安装目标位置 +![](figures/安装目标位置.png "安装目标位置") + +### 存储配置 + +在“安装目标位置”界面，您需要进行存储配置以便对系统分区。您可以手动配置分区，也可以选择让安装程序自动分区。 + +>![](public_sys-resources/icon-note.gif) **说明：** +>- 在进行分区时，出于系统性能和安全的考虑，建议您划分如下单独分区：/boot、/var、/var/log 、/var/log/audit、/home、/tmp。 +>- 系统如果配置了swap分区，当系统的物理内存不够用时，会使用swap分区。虽然 swap分区可以增大物理内存大小的限制，但是如果由于内存不足使用到swap分区，会增加系统的响应时间，性能变差。因此在物理内存充足或者性能敏感的系统中，不建议配置swap分区。 +>- 如果需要拆分逻辑卷组则需要选择“自定义”进行手动分区，并在“手动分区”界面单击“卷组”区域中的“修改”按钮重新配置卷组。 + +**自动** + +如果是在未使用过的存储设备中执行全新安装，或者不需要保留该存储设备中任何数据，建议选择“自动”进行自动分区。 + +**自定义** + +若用户需进行手动分区，选择“自定义”按钮，并单击左上角“完成”，出现如下手动分区界面。 + +**图 14** 手动分区 +![](figures/手动分区.png "手动分区") + +在“手动分区”界面可以通过如下两种方式进行分区。 + +- 自动创建：在界面单击“点击这里自动创建它们”，系统会根据可用的存储空间，自动分出4个挂载点：/boot 、/、/boot/efi、swap。 +- 手动创建：单击“![](figures/zh-cn_image_0229291243.png)”添加新挂载点，建议每个挂载点的期望容量不超过可用空间。 + + >![](public_sys-resources/icon-note.gif) **说明：** + >若设置的挂载点期望容量超过了可用空间，系统将剩余的可用空间全部分配给该挂载点。 + + +设置完成后，请单击左上角“完成”返回“安装概览”页面。 + +## 设置网络和主机名 + +在“安装概览”页面中选择“网络和主机名”，设置系统的网络功能。 + +安装程序会自动探测可本地访问的接口。探测到的接口列在左侧方框中，右侧显示相应的接口详情，如[图15](#zh-cn_topic_0186390264_zh-cn_topic_0122145831_fig123700157297)所示。用户可以通过页面右上角的开关，来开启或者关闭网络接口。用户还可以单击“配置”以配置选中的接口。 + +用户可在页面下方“主机名”字段输入主机名。主机名可以是完全限定域名（FQDN），其格式为hostname.domainname；也可以是简要主机名，其格式为hostname。 + +**图 15** 网络和主机名 +![](figures/网络和主机名.png "网络和主机名") + +设置完成后，请单击左上角“完成”返回“安装概览”页面。 + +## 开始安装 + +在安装界面上完成所有必填选项的配置后，界面上的警告会消失。此时，用户可以单击“开始安装”进行系统安装。 + +**图 16** 开始安装 +![](figures/开始安装.png "开始安装") + +## 安装过程配置 + +开始安装后会出现进度页面，显示安装进度及所选软件包写入系统的进度。 + +**图 17** 安装过程 +![](figures/安装过程.png "安装过程") + +安装软件包的过程中，需要用户配置root密码、根据个人需求可以创建用户。 + +### 密码复杂度 + +用户设置的root用户密码或新创建用户的密码均需要满足密码复杂度要求，否则会导致密码设置或用户创建失败。设置密码的复杂度的要求如下： + +1. 口令长度至少8个字符。 +2. 口令至少包含大写字母、小写字母、数字和特殊字符中的任意3种。 +3. 口令不能和账号一样。 +4. 口令不能使用字典词汇。 + - 查询字典 + + 在已装好的openEuler环境中，可以通过如下命令导出字典库文件dictionary.txt，用户可以查询密码是否在该字典中。 + + ``` + cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt + ``` + + - 修改字典 + 1. 修改上面导出的字典文件，执行如下命令更新系统字典库。 + + ``` + # create-cracklib-dict dictionary.txt + ``` + + 2. 在原字典库基础上新增其他字典内容custom.txt。 + + ``` + # create-cracklib-dict dictionary.txt custom.txt + ``` + + + + +### 设置root密码 + +单击“root密码”，弹出设置密码界面如[图18](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1323165793018)所示，输入密码并再次输入密码进行确认。 + +>![](public_sys-resources/icon-note.gif) **说明：** +>root密码需要在安装软件包的同时进行配置，如果不配置该密码则无法完成安装。root账户是用来执行关键系统管理任务，不建议您在日常工作及系统访问时使用root账户。 + +**图 18** root密码 +![](figures/root密码.png "root密码") + +完成设置后，单击左上角的“完成”返回安装过程界面。 + +### 创建用户 + +单击“创建用户”，弹出创建用户的界面如[图19](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1237715313319)所示。输入用户名，并设置密码。另外您还可以通过“高级”选项设置用户主目录、用户组等，如[图20](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig128716531312)所示。 + +**图 19** 创建用户 +![](figures/创建用户.png "创建用户") + +**图 20** 高级用户配置 +![](figures/高级用户配置.png "高级用户配置") + +完成设置后，单击左上角的“完成”返回安装过程界面。 + +单击“结束配置”，完成openEuler的相关配置。 + +![](figures/结束配置-new.png) + +## 安装完成 + +此刻，openEuler已完成安装，如[图21](#zh-cn_topic_0186390267_zh-cn_topic_0122145917_fig1429512116338)所示。单击“重启”后，系统将重新启动。 + +**图 21** 完成安装 +![](figures/完成安装.png "完成安装") + +- 如果当前使用物理光盘安装操作系统，且在重启过程中安装光盘没有自动弹出，请手动取出光盘，则可以直接进入openEuler命令行登录界面。 +- 如果当前使用虚拟光驱安装操作系统，则需要修改服务器的启动项为“硬盘”，然后重启服务器，则可以直接进入openEuler命令行登录界面。 diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md" index e065c7c5f8319bc8f57c7dff2d9fafc3e58192fe..7a39a3b14deddbbb92b80b8a635d061c4d1b69de 100644 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md" +++ "b/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md" @@ -1,18 +1,36 @@ -# 安装方式介绍 +# 安装方式介绍 >![](public_sys-resources/icon-notice.gif) **须知：** ->- 硬件服务器仅支持Taishan 200服务器和FusionServer Pro 机架服务器，具体支持的服务器型号可参考“[安装准备](安装准备.html)”章节；虚拟化平台仅支持openEuler自有的虚拟化组件（HostOS为openEuler，虚拟化组件为发布包中的qemu、KVM）创建的虚拟化平台和华为公有云的x86虚拟化平台。 ->- 安装方式当前仅支持光盘、USB盘安装、网络安装、qcow2镜像安装和私有镜像安装。其中仅华为公有云的x86虚拟化平台支持私有镜像安装。 - -## 通过光盘安装 +>- 硬件服务器仅支持Taishan 200服务器和FusionServer Pro 机架服务器，具体支持的服务器型号可参考“[硬件兼容支持](安装准备.html#硬件兼容支持)”；虚拟化平台仅支持openEuler自有的虚拟化组件（HostOS为openEuler，虚拟化组件为发布包中的qemu、KVM）创建的虚拟化平台和华为公有云的x86虚拟化平台。 +>- 安装方式当前仅支持光盘、USB盘安装、网络安装、qcow2镜像安装和私有镜像安装。其中仅华为公有云的x86虚拟化平台支持私有镜像安装。 + + +- [安装方式介绍](#安装方式介绍) + - [通过光盘安装](#通过光盘安装) + - [准备安装源](#准备安装源) + - [启动安装](#启动安装) + - [通过USB盘安装](#通过usb盘安装) + - [准备安装源](#准备安装源-1) + - [启动安装](#启动安装-1) + - [使用PXE通过网络安装](#使用pxe通过网络安装) + - [通过qcow2镜像安装](#通过qcow2镜像安装) + - [制作qcow2镜像](#制作qcow2镜像) + - [启动安装](#启动安装-2) + - [通过私有镜像安装](#通过私有镜像安装) + - [制作私有镜像](#制作私有镜像) + - [启动安装](#启动安装-3) + + + +## 通过光盘安装 本节介绍如何使用或者制作光盘安装源，并介绍相应的操作步骤，指导用户进行安装。 -### 准备安装源 +### 准备安装源 如果您获取的是系统安装光盘，那么可以直接使用光盘安装系统。如果您获取的是系统ISO镜像，可以通过刻录软件将系统的ISO镜像刻录到DVD中，使用刻录完成的DVD安装系统。 -### 启动安装 +### 启动安装 根据以下步骤启动安装程序： @@ -26,11 +44,11 @@ 在短暂的延迟后会出现图形化引导界面，该界面包含不同引导选项。如果您在一分钟内未进行任何操作，安装程序将自动以默认选项开始运行。 -## 通过USB盘安装 +## 通过USB盘安装 本节介绍如何制作USB盘安装源，并介绍基本的操作步骤，指导用户进行安装。 -### 准备安装源 +### 准备安装源 您需要注意USB盘容量的大小，它必须有足够的的空间放下整个镜像，建议USB盘空间大于16G。 @@ -90,7 +108,7 @@ 镜像写入过程中不会有进度显示，当\#号再次出现时，表明写入完成。退出root账户，拔掉USB盘。此时，您可以使用该USB盘作为系统的安装源。 -### 启动安装 +### 启动安装 请根据以下步骤启动安装程序： @@ -104,7 +122,7 @@ 在短暂的延迟后会出现图形化引导页面，该页面包含不同引导选项。如果您在一分钟内未进行任何操作，安装程序将自动开始安装。 -## 使用PXE通过网络安装 +## 使用PXE通过网络安装 要使用 PXE 引导，您需要正确配置服务器以及您的计算机需支持 PXE 的网络接口。 @@ -113,13 +131,13 @@ 对于PXE网络安装，客户机通过支持PXE的网卡，向网络发送请求DHCP信息的广播，请求IP地址等信息。DHCP服务器给客户机提供一个IP地址和其他网络信息如域名服务器、ftp服务器（它提供启动安装程序所必须的文件）的IP地址或主机名，以及服务器上文件的位置。 >![](C:/Users/Administrator/Downloads/openDocs/docs/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** ->此处不详细讨论tftp、DHCP、http等服务器配置，相关详细配置请参考“[全自动化安装指导](全自动化安装指导.html)”章节。 +>此处不详细讨论tftp、DHCP、http等服务器配置，相关详细配置请参考“[全自动化安装指导](使用kickstart自动化安装.html#全自动化安装指导)”。 -## 通过qcow2镜像安装 +## 通过qcow2镜像安装 本节介绍如何使用或者制作qcow2镜像，并介绍相应的操作步骤，指导用户进行安装。 -### 制作qcow2镜像 +### 制作qcow2镜像 1. 安装qemu-img软件包。 @@ -148,7 +166,7 @@ ``` -### 启动安装 +### 启动安装 根据以下步骤启动安装程序： @@ -161,15 +179,15 @@ 各步骤详细的操作请参考《[openEuler 20.03 LTS 虚拟化用户指南](../Virtualization/virtualization.html)》。 -## 通过私有镜像安装 +## 通过私有镜像安装 本节介绍如何使用或者制作私有镜像，并介绍相应的操作步骤，指导用户进行安装。 -### 制作私有镜像 +### 制作私有镜像 制作私有镜像的方法请参见[《镜像服务用户指南》](https://support.huaweicloud.com/usermanual-ims/zh-cn_topic_0013901628.html)。 -### 启动安装 +### 启动安装 华为公有云的x86虚拟化平台的启动请参见[ 弹性云服务器 ECS的用户指南](https://support.huaweicloud.com/wtsnew-ecs/index.html)。 diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\350\277\207\347\250\213\351\205\215\347\275\256.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\350\277\207\347\250\213\351\205\215\347\275\256.md" deleted file mode 100644 index 711116937ee0ec9477c5d1b707a862972491482d..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205\350\277\207\347\250\213\351\205\215\347\275\256.md" +++ /dev/null @@ -1,69 +0,0 @@ -# 安装过程配置 - -开始安装后会出现进度页面，显示安装进度及所选软件包写入系统的进度。 - -**图 1** 安装过程 -![](figures/安装过程.png "安装过程") - -安装软件包的过程中，需要用户配置root密码、根据个人需求可以创建用户。 - -## 密码复杂度 - -用户设置的root用户密码或新创建用户的密码均需要满足密码复杂度要求，否则会导致密码设置或用户创建失败。设置密码的复杂度的要求如下： - -1. 口令长度至少8个字符。 -2. 口令至少包含大写字母、小写字母、数字和特殊字符中的任意3种。 -3. 口令不能和账号一样。 -4. 口令不能使用字典词汇。 - - 查询字典 - - 在已装好的openEuler环境中，可以通过如下命令导出字典库文件dictionary.txt，用户可以查询密码是否在该字典中。 - - ``` - cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt - ``` - - - 修改字典 - 1. 修改上面导出的字典文件，执行如下命令更新系统字典库。 - - ``` - # create-cracklib-dict dictionary.txt - ``` - - 2. 在原字典库基础上新增其他字典内容custom.txt。 - - ``` - # create-cracklib-dict dictionary.txt custom.txt - ``` - - - - -## 设置root密码 - -单击“root密码”，弹出设置密码界面如[图2](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1323165793018)所示，输入密码并再次输入密码进行确认。 - ->![](public_sys-resources/icon-note.gif) **说明：** ->root密码需要在安装软件包的同时进行配置，如果不配置该密码则无法完成安装。root账户是用来执行关键系统管理任务，不建议您在日常工作及系统访问时使用root账户。 - -**图 2** root密码 -![](figures/root密码.png "root密码") - -完成设置后，单击左上角的“完成”返回安装过程界面。 - -## 创建用户 - -单击“创建用户”，弹出创建用户的界面如[图3](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1237715313319)所示。输入用户名，并设置密码。另外您还可以通过“高级”选项设置用户主目录、用户组等，如[图4](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig128716531312)所示。 - -**图 3** 创建用户 -![](figures/创建用户.png "创建用户") - -**图 4** 高级用户配置 -![](figures/高级用户配置.png "高级用户配置") - -完成设置后，单击左上角的“完成”返回安装过程界面。 - -单击“结束配置”，完成openEuler的相关配置。 - -![](figures/结束配置-new.png) - diff --git "a/content/zh/docs/Installation/\345\274\200\345\247\213\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/\345\274\200\345\247\213\345\256\211\350\243\205.md" deleted file mode 100644 index 389e3e76efdcdbf1a35a5fbd099b6ff103a276e1..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\274\200\345\247\213\345\256\211\350\243\205.md" +++ /dev/null @@ -1,7 +0,0 @@ -# 开始安装 - -在安装界面上完成所有必填选项的配置后，界面上的警告会消失。此时，用户可以单击“开始安装”进行系统安装。 - -**图 1** 开始安装 -![](figures/开始安装.png "开始安装") - diff --git "a/content/zh/docs/Installation/\346\200\273\344\275\223\344\273\213\347\273\215.md" "b/content/zh/docs/Installation/\346\200\273\344\275\223\344\273\213\347\273\215.md" deleted file mode 100644 index ac9b396496c32fc9137995d32248d33806896bdf..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\346\200\273\344\275\223\344\273\213\347\273\215.md" +++ /dev/null @@ -1,57 +0,0 @@ -# 总体介绍 - -## 概述 - -用户可以使用kickstart工具进行openEuler系统的自动化安装，包括如下两种方式： - -- 半自动化安装：安装人员不需要手动设定操作系统的键盘、语言、分区等具体属性（通过kickstart实现自动化），但是需要手动指定kickstart文件的位置。 -- 全自动化安装：实现操作系统的安装过程全自动化。 - -## 优缺点对比 - -使用kickstart工具进行半自动化安装和全自动化安装的优缺点对比如[表1](#table1388812373315)所示，用户可以自行选择安装方式。 - -**表 1** 优缺点对比 - - - - - - - - - - - - - - - - -

安装方式

-

优点

-

缺点

-

半自动化安装

-

不需要准备tftp，pxe，dhcp等服务

-

需要手动指定kickstart文件的位置

-

全自动化安装

-

操作系统的全自动化安装

-

需要配置tftp，dhcpd，pxe等服务

-
- -## 背景知识 - -**kickstart** - -kickstart是一种无人值守的安装方式。它的工作原理是在安装过程中记录典型的需要人工干预填写的各种参数，并生成一个配置文件（ks.cfg），在安装过程中，安装程序首先会去查找ks配置文件，如果找到合适的参数，就采用所找到的参数；如果没有找到合适的参数，便需要安装者手工设定。所以，如果kickstart文件涵盖了安装过程中需要设定的所有参数，安装者只需要告诉安装程序从何处取ks.cfg文件，就能实现系统安装的自动化。 - -kickstart 安装提供一个安装过程自动化的方法，可以是部分自动化，也可以是完全自动化。 - -**PXE** - -PXE（Pre-boot Execution Environment，预启动执行环境），工作于Client/Server的网络模式，支持PXE的客户端在启动过程中，能够从DHCP服务器获取IP结合TFTP（trivial file transfer protocol）等协议可以实现客户端的网络引导和安装。 - -**TFTP** - -TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议用来实现客户机与服务器之间的简单文件传输，它提供不复杂、开销不大的文件传输服务。 - diff --git "a/content/zh/docs/Installation/\346\234\200\345\260\217\347\241\254\344\273\266\350\246\201\346\261\202.md" "b/content/zh/docs/Installation/\346\234\200\345\260\217\347\241\254\344\273\266\350\246\201\346\261\202.md" deleted file mode 100644 index 465bc8a451d88acc732495346a0bbe6b15fc9841..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\346\234\200\345\260\217\347\241\254\344\273\266\350\246\201\346\261\202.md" +++ /dev/null @@ -1,46 +0,0 @@ -# 最小硬件要求 - -openEuler所需的最小硬件要求如[表1](#tff48b99c9bf24b84bb602c53229e2541)所示。 - -**表 1** 最小硬件要求 - - - - - - - - - - - - - - - - - - - - - - - - -

部件名称

-

最小硬件要求

-

说明

-

架构

-
  • AArch64
  • x86_64
-
  • 支持Arm的64位架构。
  • 支持Intel的x86 64位架构。
-

CPU

-
  • 华为鲲鹏920系列CPU
  • Intel® Xeon®处理器
-

-

-

内存

-

不小于4GB（为了获得更好的应用体验，建议不小于8GB）

-

-

-

硬盘

-

为了获得更好的应用体验，建议不小于120GB）

-

支持IDE、SATA、SAS等接口的硬盘。

-
- diff --git "a/content/zh/docs/Installation/\346\234\200\345\260\217\350\231\232\346\213\237\345\214\226\347\251\272\351\227\264\350\246\201\346\261\202.md" "b/content/zh/docs/Installation/\346\234\200\345\260\217\350\231\232\346\213\237\345\214\226\347\251\272\351\227\264\350\246\201\346\261\202.md" deleted file mode 100644 index 4bb509fb7895f9b65c49c80f129ea0b85a02ab45..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\346\234\200\345\260\217\350\231\232\346\213\237\345\214\226\347\251\272\351\227\264\350\246\201\346\261\202.md" +++ /dev/null @@ -1,46 +0,0 @@ -# 最小虚拟化空间要求 - -openEuler所需的最小虚拟化空间要求如[表1](#tff48b99c9bf24b84bb602c53229e2541)所示。 - -**表 1** 最小虚拟化空间要求 - - - - - - - - - - - - - - - - - - - - - - - - -

部件名称

-

最小虚拟化空间要求

-

说明

-

架构

-
  • AArch64
  • x86_64
-

-

-

CPU

-

2个CPU

-

-

-

内存

-

不小于4GB（为了获得更好的应用体验，建议不小于8GB）

-

-

-

硬盘

-

不小于32GB（为了获得更好的应用体验，建议不小于120GB）

-

-

-
- diff --git "a/content/zh/docs/Installation/\346\263\225\345\276\213\345\243\260\346\230\216.md" "b/content/zh/docs/Installation/\346\263\225\345\276\213\345\243\260\346\230\216.md" deleted file mode 100644 index 6d44fdb3e4c209523616e7e386a645ce3737ee11..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\346\263\225\345\276\213\345\243\260\346\230\216.md" +++ /dev/null @@ -1,14 +0,0 @@ -# 法律声明 - -**版权所有 © 2020 华为技术有限公司。** - -您对“本文档”的复制、使用、修改及分发受知识共享\(Creative Commons\)署名—相同方式共享4.0国际公共许可协议\(以下简称“CC BY-SA 4.0”\)的约束。为了方便用户理解，您可以通过访问[https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/) 了解CC BY-SA 4.0的概要 \(但不是替代\)。CC BY-SA 4.0的完整协议内容您可以访问如下网址获取：[https://creativecommons.org/licenses/by-sa/4.0/legalcode](https://creativecommons.org/licenses/by-sa/4.0/legalcode)。 - -**商标声明** - -openEuler为华为技术有限公司的商标。本文档提及的其他所有商标或注册商标，由各自的所有人拥有。 - -**免责声明** - -本文档仅作为使用指导，除非适用法强制规定或者双方有明确书面约定, 华为技术有限公司对本文档中的所有陈述、信息和建议不做任何明示或默示的声明或保证，包括但不限于不侵权，时效性或满足特定目的的担保。 - diff --git "a/content/zh/docs/Installation/\347\211\251\347\220\206\346\234\272\347\232\204\345\256\211\350\243\205\350\246\201\346\261\202.md" "b/content/zh/docs/Installation/\347\211\251\347\220\206\346\234\272\347\232\204\345\256\211\350\243\205\350\246\201\346\261\202.md" deleted file mode 100644 index 0da7b728477b02cf4cd2907a14d8df6303bfef89..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\347\211\251\347\220\206\346\234\272\347\232\204\345\256\211\350\243\205\350\246\201\346\261\202.md" +++ /dev/null @@ -1,5 +0,0 @@ -# 物理机的安装要求 - -若需要在物理机环境上安装openEuler操作系统，则物理机需要满足如下的硬件兼容性和最小硬件要求。 - - diff --git "a/content/zh/docs/Installation/\347\241\254\344\273\266\345\205\274\345\256\271\346\224\257\346\214\201.md" "b/content/zh/docs/Installation/\347\241\254\344\273\266\345\205\274\345\256\271\346\224\257\346\214\201.md" deleted file mode 100644 index b995df4dc7b73fe67b256230f89952d6411a08aa..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\347\241\254\344\273\266\345\205\274\345\256\271\346\224\257\346\214\201.md" +++ /dev/null @@ -1,38 +0,0 @@ -# 硬件兼容支持 - -openEuler安装时，应注意硬件兼容性方面的问题，当前已支持的服务器类型如[表1](#table14948632047)所示。 - ->![](public_sys-resources/icon-note.gif) **说明：** ->- TaiShan 200服务器基于华为鲲鹏920处理器。 ->- 当前仅支持华为TaiShan服务器和FusionServer Pro 机架服务器，后续将逐步增加对其他厂商服务器的支持。 - -**表 1** 支持的服务器类型 - - - - - - - - - - - - - - - - -

服务器形态

-

服务器名称

-

服务器型号

-

机架服务器

-

TaiShan 200

-

2280均衡型

-

机架服务器

-

FusionServer Pro 机架服务器

-

FusionServer Pro 2288H V5

-
说明：

服务器要求配置Avago 3508 RAID控制卡和启用LOM-X722网卡。

-
-
- diff --git "a/content/zh/docs/Installation/\347\263\273\347\273\237\344\270\255\345\255\230\345\234\250\346\227\240\346\263\225\346\277\200\346\264\273\347\232\204\351\200\273\350\276\221\345\215\267\347\273\204\346\227\266-\351\207\215\350\243\205\347\263\273\347\273\237\345\244\261\350\264\245.md" "b/content/zh/docs/Installation/\347\263\273\347\273\237\344\270\255\345\255\230\345\234\250\346\227\240\346\263\225\346\277\200\346\264\273\347\232\204\351\200\273\350\276\221\345\215\267\347\273\204\346\227\266-\351\207\215\350\243\205\347\263\273\347\273\237\345\244\261\350\264\245.md" deleted file mode 100644 index beff5ce73cb6166c28eaa392e5dffb271ea7858a..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\347\263\273\347\273\237\344\270\255\345\255\230\345\234\250\346\227\240\346\263\225\346\277\200\346\264\273\347\232\204\351\200\273\350\276\221\345\215\267\347\273\204\346\227\266-\351\207\215\350\243\205\347\263\273\347\273\237\345\244\261\350\264\245.md" +++ /dev/null @@ -1,48 +0,0 @@ -# 系统中存在无法激活的逻辑卷组时，重装系统失败 - -## 问题现象 - -由于磁盘故障，系统中存在无法激活的逻辑卷组，重装系统出现异常。 - -## 原因分析 - -安装时有激活逻辑卷组的操作，无法激活时会抛出异常。 - -## 解决方法 - -重装系统前如果系统中存在无法激活的逻辑卷组，为了避免重装系统过程出现异常，需在重装前将逻辑卷组恢复到正常状态或者清除这些逻辑卷组。举例如下： - -- 恢复逻辑卷组状态 - 1. 使用以下命令清除vg激活状态， 防止出现“Can't open /dev/sdc exclusively mounted filesystem”。 - - ``` - vgchange -a n testvg32947 - ``` - - 2. 根据备份文件重新创建pv。 - - ``` - pvcreate --uuid JT7zlL-K5G4-izjB-3i5L-e94f-7yuX-rhkLjL --restorefile /etc/lvm/backup/testvg32947 /dev/sdc - ``` - - 3. 恢复vg信息。 - - ``` - vgcfgrestore testvg32947 - ``` - - 4. 重新激活vg。 - - ``` - vgchange -ay testvg32947 - ``` - - -- 清除逻辑卷组 - - ``` - vgchange -a n testvg32947 - vgremove -y testvg32947 - ``` - - diff --git "a/content/zh/docs/Installation/\347\275\221\347\273\234\351\205\215\347\275\256\347\272\246\346\235\237\351\231\220\345\210\266.md" "b/content/zh/docs/Installation/\347\275\221\347\273\234\351\205\215\347\275\256\347\272\246\346\235\237\351\231\220\345\210\266.md" deleted file mode 100644 index e44ada87ee7a0ebb7c1674ee7519abbf09719f9a..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\347\275\221\347\273\234\351\205\215\347\275\256\347\272\246\346\235\237\351\231\220\345\210\266.md" +++ /dev/null @@ -1,25 +0,0 @@ -# 网络配置约束限制 - -NetworkManager、network两个服务均是网络服务管理包，两个服务之间存在部分功能重叠。 - -- 如果使用NetworkManager管理服务，则必须使用nmcli命令或修改配置文件来配置网络（如IP、路由等），而不能使用ip/ifconfig/route命令来配置。 - - >![](public_sys-resources/icon-note.gif) **说明：** - >在开启NetworkManager服务的场景下，使用ip/ifconfig/route等命令配置网络，则一段时间后配置会被NetworkManager覆盖，导致 ip/ifconfig/route配置不生效。 - - 查看NetworkManager 服务是否开启： - - ``` - systemctl status NetworkManager - ``` - - >![](public_sys-resources/icon-note.gif) **说明：** - >nmcli命令使用参考“nmcli \--help”或者“man nmcli”。 - -- 如果要使用ip/ifconfig/route等命令来管理网络，请先关闭NetworkManager服务，使用如下命令： - - ``` - systemctl stop NetworkManager - ``` - - diff --git "a/content/zh/docs/Installation/\350\216\267\345\217\226\345\256\211\350\243\205\346\272\220.md" "b/content/zh/docs/Installation/\350\216\267\345\217\226\345\256\211\350\243\205\346\272\220.md" deleted file mode 100644 index 7ac645013a8c84f3b372d28ce4bae6ce6d7057f0..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\216\267\345\217\226\345\256\211\350\243\205\346\272\220.md" +++ /dev/null @@ -1,26 +0,0 @@ -# 获取安装源 - -在安装开始前，您需要获取openEuler的发布包和校验文件。 - -请按以下步骤获取openEuler的发布包和校验文件： - -1. 登录[openEuler社区](https://openeuler.org)网站。 -2. 单击“下载”。 -3. 单击“获取ISO：”后面的“Link”，显示版本列表。 -4. 单击“openEuler-20.03-LTS”，进入openEuler 20.03 LTS版本下载列表。 -5. 单击“ISO”，进入ISO下载列表。 - - aarch64：AArch64架构的ISO。 - - x86\_64：x86\_64架构的ISO。 - - source：openEuler源码ISO。 - -6. 根据实际待安装环境的架构选择需要下载的openEuler的发布包和校验文件。 - - 若为AArch64架构。 - 1. 单击“aarch64”。 - 2. 单击“openEuler-20.03-LTS-aarch64-dvd.iso”，将openEuler发布包下载到本地。 - 3. 单击“openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。 - - - 若为x86\_64架构。 - 1. 单击“x86\_64”。 - 2. 单击“openEuler-20.03-LTS-x86\_64-dvd.iso”，将openEuler发布包下载到本地。 - 3. 单击“openEuler-20.03-LTS-x86\_64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。 - diff --git "a/content/zh/docs/Installation/\350\231\232\346\213\237\345\214\226\345\271\263\345\217\260\345\205\274\345\256\271\346\200\247.md" "b/content/zh/docs/Installation/\350\231\232\346\213\237\345\214\226\345\271\263\345\217\260\345\205\274\345\256\271\346\200\247.md" deleted file mode 100644 index 3c02858e239423ebb8b45c28b9e37e02f672f4ce..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\231\232\346\213\237\345\214\226\345\271\263\345\217\260\345\205\274\345\256\271\346\200\247.md" +++ /dev/null @@ -1,7 +0,0 @@ -# 虚拟化平台兼容性 - -openEuler安装时，应注意虚拟化平台兼容性的问题，当前已支持的虚拟化平台为： - -- openEuler自有的虚拟化组件（HostOS为openEuler，虚拟化组件为发布包中的qemu、KVM）创建的虚拟化平台。 -- 华为公有云的x86虚拟化平台。 - diff --git "a/content/zh/docs/Installation/\350\231\232\346\213\237\346\234\272\347\232\204\345\256\211\350\243\205\350\246\201\346\261\202.md" "b/content/zh/docs/Installation/\350\231\232\346\213\237\346\234\272\347\232\204\345\256\211\350\243\205\350\246\201\346\261\202.md" deleted file mode 100644 index 53b32309ad3627c92ebffa74dfe01d184f8001ec..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\231\232\346\213\237\346\234\272\347\232\204\345\256\211\350\243\205\350\246\201\346\261\202.md" +++ /dev/null @@ -1,6 +0,0 @@ -# 虚拟机的安装要求 - -若需要在虚拟机环境上安装openEuler操作系统，则虚拟机需要满足如下的虚拟化平台兼容性和最小虚拟化要求。 - - - diff --git "a/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\344\275\215\347\275\256.md" "b/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\344\275\215\347\275\256.md" deleted file mode 100644 index ccfd64ae1a0f96813e2b8cf5c4ef7bc226cddcd1..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\344\275\215\347\275\256.md" +++ /dev/null @@ -1,43 +0,0 @@ -# 设置安装位置 - -在“安装概览”页面中选择“安装位置”，设置操作系统的安装磁盘及分区。 - -在[图1](#fig1195417125015)所示的页面中您可以看到计算机中的本地可用存储设备。您还可以通过单击“添加磁盘”，添加指定的附加设备或者网络设备。 - ->![](public_sys-resources/icon-notice.gif) **须知：** ->在选择您需要安装的设备时，建议不要选择NVMe SSD存储介质作为操作系统的安装磁盘。 - -**图 1** 安装目标位置 -![](figures/安装目标位置.png "安装目标位置") - -## 存储配置 - -在“安装目标位置”界面，您需要进行存储配置以便对系统分区。您可以手动配置分区，也可以选择让安装程序自动分区。 - ->![](public_sys-resources/icon-note.gif) **说明：** ->- 在进行分区时，出于系统性能和安全的考虑，建议您划分如下单独分区：/boot、/var、/var/log 、/var/log/audit、/home、/tmp。 ->- 系统如果配置了swap分区，当系统的物理内存不够用时，会使用swap分区。虽然 swap分区可以增大物理内存大小的限制，但是如果由于内存不足使用到swap分区，会增加系统的响应时间，性能变差。因此在物理内存充足或者性能敏感的系统中，不建议配置swap分区。 ->- 如果需要拆分逻辑卷组则需要选择“自定义”进行手动分区，并在“手动分区”界面单击“卷组”区域中的“修改”按钮重新配置卷组。 - -**自动** - -如果是在未使用过的存储设备中执行全新安装，或者不需要保留该存储设备中任何数据，建议选择“自动”进行自动分区。 - -**自定义** - -若用户需进行手动分区，选择“自定义”按钮，并单击左上角“完成”，出现如下手动分区界面。 - -**图 2** 手动分区 -![](figures/手动分区.png "手动分区") - -在“手动分区”界面可以通过如下两种方式进行分区。 - -- 自动创建：在界面单击“点击这里自动创建它们”，系统会根据可用的存储空间，自动分出4个挂载点：/boot 、/、/boot/efi、swap。 -- 手动创建：单击“![](figures/zh-cn_image_0229291243.png)”添加新挂载点，建议每个挂载点的期望容量不超过可用空间。 - - >![](public_sys-resources/icon-note.gif) **说明：** - >若设置的挂载点期望容量超过了可用空间，系统将剩余的可用空间全部分配给该挂载点。 - - -设置完成后，请单击左上角“完成”返回“安装概览”页面。 - diff --git "a/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\345\217\202\346\225\260.md" "b/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\345\217\202\346\225\260.md" deleted file mode 100644 index ef19e17fbd4cd2ab7bdef189eb0a7088f2427354..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\345\217\202\346\225\260.md" +++ /dev/null @@ -1,3 +0,0 @@ -# 设置安装参数 - - diff --git "a/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\346\272\220.md" "b/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\346\272\220.md" deleted file mode 100644 index 3bffea23fa3bc22f194382a1ce9aee3573c80a0e..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\346\272\220.md" +++ /dev/null @@ -1,19 +0,0 @@ -# 设置安装源 - -在“安装概览”页面中选择“安装源”，指定安装源的位置。 - -当使用完整光盘安装，安装程序会自动探测并显示安装源信息，用户直接使用默认配置即可，不需要进行设置，如[图1](#zh-cn_topic_0186390100_zh-cn_topic_0144427079_fig93633295132)所示。 - -**图 1** 安装源 -![](figures/安装源.png "安装源") - -当使用网络https源进行安装的时候，如果https服务器使用的是私有证书，则需要在安装引导界面按“e”进入已选选项的参数编辑界面，在参数中增加inst.noverifyssl参数，如[图2](#fig113517811415)所示。 - -**图 2** 增加inst.noverifyssl参数 -![](figures/增加inst-noverifyssl参数.png "增加inst-noverifyssl参数") - -设置完成后，请单击左上角“完成”返回“安装概览”页面。 - ->![](public_sys-resources/icon-note.gif) **说明：** ->安装过程中，如果“设置安装源”有疑问，可参考“FAQ \> 选择安装源出现异常”。 - diff --git "a/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\347\250\213\345\272\217\350\257\255\350\250\200.md" "b/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\347\250\213\345\272\217\350\257\255\350\250\200.md" deleted file mode 100644 index 60ce16f5eee260e3aa799825b479db49e5174033..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\256\276\347\275\256\345\256\211\350\243\205\347\250\213\345\272\217\350\257\255\350\250\200.md" +++ /dev/null @@ -1,11 +0,0 @@ -# 设置安装程序语言 - -启动安装后，在进入安装程序主界面之前，系统会提示用户设置安装过程中使用的语言。当前默认为英语，用户可根据实际情况进行调整，如[图1](#zh-cn_topic_0186390093_zh-cn_topic_0122145864_fig144630179151)所示，选择“中文”。 - -**图 1** 选择语言 -![](figures/选择语言.png "选择语言") - -完成设置后，单击“继续”，进入安装设置主界面。 - -如果您想退出安装，可以单击“退出”并在弹出的“您确定要退出安装程序吗？”对话框中单击“是”重新进入“安装引导界面”。 - diff --git "a/content/zh/docs/Installation/\350\256\276\347\275\256\346\227\266\351\227\264\345\222\214\346\227\245\346\234\237.md" "b/content/zh/docs/Installation/\350\256\276\347\275\256\346\227\266\351\227\264\345\222\214\346\227\245\346\234\237.md" deleted file mode 100644 index 3110ea9cef3bd987994d52a513c7fef25b1d7161..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\256\276\347\275\256\346\227\266\351\227\264\345\222\214\346\227\245\346\234\237.md" +++ /dev/null @@ -1,17 +0,0 @@ -# 设置时间和日期 - -在“安装概览”页面中选择“时间和日期”，设置系统的时区、日期、时间等。 - -设置时区时，用户可通过鼠标在地图上单击指定的城市，也可以通过页面顶部的“地区”和“城市”下拉菜单中进行选择，如[图1](#zh-cn_topic_0186390096_zh-cn_topic_0122145900_fig1260162652312)所示。 - -如果您所在城市没有出现在地图或下拉菜单中，请选择同一时区中离您最近的城市。 - ->![](public_sys-resources/icon-note.gif) **说明：** ->- 手动设置时区时，请先关闭右上角“网络时间”同步开关。 ->- 如需使用网络时间，请保证网络能连通远程NTP服务器，设置网络具体请参见“安装指导 \> 通过图形化模式安装 \> 设置安装参数 \> 设置网络和主机名”章节。 - -**图 1** 日期和时间 -![](figures/日期和时间.png "日期和时间") - -设置完成后，请单击左上角“完成”返回“安装概览”页面。 - diff --git "a/content/zh/docs/Installation/\350\256\276\347\275\256\347\263\273\347\273\237\350\257\255\350\250\200.md" "b/content/zh/docs/Installation/\350\256\276\347\275\256\347\263\273\347\273\237\350\257\255\350\250\200.md" deleted file mode 100644 index ff7142aefbca4e371aee0456f398f156aa9eb362..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\256\276\347\275\256\347\263\273\347\273\237\350\257\255\350\250\200.md" +++ /dev/null @@ -1,12 +0,0 @@ -# 设置系统语言 - -在“安装概览”页面中选择“语言支持”，设置系统的语言。如[图1](#zh-cn_topic_0186390098_zh-cn_topic_0122145772_fig187301927172619)所示，用户也可根据实际情况进行调整，选择“中文”。 - ->![](public_sys-resources/icon-note.gif) **说明：** ->若选择“中文”，系统安装完成后，使用VNC登录不支持中文显示，使用串口或者SSH等方式登录支持中文显示。若选择“English”，则无影响。 - -**图 1** 语言支持 -![](figures/语言支持.png "语言支持") - -设置完成后，请单击左上角“完成”返回“安装概览”页面。 - diff --git "a/content/zh/docs/Installation/\350\256\276\347\275\256\347\275\221\347\273\234\345\222\214\344\270\273\346\234\272\345\220\215.md" "b/content/zh/docs/Installation/\350\256\276\347\275\256\347\275\221\347\273\234\345\222\214\344\270\273\346\234\272\345\220\215.md" deleted file mode 100644 index 9eb6c39d8529c0021972ac53f01f6438ddcde67b..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\256\276\347\275\256\347\275\221\347\273\234\345\222\214\344\270\273\346\234\272\345\220\215.md" +++ /dev/null @@ -1,13 +0,0 @@ -# 设置网络和主机名 - -在“安装概览”页面中选择“网络和主机名”，设置系统的网络功能。 - -安装程序会自动探测可本地访问的接口。探测到的接口列在左侧方框中，右侧显示相应的接口详情，如[图1](#zh-cn_topic_0186390264_zh-cn_topic_0122145831_fig123700157297)所示。用户可以通过页面右上角的开关，来开启或者关闭网络接口。用户还可以单击“配置”以配置选中的接口。 - -用户可在页面下方“主机名”字段输入主机名。主机名可以是完全限定域名（FQDN），其格式为hostname.domainname；也可以是简要主机名，其格式为hostname。 - -**图 1** 网络和主机名 -![](figures/网络和主机名.png "网络和主机名") - -设置完成后，请单击左上角“完成”返回“安装概览”页面。 - diff --git "a/content/zh/docs/Installation/\350\256\276\347\275\256\351\224\256\347\233\230.md" "b/content/zh/docs/Installation/\350\256\276\347\275\256\351\224\256\347\233\230.md" deleted file mode 100644 index 9eead8f43e116dbd8adb7f149a84339e0ae894cd..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\256\276\347\275\256\351\224\256\347\233\230.md" +++ /dev/null @@ -1,12 +0,0 @@ -# 设置键盘 - -在“安装概览”页面中选择“键盘”，用户可以在系统中添加或者删除多个键盘布局。 - -- 要查看键盘布局，请在左侧选框中单击选中该键盘布局，然后单击下面的“键盘”按钮。 -- 要测试键盘布局，请在左侧选框中添加键盘布局，然后在右上角键盘图标处进行点击切换为目标键盘，单击右侧文本框内部，输入文本以确认所选键盘布局可正常工作。 - -**图 1** 键盘布局 -![](figures/键盘布局.png "键盘布局") - -设置完成后，请单击左上角“完成”返回“安装概览”页面。 - diff --git "a/content/zh/docs/Installation/\350\277\233\345\205\245\345\256\211\350\243\205\347\225\214\351\235\242.md" "b/content/zh/docs/Installation/\350\277\233\345\205\245\345\256\211\350\243\205\347\225\214\351\235\242.md" deleted file mode 100644 index b0731b4461c067412b3e4ed4602a51c83cb3068a..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\350\277\233\345\205\245\345\256\211\350\243\205\347\225\214\351\235\242.md" +++ /dev/null @@ -1,11 +0,0 @@ -# 进入安装界面 - -系统安装程序正常启动后，会进入[图1](#zh-cn_topic_0186390094_zh-cn_topic_0122145883_fig5969171592212)所示的安装设置主界面。用户可以进行时间、语言、安装源、网络、安装位置等相关设置。 - -部分配置项会有告警符号，用户完成该选项配置后，告警符号消失。当界面上不存在告警符号时，用户才能单击“开始安装”进行系统安装。 - -如果您想退出安装，可以单击“退出”并在弹出的“您确定要退出安装程序吗？”对话框中单击“是”重新进入“安装引导界面”。 - -**图 1** 安装概览 -![](figures/安装概览.png "安装概览") - diff --git "a/content/zh/docs/Installation/\351\200\211\346\213\251\345\256\211\350\243\205\346\272\220\345\207\272\347\216\260\345\274\202\345\270\270.md" "b/content/zh/docs/Installation/\351\200\211\346\213\251\345\256\211\350\243\205\346\272\220\345\207\272\347\216\260\345\274\202\345\270\270.md" deleted file mode 100644 index b09cbc9dbed1ddb63200764905ad64036a36006d..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\351\200\211\346\213\251\345\256\211\350\243\205\346\272\220\345\207\272\347\216\260\345\274\202\345\270\270.md" +++ /dev/null @@ -1,14 +0,0 @@ -# 选择安装源出现异常 - -## 问题现象 - -选择安装源后出现："Error checking software selection"。 - -## 原因分析 - -这种现象是由于安装源中的软件包依赖存在问题。 - -## 解决方法 - -检查安装源是否存在异常。使用新的安装源。 - diff --git "a/content/zh/docs/Installation/\351\200\211\346\213\251\345\256\211\350\243\205\350\275\257\344\273\266.md" "b/content/zh/docs/Installation/\351\200\211\346\213\251\345\256\211\350\243\205\350\275\257\344\273\266.md" deleted file mode 100644 index 3a38670627517f9d957dd5915b9cbcd5c6b40a0d..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\351\200\211\346\213\251\345\256\211\350\243\205\350\275\257\344\273\266.md" +++ /dev/null @@ -1,15 +0,0 @@ -# 选择安装软件 - -在“安装概览”页面中选择“软件选择”，指定需要安装的软件包。 - -用户需要根据实际的业务需求，在左侧选择一个“最小安装”，在右侧选择安装环境的附加选项，如[图1](#zh-cn_topic_0186390261_zh-cn_topic_0122145865_fig03031519101414)所示。 - -**图 1** 软件选择 -![](figures/软件选择.png "软件选择") - ->![](public_sys-resources/icon-note.gif) **说明：** ->- 在最小安装的环境下，并非安装源中所有的包都会安装。如果用户需要使用的包未安装，可将安装源挂载到本地制作repo源，通过DNF工具单独安装。 ->- 选择“虚拟化主机”时会默认安装虚拟化组件qemu、libvirt、edk2，且可在附件选项处选择是否安装ovs等组件。 - -设置完成后，请单击左上角“完成”返回“安装概览”页面。 - diff --git "a/content/zh/docs/Installation/\351\200\232\350\277\207USB\347\233\230\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/\351\200\232\350\277\207USB\347\233\230\345\256\211\350\243\205.md" deleted file mode 100644 index c19910b57d0b4eb07af5ee18b90ac2d5d84eb8d4..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\351\200\232\350\277\207USB\347\233\230\345\256\211\350\243\205.md" +++ /dev/null @@ -1,77 +0,0 @@ -# 通过USB盘安装 - -本节介绍如何制作USB盘安装源，并介绍基本的操作步骤，指导用户进行安装。 - -## 准备安装源 - -您需要注意USB盘容量的大小，它必须有足够的的空间放下整个镜像，建议USB盘空间大于16G。 - -1. 将USB盘连接到该系统中，并执行 dmesg 命令查看相关的日志信息。在该日志的最后可以看到刚刚连接的USB盘所生成的一组信息，应类似如下： - - ``` - [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk - ``` - - >![](public_sys-resources/icon-note.gif) **说明：** - >连接的USB盘名称以sdb进行举例。 - -2. 切换为root用户。使用su命令，需要输入相应的密码。 - - ``` - $ su - root - ``` - -3. 确保USB盘没有被挂载。使用如下命令进行查询： - - ``` - # findmnt /dev/sdb - ``` - - - 如果执行此命令后无输出，表明未挂载，可以继续执行下一步。 - - 如果输出以下信息，表明USB盘已经自动挂载。 - - ``` - # findmnt /dev/sdb - TARGET SOURCE FSTYPE OPTIONS - /mnt/iso /dev/sdb iso9660 ro,relatime - ``` - - 此时，您需要使用umount命令卸载该设备。 - - ``` - # umount /mnt/iso - ``` - -4. 使用dd命令将ISO安装镜像直接写入USB盘： - - ``` - # dd if=/path/to/image.iso of=/dev/device bs=blocksize - ``` - - 使用您下载的ISO镜像文件的完整路径替换 /path/to/image.iso，使用之前由 dmesg 命令给出的设备名称替换device，同时设置合理的块大小（例如：512k）替换 blocksize，这样可以加快写入进度。 - - 例如：如果该ISO镜像文件位于 /home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso，同时探测到的设备名称为sdb，则该命令如下： - - ``` - # dd if=/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso of=/dev/sdb bs=512k - ``` - -5. 等待镜像写入完成，拔掉USB盘。 - - 镜像写入过程中不会有进度显示，当\#号再次出现时，表明写入完成。退出root账户，拔掉USB盘。此时，您可以使用该USB盘作为系统的安装源。 - - -## 启动安装 - -请根据以下步骤启动安装程序： - ->![](public_sys-resources/icon-note.gif) **说明：** ->您需要先设置您的系统优先从USB进行启动引导。以BIOS为例，您需要将“Boot Type Order”中的USB选项调整到首位。 - -1. 断开所有安装不需要的驱动器。 -2. 打开您的计算机系统。 -3. 在计算机中插入USB盘。 -4. 重启计算机系统。 - -在短暂的延迟后会出现图形化引导页面，该页面包含不同引导选项。如果您在一分钟内未进行任何操作，安装程序将自动开始安装。 - diff --git "a/content/zh/docs/Installation/\351\200\232\350\277\207qcow2\351\225\234\345\203\217\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/\351\200\232\350\277\207qcow2\351\225\234\345\203\217\345\256\211\350\243\205.md" deleted file mode 100644 index 3fd69068711bffa61e94b6db55b66484d22a2145..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\351\200\232\350\277\207qcow2\351\225\234\345\203\217\345\256\211\350\243\205.md" +++ /dev/null @@ -1,46 +0,0 @@ -# 通过qcow2镜像安装 - -本节介绍如何使用或者制作qcow2镜像，并介绍相应的操作步骤，指导用户进行安装。 - -## 制作qcow2镜像 - -1. 安装qemu-img软件包。 - - ``` - # dnf install -y qemu-img - ``` - -2. 使用qemu-img工具的create命令，创建镜像文件，命令格式为： - - ``` - $ qemu-img create -f -o - ``` - - 其中，各参数含义如下： - - - _imgFormat_ ：镜像格式，取值为raw, qcow2等。 - - _fileOption_ ：文件选项，用于设置镜像文件的特性，如指定后端镜像文件，压缩，加密等特性。 - - _f__ileName_ ：文件名称。 - - _diskSize_ ：磁盘大小，用于指定块磁盘设备的大小，支持的单位有K、M、G、T，分别代表KiB、MiB、GiB、TiB。 - - 例如，创建一个磁盘设备大小为32GB、格式为qcow2的镜像文件openEuler-imge.qcow2，命令和回显如下： - - ``` - $ qemu-img create -f qcow2 openEuler-image.qcow2 32G - Formatting 'openEuler-image.qcow2', fmt=qcow2 size=34359738368 cluster_size=65536 lazy_refcounts=off refcount_bits=16 - ``` - - -## 启动安装 - -根据以下步骤启动安装程序： - -1. 准备qcow2镜像文件。 -2. 准备虚拟机网络。 -3. 准备UEFI引导工具集EDK II。 -4. 准备虚拟机XML配置文件。 -5. 创建虚拟机。 -6. 启动虚拟机。 - -各步骤详细的操作请参考《openEuler 20.03 LTS 虚拟化用户指南》。 - diff --git "a/content/zh/docs/Installation/\351\200\232\350\277\207\345\205\211\347\233\230\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/\351\200\232\350\277\207\345\205\211\347\233\230\345\256\211\350\243\205.md" deleted file mode 100644 index f5cdc407ef7774b439205a3f95e47bd41b79ebf8..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\351\200\232\350\277\207\345\205\211\347\233\230\345\256\211\350\243\205.md" +++ /dev/null @@ -1,22 +0,0 @@ -# 通过光盘安装 - -本节介绍如何使用或者制作光盘安装源，并介绍相应的操作步骤，指导用户进行安装。 - -## 准备安装源 - -如果您获取的是系统安装光盘，那么可以直接使用光盘安装系统。如果您获取的是系统ISO镜像，可以通过刻录软件将系统的ISO镜像刻录到DVD中，使用刻录完成的DVD安装系统。 - -## 启动安装 - -根据以下步骤启动安装程序： - ->![](public_sys-resources/icon-note.gif) **说明：** ->您需要先设置您的系统优先从光盘进行启动引导。以BIOS为例，您需要将“Boot Type Order”中的“CD/DVD-ROM Drive”选项调整到首位。 - -1. 断开所有安装不需要的驱动器，比如USB。 -2. 启动您的计算机系统。 -3. 在计算机中插入安装光盘。 -4. 重启计算机系统。 - -在短暂的延迟后会出现图形化引导界面，该界面包含不同引导选项。如果您在一分钟内未进行任何操作，安装程序将自动以默认选项开始运行。 - diff --git "a/content/zh/docs/Installation/\351\200\232\350\277\207\345\233\276\345\275\242\345\214\226\346\250\241\345\274\217\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/\351\200\232\350\277\207\345\233\276\345\275\242\345\214\226\346\250\241\345\274\217\345\256\211\350\243\205.md" deleted file mode 100644 index 316d71156c83c7923f925a7c7727210dcd088cb9..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\351\200\232\350\277\207\345\233\276\345\275\242\345\214\226\346\250\241\345\274\217\345\256\211\350\243\205.md" +++ /dev/null @@ -1,13 +0,0 @@ -# 通过图形化模式安装 - -在“安装引导界面”中选择“Test this media & install openEuler 20.03 LTS”进入图形化模式安装。 - -可以通过键盘操作图形化安装程序。 - -- “Tab”、“shift Tab”：界面控件（按钮、区域框、复选框等）间的移动。 -- “↑”、“↓”方向键：列表里的移动。 -- “←”、“→”方向键：水平工具条和表条间移动。 -- “空格”、“Enter”：选择或删除高亮显示的选项、展开或折叠下拉菜单。 -- “Alt”+“快捷键”：选择快捷键所在的控件，其中快捷键可通过按住Alt高亮（加下划线）显示。 - - diff --git "a/content/zh/docs/Installation/\351\200\232\350\277\207\347\247\201\346\234\211\351\225\234\345\203\217\345\256\211\350\243\205.md" "b/content/zh/docs/Installation/\351\200\232\350\277\207\347\247\201\346\234\211\351\225\234\345\203\217\345\256\211\350\243\205.md" deleted file mode 100644 index 18a88360823065f1c058ec5dd2311d1a3095aed6..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\351\200\232\350\277\207\347\247\201\346\234\211\351\225\234\345\203\217\345\256\211\350\243\205.md" +++ /dev/null @@ -1,12 +0,0 @@ -# 通过私有镜像安装 - -本节介绍如何使用或者制作私有镜像，并介绍相应的操作步骤，指导用户进行安装。 - -## 制作私有镜像 - -制作私有镜像的方法请参见[《镜像服务用户指南》](https://support.huaweicloud.com/usermanual-ims/zh-cn_topic_0013901628.html)。 - -## 启动安装 - -华为公有云的x86虚拟化平台的启动请参见[ 弹性云服务器 ECS的用户指南](https://support.huaweicloud.com/wtsnew-ecs/index.html)。 - diff --git "a/content/zh/docs/Quickstart/\345\277\253\351\200\237\345\205\245\351\227\250.md" "b/content/zh/docs/Quickstart/\345\277\253\351\200\237\345\205\245\351\227\250.md" index cbd7444679648fe8a9fb014493dd203e4f6ccded..5a7804c577562f3ed188c1af6e0ae4834673c2d7 100644 --- "a/content/zh/docs/Quickstart/\345\277\253\351\200\237\345\205\245\351\227\250.md" +++ "b/content/zh/docs/Quickstart/\345\277\253\351\200\237\345\205\245\351\227\250.md" @@ -1,8 +1,19 @@ -# 快速入门 +# 快速入门 本文档以TaiShan 200服务器上安装openEuler 20.03 LTS为例，旨在指导用户快速地安装和使用openEuler操作系统，更详细的安装要求和安装方法请参考《[openEuler 20.03 LTS 安装指南](https://openeuler.org/zh/docs/20.03_LTS/docs/Installation/installation.html)》。 + -## 安装要求 +- [快速入门](#快速入门) + - [安装要求](#安装要求) + - [获取安装源](#获取安装源) + - [发布包完整性校验](#发布包完整性校验) + - [启动安装](#启动安装) + - [安装](#安装) + - [查看系统信息](#查看系统信息) + + + +## 安装要求 - 硬件兼容支持 @@ -85,7 +96,7 @@ -## 获取安装源 +## 获取安装源 请按以下步骤获取openEuler的发布包和校验文件： @@ -111,7 +122,7 @@ -## 发布包完整性校验 +## 发布包完整性校验 为了防止软件包在传输过程中由于网络原因或者存储设备原因出现下载不完整的问题，在获取到软件包后，可按以下步骤将获取到的openEuler的软件包进行完整性校验。 @@ -134,7 +145,7 @@ 如果校验值一致说明iso文件完整性没有破坏，如果校验值不一致则可以确认文件完整性已被破坏，需要重新获取。 -## 启动安装 +## 启动安装 1. 登录服务器iBMC Web界面。具体方法请参考《[TaiShan 200 服务器 用户指南 \(型号 2280\) ](https://support.huawei.com/enterprise/zh/doc/EDOC1100088652)》。 2. 在上方标题栏中，选择“配置”，在左侧导航树中选择“系统启动项”，显示“系统启动项”界面。 @@ -176,7 +187,7 @@ 9. 在安装引导界面，按“Enter”，进入默认选项“Test this media & install openEuler 20.03 LTS”的图形化安装界面。 -## 安装 +## 安装 进入图形化安装界面后，按如下步骤进行安装。 @@ -288,7 +299,7 @@ -## 查看系统信息 +## 查看系统信息 系统安装完成并重启后直接进入系统命令行登录界面，输入安装过程中设置的用户和密码，进入openEuler操作系统，查看如下系统信息。若需要进行系统管理和配置操作，请参考《[openEuler 20.03 LTS 管理员指南](https://openeuler.org/zh/docs/20.03_LTS/docs/Administration/administration.html)》。 diff --git "a/content/zh/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md" "b/content/zh/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md" index 657a789d8dd73fb5b41416bde0a7471181b83899..333a56434fd39d9fe8ea65edf8781340dd607470 100644 --- "a/content/zh/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md" +++ "b/content/zh/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md" @@ -6,7 +6,7 @@ **商标声明** -A-Tune、openEuler为华为技术有限公司的商标。本文档提及的其他所有商标或注册商标，由各自的所有人拥有。 +openEuler为华为技术有限公司的商标。本文档提及的其他所有商标或注册商标，由各自的所有人拥有。 **免责声明** diff --git a/content/zh/menu/index.md b/content/zh/menu/index.md index 93bb6896160875befe7d9846ed596a90a275d47f..7b8b661fa4dba3a3470ee8ef6446550f490eea4a 100644 --- a/content/zh/menu/index.md +++ b/content/zh/menu/index.md @@ -17,39 +17,11 @@ headless: true - [快速入门]({{< relref "./docs/Quickstart/快速入门.md" >}}) - [安装指南]({{< relref "./docs/Installation/installation.md" >}}) - - [前言]({{< relref "./docs/Installation/前言.md" >}}) - [安装准备]({{< relref "./docs/Installation/安装准备.md" >}}) - [安装方式介绍]({{< relref "./docs/Installation/安装方式介绍.md" >}}) - [安装指导]({{< relref "./docs/Installation/安装指导.md" >}}) - - [启动安装]({{< relref "./docs/Installation/启动安装.md" >}}) - - [设置安装程序语言]({{< relref "./docs/Installation/设置安装程序语言.md" >}}) - - [进入安装界面]({{< relref "./docs/Installation/进入安装界面.md" >}}) - - [设置安装参数]({{< relref "./docs/Installation/设置安装参数.md" >}}) - - [设置键盘]({{< relref "./docs/Installation/设置键盘.md" >}}) - - [设置系统语言]({{< relref "./docs/Installation/设置系统语言.md" >}}) - - [设置时间和日期]({{< relref "./docs/Installation/设置时间和日期.md" >}}) - - [设置安装源]({{< relref "./docs/Installation/设置安装源.md" >}}) - - [选择安装软件]({{< relref "./docs/Installation/选择安装软件.md" >}}) - - [设置安装位置]({{< relref "./docs/Installation/设置安装位置.md" >}}) - - [设置网络和主机名]({{< relref "./docs/Installation/设置网络和主机名.md" >}}) - - [开始安装]({{< relref "./docs/Installation/开始安装.md" >}}) - - [安装过程配置]({{< relref "./docs/Installation/安装过程配置.md" >}}) - - [安装完成]({{< relref "./docs/Installation/安装完成.md" >}}) - - [使用kickstart自动化安装]({{< relref "./docs/Installation/使用kickstart自动化安装.md" >}}) - - [总体介绍]({{< relref "./docs/Installation/总体介绍.md" >}}) - - [半自动化安装指导]({{< relref "./docs/Installation/半自动化安装指导.md" >}}) - - [全自动化安装指导]({{< relref "./docs/Installation/全自动化安装指导.md" >}}) - - [FAQ]({{< relref "./docs/Installation/FAQ.md" >}}) - - [安装openEuler时选择第二盘位为安装目标，操作系统无法启动]({{< relref "./docs/Installation/安装openEuler时选择第二盘位为安装目标-操作系统无法启动.md" >}}) - - [网络配置约束限制]({{< relref "./docs/Installation/网络配置约束限制.md" >}}) - - [openEuler开机后进入emergency模式]({{< relref "./docs/Installation/openEuler开机后进入emergency模式.md" >}}) - - [系统中存在无法激活的逻辑卷组时，重装系统失败]({{< relref "./docs/Installation/系统中存在无法激活的逻辑卷组时-重装系统失败.md" >}}) - - [选择安装源出现异常]({{< relref "./docs/Installation/选择安装源出现异常.md" >}}) - - [如何手动开启kdump服务]({{< relref "./docs/Installation/如何手动开启kdump服务.md" >}}) - - [多块磁盘组成逻辑卷安装系统后，再次安装不能只选其中一块磁盘]({{< relref "./docs/Installation/多块磁盘组成逻辑卷安装系统后-再次安装不能只选其中一块磁盘.md" >}}) - - [x86物理机UEFI模式由于security boot安全选项问题无法安装]({{< relref "./docs/Installation/x86物理机UEFI模式由于security-boot安全选项问题无法安装.md" >}}) - [管理员指南]({{< relref "./docs/Administration/administration.md" >}}) - [前言]({{< relref "./docs/Administration/前言.md" >}})