openSUSE Autoinstall June 2006

autoinstall@lists.opensuse.org

43 participants
52 discussions

Autoinstall 3ware-Supplied 3w-9xxx Module?
by Don Coffin 09 Jun '06

09 Jun '06

Howdy, all. I'm brand new to SuSE (specifically using SLES9 + SP3). I'm trying to create an autoinstall script for some custom SLES9+SP3 installation CDs. The problem I'm having is that the 3ware-supplied module is on a floppy disk and not in a packaged form. As I'm just learning how YAST2 and SuSE installation servers and such work, I haven't yet been able to figure out how to roll in the vendor-supplied driver to the "installation tree". Can anyone tell me how this is done? It looks like the module comes with a pre-install script, and I can't figure out where in the "installation tree" i need to place the script, either. Is it possible to create custom installation CDs that have 3rd party modules on them? I'm trying to put this together for a client who is very keen to keep using SLES9, otherwise I'd have them upgrade. Any help is greatly appreciated. Thanks!

2 1

encrypted partitions with 10.1 autoyast?
by Karsten Künne 08 Jun '06

08 Jun '06

Hi, I tried to use a profile from 9.3 in order to create an encrypted partition in 10.1 but it gave me a cryptic error (error code -3013, whatever that means) during installation and I ended up with an invalid partition table. Following is the piece from my profile: <partition> <crypt_fs config:type="boolean">true</crypt_fs> <crypt>twofish</crypt> <crypt_key>CRYPTOPASS</crypt_key> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">true</loop_fs> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> Do I have to do something different in 10.1? The online documentation doesn't mention encrypted partitions at all. Karsten.

2 2

sax2 --auto & keyboard set
by Stephen Mah 08 Jun '06

08 Jun '06

Hello, I'm new to autoyast. I've created a control file to automate sles9 sp3. Works great, except my keyboard character set is not coming up right. I'm not using autoyast to configure X11, but instead, running sax2 --auto in my post install script so it will auto detect my x11 config. All my keyboard keys are different, for example I type "/" and get "-" I've defined my keyboard as US. Any help would be appreciated. -regards steve

2 1

SELS 10 Network Installation Directory Layout?
by Pete Nishimoto 07 Jun '06

07 Jun '06

Hi, I'm trying to setup a PXE server to autoinstall SELS 10 and I'm running into a problem because I'm not sure how to layout the installation directories for the network install. I've setup the installation directories and links to sucessfully network install SELS 9 and I figured it would be pretty much the same. However, I've run into a problem. I've created a SELS 10 (Beta 9) installation directory much like a SLES 9 installation directory, with a sles10 directory (containing CD 1) and a core10 direcotry (containining the contents of CD 2-4 in the directories CD1-CD3). I'm able to install the first CD once I get a number of extra links (which wasn't in SELS 9), such as content.asc, content.key. I've found that I also need a link ./suse->sels10/CD1/suse to get the first CD to install. However, when the installation reboots (after installing CD1), and it start to go through the other packages, etc., it first looks for the media.2 file. Ok, so I put a link for media.2 to core10/CD1/media.2. But then it turns out that the installation procedure is trying to find the first package that I want to install (aalib) and it traverses the ./suse link to look for it. Since ./suse->sles10/CD1/suse, the aalib rpm is not there (it's in ./core10/CD1/suse). Of course, if I restart at this point and have ./suse->core01/CD1/suse, it can't find 'setup' and then the installation fails. So, I still need to know what's the right directory tree layout for SELS10. Is there any script/documentation/pointer to anything that can help me here? I'm stuck because of the problem with the ./suse link, and the installer wanting different contents for different times. I was thinking, does it have to do with the ./yast/instorder or ./yast/order files (are these still used?). Please help. I'm really close and just need a nudge in the right direction. I'll continue to search the mail lists, but a shortcut would be greatly appreciated. Pete

3 3

problems with ask
by Simon Crute 07 Jun '06

07 Jun '06

Hi, I'm trying to use the new Ask feature of autoyast, and prompt the user if they want their disk initialising. This is how the ask lines are looking in the /tmpautoinst.xml after the profiles have been merged etc. <ask-list config:type="list"> <listentry> <default>false</default> <path>partitioning,drive,initialize</path> <question>Do you want to remove all existing partitions ?</question> <stage>initial</stage> <title>Fdisk</title> <type>boolean</type> </listentry> </ask-list> However, I'm not seeing any popups during the install This is on SLED10-rc2 -- Simon Crute IS&T Bracknell Novell UK Ltd

2 6

adding net install source OSS-10.1
by Darin Perusich 07 Jun '06

07 Jun '06

hello all, has something changed when adding installation sources from 10.0 to 10.1 for network installation because it's not working as i expect it to? my directory structure layout is: /pub/suse/i386/SL-10.1 |-- inst-source |-- non-oss-inst-source |-- yast `-- instorder `-- order host:/pub/suse/i386/SL-10.1/inst-source/yast # cat instorder /non-oss-inst-source / host:/pub/suse/i386/SL-10.1/inst-source/yast # cat order /non-oss-inst-source /non-oss-inst-source / my setup for OSS-10.0 is nearly identical but it has 2 addition install sources, inst-source-extra and inst-source-java as appose to non-oss-inst-source. i've read thru Additional_YaST_Package_Repositories and Network_Installation_Source but nothing about this is mentioned so i'm a bit confused as to why this is not working. thanks -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 darinper(a)cognigencorp.com

2 5

Network installation of different service packs
by Jeremy Silver 05 Jun '06

05 Jun '06

I have an installation server for installation of SLES9 via http. Using the YaST Installation Server module I have added service packs 1-3 as they became available. They way the installation tree is setup the latest service pack gets installed with the an install source of http://x.x.x.x/autoyast/sles9/. However, for some systems I need to be able to install SP2 instead of SP3; I tried to specify the installation source as http://x.x.x.x/autoyast/sles9/SUSE-SLES-9-Service-Pack-Version-2/CD1/ as the installation source is listed for installing post-installation packages through YaST, but it does not work (drops me to the text install menu). Is there a way to do this just by specifying an alternate installation source? For reference, my pxe boot parameters are: label test kernel vmlinuz-SLES9-2 append initrd=initrd-SLES9-2.img ramdisk_size=65536 splash=silent showopts vga=788 install=http://x.x.x.x/autoyast/sles9 autoyast=http://x.x.x.x/autoyast/profile/test.xml loghost=x.x.x.x My sles9 tree is: -- Jeremy Silver jeremy(a)broadware.com This message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

How to save the list of installed packages?
by Pietro Mele 05 Jun '06

05 Jun '06

I installed SUSE 10.1 on a notebook (which does not have a floppy disk drive). Now I would like to save my system configuration and the list of packages I selected during the installation on a USB key (just in case I have to reinstall everything for any reason). During the installation process, I could find no indication about the possibility to make a backup of the list of packages I just selected. Can I do it now, once the system is up and running? How? Thank you, Pietro pietromele2(a)yahoo.com --------------------------------- Feel free to call! Free PC-to-PC calls. Low rates on PC-to-Phone. Get Yahoo! Messenger with Voice

3 2

Raid with hot spare using autoyast?
by Anton Altaparmakov 05 Jun '06

05 Jun '06

Hi, Using autoyast and trying to create a software raid device with a hot spare disk during installation. I have looked through the documentation, the list archives and through the partitioning.dtd and raid.dtd and am none the wiser, so am turning towards the list in the hope that someone can tell me if this is possible or not and if it is possible how to do it... Thanks a lot in advance! Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/

1 0

Re: [suse-autoinstall] autoyast does not remove old logical volumes
by Dejan Muhamedagic 02 Jun '06

02 Jun '06

On Fri, Jun 02, 2006 at 12:09:40PM +0100, Timothy Wright wrote: > If I understand the problem correctly, you may just need.... > > <drive> > ... > ... > <use>all</all> > </drive> It was there. What I did in the meantime is to put a pre-script which removes all LVs and the VG. The script did its thing, the installation failed again, because the partition table was not re-read, but after reboot autoinstallation worked fine. On subsequent autoinstalls, I have been getting the following messages: Jun 2 14:10:05 sapcl03 yast2[3750]: <1> [agent-storage] LvmAccess.cc(ExecuteLvmCmd):1621 lvm cmd execute:/sbin/vgchange -a y Jun 2 14:10:06 sapcl03 yast2[3750]: <1> [agent-storage] LvmAccess.cc(ExecuteLvmCmd):1650 lvm cmd output: /dev/sda1: open failed: No such device or address After pressing "Ignore" the installation, however, proceeded without problems. BTW, /dev/sda1 contains root fs and has nothing to do with LVM. Now, even though I removed that pre-script from the XML config, the installation always stops at this point with the "sda1: open failed" report. Sigh. Cheers, Dejan > > Cheers, > > Tim > > > Tim Wright > > Global Unix Engineering > Information Enterprise Services (IES) > Group Technology & Operations > > Deutsche Bank [/] - London > > Phone: +44 (0)20 754 70513 > Mobile: +44 (0)7765 894 194 > Email: timothy.wright(a)db.com > > > > Dejan Muhamedagic <dejanmm(a)fastmail.fm> > 02/06/2006 10:07 > Please respond to > Dejan Muhamedagic <dejanmm(a)fastmail.fm> > > > To > suse-autoinstall(a)suse.com > cc > > Subject > [suse-autoinstall] autoyast does not remove old logical volumes > > > > > > > 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 > [attachment "disk.xml" deleted by Timothy Wright/DMGIT/DMG UK/DeuBa] -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > --- > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorized copying, disclosure or distribution of the material in this > e-mail is strictly forbidden.

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall June 2006