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