Partition does not end on cylinder boundry

English Install/Boot/Login
1

Hi,

I get this error after BSD install

linux-ufas:/home/david # fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0007d4a8

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        5222    41945683+   7  HPFS/NTFS
/dev/sda2            9139       33691   197221972+   7  HPFS/NTFS
/dev/sda3            5223        9138    31454829   a5  FreeBSD
Partition 3 does not end on cylinder boundary.
/dev/sda4   *       33692       38913    41945715    5  Extended
/dev/sda5           36042       36563     4192965   82  Linux swap / Solaris
/dev/sda6           36564       38913    18876343+   7  HPFS/NTFS
/dev/sda7           33692       34631     7550487   83  Linux
/dev/sda8           34632       36041    11325793+  83  Linux

And

linux-ufas:/home/david # sfdisk -uS -l /dev/sda

Disk /dev/sda: 38913 cylinders, 255 heads, 63 sectors/track
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
/dev/sda1            63  83891429   83891367   7  HPFS/NTFS
/dev/sda2     146801970 541245914  394443945   7  HPFS/NTFS
/dev/sda3      83891430 146801087   62909658  a5  FreeBSD
                start: (c,h,s) expected (1023,254,63) found (281,10,1)
                end: (c,h,s) expected (1023,254,63) found (227,15,63)
/dev/sda4   * 541245915 625137344   83891430   5  Extended
/dev/sda5     578998665 587384594    8385930  82  Linux swap / Solaris
/dev/sda6     587384658 625137344   37752687   7  HPFS/NTFS
/dev/sda7     541246041 556347014   15100974  83  Linux
/dev/sda8     556347078 578998664   22651587  83  Linux
/dev/sda9             0   4194303    4194304
/dev/sda10      4194304  12584959    8390656
/dev/sda11     12584960  20973567    8388608
/dev/sda12     20973568  62900223   41926656

How to resolve this without reinstall, I have spent 3 days building BSD desktop and wont like to spoil it. When I use parted or gparted they show error information at BSD partition, it may be due to inability to read ufs or zfs.

2

Is this causing a problem? There is a small gap between 3 and 2. Ideally there should be no gaps, but operationally this should not generally hurt anything.

3

Mate, There is 1 mb gap and 2nd partition is empty atm, I can resize it. I get this error when I do fdisk from linux only. From bsd if i check the layout I dont get any errors.

4

This is a warning not an error. Does it actually effect any thing running? 1MB is pretty small on todays drives. As long as partitions don’t overlap then I don’t see any error.

5

There are no issues while accessing drives. Wish to keep it clean, that is all. can i just extend ntfs by 1 mb and make it error free.

6

No. You can only extend to the end of a partition you can not add on to the front. Also since you are not seeing this in BSD this may be a reporting error due to the file systems in on one or the other OS. To really clean this up you would need to do a total repartition. Or at least be willing to do that when you break something resizing and moving partitions.

7

I dont want to break anything now, have spent long hours on customizing desktop for bsd and wish to keep it that way for at least 6 months from hereon.

Thanks for your help.

8

On 07/17/2010 11:46 AM, avenuemax wrote:
>
> I dont want to break anything now, have spent long hours on customizing
> desktop for bsd and wish to keep it that way for at least 6 months from
> hereon.

Ignore the warning. I have had such a warning on my system since 2008 without it
causing any problems. As stated earlier, BSD does not check for this condition,
thus no warning.

9

But be warned to use Win7, because there will be some “error” corrections trashing your system when partition management is touched…

And question: Linux sfdisk can see inside BSD volume management?

10

I am not worried about windows at all. Other than games and translators I dont use it. Windows7 didnt return any error so far.

11

It IS an error, but not a serious one. It comes from the Windows OS’s when they do partitional set-ups. Windows approximates boundaries where Unicess’s actually compute the exact sizes. openSUSE checks the geometry looking for precise sizing and start end blocks, and warns of descripencies so that you know that attempts to move partitions or do resizing of partitions in the future may fail with regards to ones that don’t start and end on boundaries. BSD ignors boundary errors and if you try to resize or move partitions you will just get a failure error with out explaination as to why. openSUSE om the other hand will complain about the error and refuse to do the operation but at least you will know why it failed. Windows will not complain about the error and will attempt resizing ops even if it results in damage to other OS’s partitions.
The only good way to avoid the error is to use Linux to establish all partitions even for the windose system, then do the due dilligence of installing windose then linux.

12

I have partitioned the drive with gparted cd. I dont use windows for this stuff. Linux partition tools lack ability to read ufs or zfs. fdisk is unix program and i find it difficult to believe that it wont show same error in bsd.

what should i do to rectify this error.

13

fdisk is unix program and i find it difficult to believe that it wont show same error in bsd.

What is the output when ran from BSD ?

14

I’ve never encountered gparted creating an aproximated start end situation but … that being said, I don’t use anything but ext2 ext3 ext4 and years ago even journalfs. The only time this situation was found was when I used Windows to do partitioning. If you get this using a BSD system and used gparted to establish the fs’s you have chosen, then I know of no way to resolve it. fdisk will report the error when using an extx variant so maybe fdisk can’t handle the fs you are using when under BSD? Just a guess:O

15

@ techwiz, seems that way.