openSUSE Autoinstall February 2003

autoinstall@lists.opensuse.org

27 participants
42 discussions

Re: [suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :(

by Alejandro Gonzalez Madueno

Hi Anas First of all thanks for your help I changes the xml as you explain in the attached note but without success: <partitioning config:type="list" > <drive> <initialize config:type="boolean">true</initialize> <device>/dev/rd/c0d0</device> <reuse>all</reuse> </drive> </partitioning> what is wrong ? resierfs and DAC960 modules are loaded before autoyast2 taking place. Best Regards ---------------------- Forwarded by Alejandro Gonzalez Madueno/Spain/IBM on 03/08/2003 12:07 PM --------------------------- Anas Nashif <nashif(a)suse.de> on 02/06/2003 04:03:45 AM To: Alejandro Gonzalez Madueno/Spain/IBM@IBMES cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :( * Alejandro Gonzalez Madueno <agonzalez(a)es.ibm.com> [Feb 05. 2003 17:20]: > > Hi Anas > > I added the tag <initialize config:type="boolean">true</initialize> > but no changes (is produced the same error). > > This system has a DAC960 hardware raid and the module is successfully > loaded > before autoyast2 excution. > > fdisk -l /dev/rd/c0d0 see successfuly the phisical disk > > bellow is exposed the whole xml file: > > <?xml version="1.0"?> > <!DOCTYPE profile SYSTEM "/usr/lib/YaST2/profile.dtd"> > <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config=" > http://www.suse.com/1.0/configns" > > <configure> > <runlevels> > <default>3</default> > </runlevels> > </configure> > <install> > <bootloader> > <activate config:type="boolean" >false</activate> > <linear config:type="boolean" >false</linear> > <location>mbr</location> > <parameters></parameters> > </bootloader> > <general> > <hwclock>localtime</hwclock> > <keyboard>spanish</keyboard> > <language>es_ES</language> > <mouse>probe</mouse> > <timezone>Europe/Madrid</timezone> > </general> > <initialize config:type="boolean">true</initialize> ^^^^^^^^^^^^^^^^ This goes into partitioning->drive > <partitioning config:type="list" > > <drive> > <device>/dev/rd/c0d0</device> > <reuse>all</reuse> > </drive> > </partitioning> > <report> > <confirm config:type="boolean" >false</confirm> > <errors> > <log config:type="boolean" >true</log> > <show config:type="boolean" >true</show> > <timeout config:type="integer" >10</timeout> > </errors> > <messages> > <log config:type="boolean" >true</log> > <show config:type="boolean" >true</show> > <timeout config:type="integer" >10</timeout> > </messages> > <warnings> > <log config:type="boolean" >true</log> > <show config:type="boolean" >true</show> > <timeout config:type="integer" >10</timeout> > </warnings> > </report> > <software> > <addons config:type="list" /> > <base>standard</base> > </software> > </install> > </profile> > > > here attached the whole y2log: -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

18 years, 11 months

PXE loop

by Frank Pascher

Hi, I'm having a "small" problem concerning PXE installation. The installation and everything works fine But as it comes to a reboot of the machine the installation starts again. Ok that's still ok, because the pxe setup has to be changed to local boot for the client. But I don't want to do it by hand, cause for more than 200 clients it is a litle bit to much work. In the autoyast manual it is recommended to check the syslog for an initial transmitted RAM disk. The problem is that I can't find the appropriate line, even if I start the tftp-servecie with -v option. Could anyone give some advice, how to configure the tftpd and how to scan the syslog (example shell/perlscript ??)? Any help would be appreciated. cheers fp +----------------------------------------------------------+ | Max-Planck-Institut für Radioastronomie | | Abt.1 (wissenschaftliche DV) | | | | Frank Pascher | +----------------------------------------------------------+ | Auf dem Huegel 69 Tel.: +49 (228) 525 359 | | 53121 Bonn Fax.: +49 (228) 535 229 | +----------------------------------------------------------+ | Email: mailto:fpascher@mpifr-bonn.mpg.de | | WWW: http://www.mpifr-bonn.mpg.de | | PGP Fingerprint: 13D1 8C86 57B3 2850 F158 4879 E5F3 7E20 | +----------------------------------------------------------+

18 years, 11 months

[suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :(

by Alejandro Gonzalez Madueno

Sorry Anas :) I missed the y2log in the previous append 11:03:54 <1> linux(686) [YCP] clients/inst_prepdisk.ycp:523 partitioning .disk.rd.c0d0.partitio ns [$["delete":true, "fsid":5, "fstype":"Extended", "nr":1, "region":[0, 2212], "type":`extended, "ui_id": 1], $["delete":true, "fsid":131, "fstype":"Linux native", "nr":5, "region":[0, 653], "type":`logical, "ui_ id":2], $["create":true, "format":true, "fsid":131, "mount":"/boot", "nr":1, "region":[0, 3], "type":`prim ary, "used_fs":`ext2], $["create":true, "format":true, "fsid":130, "mount":"swap", "nr":2, "region":[3, 82 ], "type":`primary], $["create":true, "format":true, "fsid":131, "mount":"/", "nr":3, "region":[85, 2127], "type":`primary, "used_fs":`reiser]] 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):172 device '/rd/c0d0', cmd 'pa rtitions' 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(FdiskAccess):75 Head=255 Sector:63 Cyli nder:2212 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] SystemCmd.cc(SystemCmd):48 Konstruktor SystemCmd Us eTmp:1 Nr:0 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] SystemCmd.cc(InitFile):103 File:"/tmp/YaST2.tdir/st p686_0_S" 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):270 deleting partition 5 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):270 deleting partition 1 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):289 creating partition: type 5 , nr 1, start 1, end 3 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):643 DelLast=0 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):658 Ok=1 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):298 setting type of partition 1 to 83 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):289 creating partition: type 5 , nr 2, start 4, end 85 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):643 DelLast=0 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):658 Ok=1 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):298 setting type of partition 2 to 82 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):289 creating partition: type 5 , nr 3, start 86, end 2212 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):643 DelLast=0 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):658 Ok=1 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):298 setting type of partition 3 to 83 2003-02-05 11:04:01 <3> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(WritePartitionTable):544 Writing partit ion table failed 2003-02-05 11:04:01 <3> linux(686) [YCP] clients/inst_prepdisk.ycp:534 Oops, fdisk failed for device 2003-02-05 11:04:01 <3> linux(686) [Interpreter] clients/inst_prepdisk.ycp:540 Undefined function Storage: y2log lines 50-71/76 92% I tested the <initilize> tag set to "true" but does not work in another system that has /dev/hda is produced the same behaviour where is the fault ?

18 years, 11 months

autoinstall SLES8 [NFS repository / additional packages]

by Schmitt, Jochen

Hi, I try to create one single NFS Source for autoinstallation and Yast for installed systems. I followed 6.1.3 in the autoyast manual. I can select my NFS repository in "Change source of installation" but I am not able to search for packages. There seems to be nothing in it. e.g. rsync. The system was installed manually. Where do I put additional packages (rpms) which came not with SLES8 or update-packeges from the MW? Jochen

18 years, 11 months

RE: [suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :(

by Alejandro Gonzalez Madueno

18 years, 11 months

SLES8 / own and custom packages

by Schmitt, Jochen

Hi, so far I did not get an answer to my question before. Therefor I moved to another documentation for SLES8. As decribed in the SLES8 handbook I copied all the CDs into one directory, which is exported by NFS. Does anyone know where to put my own rpms? In i386 or i586? I did that. But the rebuild of the package database, as described in the SLES8 handbook on page 72 did not work. Regards, Jochen

18 years, 11 months

[suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :(

by Alejandro Gonzalez Madueno

-ct: re-read partition table HELP !!!!!!!!!!!!! :( G´day I have a trouble using autoyast2 from suse 8.0 professional version. First of all bellow is exposed my enviroment: ENVIROMENT ========== * suse 8.0 professional (with all patches applyed) * yast - 2.5.91 * yast2-module-autoinst-2.5.27rc3-0.noarch.rpm * 6GB IDE hard disk (exist primary linux partitions to destroy) XML === I wanna destroy the whole disk partitions. In order to do that I´m using this partition scheme: <partitioning config:type=list"> <drive> <device>/dev/hda</device> <reuse>all</reuse> </drive> </partitioning> When autoyast trates to creates the partitions in a unattended way (autoyast2), apears a message like: "The device /dev/hda has an invalid partition table. Set a valid one. This problem is reproduced also in a manual way, but i´m be able to fix the problem, using the re-read partiton table option located within the yast2 partitions expert menu. exist any unattended procedure to re-read the partitions table for suse 80 ? (without a system boots). right now suse 80 is a MUST in my organization and i couldn´t migrate to suse 8.1 Best Regards Alexander gonzalez

18 years, 11 months

LVM over software RAID

by Brian Strand

Has an successfully gotten an autoinstall of LVM over software RAID? I can get sw RAID alone to work, but not LVM over sw RAID. I'm working from Suse 8.1 Professional (boxed). The configuration snippet follows at the end of this email. Note that this is a class I had been trying to merge with other profiles, so it is not a comlete autoinstall configuration. I get a single error when I run this through "xmllint --valid sw-raid.xml": sw-raid.xml:145: validity error: Element raid_device content doesn't follow the DTD Expecting (device_name , parity_algorithm , persistent_superblock , raid_level , chunk_size , mount , format , filesystem), got (device_name parity_algorithm persistent_superblock raid_level chunk_size mount format lvm_group ) </raid_device> ^ I had to put multiple logical_volumes elements in to get this far; it looks like there's a bug in the DTD (the following patch against autoyast2-installation-2.6.40-0 might fix it): --- /usr/share/YaST2/include/autoinstall/misc2.dtd.orig 2003-01-01 19:40:39.000000000 +0000 +++ /usr/share/YaST2/include/autoinstall/misc2.dtd 2003-02-04 20:50:57.000000000 +0000 @@ -20,7 +20,7 @@ <!ATTLIST inetd_services config:type CDATA #REQUIRED > -<!ELEMENT logical_volumes (lv)> +<!ELEMENT logical_volumes (lv+)> <!ATTLIST logical_volumes config:type CDATA #REQUIRED > I'm not sure how strictly (or if) the auto-installer follows the DTD, so I don't know if there are other fixes needed besides the DTD. In spite of this and a few other minor issues, I have to say I'm quite impressed with Suse's auto-install system; Anas has done a great job! (Especially as it appears to be a one-person show, judging from the traffic on this list.) Best regards, Brian sw-raid.xml: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd">  <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <install> <lvm config:type="list"> <lvm_group> <lvm_name>switch</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>root</lv_name> <lv_size>1000M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>usr</lv_name> <lv_size>1800M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/usr</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>usr-local</lv_name> <lv_size>200M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/usr/local</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>opt</lv_name> <lv_size>1000M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/opt</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>var</lv_name> <lv_size>2000M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/var</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>home</lv_name> <lv_size>1000M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/home</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>tmp</lv_name> <lv_size>800M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/tmp</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>tmp</lv_name> <lv_size>200M</lv_size> <lv_fs>swap</lv_fs> <lv_mount>/tmp</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> <partitioning config:type="list"> <drive> <device>/dev/hde</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <mount/> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_name>/dev/md0</raid_name> <size>100M</size> </partition> <partition> <format config:type="boolean">false</format> <mount/> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdg</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <mount/> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_name>/dev/md0</raid_name> <size>100M</size> </partition> <partition> <format config:type="boolean">false</format> <mount/> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <raid config:type="list"> <raid_device> <device_name>/dev/md0</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock>true</persistent_superblock> <raid_level>1</raid_level> <chunk_size>4</chunk_size> <mount>/boot</mount> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext2</filesystem> </raid_device> <raid_device> <device_name>/dev/md1</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock>true</persistent_superblock> <raid_level>1</raid_level> <chunk_size>4</chunk_size> <mount/> <format config:type="boolean">false</format> <lvm_group>switch</lvm_group> </raid_device> </raid> </install> </profile>

18 years, 11 months

corrupt files on Suse 8.1 DVD?

by Brian Strand

Has anyone else encountered corrupted files on the DVD version of Suse 8.1? The size of some files does not match that of the same files on the CD. The files I ran into included boot/root (DVD 7073792 bytes, CD 40628224 bytes) and the kernel RPMs suse/i586/k_*.i586.rpm. Hopefully if anyone else is having mysterious errors like "cannot execute /almost/any/file" and such during autoinstall (caused by a corrupt cramfs image file boot/root), this will save them some grief. I spent 6 hours chasing down this problem (I thought it was PXE booting that was causing the problems). Once I replaced the DVD files with the CD files, everything worked well (I have the DVD copied to an NFS-exported filesystem). Or perhaps my DVD or player is just messed up; unfortunately I only have one DVD drive operational at the moment, and only one DVD. Best regards, Brian

18 years, 11 months

X11 configuration does not work after autoinstall

by Martin.Pelikan＠t-systems.com

Hi, I installed SuSE 8.0 with autoinstall from an NFS Server and it worked fine. The only problem is when I start to configure X11 (yast2 x11), the X server configuration starts and stops after a second again, I can't do any changes . yast x11 also doesn't work. When I install the System from DVD or CD (interactive) , i don't have any problems with the X11 configuration. Any ideas ? Thanks for help, Martin

18 years, 11 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall February 2003