January 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

empty raid
by Dejan Muhamedagic 24 Jan '06

24 Jan '06

Hello, This is a simple disk configuration, two hard disks with two partitions each, the first partition containing the root fs and the two second partitions reserved for the sw raid. The installation stops with this message: echo y | /sbin/pvcreate -ff -M2 /dev/md0 /dev/md0: Couldn't find device. because autoyast tries to create the raid with no partitions. The autoyast found both /dev/sda2 and /dev/sdb2 as raid members, but then didn't put them in the /etc/raidtab: Jan 20 15:21:46 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:122 dev:/dev/md0 type:raid1 Jan 20 15:21:46 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:126 partition_list:[$["create":true, "device":"/dev/sda2", "devkey":"2//dev/sda", "format":false, "fs_options":$[], "fsid":253, "fstype":"Linux RAID", "maindev":"/dev/sda", "mount":"", "nr":2, "raid_name":"/dev/md0", "raid_type":"raid1", "region":[66, 2146], "size_byte":17650352128, "size_str":" 16.4 GB", "type":`primary, "used_fs":`unknown], $["create":true, "device":"/dev/sdb2", "devkey":"2//dev/sdb", "format":false, "fs_options":$[], "fsid":253, "fstype":"Linux RAID", "maindev":"/dev/sdb", "mount":"", "nr":2, "raid_name":"/dev/md0", "raid_type":"raid1", "region":[66, 2146], "size_byte":17650352128, "size_str":" 16.4 GB", "type":`primary, "used_fs":`unknown]] Jan 20 15:21:59 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:855 RAID_: # autogenerated /etc/raidtab by YaST2 raiddev /dev/md0 raid-level 1 nr-raid-disks 0 nr-spare-disks 0 persistent-superblock 1 chunk-size 32 Jan 20 15:21:59 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:875 created raids: [0] Jan 20 15:22:04 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:905 success for: /sbin/mkraid -c /etc/raidtab --really-force /dev/md0 The system is SLES9 with SP3 and here's the relevant xml part: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>512M</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/md0</raid_name> <raid_type>raid1</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/rootcopy</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>512M</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/md0</raid_name> <raid_type>raid1</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <lvm_group>rootvg</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <chunk_size>32</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> BTW, the partitioning is sourced using <classes>. Thanks. Dejan

2 2

Re: AW: [suse-autoinstall] Re: Login incorrect
by Michael Schulz 19 Jan '06

19 Jan '06

Thanks for the Answer, is there no way that I can use a Autoyast installation with the password from the original System? Regards Am Thursday 19 January 2006 12:53 schrieben Sie: > Hi, > > the reference profile uses the crypted passwords of your reference system, > but does not set the flag for encryption. Try using your crypted password > from your reference system. > > Mit freundlichen Grüßen / kind regards > SoftService GmbH > > Holger Meyers > Consulting > > Tel 0211 977 09 69 > Fax 0211 977 09 27 > Mobil 0172 2740969 > http://www.softservice.de > > > ________________________________ > > Von: Michael Schulz [mailto:problems@gmx.net] > Gesendet: Do 19.01.2006 12:35 > An: suse-autoinstall(a)suse.com > Betreff: [suse-autoinstall] Re: Login incorrect > > > > Hi List, > > i have the following problem: > > I created with the "Reference Profile Tool" an xml file. > All works fine but after the installation I can't login with > both automatic created users. What can be the reasons > for this. > > I use SLES9 without any SP. > > Regards > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 4

Re: Login incorrect
by Michael Schulz 19 Jan '06

19 Jan '06

Hi List, i have the following problem: I created with the "Reference Profile Tool" an xml file. All works fine but after the installation I can't login with both automatic created users. What can be the reasons for this. I use SLES9 without any SP. Regards

1 0

device.map issue
by Karl Merritts 17 Jan '06

17 Jan '06

I am currently seeing an issue with specifying my device.map inside of the bootloader menu for autoyast. Each time I type in the device (/dev/sda) and hit save, exit autoyast and reopen the autoinst.xml file. The device is always gone once I reopen the file. Save as has also been tried. I am still using SuSE 9.2 and the bug has probably been fixed in later versions. All I am looking is what the xml block will look like inside of the file. Attached is my configuration file. -Karl

1 0

Autoyast SuSE 10.0 erro.
by Rodrigo_Albert_Fedosi 17 Jan '06

17 Jan '06

Hi, Already there is solution for the bug ? OpenSuSE 10.0 error in autoyast: > Error > Storage modification failed. > System error code was -6002. > Failure occured during following action: > Creating software RAID /dev/md0." Att. Rodrigo Albert Fedosi Suporte TI Tel: (31) 3419-8854 Fax: (31) 3419-8803 rodrigo(a)bhz.jamef.com.br www.jamef.com.br

2 1

AutoYast rules.xml and <profile> location?
by Chris Bradshaw 16 Jan '06

16 Jan '06

Hi.... I was just wondering if someone could tell me if it is possible to have something like the following for a rules.xml file: <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script><![CDATA[ #!/bin/sh wget -q -O /tmp/dynamic.xml http://autoyast/cgi-bin/ay_gen.pl?hostname=${hostname}\&hostnetmask=${Netma… echo -n "modified" ]]></script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>/tmp/dynamic.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> </rules> </autoinstall> Specifically I am retrieving the rules.xml file via http as part of an autoyast suse install and I want to use wget in the rules.xml file to retrieve a dynamic control file which I save in /tmp/dynamic.xml and then in the <result><profile> section I would like my rules.xml file to point at this local file. The wget works and does download the file correctly, but the <profile> section doesn't seem to let me refer to a local file.....it keeps trying to wget the file from the same URL where the rules/rules.xml file resides. I have tried just specifying /tmp/dynamic.xml (as shown above) and also file:///tmp/dynamic.xml but neither of these work. Is there any way I can get this to work? Thanx in advance. Chris Bradshaw.

2 7

NLD and SP2
by Rob Thompson 16 Jan '06

16 Jan '06

Hello, I am setting up an Autoyast server to deploy Novell Linux Desktop and I am doing this using iso files. The autoyast server allows me to specify the NLD files fine, but it never asks for the SP2 iso's? I check the box to specify additional cd's but I cannot get Autoyast to prompt for the SP2 files? Anyone know how to solve this? Thanks, Rob

1 0

Missing system users
by Frank Steiner 16 Jan '06

16 Jan '06

Hi, I'm running autoyast on opensuse 10.0.42 (10.1 alpha 4). The installation works fine, but most of the system users are missing although the rpms got installed, e.g.: /root/tmp# rpm -q dhcpcd dhcpcd-1.3.22pl4-212 /root/tmp# grep dhcp /etc/passwd /root/tmp# /root/tmp# rpm -q at at-3.1.8-909 /root/tmp# grep ^at /etc/passwd /root/tmp# In y2logRPM I find entries like this: 2006-01-10 17:58:37 at-3.1.8-909.i586.rpm installed ok Additional rpm output: warning: user at does not exist - using root warning: group at does not exist - using root warning: user at does not exist - using root warning: group at does not exist - using root warning: user at does not exist - using root warning: group at does not exist - using root I can see the reason in y2logRPM: pwdutils are installed quite late, after e.g. at and dhcpd. But I don't understand why: the packages file in my SuSE/setup/descr/ directory has this entry for at: =Pkg: at 3.1.8 909 x86_64 +Req: /usr/sbin/useradd /usr/sbin/groupadd fillup coreutils ... So, Yast should install pwdutils first! Any ideas? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

2 2

software raid initrd fstab problem
by Paul Ingram 12 Jan '06

12 Jan '06

Hi, I am in the process of installing SuSe 10 on a bunch of amd64 boxes, each with 2 sata drives and I wish to configure them as s/w raid 1, mirrored with a /dev/md device for each partition of /boot, / swap and /home. I can install ok onto a single sata device but the s/w raid is being a little more troublesome. After trying to find an optimal way of setting up the autoinstall file, I now have a hybrid file. I started by running an autogeneration script from my install server, as it is the same config, but then I found that the s/w raid was not being set up correctly. As being reported on the 'net the s/w raid support is sparse in autoyast. I managed to manipulate the file with regards to disk partitioning and it seems to have got further. Now I have the s/w raid building correctly I think but at the end of cd1 I get an error 'mkinitrd line 2880 /etc/fstab no such file or directory, no / mountpoint in /etc/fstab' I suspect it may be a grub problem because the setup screen isn't exactly the same as the server but I don't know how to make it the same. I can post my autoinstall file here but it is quite long. ?? Any advice would be gratefully received. Paul -- Paul Ingram Technical Support WorkstationsUK Ltd, Amersam, England www.workstationsuk.co.uk Tel. 01494 724 498 Fax. 01494 433 375

1 0

Changing installation-kernel
by Thomas Rensing 12 Jan '06

12 Jan '06

Hi! I am trying to install Suse 10.0 using "AutoYast". Everything works fine, but since i have to install it on an FSC AMD64 PC with SIS761 chipset, autoinstallation does no longer work. the problem is, that the kernel-version loaded into ramdisk does not support this chipset (especially the sata-chipset), since it is to old. That's why i have got the following question: Is it possible to change the kernel loaded into ramdisk by the installation-routine into a newer one? I think since Kernel 2.6.13 it should recognize the SIS-chipset. I googled a lot but found noting regarding this problem... I installed SuSE 10.1 alpha just for testing and everything worked fine. Thanks a lot, Thomas Rensing

1 0