Partition 1 does not end on cylinder boundary.

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
jozien17

Partition 1 does not end on cylinder boundary.

Post by jozien17 »

I just upgraded my 160GB hdd to 500GB on my ThinkPad T60
and everything was fine with my original 2 distros.
fdisk -l listed with no errors.
I installed 5 new distros including linux mint 9 KDE.
Mint works fine but now:
# fdisk -l now reads:

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 6374 51196288+ 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 6374 7167 6365520 c W95 FAT32 (LBA)
Partition 2 does not end on cylinder boundary.
/dev/sda3 7167 8670 12073320 c W95 FAT32 (LBA)
Partition 3 does not end on cylinder boundary.
/dev/sda4 8670 60802 418751369+ f W95 Ext'd (LBA)
/dev/sda5 8670 8798 1028128+ 82 Linux swap / Solaris
/dev/sda6 8798 13897 40960048+ 83 Linux
/dev/sda7 13897 18996 40960048+ 83 Linux
/dev/sda8 18996 19379 3076888+ 83 Linux
/dev/sda9 19379 23204 30723808+ 83 Linux
/dev/sda10 23204 27029 30723808+ 83 Linux
/dev/sda11 27030 27794 6144831 83 Linux
/dev/sda12 27795 28559 6144831 83 Linux
/dev/sda13 28560 29324 6144831 83 Linux

sda6, sda7, sda8, and sda9 end at cylinder and the next
partition starts at same cylinder as the previous cylinder.
The next partition should start at the next cylinder as sda10,sda11,sda12 and sda13.

How can I correct this?
Does testdisk correct this, is it safe to use?

jozien17
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
viking777

Re: Partition 1 does not end on cylinder boundary.

Post by viking777 »

That is certainly a fascinating problem.

I don't believe that partitions ending on a cylinder boundary is all that critical, but cylinder boundaries should really not begin and end at the same place, it could lead to some serious file corruption.

What created partitions 1 through 10 (where they overlap) and 11 through 13 (where they don't)? Did you pre-partition before installing or did you select automatic partitioning from the various install disks?

As for Testdisk, I have only ever used it once to recover a lost partition (and it worked, although it scared me to death using it!). I think it is largely designed for rescuing lost partitions/partition tables as in my case rather than correcting disk formatting errors.

I hope I am wrong, considering the work you must have done to install all that lot, but I have the feeling that reinstallation may be the only way to correct this.
Locked

Return to “Hardware Support”