How Do I preserve lvm1?
I'm trying to install SuSE 9.2 using autoyast. I have a a cluster of SuSE 8.1 systems that were installed with a different installer. They each have one filesystem in an lvm1 logical volume that I really want to preserve. If push comes to shove, I can restore the data, but it would make my upgrade very time consuming. No matter what tags I set in the control file, my pv's,vg's,and lv's are erased and then re-created. Is there a way to prevent this? Brian
Hi Brian, I am having the same issue. I have tried with yast and under installation mode selected "update an existing system" and it works fine - that is, the disk partitions from SuSE 8.1 are preserved and the network static ip and fstab settings are preserved. However, I can't figure out how to do it with autoyast. In the DTD definition file /usr/share/autoinstall/dtd/general.dtd I do not see any options for updating an existing installation. Can someone please confirm if autoyast supports update installation from SuSE 8.1 to 9.2. Many thanks, Bis. Brian Childs wrote:
I'm trying to install SuSE 9.2 using autoyast.
I have a a cluster of SuSE 8.1 systems that were installed with a different installer. They each have one filesystem in an lvm1 logical volume that I really want to preserve.
If push comes to shove, I can restore the data, but it would make my upgrade very time consuming.
No matter what tags I set in the control file, my pv's,vg's,and lv's are erased and then re-created. Is there a way to prevent this?
Brian
I am also having a very similiar issue. I have an older system using LVM1 and I am trying to upgrade it to LVM2 in SLES9 with no luck. The procedure I am using it not through yast or any other common means but I am pretty much moving a working system on top of an older system. The system boots with the new 2.6.10 (from 2.4.20) with a new initrd. LVM comes up, detects all my partitions, then an error stating that there is no EXT3 filesystems on the partitions appears. Shortly after that the kernel panics because my root filesystem is on LVM. I've been trying numerous ideas with no luck. -Nick ~=-,_,-=~=-,_,-=~=-,_,-=~=-,_,-=~=-, Linux, no additives or preservatives ~=-,_,-=~=-,_,-=~=-,_,-=~=-,_,-=~=-, On Mon, 31 Jan 2005, Brian Childs wrote:
I'm trying to install SuSE 9.2 using autoyast.
I have a a cluster of SuSE 8.1 systems that were installed with a different installer. They each have one filesystem in an lvm1 logical volume that I really want to preserve.
If push comes to shove, I can restore the data, but it would make my upgrade very time consuming.
No matter what tags I set in the control file, my pv's,vg's,and lv's are erased and then re-created. Is there a way to prevent this?
Brian
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
I think I've got it. here's what I've found: <use>none</use> seems to prevent the deletion of partitions using 'parted rm', and it also stops pvcreate! <format>false</format> prevents mkfs/mkswap <create>false</create> Seems to prevent the creation of partitions using 'parted mkpart', and the creation of vg's & lv's. This seems to imply <format>false</format>. If I've got that wrong, somebody please let me know, but the following works for me... <partitioning config:type="list"> <drive> <device>/dev/sda</device> <use>none</use> <partitions config:type="list"> <partition> <format config:type="boolean">true</format> <create config:type="boolean">false</create> <mount>/boot</mount> (snip) </partition> (snip) <partition> <create config:type="boolean">false</create> <lvm_group>data_volume</lvm_group> <size>max</size> </partition> </partitions> </drive> <drive> <device>/dev/data_volume</device> <use>none</use> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <lvm2 config:type="boolean">false</lvm2> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <mount>/export</mount> (snip) </partition> </partitions> </drive> </partitioning> On Tue, Feb 01, 2005 at 03:06:58PM -0500, Nicholas DeClario wrote:
I am also having a very similiar issue. I have an older system using LVM1 and I am trying to upgrade it to LVM2 in SLES9 with no luck.
The procedure I am using it not through yast or any other common means but I am pretty much moving a working system on top of an older system. The system boots with the new 2.6.10 (from 2.4.20) with a new initrd. LVM comes up, detects all my partitions, then an error stating that there is no EXT3 filesystems on the partitions appears. Shortly after that the kernel panics because my root filesystem is on LVM.
I've been trying numerous ideas with no luck.
-Nick
~=-,_,-=~=-,_,-=~=-,_,-=~=-,_,-=~=-, Linux, no additives or preservatives ~=-,_,-=~=-,_,-=~=-,_,-=~=-,_,-=~=-,
On Mon, 31 Jan 2005, Brian Childs wrote:
I'm trying to install SuSE 9.2 using autoyast.
I have a a cluster of SuSE 8.1 systems that were installed with a different installer. They each have one filesystem in an lvm1 logical volume that I really want to preserve.
If push comes to shove, I can restore the data, but it would make my upgrade very time consuming.
No matter what tags I set in the control file, my pv's,vg's,and lv's are erased and then re-created. Is there a way to prevent this?
Brian
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
participants (3)
-
Bis Kanungo -
Brian Childs -
Nicholas DeClario