LinuxQuestions.org - How to fix 'partition not end on cylinder boundary'?

- Ubuntu (https://www.linuxquestions.org/questions/ubuntu-63/)

- - How to fix 'partition not end on cylinder boundary'? (https://www.linuxquestions.org/questions/ubuntu-63/how-to-fix-partition-not-end-on-cylinder-boundary-768635/)

How to fix 'partition not end on cylinder boundary'?

I found this after executed: sudo fdisk -l:

Quote:

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x95f3457a

Device Boot Start End Blocks Id System
/dev/sda1 1 1146 9198592 27 Unknown
Partition 1 does not end on cylinder boundary.
/dev/sda2 * 1146 6368 41943760 7 HPFS/NTFS
Partition 2 does not end on cylinder boundary.
/dev/sda3 6368 14593 66067313 5 Extended
Partition 3 does not end on cylinder boundary.
/dev/sda5 6369 11858 44098425 7 HPFS/NTFS
/dev/sda6 11859 14332 19872373+ 83 Linux
/dev/sda7 14333 14593 2096451 82 Linux swap / Solaris

I want to fix this problem, but I don't know How to do this and do not affect existing OS boot.

Thanks for any advice!

Not a problem - ignore it.

Quote:

Originally Posted by syg00 (Post 3754120)

Not a problem - ignore it.

Thank you for your reply. I know it does not affect my computer's working, but if I want to fix it then HOW?

Call me a "sqare" but I decided to avoid this message at all costs when partitioning my USB drive. Therefore I calculated a bit and give fdisk cylinder numbers instead of Mbytes, but it stil gives me this warning.
How is that possible? Is fdisk buggy?

Some crazy thing is happening with fdisk, or I should learn a bit more about it. I can create the same sized partition, with 3 different result.

I have a 16 Gb USB stick, with these parameters:

Code:

Disk /dev/sdb: 16 GB, 16047521280 bytes

255 heads, 63 sectors/track, 1951 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

I deleted all partition and then created one, from cylinder:0 to cyl:382 (about the size of 3 Gb).

First try:
Then created a new partition from cyl:383 to cyl:512.

This has resulted the warning message:

Code:

  Device Boot      Start        End      Blocks  Id  System 

/dev/sdb1              1        382    3068383  83  Linux

/dev/sdb2            383        513    1044225  83  Linux

Warning: Partition 2 does not end on cylinder boundary.

Notice that I started the 2nd partition at the first's end+1. The important factor is that I manually entered the parameter to 'fdisk'.

Second try:
Deleted the 2nd partition.
Then created a new one from fdisk's default offer (it was cyl:382) to cyl:512. The difference here that I didn't enter any data, simply pressed Enter on the empty field (at the starting cylinder)

Result? Everything is fine:

Code:

  Device Boot      Start        End      Blocks  Id  System 

/dev/sdb1              1        382    3068383  83  Linux

/dev/sdb2            383        512    1036192  83  Linux

...it is strange that fdisk suggested '382' what I accepted, but the 2nd partition still starts from cyl:383 which caused Warning, when entered manually.

Third try (the most interesting):
Deleted the 2nd partition.
Then created a new one. Fdisk suggested cyl:382, but I didn't hit Enter this time, but manually entered "382". The result is:

Code:

Command (m for help): n

Partition

type

  e  extended

  p  primary partition (1-4)

p

First cylinder  (default 382cyl):382

Last cylinder or +size or +sizeMB or +sizeKB  (default 1950cyl): 511

Warning: You requested a partition from 382cyl to 511cyl.

The closest location we can manage is 382cyl to 510cyl.  Is this still acceptable to you?

  y Yes                                                                

  n No

The concept of "cylinders" is meaningless on modern LBA disks - even more so on flash.
Merely maintained for compatability. IMO you're chasing smoke.

Quote:

Originally Posted by syg00 (Post 3811110)

The concept of "cylinders" is meaningless on modern LBA disks - even more so on flash.
Merely maintained for compatability. IMO you're chasing smoke.

Thanks.

:D "chasing smoke".

I'd resized my disk partitions from the #1 to the last in ascending order with GParted and keep the integrity of partitions at the same time. Now, the problem had been resolved.

Quote:

Originally Posted by syg00 (Post 3754120)

Not a problem - ignore it.

This was the best answer in this thread.....

Quote:

Originally Posted by pixellany (Post 3811558)

This was the best answer in this thread.....

There are no the best answer, OK?!