[opensuse-autoinstall] partitioning
I have an autoYast xml file with the following section as part of my
overall partition plan
<partition>
<create config:type="boolean">false</create>
on Friday 20 November 2009 dutchguy69 wrote:
Can someone please indicate what I'm doing wrong here since I do not see any obvious errors in the logfiles as well.
you have found a bug. If you reuse a logical volume, the configured filesystem is ignored. It only happens when you reuse an existing logical volume and not if you recreate it. So if you set "create" to true, it should work. -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hello,
I installed yesterday a machine with existing partitioning. It was 32-bit system with opensuse 11.2.
What happened was that the installation in the second stage (after boot) stopped in
filesystemcheck on /var. A closer look showed that this partitition had somehow changed.
It had size zero (ending at the same cylinder as it started).
I could fix manually with fdisk that just putting a logical partition of maximal size in extended
partition as it was formerly.
The data generated during of stage 1 of installation reappeared and I could continue.
The scheme I applied was:
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<initialize config:type="boolean">false</initialize>
<partitions config:type="list">
<partition>
<create config:type="boolean">false</create>
<filesystem config:type="symbol">ext4</filesystem>
<format config:type="boolean">true</format>
<mount>/</mount>
on Tuesday 24 November 2009 David Werner wrote:
I installed yesterday a machine with existing partitioning. It was 32-bit system with opensuse 11.2. What happened was that the installation in the second stage (after boot) stopped in filesystemcheck on /var. A closer look showed that this partitition had somehow changed. It had size zero (ending at the same cylinder as it started). I could fix manually with fdisk that just putting a logical partition of maximal size in extended partition as it was formerly. The data generated during of stage 1 of installation reappeared and I could continue. The scheme I applied was:
I was able to reproduce that. On the first sight it looks like a bug in yast2- storage to me but it needs some more debugging. I have created a bugreport: https://bugzilla.novell.com/show_bug.cgi?id=557994 Thanx. -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Tuesday 24 November 2009 Uwe Gansert wrote:
I was able to reproduce that. On the first sight it looks like a bug in yast2- storage to me but it needs some more debugging. I have created a bugreport: https://bugzilla.novell.com/show_bug.cgi?id=557994
it's a bug in autoyast. You can workaround that by providing the partition_id.
Autoyast is "guessing" it wrong.
On Tue, Nov 24, 2009 at 03:33:44PM +0100, Uwe Gansert wrote:
131 should solve it
Many thanks. I'll try that. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
David Werner -
dutchguy69 -
Uwe Gansert