problem while creating partitions on 2 harddisks
Hello! I found some very strange behaviour while trying to let autoyast create partitions on /dev/hda and /dev/hdb. The partitioning scheme I need is very simple: /dev/hda1 - /boot (primary, auto size, ext2) /dev/hda2 - swap (primary, auto size) /dev/hda3 - / (primary, max size, reiser) /dev/hdb1 - /home (primary, max size, reiser) Autoinstall was fine while I was using /dev/hda only. But after /dev/hdb1 was added, yast2 died while installing the RPMs - fried by the OOM-killer. I could strip down the problem to a possible bug in autoyast. The XML below contains only the partition info, it was created from scratch with autoyast from SUSE 10.0 (but SUSE 9.3 does the same). The partitioning in the first interactive install screen says only "create /dev/hdb1 with reiserfs", all info from /dev/hda ist lost. With my full autoinstall XML this screen was not shown, the installer has no real root, uses the ramdisk - and gets slayed some minutes later by the OOM-killer. Can anyone comfirm this problem, or am I misunderstanding some of the autoyast options (i.e.the "primary" or the "auto/max")? Thanks Michael ---- snip <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <partitioning config:type="list"> <drive> <device>/dev/hdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,acl,user_xattr</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/home</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext2</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>auto</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> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>acl,user_xattr</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> </profile> ---- snip __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Thursday 02 February 2006 23:19, Michael D. wrote:
I found some very strange behaviour while trying to let autoyast create partitions on /dev/hda and /dev/hdb. The partitioning scheme I need is very simple:
/dev/hda1 - /boot (primary, auto size, ext2) /dev/hda2 - swap (primary, auto size) /dev/hda3 - / (primary, max size, reiser) /dev/hdb1 - /home (primary, max size, reiser)
I'll check that. You are using a 10.0? At least I don't see any problem or known bugs with that partitioning. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
On Thursday 02 February 2006 23:19, Michael D. wrote:
Can anyone comfirm this problem, or am I misunderstanding some of the autoyast options (i.e.the "primary" or the "auto/max")?
it's a bug in 10.0 and it's fixed in 10.1 You can workaround that by removing the <initialize...> on hdb. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, 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)
-
Michael D.
-
Uwe Gansert