[SOLVED] Giving cylinders in kickstart file - CentOS 6.2
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Wouldn't you be better off just specifying a partition size? You can't rely on disk geometry being the same across all platforms.
Hi TenTenths,
Thanks for reply. Yes, I am trying to configure partition to by specifying the cylinder size as in the customer's environment disk geometry (VM disks) are of same size. Also, he is somehow not happy seeing the below bold line in fdisk output. I know this does no harm but you know customer is always right
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 102400 83 Linux Partition 1 does not end on cylinder boundary.
/dev/sda2 13 3917 31353856 8e Linux LVM
Any ideas to overcome this via kickstart, I found one option to specify cylinder size by --start and --end but these options are not available for CentOS/RHEL 6.X.
Disk geometry doesn't really matter now, partitions do not need to start / end on a cylinder border.
Point 1 is even LESS important on a VM as there is no relationship between a VM disk and the physical layout.
Because of point 1 and point 2 RedHat/CentOS no longer feel the need to support specifying cylinders.
If the customer STILL has problems then the best you can do is calculate the exact size of partition needed to fill his mythical boundry and specify that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.