I noticed that (in a case with a two disk md mirror and lvm), the CentOS 7 installer is now placing /boot as the *last* partition on the disk.
I'm assuming that others are seeing this behavior. Does anyone know why it's now the last instead of the first? (Seems to work, though.)
Devin
On 04/25/2015 01:43 PM, Devin Reade wrote:
I noticed that (in a case with a two disk md mirror and lvm), the CentOS 7 installer is now placing /boot as the *last* partition on the disk.
The position doesn't really matter. Some old bios needed the boot sector inside the LBA (first 1024 cylinders) - but the partition number doesn't equate to the sectors/cylinders you're assigning to them. So you may want to look at the actual addresses for each partition.
I'm assuming that others are seeing this behavior. Does anyone know why it's now the last instead of the first? (Seems to work, though.)
It should work. My guess is that you may have forgotten to set "force primary" on the boot partition. Again, grub doesn't care if it's a primary partition but they usually are created first if that matters to you.
Devin
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
--On Sunday, April 26, 2015 11:13:02 PM -0400 Peter Larsen peter@peterlarsen.org wrote:
On 04/25/2015 01:43 PM, Devin Reade wrote:
I noticed that (in a case with a two disk md mirror and lvm), the CentOS 7 installer is now placing /boot as the *last* partition on the disk.
The position doesn't really matter.
Correct, and I wasn't sufficiently clear. Not only did the installer put /boot on the last partition, but on the last sectors of the disk (which is really what caught my attention). And yes, both are forced to primary partitions:
# fdisk -l /dev/sda Device Boot Start End Blocks Id System /dev/sda1 2048 975749119 487873536 fd Linux raid autodetect /dev/sda2 * 975749120 976773119 512000 fd Linux raid autodetect
I wasn't so much surprised at the partition number but rather the sector offset of /boot.
Devin
-
Devin Reade -
Peter Larsen