August 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

[Fwd: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283)]
by Stephan A. Rickauer 04 Sep '04

04 Sep '04

Hard to believe, but it works! Thanks Jan. However, it would be really helpful to know, why it has to be i586 and not "noarch". Furthermore, I'd like to specify my own subdirs, like "uni" or something similar ... isn't that possible? Stephan A. Rickauer ---------------------------- Institut für Neuroinformatik IT-Koordinator Universität / ETH Zürich Winterthurerstr. 190 CH-8057 Zürich Tel: +41 1 635 30 50 Sek: +41 1 635 30 52 Fax: +41 1 635 30 53 http://www.ini.unizh.ch ------------------------ Jan-Marc Pilawa wrote: > Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und > genau das getan, was in der Mail beschrieben stand. > > Mit freundlichen Gruessen / Sincerely > > Jan Pilawa > -------- Original Message -------- Subject: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283) Date: Thu, 8 Jul 2004 14:22:12 +0200 From: Jan-Marc Pilawa <j.pilawa(a)tu-bs.de> Organization: Rechenzentrum To: Stephan A. Rickauer References: <40ED38D7.7020101(a)ini.phys.ethz.ch> Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und genau das getan, was in der Mail beschrieben stand. Mit freundlichen Gruessen / Sincerely Jan Pilawa -- + Kontakt ----------------------------------------------------+ + Systembetreuung Rechenzentrum TU Braunschweig + + Hans-Sommer-Str. 65, D-38092 Braunschweig + + Tel: +49 531 391-5548 E-Mail: j.pilawa(a)tu-bs.de ____________+

3 6

X11 configuration, SLES8
by Oliver Schwabedissen 03 Sep '04

03 Sep '04

Hello, I have a problem with configuring X11 when installing SLES8. I want to configure X11, but don't want KDE to start when the server comes up. So I configured runlevel 3 and X11 like this: [...] <runlevels> <default>3</default> </runlevels> <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <monitor> <display> <max_hsync config:type="integer">60</max_hsync> <max_vsync config:type="integer">60</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">30</min_vsync> </display> <monitor_device>1024X768@60HZ</monitor_device> <monitor_vendor>LCD</monitor_vendor> </monitor> <resolution>1024x768</resolution> <start_x11 config:type="boolean">false</start_x11> </x11> </configure> However, when autoinstall finishes the system boots to runlevel 5, which is now also the default runlevel in /etc/inittab. Why does autoyast ignore my configured runlevel? Doesn't <start_x11 config:type="boolean">false</start_x11> mean that X11 should not be started automatically? I'm starting installation by booting from SP3 CD1 with an info file on floppy. It then connects to the installation server through NFS. Oliver -- Superg�nstige DSL-Tarife + WLAN-Router f�r 0,- EUR* Jetzt zu GMX wechseln und sparen http://www.gmx.net/de/go/dsl

1 1

SLES9 bootloader for PPC iSeries
by Carl Pecinovsky 31 Aug '04

31 Aug '04

Hi. I'd just like to post notice of a difference between SLES8 and SLES9 autoyast that needs to be configured for iSeries PPC (power4) logical partitions. For installing SLES8, I can get away with a simple bootloader section: <bootloader> <activate config:type="boolean">false</activate> <location>/dev/hda1</location> </bootloader> The booting is actually controlled by an i5/OS instance running that is hosting the disk. But without any hardware change, if I try to install SLES9, the above doesn't work. I get a message within i5/OS stating: "--0007: IPL source not valid." I used YaST to output a CHRP bootloader section which works fine after a little tweaking, but it is quite long: <bootloader> <activate config:type="boolean">true</activate> <board_type>chrp</board_type> <default>linux</default> <global config:type="list"> <global_entry> <key>timeout</key> <value config:type="integer">100</value> </global_entry> <global_entry> <key>boot</key> <value>/dev/iseries/vda1</value> </global_entry> <global_entry> <key>activate</key> <value config:type="boolean">true</value> </global_entry> <global_entry> <key>default</key> <value>linux</value> </global_entry> </global> <initrd_modules config:type="list"> <initrd_module> <module>ipr</module> </initrd_module> <initrd_module> <module>iseries_veth</module> </initrd_module> </initrd_modules> <loader_device>/dev/iseries/vda1</loader_device> <loader_type>ppc</loader_type> <location>boot</location> <of_defaultdevice config:type="boolean">false</of_defaultdevice> <prep_boot_partition>/dev/iseries/vda1</prep_boot_partition> <sections config:type="list"> <section config:type="list"> <section_entry> <key>image</key> <value>/boot/vmlinux</value> </section_entry> <section_entry> <key>label</key> <value>linux</value> </section_entry> <section_entry> <key>root</key> <value>/dev/iseries/vda3</value> </section_entry> <section_entry> <key>initrd</key> <value>/boot/initrd</value> </section_entry> <section_entry> <key>append</key> <value>selinux=0 elevator=cfq</value> </section_entry> </section> </sections> </bootloader> I wonder if this section can be cut down, or what all the options mean (like <of_defaultdevice>)? Carl Pecinovsky (507) 253-3861, TL: 553-3861, email: csky(a)us.ibm.com "It is never safe to look into the future with eyes of fear." --E.H Harriman

2 1

autoyast=defualt not working
by Schwartz, Matthew (MED) 30 Aug '04

30 Aug '04

In the isolinux.cfg file I added the following lines: #auto yast label Autoinstall kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default netsetup=0 instmode=cd I then added my autoinst.xml file to the root partition on the DVD (Suse9.1), however I get a error message saying it can't find the control file?? However if I change autoyast=default to autoyast=device://hdc/autoinst.xml it works, however the on some system the DVD-ROM is not hdc.. Matthew

1 0

Variables in control file
by Martijn Dekkers 29 Aug '04

29 Aug '04

Hi all, I would like to know how to use (system) variables in the control file - I need to use the asset tag of the systems as the system hostname, and it is not immediatly obvious from the docs and examples how to do this. I have a one-line shell script that uses hwinfo to get the asset tag, but I am not sure how to get this into the control file. I am using suse9.1 on the clients and sles9 on the server. I tried searching on google, and the archives, but no luck. Any help would be appreciated. Cheers, Martijn

1 0

Post Install script and the Location element
by leonard.jacobsen＠usbank.com 29 Aug '04

29 Aug '04

I'm having some problems getting the "location" element to work in my control file. It appears that the post-scripts section is unable to retrieve the shell script, however, if I use the URL listed in the control file and pass it to 'curl', I am able to retrieve the contents just fine. I have tried using NFS and HTTP, but they both have the same issue. The following is what is defined in my control file <scripts> <post-scripts config:type="list"> <script> <interpreter>shell</interpreter> <location>http://192.168.2.2/post-install.sh</location> </script> </post-scripts> </scripts> Here is a snippit from /var/log/YaST2/y2log 2004-08-27 12:08:37 <1> slestest(1316) [YCP] AutoinstScripts.ycp:440 Writing script into /var/adm/autoinstall/scripts/post-scripts 2004-08-27 12:08:37 <1> slestest(1316) [agent-curl] CurlAgent.cc(Execute):209 Data: 2004-08-27 12:08:37 <1> slestest(1316) [agent-curl] CurlAgent.cc(Execute):210 Output: /var/adm/autoinstall/scripts/post-scripts 2004-08-27 12:08:37 <3> slestest(1316) [agent-curl] CurlAgent.cc(Get):70 curl told us 7 2004-08-27 12:08:37 <3> slestest(1316) [YCP] autoinstall/io.ycp:69 Can't find URL: http://192.168.2.2/post-install.sh 2004-08-27 12:08:37 <3> slestest(1316) [YCP] AutoinstScripts.ycp:445 script http://192.168.2.2/post-install.sh could not be retrieved 2004-08-27 12:08:37 <1> slestest(1316) [YCP] AutoinstScripts.ycp:475 Script Execution command: /bin/sh -x /var/adm/autoinstall/scripts/post-scripts 2&> /var/adm/autoinstall/logs/post-scripts.log Does anyone have any ideas? This is driving me crazy that I cant get something this simple working :) Thanks. Len. ------------------------------------------------------------------------------ Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==============================================================================

1 0

Post & chroot scripts
by Penney, Christopher (C.) 26 Aug '04

26 Aug '04

I've looked at the documentation at http://www.suse.de/~nashif/autoinstall/ as well as a few examples and I still can't quite figure out the right way to get these scripts to work. They appear to simply not be running. For example, I have the following xml in a SuSE 9.0 build script: <configure> <scripts> <chroot-scripts config:type="list"> <script> <filename>chroot.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#!/bin/sh df > /test df > /mnt/test df | rsh 10.6.1.1 dd of=/tmp/test ]]> </source> </script> </chroot-scripts> </scripts> ... I don't think it ever runs. I don't see the file in / or /mnt nor does the rsh work. I've tried it both chroot and post. I also have a question about the chroot script. Am I right to assume that the system is all contained under /mnt when it's executed? The documentation wasn't completely clear to me. Thanks Chris

2 1

Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues.
by Anthony Staples 25 Aug '04

25 Aug '04

Anas, I will check on the email situation... sorry for the inconvenience... Humana has some sort of filtering, so who knows what it is blocking... And I will see about getting the logs from 3rd console or by redirection Cheers, Tony Anas Nashif <nashif(a)planux.c To: Anthony Staples <astaples(a)humana.com> om> cc: dvosburg(a)novell.com, lmarks(a)novell.com, Mike Robinson <mrobinson(a)humana.com>, pgriffen(a)novell.com, suse-autoinstall(a)suse.com, 08/25/2004 03:12 swilson(a)novell.com PM Subject: Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues. Anthony, For some reason, my direct emails to you do not reach you. Can you please check whats going on. Problem cant be on my side, cause everybody else seems to receive my emails. I am sending this email using a different account hoping it will reach you. I need logs from the setup which is not working. You can always get the logs during installation by switching to 3rd console. An alternative is to boot with logserver=<log server ip> and have a remote machine with syslog capture the messages from the installed client. Regards, Anas Anthony Staples wrote: > > > > Anas, > > When the install fails, /dev/hda2 is not formatted and so nothing is really > written to it. > I forgot to mention in my previous post that the SWAP is created (8GB for > some reason), but / is not. That is where the format step fails. > Is there a facility to redirect logging to the NFS repository? > > Cheers, > Tony > > > > > Anas Nashif > <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> > cc: suse-autoinstall(a)suse.com, lmarks(a)novell.com, pgriffen(a)novell.com, > 08/25/2004 12:42 swilson(a)novell.com, dvosburg(a)novell.com, Mike Robinson <mrobinson(a)humana.com> > PM Subject: Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues. > > > > > > > > Anthony, > Can you please provide the log files for a failed installation? > > Thanks, > Anas > > Anthony Staples wrote: > >> >> >>Anas, >> >>RE: Strange behavior regarding Autoinstall and some Western Digital HDDs: >> >>I am trying to develop an autoinstall for NLD 1.6 using a boot cd and an >>NFS repository. >>I have three machines that I am using for testing of autoinstall >>deployments. All are Dell GX60s with 40GB WD HDD, 512 MB RAM and Cereron >>2.2Ghz CPUs. All have been updated to the latest DELL GX60 Bios (A08). >> >>As I have posted previously, I have not been able to get any control > > files > >>built on my primary test PC to work correctly on the other two units. >>Autoinstall always fails during the format phase on these other two > > units, > >>and so the install does not complete. Here is the text of the error. >> >>"Could not format /dev/hda2. you can continue if you know what you are >>doing, but, to prevent damage to your filesystems, it is safer to cancel >>and reboot" >> >>I have tried many different approaches from explicitly setting the >>partition scheme to using the most generic scheme outlined in the >>documentation. >>Each time, the control file works as planned on my primary machine, but >>fails on the other two test units. >> >>Yesterday, Tuesday, 8/24/2004, I had Steve Wilson and Don Vosburg from >>Novell in to help me troubleshoot and possibly solve this conundrum. >>Together we went thru all the different iterations of control files I had >>tried and some that Don came up with on the spot to try and make >>partitioning work on the secondary test machines. We rec'd the same >>results I had encountered over and over. Finally, as a last effort, we >>switched the hard drive in the "good" primary unit with the hard drive in >>one of the "bad" secondary units. This switch cause the two machines to >>exchange behavior. On closer inspection of the HDD we switched out, they >>were not exactly identical. Though both are Western Digital 40GB HDD, > > the > >>model numbers differed slightly and they were manufactured in different >>countries... >> >>The "good" drive details from visual inspection and WD diagnostics: >>Completely black outer shell. >>Manufactured in Thailand >>M/N: WDC WD400BB-75FJA1 >>S/N: WD-WCAJC2052229 >>Firmware: 14.03G14 >>C H S : 77504 16 63 >>Drive 0, port 0x01F0 >>Build Date unknown >> >>The "bad" drive details from visual inspection and WD diagnostics: >>Black and silver outer shell >>Manufactured in Malaysia >>M/N: WDC WD400BB-75FRA0 >>S/N: WD-WMAJF1089739 >>Firmware: 77.07W77 >>C H S: 77504 16 63 >>Drive 0, port 0x01F0 >>Build Date: 8-JAN-04 >> >>The other failing test machine's drive was manufactured in Singapore... > > and > >>also has the black and silver outer shell. >> >>During the testing we also were able to recreate the issue using SLES 9.0 >>while performing a cdrom autoinstall to the "bad" secondary test unit. >> >>Manual installs do not seem encounter the issue. >> >>Autoinstalls seemed to ignore the partitioning info in the control files > > on > >>the secondary test machines. >> >>I have attached many of the autoinstall control files I have used during > > my > >>testing and the testing done with Steve and Don from Novell. >> >> >>(See attached file: ay_006.xml)(See attached file: > > autoyast2_gx60.xml)(See > >>attached file: autoyast3_gx60.xml)(See attached file: >>autoyast_generic_gx60.xml)(See attached file: > > autoyast_refpro_gx60.xml)(See > >>attached file: ay_003.xml)(See attached file: ay_004.xml)(See attached >>file: ay_005.xml) >> >>Anyone's insights appreciated!!! >>If other info is needed please let me know, I will be happy to provide >>whatever I can . >> >>Cheers, >>Tony >> >> >> >>The information transmitted is intended only for the person or entity to > > which it is addressed and may contain CONFIDENTIAL material. If you > receive this material/information in error, please contact the sender and > delete or destroy the material/information. > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

1 0

Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues.
by Anthony Staples 25 Aug '04

25 Aug '04

Anas, When the install fails, /dev/hda2 is not formatted and so nothing is really written to it. I forgot to mention in my previous post that the SWAP is created (8GB for some reason), but / is not. That is where the format step fails. Is there a facility to redirect logging to the NFS repository? Cheers, Tony Anas Nashif <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> cc: suse-autoinstall(a)suse.com, lmarks(a)novell.com, pgriffen(a)novell.com, 08/25/2004 12:42 swilson(a)novell.com, dvosburg(a)novell.com, Mike Robinson <mrobinson(a)humana.com> PM Subject: Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues. Anthony, Can you please provide the log files for a failed installation? Thanks, Anas Anthony Staples wrote: > > > > Anas, > > RE: Strange behavior regarding Autoinstall and some Western Digital HDDs: > > I am trying to develop an autoinstall for NLD 1.6 using a boot cd and an > NFS repository. > I have three machines that I am using for testing of autoinstall > deployments. All are Dell GX60s with 40GB WD HDD, 512 MB RAM and Cereron > 2.2Ghz CPUs. All have been updated to the latest DELL GX60 Bios (A08). > > As I have posted previously, I have not been able to get any control files > built on my primary test PC to work correctly on the other two units. > Autoinstall always fails during the format phase on these other two units, > and so the install does not complete. Here is the text of the error. > > "Could not format /dev/hda2. you can continue if you know what you are > doing, but, to prevent damage to your filesystems, it is safer to cancel > and reboot" > > I have tried many different approaches from explicitly setting the > partition scheme to using the most generic scheme outlined in the > documentation. > Each time, the control file works as planned on my primary machine, but > fails on the other two test units. > > Yesterday, Tuesday, 8/24/2004, I had Steve Wilson and Don Vosburg from > Novell in to help me troubleshoot and possibly solve this conundrum. > Together we went thru all the different iterations of control files I had > tried and some that Don came up with on the spot to try and make > partitioning work on the secondary test machines. We rec'd the same > results I had encountered over and over. Finally, as a last effort, we > switched the hard drive in the "good" primary unit with the hard drive in > one of the "bad" secondary units. This switch cause the two machines to > exchange behavior. On closer inspection of the HDD we switched out, they > were not exactly identical. Though both are Western Digital 40GB HDD, the > model numbers differed slightly and they were manufactured in different > countries... > > The "good" drive details from visual inspection and WD diagnostics: > Completely black outer shell. > Manufactured in Thailand > M/N: WDC WD400BB-75FJA1 > S/N: WD-WCAJC2052229 > Firmware: 14.03G14 > C H S : 77504 16 63 > Drive 0, port 0x01F0 > Build Date unknown > > The "bad" drive details from visual inspection and WD diagnostics: > Black and silver outer shell > Manufactured in Malaysia > M/N: WDC WD400BB-75FRA0 > S/N: WD-WMAJF1089739 > Firmware: 77.07W77 > C H S: 77504 16 63 > Drive 0, port 0x01F0 > Build Date: 8-JAN-04 > > The other failing test machine's drive was manufactured in Singapore... and > also has the black and silver outer shell. > > During the testing we also were able to recreate the issue using SLES 9.0 > while performing a cdrom autoinstall to the "bad" secondary test unit. > > Manual installs do not seem encounter the issue. > > Autoinstalls seemed to ignore the partitioning info in the control files on > the secondary test machines. > > I have attached many of the autoinstall control files I have used during my > testing and the testing done with Steve and Don from Novell. > > > (See attached file: ay_006.xml)(See attached file: autoyast2_gx60.xml)(See > attached file: autoyast3_gx60.xml)(See attached file: > autoyast_generic_gx60.xml)(See attached file: autoyast_refpro_gx60.xml)(See > attached file: ay_003.xml)(See attached file: ay_004.xml)(See attached > file: ay_005.xml) > > Anyone's insights appreciated!!! > If other info is needed please let me know, I will be happy to provide > whatever I can . > > Cheers, > Tony > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues.
by Anas Nashif 25 Aug '04

25 Aug '04

Anthony, Can you please provide the log files for a failed installation? Thanks, Anas Anthony Staples wrote: > > > > Anas, > > RE: Strange behavior regarding Autoinstall and some Western Digital HDDs: > > I am trying to develop an autoinstall for NLD 1.6 using a boot cd and an > NFS repository. > I have three machines that I am using for testing of autoinstall > deployments. All are Dell GX60s with 40GB WD HDD, 512 MB RAM and Cereron > 2.2Ghz CPUs. All have been updated to the latest DELL GX60 Bios (A08). > > As I have posted previously, I have not been able to get any control files > built on my primary test PC to work correctly on the other two units. > Autoinstall always fails during the format phase on these other two units, > and so the install does not complete. Here is the text of the error. > > "Could not format /dev/hda2. you can continue if you know what you are > doing, but, to prevent damage to your filesystems, it is safer to cancel > and reboot" > > I have tried many different approaches from explicitly setting the > partition scheme to using the most generic scheme outlined in the > documentation. > Each time, the control file works as planned on my primary machine, but > fails on the other two test units. > > Yesterday, Tuesday, 8/24/2004, I had Steve Wilson and Don Vosburg from > Novell in to help me troubleshoot and possibly solve this conundrum. > Together we went thru all the different iterations of control files I had > tried and some that Don came up with on the spot to try and make > partitioning work on the secondary test machines. We rec'd the same > results I had encountered over and over. Finally, as a last effort, we > switched the hard drive in the "good" primary unit with the hard drive in > one of the "bad" secondary units. This switch cause the two machines to > exchange behavior. On closer inspection of the HDD we switched out, they > were not exactly identical. Though both are Western Digital 40GB HDD, the > model numbers differed slightly and they were manufactured in different > countries... > > The "good" drive details from visual inspection and WD diagnostics: > Completely black outer shell. > Manufactured in Thailand > M/N: WDC WD400BB-75FJA1 > S/N: WD-WCAJC2052229 > Firmware: 14.03G14 > C H S : 77504 16 63 > Drive 0, port 0x01F0 > Build Date unknown > > The "bad" drive details from visual inspection and WD diagnostics: > Black and silver outer shell > Manufactured in Malaysia > M/N: WDC WD400BB-75FRA0 > S/N: WD-WMAJF1089739 > Firmware: 77.07W77 > C H S: 77504 16 63 > Drive 0, port 0x01F0 > Build Date: 8-JAN-04 > > The other failing test machine's drive was manufactured in Singapore... and > also has the black and silver outer shell. > > During the testing we also were able to recreate the issue using SLES 9.0 > while performing a cdrom autoinstall to the "bad" secondary test unit. > > Manual installs do not seem encounter the issue. > > Autoinstalls seemed to ignore the partitioning info in the control files on > the secondary test machines. > > I have attached many of the autoinstall control files I have used during my > testing and the testing done with Steve and Don from Novell. > > > (See attached file: ay_006.xml)(See attached file: autoyast2_gx60.xml)(See > attached file: autoyast3_gx60.xml)(See attached file: > autoyast_generic_gx60.xml)(See attached file: autoyast_refpro_gx60.xml)(See > attached file: ay_003.xml)(See attached file: ay_004.xml)(See attached > file: ay_005.xml) > > Anyone's insights appreciated!!! > If other info is needed please let me know, I will be happy to provide > whatever I can . > > Cheers, > Tony > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1