Recent content by NerdUno

http://forum.proxmox.com/threads/23923-Proxmox-4-Won-t-Boot-Automatically?p=120613#post120613

Nerd Vittles is pleased to announce the release of our new Unified Communications Server tutorial for Proxmox 4. Comments/suggestions are always welcomed.

1. True as long as the GPT drive on a non-UEFI platform also has a master boot record. Non-UEFI platforms know nothing about a GUID Partition Table (GPT) so a GPT-only drive would not boot without UEFI. 2. True up to "so..." The drive format matters because the GPT disk label tells a...

Let's try this from a different angle. You said Proxmox always labels a drive as GPT whether it is or not. As you observed, this doesn't cause a problem with a legacy machine such as your HP DL160 which is non-UEFI. The reason is because that machine only knows how to boot using the MBR so it...

The problem is Proxmox not honoring the Legacy Boot setting in the BIOS. You should never have a GPT-partitioned disk on a non-UEFI or UEFI-disabled machine, and Proxmox should honor that just as all the other operating systems do. Having spent two days on this, it doesn't matter to me...

Let's just agree that somebody is wrong. Having a GPT partition can (and often does) cause problems on a non-UEFI machine or on a machine on which UEFI is disabled. See https://en.wikipedia.org/wiki/BIOS_boot_partition and https://wiki.archlinux.org/index.php/GUID_Partition_Table.

No, GPT is set by Proxmox during the install based upon the fact that your motherboard has (not uses) UEFI to control the drive. Whether the drive itself can function as a UEFI device without further tweaking in the BIOS is what makes the drive UEFI-compatible. Some can and many cannot. So it...

http://www.farstone.com/articles/what-is-uefi.php

The issue is whether you have a UEFI-compatible drive. If so, it obviously will work fine. If not, it won't... even with UEFI disabled in the BIOS.

Not sure how to say it any more clearly. It's a bug because the Proxmox installer does not honor the BIOS setting that has disabled UEFI on the machine. Proxmox creates a GPT disk label type that only can be used on a UEFI-enabled machine. Thus, it will not boot from power on. And, no, "all...

That was my first thought as well. But the problem is that this only happens with the Proxmox installer. CentOS 6.7 and Ubuntu 14.04 install fine, and system boots properly. To repeat, the Proxmox installer is NOT honoring the BIOS settings for UEFI and Legacy boot. If UEFI is set OFF and Legacy...

The problem with the design (as documented above) is that you end up with servers that won't boot automatically and a cryptic message that "no boot device was found." Since we're talking about Intel motherboards with Intel BIOS, this isn't a rare occurrence and will become more prevalent as more...

So... to document the BUG... Proxmox 4.0 and 3.x incorrectly determine that servers are UEFI devices even when UEFI is turned off and legacy mode (only) is enabled in the BIOS. Whether this is due to incorrect information being passed from Intel's BIOS or whether it is a misinterpretation of...

For those that are interested, here's the partition layout when the Proxmox installer finishes: This causes all sorts of problems for backup software such as Clonezilla because it doesn't expect to find a bios_grub partition on a GPT-partitioned server. So... it skips /dev/sda1 during backup...

Sorry that my link did not meet your standards of political correctness. Wasn't aware that LMGTFY should only be used to insult people. But since you're apparently the resident expert on insults, I'll take your word for it. As for the real issue, here's the solution: When you reboot the...