The Master Boot Record (MBR) partitioning scheme attempts to store partition start and end points in two ways:
- Using a cylinder/head/sector (CHS) triplet, which maxes out at about 8GiB
- Using a logical block addressing (LBA) scheme, which maxes out at 2TiB
The message you note says that these two values don't match. This is most likely caused by either a bug in the original partitioning software or a different interpretation of the disk's CHS geometry (that is, how many cylinders and heads it supports) by the original partitioning software vs. fdisk.
The danger here is that two different OSes or low-level utilities will use different values (one using CHS and the other LBA), or that they'll both use CHS but interpret the CHS geometry differently. The result will be inconsistencies in the start and/or end points of the partition(s) on the disk, which in turn will lead to problems. Most likely the problems would manifest as an inability to mount the partition in one OS, but there could be more serious issues. For instance, an attempt to fix what appears to be a corrupt filesystem because of varying interpretations could end up harming it.
That said, my impression is that most modern OSes favor the LBA values; the CHS values are present mostly for historical purposes. Certainly the CHS values are useless on any disk over 8GiB in size. To completely eliminate the chance of misinterpretation, you could convert the disk to use the GUID Partition Table (GPT) instead of MBR; GPT doesn't use CHS values at all, only LBA values.
Bookmarks