- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Servers - General
- >
- Re: Can't boot over uefi pxe on new HPE ProLiant D...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2022 06:42 AM - last edited on 04-06-2022 09:05 PM by support_s
03-31-2022 06:42 AM - last edited on 04-06-2022 09:05 PM by support_s
Hi together,
I'm trying to setup a diskless Rhel 8 HPE Server. The boot images are provided over pxe over uefi. All boot images are built with Ansible automation language (Redhat).
When I'm trying to boot over pxe and select my menu entry, I'm getting the following error message (Unfortunately I don't have permissions to upload pictures):
error: ../../grub-core/loader/-386/efi/linux/.c:119:cant' allocate initrd.
Press any key to continue...
After pressing continue the boot progress continues, but after a view seconds a kernel panic appears:
2.0219551 Kernel panic- not syncing: UFS: Unable to mount root fs on unknown-Block(0,07
2.0219571 CPU: 4 PID: 1 Comm: swapper/0 Not tointed 4.10.0-740.cl0.x06 64 #1
2.021956] Harduare name: HPE ProLiant DL380 Gen10 Plus/Proliant DL360 Gen10 Plus, BIOS 016 01/13/2022
2.0375321 tsc: Refined 13C clocksource calibration: 0591.522 M lz
2.010969] Call Trace:
2.0409731 dump_slack+0x5c/0xB0
2.0109751 panicrOxc7/0x209
2.040977] mount block root+Ox2be/0x2e2
2.0409001 ? do_early_param+0x91/0x91
2.0109611 prepare_namespace+0x135/0x16b
2.0409021 kernel_init frecable+0xtle/0x220
2.0109841 ? rest_initroxad/Oxaa
2.0409051 kernel init+Oxa/Oxf6
2.0109861 ret, fron_ fork+0xlf/0x10
2.0410651 Kernel Offset: 0x25c00000 from Oxffffff81000000 Crelocation range: Oxffff((f(B0000000-Oxffffft
2.2506721 -I end Kernel panic noz syncing: UFS: Unable to mount ront fs on unknnun-block(0,0)
Environment:
- DHCP and TFTP server on a ubuntu server
What I have already done:
- Updated the HPE Firmware and ILO Version
- Tested the diskless initramfs image inside a VMware virtual machine -> vm booted fast and completly into the system
- Tested the diskless initramfs image on an older Intel Bare Metal Server -> server booted completly into the system
- Unfortunately when I'm trying to boot over legacy the server don't request a dhcp address.
I would be very happy if someone can help me solving these problems. Thank you for your help.
Best regards
Manuel
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2022 07:42 AM
03-31-2022 07:42 AM
Query: Can't boot over uefi pxe on new HPE ProLiant DL380 Gen10 Plus Server
System recommended content:
2. HPE ProLiant DL380 Gen10 Plus Server User Guide
Please click on "Thumbs Up/Kudo" icon to give a "Kudo".
Thank you for being a HPE valuable community member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2022 09:02 PM
04-06-2022 09:02 PM
Solution
Enable PXE boot for the desired network interface first before changing the boot mode to Legacy.
Try to reduce the size of the image, likely due to bigger size its unable load/allocate.
Refer following third party article , this might be useful
https://bugzilla.redhat.com/show_bug.cgi?id=1572126
>