Partition order with new autoinst-rpm
Hi, I tried the new autoinst rpms for an install. But it generates the partitions in the wrong order and creates an extended partition, even if there are only four partitions to be created. The order for the partitions (which are /, /boot, swap and lvm) should be /boot first, after that / or swap and the last should be lvm (probably inside an extended partition). Is there any way to force this order? bye Felix ________________________________________ Zeitschriftenabos online bestellen - jetzt neu im Infoboten! http://www.epost.de
* felix.schumacher@epost.de
Hi,
I tried the new autoinst rpms for an install. But it generates the partitions in the wrong order and creates an extended partition, even if there are only four partitions to be created.
The order for the partitions (which are /, /boot, swap and lvm) should be /boot first, after that / or swap and the last should be lvm (probably inside an extended partition).
Is there any way to force this order?
I have just tried a similar configuration like the one you have
described and it works fine for me and everything is in the right order,
except that all partitions are created as logical, which is the right
thing and the default behaviour and was a result of a bug fix ( see bugs
page: http://www.suse.de/~nashif/autoinstall/).
Please verify in the profile that the partitions are listed in the
correct order..
To force the creation of a primary partition, add
On Wed, 12 Jun 2002 felix.schumacher@epost.de wrote:
I tried the new autoinst rpms for an install. But it generates the partitions in the wrong order and creates an extended partition, even if there are only four partitions to be created.
I did not observe a wrong partition order, but for my setup yast did not succeed in creating a file system on my logical volume (same configuration as posted yesterday, but with previously missing <lv> </lv>-tags). The mke2fs command stalled at 0% formatting for about 20 minutes (and ps/top did not show any process time spent on mke2fs). No error messages and no warnings occured during this time. I killed the process and formatting of the other partitions went okay. Any hints? Volkmar -- Volkmar Glauche Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg WWW http://glauche.home.pages.de/ Martinistr. 52 Phone 49(0)40-42803-5781 20246 Hamburg Fax 49(0)40-42803-9955
On Wed, 12 Jun 2002, Volkmar Glauche wrote:
I did not observe a wrong partition order, but for my setup yast did not succeed in creating a file system on my logical volume (same configuration as posted yesterday, but with previously missing <lv> </lv>-tags). The mke2fs command stalled at 0% formatting for about 20 minutes (and ps/top did not show any process time spent on mke2fs). No error messages and no warnings occured during this time. I killed the process and formatting of the other partitions went okay.
It seems, that yast2 does create the VolumeGroup, but does not attempt to
create the Logical volume in it.
The lvm section now looks like this:
<lvm config:type="list">
On Wed, 12 Jun 2002, Volkmar Glauche wrote:
The lvm section now looks like this:
<lvm config:type="list">
</lvm> HomeVol <pesize>4M</pesize><lv> LHomeVol 28800mb ext3 /export/home </lv>
After all I found out, that only 1 of 2 partitions were assigned to the
volume group and - again swap space was neither initialised nor entered
into /etc/fstab. Here are the relevant sections of the config file:
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<use>all</use>
<partitions config:type="list">
<partition>
On Wed, 12 Jun 2002, Volkmar Glauche wrote:
I did not observe a wrong partition order, Ok, the wrong order was a result of my forcing lvm to be a primary partition, but / and /boot not.
but for my setup yast did not succeed in creating a file system on my logical volume (same configuration same for me. If I change to a console while running the setup I observe that there is no active vg. pvscan shows, that the partition is a pv. vgscan shows, that there are no active vg. But I can see /dev/system/group (I can remove /dev/system and recreate a vg system. After that the installation will continue)
Generally, it would be a good idea to have ALL standard decisions made by yast driven by a config file (something like template.xml). This would allow - inspection of standard decisions - change of standard behaviour without undocumented side-effects For partitioning, the option to specify a more detailed partitioning plan (ie assigning custom partition numbers) would be nice. I wish you could have classes (or templates) which you could easily combine not only in the yast2-config-tool. (which is awful to use if you have to run it in textmode)
The classes should not only be reserved for normal config, but also
for software-selections.
Btw. Why is it that attribute-type entries are saved as tag-entries
in the xml format. like
* Volkmar Glauche
On Wed, 12 Jun 2002 felix.schumacher@epost.de wrote:
I tried the new autoinst rpms for an install. But it generates the partitions in the wrong order and creates an extended partition, even if there are only four partitions to be created.
I did not observe a wrong partition order, but for my setup yast did not succeed in creating a file system on my logical volume (same configuration as posted yesterday, but with previously missing <lv> </lv>-tags). The mke2fs command stalled at 0% formatting for about 20 minutes (and ps/top did not show any process time spent on mke2fs). No error messages and no warnings occured during this time. I killed the process and formatting of the other partitions went okay.
Any hints?
I dont have a large harddisk as the one you have in your config, so I
removed a zero and create 2 PVs with 1400mb and then
<lvm config:type="list">
Volkmar
-- Volkmar Glauche
Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg WWW http://glauche.home.pages.de/ Martinistr. 52 Phone 49(0)40-42803-5781 20246 Hamburg Fax 49(0)40-42803-9955
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
--
Anas Nashif
On Wed, 12 Jun 2002, Anas Nashif wrote:
I dont have a large harddisk as the one you have in your config, so I removed a zero and create 2 PVs with 1400mb and then
<lvm config:type="list">
</lvm> HomeVol <pesize>4M</pesize><lv> LHomeVol 2920mb ext3 /home </lv>
In the last config I used (and which I think posted today) the sizes match: ie 14400M for each partition, and 28800mb for the lv_size. Still, as posted in the follow-ups (and cofirmed by Felix), yast2 does not create the lv for me. There is no error message, either (not in the log, not on the screen). Strange... Yours, Volkmar -- Volkmar Glauche Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg WWW http://glauche.home.pages.de/ Martinistr. 52 Phone 49(0)40-42803-5781 20246 Hamburg Fax 49(0)40-42803-9955
participants (3)
-
Anas Nashif -
felix.schumacher＠epost.de -
Volkmar Glauche