A very basic partitioning problem
Hello, I habe a suse10.1 system and I am trying to do an autoinstall on it. This works if there are no linux partitions on it but it fails when I do the auto install the second time, so there are already linux partitions (boot, swap, /) in place. In the autoyast file I said: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <use>linux</use> <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> <size>64M</size> </partition> ... </partitions> </drive> </partitioning> As far as I understood the documentation <use>linux</use> should delete all linux specific partitions or reuse them. What I get is during "Create parrtition plans" an error box simply saying "Error while configuring partitions. Try again". However this does not tell me what autoyast thinks is wrong. I looked in /var/adm/autoinstall/logs/ but this directory is still empty. Does anyone know how to get more information what went wrong or why autoyast fails to drop the existing linux partitions and create new ones? Thanks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke@uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------
On Thursday 13 April 2006 14:48, Rainer Krienke wrote:
I habe a suse10.1 system and I am trying to do an autoinstall on it. This works if there are no linux partitions on it but it fails when I do the auto install the second time, so there are already linux partitions (boot, swap, /) in place.
actually that should work. What is the exact partitioning on the harddisk? Paste the complete partitioning section from your profile too please.
As far as I understood the documentation <use>linux</use> should delete all linux specific partitions or reuse them.
true
/var/adm/autoinstall/logs/ but this directory is still empty.
it's in /var/log/YaST2/y2log -- 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
Am Donnerstag, 13. April 2006 15:24 schrieb Uwe Gansert:
On Thursday 13 April 2006 14:48, Rainer Krienke wrote:
I habe a suse10.1 system and I am trying to do an autoinstall on it. This works if there are no linux partitions on it but it fails when I do the auto install the second time, so there are already linux partitions (boot, swap, /) in place.
actually that should work. What is the exact partitioning on the harddisk? Paste the complete partitioning section from your profile too please.
The partitioning is: Disk /dev/hda: 255 heads, 63 sectors, 4866 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 1 1912 15358108+ 7 HPFS/NTFS /dev/hda2 * 1913 1921 72292+ 83 Linux /dev/hda3 1922 4866 23655712+ f Win95 Ext'd (LBA) /dev/hda5 1922 2052 1052226 82 Linux swap /dev/hda6 2053 3358 10490413+ 83 Linux The partitioning section of the autoyast file is: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <use>linux</use> <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>64M</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>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>10G</size> </partition> </partitions> </drive> </partitioning> Thanks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke@uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------
On Thursday 13 April 2006 15:51, Rainer Krienke wrote:
The partitioning is: ... The partitioning section of the autoyast file is:
both looks good. I don't see anything wrong. I tried your profile on a disk with a very similar partitioning and it works fine here. Do you really have a Windows Filesystem on hda1? <use>linux</use> checks the filesystem but anyway, you should not get such an error message. -- 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
Am Donnerstag, 13. April 2006 16:27 schrieb Uwe Gansert:
On Thursday 13 April 2006 15:51, Rainer Krienke wrote:
The partitioning is:
...
The partitioning section of the autoyast file is:
both looks good. I don't see anything wrong. I tried your profile on a disk with a very similar partitioning and it works fine here. Do you really have a Windows Filesystem on hda1? <use>linux</use> checks the filesystem but anyway, you should not get such an error message.
The filesystem on hda1 is "ntfs" so clearly not linux. Running a rescue system I can even mount it (as ntfs) and show the contents. I also tried to add <is_evms_vg config:type="boolean">false</is_evms_vg> to the drive section but this did not change anything. I will try to download suse10.1 rc1 perhaps things are different there. Thanks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke@uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------
Am Donnerstag, 13. April 2006 16:27 schrieb Uwe Gansert:
On Thursday 13 April 2006 15:51, Rainer Krienke wrote:
The partitioning is:
...
The partitioning section of the autoyast file is:
both looks good. I don't see anything wrong. I tried your profile on a disk with a very similar partitioning and it works fine here. Do you really have a Windows Filesystem on hda1? <use>linux</use> checks the filesystem but anyway, you should not get such an error message.
In between I tried the very same with SuSE 10.1 RC1. The effect remaines. Reuse of existing linux partitions fails using autoyast. Any idea Thanks Rainer --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke@uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------
On Thu, Apr 13, 2006 at 03:51:59PM +0200, Rainer Krienke wrote:
<partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <use>linux</use>
Try adding: <is_evms_vg config:type="boolean">false</is_evms_vg> under the <drive> directive. Even though the docs say the default it false, I noticed (sles10 beta9 testing vs sles10.1) that the partition map errors in y2log had mentions of evms in them. When I added the above tags, and made no other changes.. it worked. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com _Charlie_: "That was beautiful! I got chills! What side of whose bed did you wake up on?" From _The Mask_
participants (3)
-
Mike Marion -
Rainer Krienke -
Uwe Gansert