I have read the archives and cannot find a simular problem. I want to create an auto-install CD that uses all available space on the disk. I want to create these partitions: swap - 2GB / - 6GB /boot - 2GB /home - max(The rest of the drive) ... its a 36GB SCSI. After the install i do a "df -h" to get these values for my partition. rootfs - 2.0G - / tmpfs - 2.0G - / /dev/loop0 - 155M - /mounts/instsys /dev/hdc - 340M - /var/adm/YaST/InstSrcManager/....... /dev/sda2 - 773M - /mnt /dev/sda3 - 259M - /mnt/boot /dev/sda4 - 3.1G - /mnt/home I noticed, however, that if before I boot from the CD, I run fdisk /dev/sda, and clear the partition table, THEN boot from the CD I get the partition sizes I want. In AutoYast I selected to initialize the drive, and to "Reuse all existing partitions". It is a requirement that I have no user interaction setting up these machines with SuSe, and I dont want to have to clear out the partition table before I boot with the install CD every time. Here is my partitioning section. Anyone see what I'm doing wrong? Is there a way to run fdisk and clear it out automatically before Yast probes the hard drives? I know the pre-install scripts run after the probe and the rules suggestion in previous postings do not work either. Thanks in advance. <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <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> <partition_type>primary</partition_type> <size>2GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</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> <partition_type>primary</partition_type> <size>6GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</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> <partition_type>primary</partition_type> <size>2GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning>
On Tuesday 09 August 2005 22:42, Sean Siemsen wrote:
I have read the archives and cannot find a simular problem.
which SUSE version do you use?
I want to create an auto-install CD that uses all available space on the disk. I want to create these partitions: swap - 2GB / - 6GB /boot - 2GB /home - max(The rest of the drive) ... its a 36GB SCSI.
that's fine so far. I don't see a problem here.
After the install i do a "df -h" to get these values for my partition.
"after the install"? What does that mean in your terms? For me it's after the first boot but obviously for you it's somewhen during the installation process?
rootfs - 2.0G - / tmpfs - 2.0G - / /dev/loop0 - 155M - /mounts/instsys /dev/hdc - 340M - /var/adm/YaST/InstSrcManager/....... /dev/sda2 - 773M - /mnt /dev/sda3 - 259M - /mnt/boot /dev/sda4 - 3.1G - /mnt/home
I noticed, however, that if before I boot from the CD, I run fdisk /dev/sda, and clear the partition table, THEN boot from the CD I get the partition sizes I want.
and if you don't do that, what sizes do you get then? the "df -h" does not tell us how big the partitions are.
Here is my partitioning section. Anyone see what I'm doing wrong?
I tried your profile on the 9.3 and it worked fine here (well, actually I had to change the sda to hda but I don't expect this to be a problem).
Is there a way to run fdisk and clear it out automatically before Yast probes the hard drives?
I did that once and I had to patch autoyast for that. You don't want that. What you want should be solvable without patching autoyast. I don't see anything special here. Maybe something is weird with the hardware? A special SCSI controller or something like that?
<partitioning config:type="list"> <drive>
...
</drive> </partitioning>
your profile works fine here on a 9.3 -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
participants (2)
-
Sean Siemsen
-
Uwe Gansert