mbr - Intel BOXDH77KC won't boot Linux GPT disk
2013-10
CajunLuke
To be complete, it won't get to grub without going through the boot menu - even if the disk is the only option in the boot menu. (It's annoying enough that I have to hit F10 every time I boot that I never allowed it to finish booting, though it might have.)
I'm using Linux Mint (the latest), installed off a USB disk, booting from an mSATA drive. There are no other drives in the system and I've turned network booting off. Windows is not involved anywhere.
The Question: how can I boot Linux from a GPT-formatted mSATA disk on this motherboard?
(I'm now reinstalling, having re-formatted the drive MBR/msdos in hopes that this will work, so I'm mostly interested academically. I'm not done setting the build up, though, so I can reformat and reinstall to try things if that'd be useful.)
Edit: I should also mention that either a) the drive came MBR-formatted from the factory or b) the Mint installer formatted the disk MBR. I'm not really certain which. When I noticed this in the first install, I changed the partition table to GPT, and thus our story begins.
Rod Smith
This is a guess that you likely won't be able to confirm, given that you're now re-installing, but....
My guess is that you installed in BIOS mode on a GPT disk. I'm not familiar with recent Intel motherboards, but as of a couple of years ago, Intel boards with that configuration required that the EFI protective partition in the MBR (the type-0xEE partition that spans the whole disk) be marked as bootable in order to enable BIOS-mode booting from GPT disks. Alternatively, you could have gotten it to work by creating an EFI System Partition (ESP), installing an EFI-mode boot loader, and booting in EFI mode.
Phenom
I have a 64-bit AMD Phenom II and I'm installing a new hard drive on it. One of the options when formatting the drive is to use a GPT partition table instead of an MBR. I read somewhere that only Itaniums can boot disks formatted with GPT. What about AMDs?
Also, are there any advantages of using GPT instead of MBR for a partition table? Is it more secure?
William Hilsum
I read somewhere that only Itaniums can boot disks formatted with GPT. What about AMDs?
AMD Opteron server CPUs certainly do support GUID Partition Tables.
are there any advantages of using GPT instead of MBR for a partition table? Is it more secure?
- What is a GPT disk? The GUID Partition Table (GPT) was introduced as part of the Extensible Firmware Interface (EFI) initiative. GPT provides a more flexible mechanism for partitioning disks than the older Master Boot Record (MBR) partitioning scheme that has been common to PCs.
A partition is a contiguous space of storage on a physical or logical disk that functions as though it were a physically separate disk. Partitions are visible to the system firmware and the installed operating systems. Access to a partition is controlled by the system firmware before the system boots the operating system, and then by the operating system after it starts.
- What is wrong with MBR partitioning? MBR disks support only four partition table entries. If more partitions are wanted, a secondary structure known as an extended partition is necessary. Extended partitions can then be subdivided into one or more logical disks. By convention, Windows creates MBR disk partitions and logical drives on cylinder boundaries based on the reported geometry, although this information no longer has any relationship to the physical characteristics of the hardware (disk driver or RAID controller)., For Windows Vista and Windows Server 2008, more logical boundaries will be selected when the hardware provides better hints at the true cache or physical alignment. Because this partition information is stored on the drive itself, the operating system is not dependent on the alignment. MBR partitioning rules are complex and poorly specified. For example, does cylinder alignment mean that each partition must be at least one cylinder in length? An MBR partition is identified by a two-byte field, and coordination is necessary to avoid collision. IBM originally provided that coordination; today there is no single authoritative list of partition identifiers.
Another common practice is to use partitioned or "hidden" sectors to hold specific information. That practice is undocumented and results in severe system problems that are difficult to debug. Over the years, vendor-specific implementations and tools have been released to the public, making support difficult.
- Why do we need GPT? GPT disks can grow to a very large size. The number of partitions on a GPT disk is not constrained by temporary schemes such as container partitions as defined by the MBR Extended Boot Record (EBR).
The GPT disk partition format is well defined and fully self-identifying. Data critical to platform operation is located in partitions and not in unpartitioned or "hidden" sectors. GPT disks use primary and backup partition tables for redundancy and CRC32 fields for improved partition data structure integrity. The GPT partition format uses version number and size fields for future expansion.
Each GPT partition has a unique identification GUID and a partition content type, so no coordination is necessary to prevent partition identifier collision. Each GPT partition has a 36-character Unicode name, which means that any software can present a human-readable name for the partition without any additional understanding of the partition.
Where can I find the specification for GPT disk partitioning? Chapter 16 of the Extensible Firmware Interface (EFI) specification defines the GPT format. This document is available at http://www.Intel.com/technology/efi/
Is EFI required for a GPT disk? No. GPT disks are self-identifying. All the information needed to interpret the partitioning scheme of a GPT disk is completely contained in structures in specified locations on the physical media.
How big can a GPT disk be? In theory, a GPT disk can be up to 2^64 logical blocks in length. Logical blocks are commonly 512 bytes in size.
The maximum partition (and disk) size is a function of the operating system version. Windows XP and the original release of Windows Server 2003 have a limit of 2TB per physical disk, including all partitions. For Windows Server 2003 SP1 Windows XP x64 edition, and later versions, the maximum raw partition of 18 exabytes can be supported. (Windows file systems currently are limited to 256 terabytes each.)
How many partitions can a GPT disk have? The specification allows an almost unlimited number of partitions, but the Windows implementation restricts this to 128 partitions. The number of partitions is limited by the amount of space reserved for partition entries in the GPT.
Can a disk be both GPT and MBR? No. However, all GPT disks contain a Protective MBR.
What is a Protective MBR? The Protective MBR, beginning in sector 0, precedes the GPT partition table on the disk. The MBR contains one type 0xEE partition that spans the disk.
Why does the GPT have a Protective MBR? The Protective MBR protects GPT disks from previously released MBR disk tools such as Microsoft MS-DOS FDISK or Microsoft Windows NT Disk Administrator. These tools are not aware of GPT and do not know how to properly access a GPT disk. Legacy software that does not know about GPT interprets only the Protected MBR when it accesses a GPT disk. These tools will view a GPT disk as having a single encompassing (possibly unrecognized) partition by interpreting the Protected MBR, rather than mistaking the disk for one that is unpartitioned.
Why would a GPT-partitioned disk appear to have an MBR on it? If this occurred, you must have used an MBR-only-aware disk tool to access the GPT disk. See answers #8 through #10, earlier.
If the disk is larger than the maximum size an MBR can report, will the entire disk contents be protected? The EE partition in the Protective MBR is specified to be the maximum size allowable in an MBR.