January 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: No Kernel SLES8 SP3 autoinstallation
by Anas Nashif 16 Jan '04

16 Jan '04

Martin Möser wrote: > Hello Anas, > > I still have the problem when autoinstalling with autoyast with > custom-CD, that no kernel is installed at all. > This appears since we updated our installation server with SP3 and put > the SP3 packages into the repository. > > I told You before that we built our own script for setting up an > iso-skeleton where the necessary packages are copied to and the iso > image is generated from. This doesn't work anymore since the update was > processed. > > Now I tried to build an iso-image with the > autoyast-configuration-interface, but that has no better effect, the > kernel is still missing. What can be the reason for this? The > kernel-packages (k_deflt etc.) are on the CD. I already sent You an > excerpt of the y2log before, maybe it helps You. > The kernel to be installed is determined during installation, so if you 100% not sure about the system you are installing on, you should include all kernel packages on the CD. Besides, the kernel package should not be listed in the packages list, this might cause some conflicts as it is determined automatically. SLES8 and SP3 installation using only one, custom built CD is not easy to accomplish, you have to select the right packages from each source or you have to include the different sources (3 in this case) on the CD and use the order/instorder files for processing the CD. The autoyast2 interfaec does not support creating CD for SLES8 installation or in general terms, a CD from multiple sources. We need more information about what you are doing here, otherwise there is no way to know whats happening. Anas P.S.: Please dont email me directly, others on the list might be interested in the solution of such issues. > Best regards, > > > Martin >

3 2

Warning message in create_package_descr 8.1
by Fermín Galán Márquez 16 Jan '04

16 Jan '04

Hello, When creating a package description for a SuSE 8.1 repository using the create_package_descr script for that version (in autoyast-2.6.42), I'm getting a lot of warning messages with the following text: "only V3 signatures can be verified, skipping V4 signature" Somebody knows what if the cause of that message, how to fix it and if this situation can lead to a incorrect package database description? Thanks in advance! ------ Fermín

2 2

Autoinstall+pxe+raid1
by Mouncef_Belcaid＠blm.gov 16 Jan '04

16 Jan '04

Hi everyone! I have two 40GB drives that I want to mirror (hda and hdc). I am trying to install SuSE 9.0 Pro using autoyast. I tried using software raid (raid1) with no success. At the formatting stage of the auto installation I get the following error: "Error Could not load module raid1" I would like to put /boot and / in /dev/md0 and /dev/md1. I also created two swap partitions, one in each drive. Here is my raid config in the XML control file: ======================================================= <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>100mb</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>36gb</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>1gb</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdc</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>100mb</size> </partition> <partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>36gb</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>1gb</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> </partitioning> ========================================================= Any help will be greatly appreciated. Thanks, mb

3 2

AW: [suse-autoinstall] Autoinstall+pxe+raid1
by Mouncef_Belcaid＠blm.gov 14 Jan '04

14 Jan '04

Thanks Stefan. I did what you suggested without success. I still get the same error. Do you have any other suggestions? Thanks in advance. mb ----- Forwarded by Mouncef Belcaid/NIRM/BLM/DOI on 01/14/2004 09:34 AM ----- Voss Stefan <stefan.voss@itel To: "'Mouncef_Belcaid(a)blm.gov '" <Mouncef_Belcaid(a)blm.gov>, lium.com> "'suse-autoinstall(a)suse.com '" <suse-autoinstall(a)suse.com> cc: 01/14/2004 02:44 Subject: AW: [suse-autoinstall] Autoinstall+pxe+raid1 AM Hi, you probably have to put the raid1 module into the initrd: <install> <bootloader> <initrd_modules config:type="list"> ... <initrd_module> <module>raid1</module> <module_args/> </initrd_module> ... </initrd_modules> </bootloader> </install> Regards, Stefan Voss

1 0

invalid ram disk image error since 9.0
by Felix Guettler 14 Jan '04

14 Jan '04

Hi *, i use 3com PXE Util to load different images for installation. Thats what i do: 1) Format boot disk and "syslinux /dev/fd0" 2) Copy "bootlogo isolinux.bin linux message initrd isolinux.cfg memtest" from "/boot/loader" to diskimage using 3com PXE Util 3) Rename "isolinux.cfg" to "syslinux.cfg" 4) Generate PXE Menue and link the diskimage 5) Place diskimage and PXE Menuefile on tftp server 6) Link PXE Menuefile in dhcpd.conf This workes fine - i have done such images for SuSE 8.x, Redhat 8.x and 9.x for Debian 3.x and Fedora 1.0 - with SuSE 9.0 the Kernel panics when try to access the ramdisk, caused by the previous error: "Couldn't find valid ram disk image starting at 0". Files in image (and LDLINUX.SYS of course): 117523 Oct 20 14:53 bootlogo 5459309 Oct 20 14:53 initrd 14840 Oct 20 14:53 isolinux.bin 802 Oct 20 14:53 syslinux.cfg 1191629 Oct 20 14:53 linux 80324 Oct 20 14:53 memtest 490 Oct 20 14:53 message the initrd is original and unmodified version. load_ramdisk=1 wont change anything and got nothing to deal with the problem anyway (not 120% sure of this). I already replaced isolinux.bin with the latest version from kernel.org. I can reproduce the error on different systems. BTW, is there somebody out there using 3com PXE Util (except for RIS) ? Thanks, Felix.

1 0

Empty lines at start and end of Config-files
by Theo Gross 14 Jan '04

14 Jan '04

Hello, we are trying to use the autoinstall feature of SuSE Linux 9.0. When adding complete config files to the autoinst.xml using the editor provided by yast2 autoinstall, we discovered a Problem. (In German: Yast2: Modul: "Automatische Installation" -->"Sonstiges"-> "Komplette Konfigurationsdateien") To each file 3 or 4 empty lines are added before the first line and after the last line. These empty lines are not present in the XML-file. for example: ---begin of file--- Line1 Line2 Line3 ---end of file --- is writen on the installed System as follows: ---begin of file--- Line1 Line2 Line3 ---end of file --- This is not a Problem for most config-files, but some are diffrent. So my question ist, what to do against that? At the moment we have a workaraound for that by using a post-install-script. Theo Gross --- Theo Gross Sysadmin WsPool Informatik/ServiceGruppe University of Ulm theo.gross(a)informatik.uni-ulm.de James-Franck-Ring Work: 0731/50-24205 89081 Ulm Fax: 0731/50-24202 Germany

1 0

create_package_descr questions
by Fermín Galán 14 Jan '04

14 Jan '04

Hello, I have a pair of questions about the package database creation process (performed by create_package_descr script): 1. Can be used the same script for all SuSE versions (SuSE 8.1, SuSE 8.2 and SuSE 9.0) or each version have its own script file (in the autoyas2 package that comes with the version)? 2. Is create_package_descr a stand-alone program? (It seems that it uses the file /usr/share/autoinstall/EXTRA_PROV) Thanks in advance! ------- Fermín

4 4

example for sles8 + sp3 install server setup?
by Hal Wine 13 Jan '04

13 Jan '04

Can anyone point me to an example install server layout for autoyast installations of sles 8 + service pack 3? I followed Anas' example laytout for my original installation server setup. I'ts unclear to me if I should: 1) replace the sles8 cd content with the content from sp3 cd's, or 2) add sp3 content as another source. If #2, I think I would place it at the end of the order file, and the beginning of the instorder. Is that correct? Finally, what do folks typically do to handle maintenance updates? I.e. where do they place the RPMs. Thanks, --Hal

1 0

Integrate a 3rd party module into an autoyast configuration
by Schlabach, Torsten 13 Jan '04

13 Jan '04

Dear list, we have some machines that require a vendor supplied kernel module for their RAID controller. How could we integrate such a module into an autoyast installation? P.S.: Bear with me if this has been asked before, but I was not able to find any _searchable_ archive of this list. ----------------------------------------- Torsten Schlabach +49 228 936 34735 torsten.schlabach(a)t-mobile.de T-Mobile Deutschland GmbH -----------------------------------------

3 2

Developer team info required - yaST
by Anoop Kumar 13 Jan '04

13 Jan '04

Hi : Can somebody give a lead to find out which team works on yaST. I have to clarify some doubts on yaST. Thanks Anoop

1 0