From: Bryan Fields <Bryan@bryanfields.net>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] 8.2-1 ISO doesn't boot via UEFI on usb
Date: Fri, 6 Sep 2024 19:07:42 -0400 [thread overview]
Message-ID: <6b8cdfd2-7246-2047-a9b4-64a77f8dcdbf@bryanfields.net> (raw)
In-Reply-To: <mailman.99.1725653507.414.pve-user@lists.proxmox.com>
On 9/6/24 4:06 PM, Stefan Radman via pve-user wrote:
> I’ve been using both Ventoy <https://www.ventoy.net/en/index.html> and YUMI <https://pendrivelinux.com/yumi-multiboot-usb-creator/> to install PVE 8.2-1 from USB thumbdrives on Dell servers (UEFI by default).
> Works very well for me.
>
> My “PVE Install & Rescue” thumb drive contains several LiveCD ISO images alongside the PVE ISO:
> * clonezilla to backup the boot drive(s)
> * gparted
> other useful tools for troubleshooting as well as the host's clonezilla image if needed.
> Makes my life a lot easier.
>
> Ventoy claims to support Secure Boot in UEFI Mode <https://www.ventoy.net/en/doc_secure.html>
> Haven’t tried PVE installation with secure boot enabled though and would be interested to hear from someone who has.
I used ventoy to boot the proxmox-ve_8.2-2.iso (using the GRUB), it was able
to boot, detect UEFI and did an install with the UEFI loader. I rebooted the
the system locked hard right after"
10.691682] acpi device:17c: hash matches
10.692362] acpi LMXCPU:04: hash matches
10.692790] acpi PNPOA03:00: hash matches
10.718413] RAS: Correctable Errors collector initialized.
10.719105] clk: Disabling unused clocks
10.830285] atal: SATA link down (Status 0 SControl 330)
10.830662] ata2: SATA link down (Status 0 Control 330)
[10.830996] md: Waiting for all devices to be available before autodetect
I disabled md autodetect and it still hard locked at the ata2: line.
I tried to boot the following directly (it's using ipmi emulating the cdrom
from a http directory) and none would boot.
proxmox-ve_8.1-2.iso
proxmox-ve_8.2-1.iso
proxmox-ve_8.2-2.iso
proxmox-ve_7.4-1.iso did boot and let me run through an install, and booted.
I'm going to try an in-situ upgrade from it to 8.2.2.
Now I'm thinking there may be some issue with disk detection on this during
boot, as I ran into this on my other recent server build, it seemed the EFI
bootloader wanted to scan all the drives on the SAS HBA, but I disconnected it
and it went much faster at boot. This current server has 45 disks across a
couple expanders and I cannot disable them in the bios to try this theory.
As of now, this seems to be a bug relating to supermicro x10/x11 servers with
the 8.x distros.
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-09-06 23:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 11:52 Bryan Fields
2024-08-21 12:10 ` Gilberto Ferreira
2024-08-21 12:10 ` Bryan Fields
2024-08-21 12:20 ` FingerlessGloves via pve-user
2024-08-21 12:39 ` Demian Romeijn via pve-user
2024-08-21 16:17 ` Bryan Fields
2024-09-06 17:28 ` Bryan Fields
2024-09-06 20:06 ` Stefan Radman via pve-user
2024-09-06 23:07 ` Bryan Fields [this message]
2024-09-07 0:04 ` [PVE-User] Proxmox 8.x UEFI boot issues on supermicro x10/x11 (was 8.2-1 ISO doesn't boot via UEFI on usb) Bryan Fields
2024-09-07 9:42 ` Gilberto Ferreira
2024-09-07 16:47 ` Bryan Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b8cdfd2-7246-2047-a9b4-64a77f8dcdbf@bryanfields.net \
--to=bryan@bryanfields.net \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox