autoyast tries to install into memory disk
I've finally solved my raid partitioning problem (though autoyast does try to use the separate swap devices in the swap raid for swap, sigh). However, now yast tries to install the distribution into memory disk (or at least somewhere with not enough room). It fails a couple of minutes in with a ERROR(InstTarget:E_RpmDB_subprocess_failed). I have /dev/md0 specified as /, so I have no idea why it's not installing the distribution there. <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <create config:type="boolean">false</create> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> <partition_type>primary</partition_type> </partition> <!-- /dev/md1 = swap --> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <create config:type="boolean">false</create> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> <!-- /dev/md2 = /soft3 --> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <mount>/soft3</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>none</use> </drive> Maybe it's the use directive, but I can't see the possible values documented anywhere. I suppose autoyast may not like partitions with a partition_id of 0 or something... Thanks Jeremy -- Jeremy Sanders <jss@ast.cam.ac.uk> http://www-xray.ast.cam.ac.uk/~jss/ X-Ray Group, Institute of Astronomy, University of Cambridge, UK. Public Key Server PGP Key ID: E1AAE053
Jeremy, when this happens, then yast2 could not mount the root partition. This error is not caught anywhere unfortunatly. I will try to reproduce and offer a solution. Is that SLES9 you are using? Anas Jeremy Sanders wrote:
I've finally solved my raid partitioning problem (though autoyast does try to use the separate swap devices in the swap raid for swap, sigh).
However, now yast tries to install the distribution into memory disk (or at least somewhere with not enough room). It fails a couple of minutes in with a ERROR(InstTarget:E_RpmDB_subprocess_failed). I have /dev/md0 specified as /, so I have no idea why it's not installing the distribution there.
<drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <create config:type="boolean">false</create> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> <partition_type>primary</partition_type> </partition>
<!-- /dev/md1 = swap --> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <create config:type="boolean">false</create> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition>
<!-- /dev/md2 = /soft3 --> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <mount>/soft3</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>none</use> </drive>
Maybe it's the use directive, but I can't see the possible values documented anywhere.
I suppose autoyast may not like partitions with a partition_id of 0 or something...
Thanks
Jeremy
On Fri, 4 Mar 2005, Anas Nashif wrote:
when this happens, then yast2 could not mount the root partition. This error is not caught anywhere unfortunatly. I will try to reproduce and offer a solution. Is that SLES9 you are using?
Yes - SLES9 SP1. Presumably it should be able to mount it as it was formatted. Thanks Jeremy -- Jeremy Sanders <jss@ast.cam.ac.uk> http://www-xray.ast.cam.ac.uk/~jss/ X-Ray Group, Institute of Astronomy, University of Cambridge, UK. Public Key Server PGP Key ID: E1AAE053
participants (2)
-
Anas Nashif -
Jeremy Sanders