I did search maemo.org and googled, read a lot of posts but i am still confused and worried.
So i ask and thank for the advised opinions of this community.

Some days ago i repartitioned my N900 EMMC using gparted running in my linux desktop pc with my N900 in USB storage rd mode.

I follow the solution #6 in wiki.maemo.org/Repartitioning_the_flash and everything went fine. Gparted did move and resize the partitions and all my data was preserved.

After reboot all my installed applications and also multiboot / nitroid and powerkernel oc are working as before without any problem.

What i don't like are the warnings that sfdisk reports:

As i understand sfdisk detects that the disk geometry reported by the kernel (977024 cylinders, 4 heads, 16 sectors/track) is different from that in the partition table (30532 cylinders, 64 heads, 32 sectors/track)
Is this a problem? Can my file system be corrupted in the future because of this?

The "start: (c,h,s) expected (0,2,1) found (1,0,1)" warning in sfdisk is (as i found in some articles) caused by the partitions not ending on a cylinder boundary. This could be avoided if i have checked the "round to cylinders" option in gparted.
It seams however that this is harmless and there is no risk for the file system integrity.

Using "fdisk" i get no warnings at all:

If fdisk reports no problems at all may i assume that the differences in sfdisk reported disk geometry don't matter?
Where does the kernel keep the disk geometry parameters?

Thanks for your comments

Bump (excuse me)

Anyone please.
Help is much appreciated.

Thanks

IMO there's nothing to worry about. Mine shows the same thing for my SD card. Like you said everything works fine. Linux can handle it.

Why don't you go back and "round to cylinders" ?

Thanks for your answer and suggestion.

I thought about doing it and maybe later i will do it. However i read several posts in the net about that issue (linux in general not only maemo) and all of them agree that linux can handle that without any problem. Old dos systems however could have problems with partitions not ending at cylinder boundaries. That justifies the sfdisk's warning.

The 1st warning, about the difference between disk geometry reported by the kernel and the partition table, is what i really don't like as i couldn't find any reference about how the kernel handles that and how it can be fixed.

stlPaul

Thanks for your answer.
Are you sure linux can handle it ?
Until now, I have to admit that you are wright but, If there is a reference in the kernel about the geometry of the disk there must be a reason for it.
Note that sfdisk doesn't report an error but a warning and for me a warning means "you may proceed but take care"

The kernel should be getting the geometry straight from the drive controller - maybe this link might shed a little more light on it.

Pretty much you don't need to worry about drive geometry anymore on modern operating systems (and hardware)

dchky

Many thanks for that link

That article is difficult to digest (at least for me) as there is so many information about how the firmware bios and os deal with disks since the old dos systems.

However, if i understood well, modern linux and windows systems don't use CHS (cylinder,head, sector) adressing anymore. They rely on LBA (linear block addressing) that is handled by the bios and the disk drivers.

So, if i am wright, the reported sfdisk warnings may be safely ignored.

Maybe sfdisk should be updated to check if the OS is a modern one and omit the "warning" word from the report.