Probably, but I was getting that error by simply editing free space into a
partition.
It was only when I first set up lvm-on-raid and then edited free space into an
LVM partition that I got the traceback to follow the "cylinder boundary" error
dialog.

This is something I cannot reliable reproduce. If you have a particular
machine/hard drive combination that will do this I can take a look.
BTW the LVM and RAID stuff are a red herring as far as I can tell. Its more
related to something in parted that gets confused about partition offsets and
tells us there is a range of cylinders free and yet if you ask for that range it
reports a problem.