So I did some investigation for my own sake. Apparently this seems to be fixed in opensuse 11.3. Here is a partition layout from one of my older VMs that was created with autoyast from opensuse 11.1: ~ # fdisk -lu Disk /dev/sda: 6442 MB, 6442450944 bytes 255 heads, 63 sectors/track, 783 cylinders, total 12582912 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00020ac8 Device Boot Start End Blocks Id System /dev/sda1 * 63 8369864 4184901 83 Linux /dev/sda2 8369865 12578894 2104515 82 Linux swap / Solaris As you can see, we start a sector 63. 63 is not cleanly divisible by 8 so we are in trouble. This VM will have to be "fixed". But if you look at a partition layout on a VM created by autoyast 11.3 you'll see that you are in business, even the LVM partition is created on a good starting sector: ~ # fdisk -lu Disk /dev/sda: 16.1 GB, 16106127360 bytes 255 heads, 63 sectors/track, 1958 cylinders, total 31457280 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0008cdc7 Device Boot Start End Blocks Id System /dev/sda1 * 2048 20965375 10481664 83 Linux /dev/sda2 20965376 31457279 5245952 82 Linux swap / Solaris Disk /dev/sdb: 10.7 GB, 10737418240 bytes 255 heads, 63 sectors/track, 1305 cylinders, total 20971520 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000d0bfa Device Boot Start End Blocks Id System /dev/sdb1 2048 20971519 10484736 8e Linux LVM On Mon, Mar 28, 2011 at 3:07 PM, Ruediger Gunreben wrote:

Hi Paul,

I'm very interested in the yast config. Can you share your knowledge.

Regards Ruediger

On 12/05/2010 08:21 PM, Paul wrote:

...

On Sat, Dec 04, 2010 at 05:25:43PM +0000, Paul wrote:

...

Can anyone suggest how to ensure AutoYAST creates partitions that are aligned to 4K boundaries?  As far as I can tell, AY doesn't allow for specifying start sectors -- only by size.

If anyone's interested, I discovered that it is possible to specify the size of a partition using sectors instead of the GB size.  The properties partition_id and partition_type control such behaviour.  To specify the size in sectors, the list resource region is used.

-Paul.

--

mit freundlichem Gruss Rüdiger Gunreben

-- ruediger.gunreben@isarnet.de

Office           : 0811 99829 - 116 IsarFlow Support : 0811 99829 - 270                 : support@isarflow.de Website          : http://www.isarflow.de

-- IsarNet Software Solution Terminalstr. Mitte 18 85356 München

Tel. 07000 ISARNET oder Tel. 089 97007 401 Fax. 089 97007 200

info@isarnet.de http://www.isarnet.de -- -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org