June 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

autoinstall fails with SuSE 9.1
by David Corlette 19 Jun '04

19 Jun '04

Hello all, I'm having trouble getting autoinstall to work with SuSE 9.1. I'm not sure if I'm doing something wrong or if something's broken. Here are the basics: - I've downloaded a complete copy of the 9.1 distribution, put it on an NFS server (10.0.0.57) and exported it as /home/suse. - I've created a customized control file using YaST2-autoinstall (with manual customization) and placed it in /home/suse on the NFS server. - I've cut a CD using "boot.iso" from the distribution, with no customization; I'm just planning to manually enter the correct autoyast command-line. - I boot off the CD, interrupt the timer, and then put "autoyast=nfs://10.0.0.57/home/suse/arpmin.xml" in the command-line options line. - The system starts to attempt the autoinstall, then fails saying it can't contact the install server. Log attached below, please note comments following: Log from installer: ---trim--- Looking for network server.. Ok, that didn't work; see if we can activate another network device... insmod /modules/mii.ko insmod /modules/e100.ko Ok, that seems to have worked. :-) Looking for a network server again... Trying to activate eth0 Setting up localhost...done Sending DHCP request to eth0... no/incomplete answer. Ok, that didn't work;see if we can activate another network device... No further network carcds found giving up. hostname: 10.0.0.200 netmaks: 255.255.255.0 broadcast: 10.0.0.255 gateway: 10.0.0.1 server: 10.0.0.10 nameserver: 10.0.0.8 Looking for a network server... Trying to activate eth0 Setting up locathost...done **** dhcpcd: already running **** dhcpcd: if not then delete /var/run/dhcpd-eth0.pid file Sending DHCP request to eth0... no/incomplete answer. Ok that didn't work; see if we can activate another network device... No further network cards found; giving up.. Automatic setup not possible. ---end--- Does anyone else find it odd that the script appears to give up on DHCP just before the machine apparently gets a full set of parameters from DHCP? Perhaps the timeout is ridiculously low? In any case, if anyone has any idea how to fix this, I would really appreciate it. Thanks! Dave C --------------------------------------------------------- David Corlette mailto:corlette@huarp.harvard.edu (617)495-5922 http://www.arp.harvard.edu

2 1

Re: Error while configuring software selections on SLES 8 SP3 ia64
by Anas Nashif 18 Jun '04

18 Jun '04

Bruno Cornec wrote: > Hello, > > After reading tons of documents and passing more than 2 days on that problem, > I think I need some help ;-) > The target is to deploy 50+ rx2600 HP ia64 servers, and I'd prefer not doing > that by hand ;-) > > Any hint, pointer would be greatly appreciated. > Bruno. > > Problem description: > =================== > > Autoyast doesn't validate our package selection stating > that the "default" selection is incorrect. This means something is wrong with your installation source setup. > > Details: > ======== > > When autoyast tries to analyse the autoyast.xml file that he gets > from the deployment servers, it aborts at the "configure software" > step issuing the following message: > > Error > Error while configuring software selections > Please try again ! > [OK] > > The autoyast.xml generated by the SUSE tool doesn't work from scratch. > > I've attached all the relevant files I found on both the server > and the client in order to help for the debug. If you'd like to > have other missing files, please ask ! > > My setup follows what is described here: > 1. http://www.suse.de/~nashif/autoinstall/faq.html > 2. http://www.suse.de/~nashif/autoinstall/sles8/html/x910.html > 3. http://www.suse.de/~nashif/autoinstall/multiplesource.html > > Especially I put the driverupdqte file in my root dir > I also used the sp3 kernel and initrd in my elilo configuration. > > The problem I see is around the order and instorder files: > > order: > > /sp3/CD1 /sp3/CD1 > /sles/CD1 /sles/CD1 > /ul/CD1 /ul/CD1 > > instorder: > > /ul/CD1 /ul/CD1 > /sles/CD1 /sles/CD1 > /sp3/CD1 /sp3/CD1 > once column is the right thing, I still have to update it in all docs, but this should not be the cause of the problem. Something is not right with the directories although your description below looks OK. > [Don't know why n the same doc it has once 2 columns and another time only one] > > and that part of autoyast.xml > > <software> > <addons config:type="list"/> > <base>default</base> > <packages config:type="list"> > [...] > </packages> > </software> > this is Ok. > > The documentation in 3. isn't for me sufficiently detailed and I > do not understand really what these 2 files do. > > I suspect that autoyast doesn't find the correct default.sel at > the right place, even if the log shows that it's loaded: > > [Note: we created files packages.en_US from packages.en in all directories as > it was missing, and changing language to en alone raised other issues] The logs show a bug that is known with SLES8 GA which was fixed with SP3. The driverupdate is featched correctly though. Can you verify that a directory named /y2update/modules does exist on the client during installation? Anas

2 1

autoinstall problem on ibm e325 and broadcom 5704
by nicolas.raspail＠bnpparibas.com 18 Jun '04

18 Jun '04

Hi, autoyast doesn't work on my ibm e325. I reach the autodection hardware, it loads tg3 or bcm5700 driver (depends on my test) but dhcp requests don't reach my dhcp server or if static IP are used, il can't activate the first time the networkd card so it tries a second time, it succeeds, but it tries to mount 0.0.0.0:/install/suse ! It seems it has forgotten the nfs server IP between the two activation. Morever, when I used the following setting DEFAULT linux64 LABEL linux64 KERNEL linux64 APPEND initrd=initrd64 insmod=tg3 hostip=10.252.82.231 netmask=255.255.255.0 gateway=10.252.82.1 nameserver=10.252.0.228 server=10.252.82.254 install=nfs://10.252.82.254/install/mirrors/suse/64/ autoyast=nfs://10.252.82.230/var/lib/autoinstall/repository/cg99-005.xml textmode=1 PROMPT 1 TIMEOUT 50 and switch to alt+F3 console, I see the following strange line server: 10.252.82.254 (no ip) <-- what does this no ip means ? linux64 and initrd34 are copied from the DVD and renamed to suit my needs. I do the same with the 32 bits version and it's works fine. Can anyone has auto installed the Suse 9.1 Pro (amd64) on an IBM e325 ? I've no problem install it on an IBM x335 (bi xeon) with a broadcom 5703, so I think the problem is on the network card. I'll receive soon a Sunfire v20z for some test, anyone have some information about suse 9.1 pro amd64 and this computer ? Best regards Nicolas This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

2 1

rules
by Werner Hack 18 Jun '04

18 Jun '04

Hi, I try to install a server machine with autoyast booting from a selfmade CD. A copy of the SuSE distribution is located on a local disk. There are several disks attached to this system. To determine the right harddisk where I intend to install the OS I want to use 'rules.xml'. These are my boot parameters for autoyast : > autoyast=device://sdb1/install/autoyast/profiles/ > serverdir=device://sdb1/install/autoyast/SuSE partition=sdb1 If no profile is specified, autoyast should go for the rules file. But when the system comes up autoyast stops : 'No profile for this machine could be found or retrieved' ... and autoyast shows the given profile location in its installation window for choosing an new one. This is my rules file located in .../profiles/rules : > <rules config:type="list"> > <rule> > <disksize> > <match>/dev/sda 100000</match> > <match_type>greater</match_type> > </disksize> > <result> > <profile>server.xml</profile> > <continue config:type="boolean">false</continue> > </result> > </rule> > </rules> While booting all disks are detected (and modules are loaded) the right way. Any idea what went wrong ? Thanks in advance Regards Werner Hack BTW: What's the right syntax for the MAC attribute in rules.xml ? <mac> <match>123456ABCDEF</match> <match_type>exact</match_type> </mac> Is this correct ? Has the module for the network device to be loaded to detect the MAC address ?

2 1

How to keep a pre-install script partition scheme?
by Mike Rose 17 Jun '04

17 Jun '04

Hi, Our requirement for partitioning is not covered by autoyast (IMHO) so I've had to use a pre-install script that uses sfdisk to create what we want - create / as a primary partition, an extended partition with swap and the rest of the disk as another partition (later to be mounted as /scratch for obvious reasons), but not all of the HDDs we have can take a / partition of 10GB so sometimes we need not to create a 3rd partition and to reduce the size of /. I've added the script that does this to end of this email. Unfortunately this does not work. I am assuming I have messed up my partition XML - can you help? I am now going to try using the "Auto-detection of partitions to be kept" method while I wait for a reply. partitions before install (using exec /bin/bash -x so that I get an interactive prompt to be able to check that the pre-install script has worked): Disk /dev/hda: 9729 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hda1 0+ 1305 1306- 10490413+ 83 Linux /dev/hda2 1306 9728 8423 67657747+ 5 Extended /dev/hda3 0 - 0 0 0 Empty /dev/hda4 0 - 0 0 0 Empty /dev/hda5 1306+ 1434 129- 1036161 82 Linux swap /dev/hda6 1435+ 9728 8294- 66621523+ 83 Linux partitions after install: Disk /dev/hda: 9729 cylinders, 255 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hda1 0+ 1305 1306- 10490413+ 5 Extended /dev/hda2 1306 9728 8423 67657747+ 5 Extended /dev/hda3 0 - 0 0 0 Empty /dev/hda4 0 - 0 0 0 Empty /dev/hda5 1306+ 1434 129- 1036161 82 Linux swap /dev/hda6 1435+ 9728 8294- 66621523+ 83 Linux which is a bit of a mess so no wonder the installatin cannot succeed. >From reading: http://www.suse.de/~nashif/autoinstall/9.1/html/CreateProfile.Partitioning.… I thought I had understood the XML I needed to use to be: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_nr config:type="integer">1</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_nr config:type="integer">5</partition_nr> </partition> </partitions> </drive> </partitioning> The XML pre_install script: <source><![CDATA[ #!/bin/sh wget http://XXXX/~install/suse9.1/pre_install_suse91.sh wget http://XXXX/~install/suse9.1/sfdisk chmod +x sfdisk chmod +x pre_install_suse91.sh ./pre_install_suse91.sh # exec /bin/bash -x ]]></source> pre_install_suse91.sh: #!/bin/sh -x # setup detault route to install server route add -net XXXXX netmask 255.255.255.0 dev eth0 # Now partition the disk SFDISK=./sfdisk mknod /tmp/hda b 3 0 CREATETEMP=false $SFDISK --no-reread -V /tmp/hda if $SFDISK --no-reread -V -q /tmp/hda; then DOPARTITION=false else DOPARTITION=true DISKSIZE=$((`$SFDISK --no-reread -s /tmp/hda` / 1024 )) # assume 1k blocks echo $DISKSIZE MEMSIZE=`cat /proc/meminfo | grep "MemTotal:" | cut -d":" -f2 | cut -d"k" -f1` echo $MEMSIZE if [ $(($MEMSIZE / 1024 )) -gt 128 ]; then SWAPSIZE=$(($MEMSIZE / 1024)) else SWAPSIZE=128 fi ROOTSIZE=$(($DISKSIZE - $SWAPSIZE)) # disk - swap if [ $ROOTSIZE -gt 10240 ]; then # 10GB in MB CREATETEMP=true ROOTSIZE=10240 TEMPSIZE=$(($DISKSIZE - $ROOTSIZE)) fi # if we always put swap in an extended partition, we can # guarantee: # # / is /dev/hda1 # swap is /dev/hda5 # /scratch is /dev/hda6 # and all is well and happy throughout the land ... echo $ROOTSIZE $SWAPSIZE $CREATETEMP fi if $DOPARTITION; then echo "past DOPARTITION" if $CREATETEMP; then # we're lurching into a different partitioning echo "createtemp" $SFDISK --no-reread -D -uM /tmp/hda <<EOF ,$ROOTSIZE ,,E , , ,$SWAPSIZE,S ,,L EOF else # we must have no /temp. echo "notemp" $SFDISK --no-reread -D -uM /tmp/hda <<EOF ,$ROOTSIZE ,,E , , ,,S EOF fi fi cheers, Mike Rose

2 2

RE: [suse-autoinstall] UK language and timezone settings ignored
by Wallace, Andrew 17 Jun '04

17 Jun '04

> Hi, > > I'm using autoyast-installation on SuSE 8.2 (I know it's old > but I don't > have a choice). > > I used the YaST GUI tool to create the inital configuration, and the > resulting xml file > looks OK. It works, it builds the boxes OK, runs my > post-install script OK > etc etc > > However, the time is set to 5 hours forward and the encoding > is ANSI-1968, > when it > should be ISO-8859-1. > <snip> Never mind, it's my fault. I'm using a custom package selection file and forgot to include glibc-locale, so there was no ISO-8859-1.so on the system. Oops.

1 0

UK language and timezone settings ignored
by Wallace, Andrew 17 Jun '04

17 Jun '04

Hi, I'm using autoyast-installation on SuSE 8.2 (I know it's old but I don't have a choice). I used the YaST GUI tool to create the inital configuration, and the resulting xml file looks OK. It works, it builds the boxes OK, runs my post-install script OK etc etc However, the time is set to 5 hours forward and the encoding is ANSI-1968, when it should be ISO-8859-1. It looks to me like the default US locale has been used instead. Here's the relevant bit of autoinst.xml <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/London</timezone> </clock> <keyboard> <keymap>english-uk</keymap> </keyboard> <language>en_GB</language> ... I can see nowhere else to specify which character encoding is used. A normal manual install sets it correctly to ISO-8859-1 Help! Have I missed something? Regards, Andrew Wallace Linux Administrator/Developer Siemens Business Services Coventry Tel: 02476 838433 Mob: 07766 560211

1 0

Réf. : Re: [suse-autoinstall] autoyast2, Suse 9.1 Pro and resolv.conf
by nicolas.raspail＠bnpparibas.com 17 Jun '04

17 Jun '04

Hi, thanks for the tip, I've a good resolv.conf. Now I must understand te meaning of these lines :) Best regards Nicolas PS : sorry for the quote, but I use Lotus notes at work ;( Extranet ulrich.bernhard(a)id.unizh.ch - 17/06/2004 09:06 Pour : suse-autoinstall cc : Objet : Re: [suse-autoinstall] autoyast2, Suse 9.1 Pro and resolv.conf Hi, I have had the same problem with more or less the networking definitions. At the end I have added the following sysconfig lines and now I have a /etc/resolv.conf file: <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>MODIFY_RESOLV_CONF_DYNAMICALLY</sysconfig_key> <sysconfig_path>/etc/sysconfig/network/config</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> </sysconfig> Best regards Ulrich nicolas.raspail(a)bnpparibas.com wrote: <snip> -- +-----------------------------------------------------------+ | Ulrich Bernhard | | Informatikdienste Tel: (+41-44) 635 67 73 | | Universitaet Zuerich Fax: (+41-44) 635 45 05 | | Winterthurerstr. 190 | | CH-8057 Zuerich Email: ulrich.bernhard(a)id.unizh.ch | | Switzerland | +-----------------------------------------------------------+ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

1 0

autoyast2, Suse 9.1 Pro and resolv.conf
by nicolas.raspail＠bnpparibas.com 17 Jun '04

17 Jun '04

Hi, I've just discovered Suse and autoyast2 (we are switching from Redhat and Systemimager for deployment) and I've have one problem. With yast2, I create a xml file for autoyast and everything works fine except for /etc/resolv.conf. The computer has the right IP address, the right gateway but no /etc/resolv.conf. I use static IP and here is an extract of my configuration file : <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>equities.net.intra</domain> <hostname>cg99-005</hostname> <nameservers config:type="list"> <nameserver>10.252.0.228</nameserver> <nameserver>10.252.0.248</nameserver> </nameservers> <searchlist config:type="list"> <search>equities.net.intra</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>10.252.82.255</broadcast> <device>eth0</device> <ipaddr>10.252.82.231</ipaddr> <netmask>255.255.255.0</netmask> <network>10.252.82.0</network> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>bcm5700</module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>10.252.82.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> I've read some mails on this list and see it seems I can remove the <module_entry> (moreover, the tg3 driver is used instead on my IBM x335) but I've not tested that at te moment. Does anyone have an idea about the non-creation of the /etc/resolv.conf ? Where I can search logs for more information ? I'm using dhcp+pxe+nfs to boot the system and install it Thanks Nicolas This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

2 1

Re: [suse-autoinstall] Determining file layout
by D Umesh 17 Jun '04

17 Jun '04

There is a file called ls-lR.gz file in each CD which contains list of all files, I think while installing this file would get uncompressed, yast seaches in this file and prompts for correct CD. Regards Umesh >>> "Dustin Nielson" <DUNIELSON(a)novell.com> 06/14 8:17 PM >>> In a multi CD install, how does YaST know on which CD a given RPM resides on in order to prompt for the correct CD?

2 1