Click here to view detailed analysis and solution
openEuler-24.03-LTS-SP1 Installation Failure: System Won’t Boot After Installation
Based on your provided information, you encountered a system boot failure after installing openEuler-24.03-LTS-SP1 on an HP 280G PC. Although the installation appeared successful, the system fails to boot after restart, reporting “no bootable disk found.” Below is a comprehensive analysis of potential causes and solutions, based on information from the knowledge base.
Problem Summary
| Disk Model |
Installation Result |
Can Boot After Restart? |
| WD3200AAJS (Western Digital) |
Multiple successful installations |
All failed to boot |
| ST3320418AS (Seagate) |
First installation succeeded |
Only first time worked; subsequent attempts failed |
Both disks successfully install and boot CentOS 7 and Rocky Linux 9.7, indicating no major hardware compatibility or BIOS configuration issues.
This issue exhibits unpredictable behavior (occasionally successful), suggesting the root cause may lie in boot configuration, disk selection, or low-level driver/compatibility problems.
Possible Causes Analysis
1. Boot Loader Not Correctly Installed
From the knowledge graph:
"Boot Loader Install Failed" is an error message indicating that the system failed to install the boot loader, which prevents the system from booting.
"The failure was due to incorrect selection of the hard disk during the boot loader installation process."
Even if the installer reports “installation complete,” if the GRUB boot loader is not correctly written to the target disk’s MBR or EFI partition, the BIOS/UEFI will fail to detect a bootable device upon reboot.
Troubleshooting Suggestions:
- During installation, explicitly specify the target disk (e.g.,
/dev/sda) for boot loader installation — do not rely on automatic selection.
- Verify that the boot loader was not mistakenly installed on the USB drive or another temporary device.
- Confirm that the installed disk is set as the first boot device in BIOS.
2. Disk Compatibility or Firmware Issues
Although both disks work with other Linux distributions (e.g., CentOS/Rocky), openEuler uses a newer kernel and installer (Anaconda), which may expose:
- Kernel-level incompatibility with older AHCI controllers on certain HDD models
- GRUB2 bugs in handling specific disk partition tables or GPT formats
The openEuler-24.03-LTS-SP1-x86_64-dvd release has reported system freeze during reboot issues.
This could be related to disk response latency, power management (ACPI), or firmware quirks.
3. Filesystem Anomalies or Insufficient /boot Partition Space
The knowledge base states:
"Boot Partition is a dedicated disk partition essential for system startup... The Boot Partition is typically mounted at /boot."
"Insufficient space in the boot partition was identified as the direct cause of the installation failure."
If the /boot partition is too small or incorrectly created, the kernel image cannot be written, leading to boot failure.
Troubleshooting Suggestions:
- Use Manual Partitioning during installation.
- Ensure
/boot partition is at least 1GB (recommended: 2GB).
- Format as
ext4.
- Set the correct mount point (
/boot).
4. UEFI/BIOS Mode Mismatch or Boot Conflict
The HP 280G supports both UEFI and Legacy BIOS modes.
- If the ISO is booted in UEFI mode, but BIOS is set to Legacy-only, boot fails.
- Conversely, if installed in Legacy mode but the system attempts UEFI boot on restart, failure occurs.
Recommended Consistent Settings:
| Item |
Recommended Value |
| BIOS Boot Mode |
Legacy Mode (CSM Enabled) |
| USB Boot Drive Creation |
Use Rufus with MBR + BIOS (or UEFI-CSM) |
| Disk Partition Table |
Use MBR (msdos) to avoid GPT compatibility issues |
Note: Using GPT with BIOS mode requires an additional BIOS boot partition (1MB, unformatted) to store GRUB core.
5. ACPI or Hardware Initialization Issue
Log entries have shown:
ACPI Warning: \\\\_SB.PCO0.PEG1.PEGP._DSM: Argument #4 type mismatch
Although this log comes from a different context, it indicates that openEuler enforces stricter ACPI behavior on older platforms. You can try bypassing this via kernel parameters.
Add Kernel Parameters to Bypass:
In the GRUB boot menu (press e to edit), append one of the following:
acpi=off # Disables ACPI (use only in extreme cases; affects power management)
noapic # Disables Advanced Programmable Interrupt Controller
nomodeset # Disables GPU driver initialization
Or use a gentler approach:
acpi=strict # Enforces standard ACPI behavior
Recommended Solution Steps
Suggested Workflow:
-
Create Bootable USB Using openEuler-24.03-LTS-SP1-everything-x86_64-dvd.iso
- Use Rufus, set:
- Partition scheme: MBR
- Target system: BIOS (or UEFI-CSM)
- File system: FAT32
- Run Rufus as Administrator
-
Enter BIOS Setup (Press F10)
- Disable Secure Boot
- Set boot mode to Legacy (enable CSM)
- Confirm SATA mode is AHCI
-
During Installation: Choose “Manual Partitioning”
- Delete existing partition tables
- Manually create:
/boot: 2 GB, ext4
/: Remaining space, ext4
- (Optional) swap: ≥ physical RAM size
- Ensure boot loader is installed to the target disk (e.g.,
/dev/sda)
-
Reboot and Select Hard Disk as Boot Device
- If still failing, check BIOS to confirm disk is detected as bootable
-
If Boot Still Fails: Use Rescue Mode
Summary
| Possible Cause |
Evidence |
Recommended Action |
| Boot loader not properly installed |
Knowledge graph mentions “Boot Loader Install Failed” related to disk selection |
Manually specify the boot installation disk |
| BIOS/UEFI mode mismatch |
HP 280G supports multiple modes |
Force use of Legacy + MBR |
Insufficient space in /boot partition |
Prevents kernel image from being written |
Manually set /boot ≥ 2GB |
| Disk compatibility or firmware issues |
One successful installation suggests not fully incompatible |
Replace disk or update BIOS |
| ACPI initialization issue |
ACPI warning logs present |
Add acpi=off or noapic kernel parameter |
Follow-up Verification Suggestions
To improve success rate, try the following combinations:
- Replace disk with a newer Seagate model
- Update HP BIOS to the latest version
- Use
netinst ISO + manual partitioning + console-only installation (reduces GUI interference)
If you’re willing to provide additional details such as:
- GRUB installation target
- Partition layout
- BIOS settings screenshot or logs
We can perform deeper diagnostics.
For further assistance, please submit a detailed report on the openEuler Official Forum.