April 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

problem using grub for NFS install
by anna cheng 14 Apr '04

14 Apr '04

I have tried this at home and it worked, but for some reasons I was not able to make it to work in my office. My home machine is a Compaq desktop and the machine at work is Dell PowerEdge 1650. I downloaded the grub floppy from http://www.suse.de/~nashif/autoinstall/ and updated menu.lst to use the following. It works like a charm at home. title autoinstall-ip ifconfig --address=172.20.212.51 --server=172.20.212.41 --mask=255.255.255.0 --gateway=172.20.212.1 root (nd) kernel (nd)/linux install=nfs://172.20.212.41/usr/local/SuSE autoyast=nfs://172.20.212.41/usr/local/SuSE/profiles/autoinst.xml ip=172.20.212.51 netmask=255.255.255.0 initrd (nd)/initrd title floppy root (fd0) chainloader +1 However, I updated the IP and use the **same floppy** to test a PowerEdge server at work, it hangs on kernel (nd)/linux install=nfs://172.20.212.41/usr/local/SuSE autoyast=nfs://172.20.212.41/usr/local/SuSE/profiles/autoinst.xml ip=172.20.212.51 netmask=255.255.255.0 Basically after I picked autoinstall-ip from the grub menu, the messages from the console are Booting autoinst-ip ifconfig --address=172.20.212.51 --server=172.20.212.41 --mask=255.255.255.0 --gateway=172.20.212.1 Probing ..[RTL8139]... The PCI BIOS has not enabled this device Updating PCI command 0000->0005. PC_bus 00 pci_device_fn 00 ioaddr 0x0000, addr 00:00:00:00:00:FF 10mbs full-deplex Filesystem is tftp, using whole disk root (nd) kernel (nd)/linux install=nfs://172.20.212.41/usr/local/SuSE autoyast=nfs://172.20.212.41/usr/local/SuSE/profiles/autoinst.xml ip=172.20.212.51 netmask=255.255.255.0 Then it just hangs.... I was not sure whether it was related to the PC BIOS has not been enabled, even I think the version under http://www.suse.de/~nashif/autoinstall/ may already have those options enabled, but I downloaded grub and recompiled with the options --enable-diskless and --enable-rtl8139 and still have the same problem. Have anyone seen this before? and I appreciate any suggestion in fixing the problem. Thanks anna --------------------------------- Do you Yahoo!? Yahoo! Tax Center - File online by April 15th

1 0

AW: [suse-autoinstall] Dynamic partitioning
by itredl＠freudenberg.de 14 Apr '04

14 Apr '04

>> It all depends on what SuSE Linux release you are using. With recent >> releases this might be possible using rules. >> >> Anas > We use SuSE Linux Enterprise Server release 8. Should be recent enough, > shouldn't it? I've just done some research concerning rules with SLES8 and now I'm almost sure that SLES8 does not support them. My assumption comes from the facts that it ignores my rules/rules.xml file, that I didn't find any rules.dtd file and that rules appear in your documentation for 8.2 at first. (suggestion: It would be nice if you provided a changelog which can be reached through your website easily.) Is my assumption - it is only a assumption because I could not find a changelog - true? As I've already mentioned we use SLES8. Since we would need such a solution (and I'm not really willing to write sfdisk-scripts or something like that) I've had another idea: Is it possible to update AutoYast and continue using SLES8? If so, what has to be done? Thanks in advance! Best regards Matthias Redlich

2 1

AW: [suse-autoinstall] Dynamic partitioning
by itredl＠freudenberg.de 14 Apr '04

14 Apr '04

> It all depends on what SuSE Linux release you are using. With recent > releases this might be possible using rules. > > Anas We use SuSE Linux Enterprise Server release 8. Should be recent enough, shouldn't it? Best regards Matthias Redlich

1 0

Dynamic partitioning
by itredl＠freudenberg.de 14 Apr '04

14 Apr '04

Hello list, we use AutoYast for a lot of different server types. Some of them have 32GB harddrives, others have bigger once with 72GB and so on. Thus the partitioning differs from server to server. Currently our linux system, with all its filesystems (/tmp, /usr ..), is about 2GB. The rest of the disk space is used for 10GB partitions for databases. Since we have different harddrives the number of additional 10GB partitions may vary. (example: 32GB means 3 additional partitions; 72GB => 7 additional partitions) Is there a feature (or a simple solution) which makes AutoYast create as much 10GB partitions as possible until the disk is full automatically? Therefore it should detect the size of the disk and then decide how many partitions it can create. Or do we have to change the control file manually? Or do we have to manage this with self-written scripts? Best regards Matthias Redlich

2 1

unable to see info file
by anna cheng 13 Apr '04

13 Apr '04

I understand this may not be an autoinstall program, but I thought some of you may have seen this. I have read the documentation in http://www.suse.com/~nashif/autoinstall and created a floppy which contains an autoinst.xml and info file. I put the first SLES 8 CD in the CDROM and entered autoyast=floppy when the system came up. I put the floppy in the floppy drive and have no problem setting up the machine at home using NFS. However, I was not able to repeat the same setup at work. For some reasons, the machine kept on reporting cannot see info file and tried to start manual install. I tried different settings on autoinst.xml and even use the same settings I have at home (with the IP address updated to reflect the IP address at work), but without success. My home machine is Compaq but my machine at work is Dell PowerEdge 1650. Will this be a problem? ( I have tested including aacraid aic7xxx usb-storage in the kernel_parameter of the autoinst.xml file and I have also tested removing the CDATA portion from the xml file) It failed after "Searching for the infofile", it returned a manual install screen. When I attemtped to do a manual install, it was obvious that the system already knew the IP of the machine and the server, it even knew the serverdir of the software. <?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"> <configure> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain></domain> <hostname></hostname> <nameservers config:type="list"/> <searchlist config:type="list"/> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>172.20.212.255</broadcast> <device>eth0</device> <ipaddr>172.20.212.51</ipaddr> <module></module> <netmask>255.255.255.0</netmask> <network>172.20.212.0</network> <options></options> <remote_ipaddr></remote_ipaddr> <startmode>onboot</startmode> <wireless>no</wireless> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>172.20.212.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>3ssF48KCbJon2</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <user_password>wxEGdL44Qe4IY</user_password> <username>acheng</username> </user> </users> </configure> <install> <bootloader> <activate config:type="boolean">false</activate> <kernel_parameters></kernel_parameters> <lba_support config:type="boolean">false</lba_support> <linear config:type="boolean">false</linear> <location>mbr</location> </bootloader> <general> <clock> <hwclock>localtime</hwclock> <timezone>US/Eastern</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> <mouse> <id>00_ps2</id> </mouse> </general> <software> <addons config:type="list"> <addon>YaST2_modules</addon> <addon>LSB</addon> <addon>sles_admin</addon> <addon>Basis-Devel</addon> <addon>X11</addon> </addons> <base></base> <packages config:type="list"/> </software> <init> <info_file> <![CDATA[ # #start_linuxrc_conf # install nfs://172.20.212.41/usr/local/SuSE/current ip: 172.20.212.51 netmask: 255.255.255.0 gateway: 172.20.212.1 server: 172.20.212.41 serverdir: /usr/local/SuSE/current netdevice: eth0 # #end_linuxrc_conf ]]> </info_file> </init> </install> </profile> thanks anna --------------------------------- Do you Yahoo!? Yahoo! Tax Center - File online by April 15th

1 0

root passwort, sound
by Dominic Lukwata 13 Apr '04

13 Apr '04

Hi all, we autoinstall Suse 9.0. It work better and better but there still some problems: 1. we have not succeeded to set a root passowrd per autoinstall. 2. The sound module makes post installation after the first log in and the Master volume ist at zero. We use the onboard sound on the motherboard ASUS P4P800 Delux Hier ist the sound section in the controll file <sound> <autoinstall config:type="boolean">true</autoinstall> <modules_conf config:type="list"> <module_conf> <alias>snd-card-0</alias> <model>82801DB-ICH4, Intel</model> <module>snd-intel8x0</module> <options> <snd_ac97_clock>0</snd_ac97_clock> <snd_enable>1</snd_enable> <snd_index>0</snd_index> </options> <unique_key>uniq.virtual</unique_key> </module_conf> </modules_conf> <volume_settings config:type="list"> <listentry> <Master config:type="integer">75</Master> </listentry> </volume_settings> </sound> Does any one has any hint how to fix these? Thanks Dominic

3 3

Helge Koehn/Germany/IBM is out of the office.
by Helge Koehn 09 Apr '04

09 Apr '04

I will be out of the office starting 04/08/2004 and will not return until 04/14/2004. I will respond to your message when I return.

1 0

Re: SuSE - Yast2 Autoinstall CD for SLES8
by Robert Pollak 09 Apr '04

09 Apr '04

On Thu, 2004-04-08 at 09:30, s-steins(a)web.de wrote in private mail: > (refering to: http://lists2.suse.com/archive/suse-autoinstall/2004-Feb/0020.html) > > have you now been successful creating a single SLES8-YaST2-Autoinstall-CD from the > CD-Rom-Sources of the 4 CDs which came with the SLES-box? Hello, I'm afraid no. I only managed to create a version of the SLES8-CD (dependent on hd type: ide or scsi) containing the control file. This makes it possible to install SLES8 without floppy with two cd changes and one click of "OK". (SP3 is not necessary for this.) I did not manage to collect the needed rpms on one cd. According to Anas Nashif, "Create iso image" from autoyast2 cannot be used for this, because it only processes packets of one software source. (Since "Create iso image" started working in SP3, we have got three sources: UnitedLinux, SLES8, SP3.) The following approaches were unsuccesful so far: - Collecting the needed packets in one directory and using this as software source for "Create iso image". - Copying rpms from UnitedLinux-cd1 into the custom version of the sles8 cd; changing the package files entries s.t. the rpms are found at the new location. The next thing I had planned was to try it the other way round: to include rpms from sles8 into the UL cd. This could be easier, since the UL cd only contains one "product". But then the task was assigned to a coworker, and I think nothing has happened since then. Let me (and the list) know about your progress - I wish you good luck. -- Robert Pollak GPG Key ID: 748646AD

1 1

autoinst.xml on self-made cd
by Manuel.Laesser＠telekurs.com 07 Apr '04

07 Apr '04

Hello, sorry to bother you again and again. I'm using SLES8 with autoyast2-2.6.44-7 and autoyast2-installation-2.6.44-7. I think this is the latest version for SLES8 (comming with SP3). I copied autoinst.xml to the root of my self-made CD-ROM and I'm using the following parameter in isolinux.cfg # autoyast label autoyast kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 textmode=1 If you use parameter "autoyast=default" YaST2 will look for autoinst.xml in the following three places (according to Anas Nashif PDF SLES8 - Automatic Linux Installation and Configuration with YaST2) : 1. the root directory of the floppy disk 2. the root directory of the installation medium (CD-ROM in my case) 3. the root directory of the initial ram disk used to boot the system Cool......unfortunately it doesn't work at all in my environment. I tried with "autoyast=file:/autoinst.xml", "autoyast=file://autoinst.xml", "autoyast=default" I always got this bloody control menu where it asks for the location of the autoinst.xml! From there I could choose http, device, floppy, nfs....but I didn't manage to access the cdrom. If I insert a floppy with my autoinst.xml in the root, the installation is proceeding. I also can edit isolinux.cfg with "autoyast=floppy://autoinst.xml" and it'll find autoinst.xml. Why do I get always very nice and well meant hints from the autoinstall mailing list telling me that the are using "...autoyast= default instmode=cd..." and everything is working fine. Does this have a coherence that I'm using SLES8 with autoyast2-2.6.44-7 and most of people Suse x.x with the newest autoyast2 autoyast2-2.8.14-20 or so..... I'm really stumped.... Any comment is welcome. Regards Manuel p.s. I'll send a box of the finest original swiss chocolate to the one who can give me the right tip to solve this problem...... ;-)) ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

2 4

lvm: autoyast complains about wrong lvcreate parameters
by Mathias Pietsch 07 Apr '04

07 Apr '04

hello. when i run an autoyast profile (for suse 8.2) with this lvm-configuration: <lvm config:type="list"> <lvm_group> <lvm_name>HomeVol</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>Linux_home_lv</lv_name> <lv_size>21296</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/export</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> i get the following errors: 1) yast says that on /export are some megabytes of disk space missing and i should deselect some packages (allthough nothing at all will be installed there during installation). and when i continue ... 2) yast complains about wrong lvcreate parameters. but when i run "lvcreate --name Linux_home_lv --size 21296 HomeVol" (these are exactly the parameters that should be used by autoyast, too) manually, the command succeeds and i can continue and finish the installation successfully. from the last line of /var/log/YaST2/y2log i can read that yast thinks the lv_size parameter is 0. (but i have to admit that i hardly can understand the content of these y2log* files). has anyone a clue about what goes wrong here? thanks in advance mp -- ---------------------------------------------------------------- Mathias Pietsch Network and System Administration - Neuroimage Nord, Bldg S10, 3rd Floor, Room 301 Department of Neurology Universitätsklinikum Hamburg-Eppendorf Martinistr. 52 D-20246 Hamburg Germany - Phone: +49-40-42803-8673 Fax: +49-40-42803-9955 Mail: m.pietsch(a)uke.uni-hamburg.de ---------------------------------------------------------------- GnuPG/PGP (http://www.gnupg.org) key id: 644112F2, fingerprint: E37B 77F4 87C7 6309 758D F507 A93C 207C 6441 12F2 ---------------------------------------------------------------- Please avoid sending me Word, Excel or PowerPoint attachments. (see http://www.fsf.org/philosophy/no-word-attachments.html) ----------------------------------------------------------------

1 0