RE: [suse-autoinstall] Funny partitioning behaviour
I think you need to use the partition_nr property in the definition of your partitions, Ryan. If you tell autoyast that /boot is 1, swap is 2, and / is 3, I think you will not run into the problem of YaST attempting to add new partitions to the disk: . . . <partitions config:type="list"> <partition> <mount>/boot</mount> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> * --> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>1gb</size> . . . -- Charlie -----Original Message----- From: Ryan Allen [mailto:r.allen@f5.com] Sent: Tuesday, February 01, 2005 8:44 PM To: suse-autoinstall@suse.com Subject: [suse-autoinstall] Funny partitioning behaviour Hi, I'm doing automated (no user intervention) installs of suse 9.2 using autoyast. I would like autoyast to wipe clean the partition table, create new partitions regardless of what's there, and format them. For some reason, it's creating the first partition on /dev/hda6, and going up from there. The install fails because it thinks there is not enough HD space. I'd like it to start from /dev/hda1: /dev/hda1 30 Megs /boot /dev/hda2 1 Gig /var /dev/hda3 512 Megs swap /dev/hda4 remainder of HD / Here is my config. What am I doing wrong? Thanks, Ryan P.S. also, why did autoyast put in the <crypt> tags and can I take them out? Thanks again! <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <size>30M</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>512M</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <size>1G</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning>
On Tue, Feb 01, 2005 at 09:01:18PM -0500, Suffin, Charles wrote:
I think you need to use the partition_nr property in the definition of your partitions, Ryan. If you tell autoyast that /boot is 1, swap is 2, and / is 3, I think you will not run into the problem of YaST attempting to add new partitions to the disk:
Also, if you want autoyast to delete a partition, then you need a 'use' tag, see below...
. . .
<drive> <device>/dev/hda</device> *--> <use>all</use>
<partitions config:type="list"> <partition> <mount>/boot</mount> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> * --> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>1gb</size> . . .
-- Charlie
-----Original Message----- From: Ryan Allen [mailto:r.allen@f5.com] Sent: Tuesday, February 01, 2005 8:44 PM To: suse-autoinstall@suse.com Subject: [suse-autoinstall] Funny partitioning behaviour
Hi,
I'm doing automated (no user intervention) installs of suse 9.2 using autoyast. I would like autoyast to wipe clean the partition table, create new partitions regardless of what's there, and format them. For some reason, it's creating the first partition on /dev/hda6, and going up from there. The install fails because it thinks there is not enough HD space.
I'd like it to start from /dev/hda1:
/dev/hda1 30 Megs /boot
/dev/hda2 1 Gig /var
/dev/hda3 512 Megs swap
/dev/hda4 remainder of HD /
Here is my config. What am I doing wrong?
Thanks,
Ryan
P.S. also, why did autoyast put in the <crypt> tags and can I take them out? Thanks again!
<partitioning config:type="list">
<drive>
<device>/dev/hda</device>
<initialize config:type="boolean">false</initialize>
<partitions config:type="list">
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/boot</mount>
<partition_id config:type="integer">131</partition_id>
<size>30M</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>swap</mount>
<partition_id config:type="integer">130</partition_id>
<size>512M</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/var</mount>
<partition_id config:type="integer">131</partition_id>
<size>1G</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/</mount>
<partition_id config:type="integer">131</partition_id>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
participants (2)
-
Brian Childs
-
Suffin, Charles