Answer the question
In order to leave comments, you need to log in
How does fdisk deal with extended partitions?
A partition table is created via fdisk: 3 primary partitions, one extended, and there are several logical partitions in it.
Let the extended partition start with block 2016. When creating the first logical partition, fdisk asks which block to make initial, and the minimum possible number is 2016 (which I specify). But when checking the resulting table, it turns out that this section begins with block 2079. Accordingly, all other logical disks are also shifted by 63 blocks relative to the number I specified.
Actually the question is: why and why is this happening? What will happen if I can still force logical disks to stand one after another without this "gap" of 63 blocks? And why are empty 63 blocks always allocated at the beginning of the disk, and what will happen if the very first partition starts from the very first block?
PSfdisk is the one used on linux, specifically slackware 14.1.
Answer the question
In order to leave comments, you need to log in
In the days of DOS, it was customary to align partitions along the border of a cylinder: there are 63 sectors in one cylinder. Today, alignment is applied along the border of 1 Megabyte - 2048 sectors of 512 bytes. More details: habrahabr.ru/company/paragon/blog/97436
If you try to create a partition starting from the very first sector, then, most likely, such a partition will not be available to operating systems, since the very first sector must have an MBR with a partition table (or protective MBR in the case of GPT), without this table, the location of partitions on the disk is unclear to the operating system.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question