openSUSE Autoinstall

Download

autoinstall@lists.opensuse.org

June 2006

43 participants
52 discussions

Avoid automatic partitioning in autoyast?
by Rainer Krienke 02 Jun '06

02 Jun '06

Hello, since suse10.1 (with its signed files, sigh) its quite hard to include additional RPMs in the installation process eg for doing postinstall tasks. Thats where I started trying autoyast for a basically standard installation with an additional postinstall script for each host I have. Basically this works fine. However I have one problem: The partitioning. I cloned an installed system and used this autoyast file (slightly modified) for installation. So it has sections for the partitions to be created. I also included a confirmation tag so that I have a way to change installation settings if I like before the installation begins. Since the cloned system was a IDE based one, the xml file has entries to create partions eg hda etc. Now when I start an autoyast installation on an IDE based system this works fine. But if I do the same on a SATA system the installation fails when creating the partioning plan because of the fact that there is no hda device but instead a sda. Actually I do not care about this failure since I would like to do this manually, but I cannot because of this error the complete installtion is stopped and I do not get to the point in yast where I could correct the partitioning and other installation parameters. Is there a way to tell autoyast not to take care of the partitioning because I am going to do this manually? This way I could use the same autoyast file for IDE and SATA and SCSI based systems. Else the only way I see is to use two autoyast files one for systems with hda devices and one for systems with sda devices. I tried an empy <partitioning config:type="list"></partitioning> section but this does not work either. autoyast still complains that partitioning did not work. Any other way? A second question is if there is a way to pause autoyast after the initial reboot, when in a standard yast installation the user is asked to do the printer, network, soundcard etc configuration. It would be nice (but not vital) if I could change things manually at this point too in the standard yast way. Any way to do this? Thanks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke(a)uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------

4 5

autoyast does not remove old logical volumes
by Dejan Muhamedagic 02 Jun '06

02 Jun '06

Hi, Probably an old problem, but could not find a solution to it. Autoyast complains because it found logical volumes on the disk to be configured: Jun 2 10:27:31 sapcl03 yast2[3736]: <3> [YCP] Report.ycp:391 Logical volumes of group "rootvg" exist on unconfigured devices. Delete old volume groups first or configure all devices containing physical volumes belonging to this group. Subsequently, the installation aborts: Jun 2 10:27:31 sapcl03 yast2[3736]: <3> [YCP] Report.ycp:391 Error while configuring partitions. Try again. Jun 2 10:27:31 sapcl03 yast2[3736]: <3> [YCP] clients/inst_autosetup.ycp:126 Aborting... Is there a way to tell autoyast to kill whatever LVs/VGs it finds on the target disk? This was on the SLES9/SP3. I'll attach the relevant log and config. Cheers, Dejan

1 1