February 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] Load initrd hangs (SuSe 9.0)
by Mouncef_Belcaid＠blm.gov 24 Feb '04

24 Feb '04

Hi Dominic, I had the same issue with SuSE 9.0 Pro. You need to download the latest version of Syslinux tar file from http://www.kernel.org/pub/linux/utils/boot/syslinux/, I believe it's version 2.0.8. Untar it and copy pxelinux.0 to your tftpboot directory. Then try your automatic installation again. Mouncef |---------+----------------------------> | | Dominic Lukwata | | | <d.lukwata@fh-man| | | nheim.de> | | | | | | 02/24/2004 11:36 | | | AM | | | | |---------+----------------------------> >--------------------------------------------------------------------------------------------------------------| | | | To: <suse-autoinstall(a)suse.com> | | cc: Dominic Lukwata <d.lukwata(a)fh-mannheim.de> | | Subject: [suse-autoinstall] Load initrd hangs (SuSe 9.0) | >--------------------------------------------------------------------------------------------------------------| Hi, We have set up an Installations Server for SuSe 9.0 as specified in the documentations of Anas Nashif. We have used original files from the SuSe 9.0 Pro distribution. I like to use it for a network install of SuS9.0 to a number of workstations. The client boots and PXE is startet und makes contact to a dhcp-Server. The it loads the linux kernel. But when its starts loading the raddisk it hangs: Loading initrd ... And the boot fails. We have now spent around over a week on this problem and are stuck now. Does anybody have a hint how to make this work. Thanks Dominic -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Re: [suse-autoinstall] Problems with autoinstall of sles8 via HTTP
by Jeff Crow 23 Feb '04

23 Feb '04

It appears that I have discovered what the problem is, it looks like you must have valid forward and reverse DNS entries for any DHCP or static addresses used for the Network installation to work properly. The problem is that I am in a lab that does not have this configured. Does anyone know if there is a way around this for SLES8? Any help is much appreciated. Jeff >>> Anas Nashif nashif(a)suse.de> 2/10/2004 1:04:56 PM >> Jeff Crow wrote: >> I am having difficulties with the autoinstall of sles8 via HTTP. When I >> boot up, I receive the following error after the hardware detection and >> activation of usb devices: "Could not find the UnitedLinux Installation >> Source. Activating manual setup program." So I then go through the >> manual screen and verify that my network card (eth0) is loaded, and >> select 'Start Installation / System > Start Installation / Update > >> network > HTTP. If I choose 'Automatic Configuration via DHCP?', I get >> this error: "DHCP Configuration Failed." If I choose no on 'Automcatic >> Configuration via DHCP" and manually put in my static IP address, >>netmask and gateway, I get this error: "An error occurred during the >> network configuration. Probably your network card was not recognized by >> the kernel!" >> Here are some more details of my setup. My installation source is loop >> mounted ISO's setup as described here: >> http://www.suse.de/~nashif/autoinstall/faq.html#id2459380. I am using >> the SP3 kernel, initrd and have the driverupdate at the root of the >> source as suggested. I have tried this on multiple machines with the >> same result. >> >At this point of the installation, you haveto verify two things: >1. You have supplied the correct installation source with the "install" >keyword and make sure the files are accessable. >2. Verify the NIC is actually configured. This can be seen on the third >console. Follow the messages on the console and see where it is hanging >and why. Usually its the wrong kernel module or something similar. > > > >Anas >> I would appreciate any suggestions or solutions. >> >> Thanks, >> >> Jeff >> -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Re: [suse-autoinstall] SLES 8, PXE, can't get textmode=1 to work, also prompt about lilo install...
by game82＠unixpeople.com 20 Feb '04

20 Feb '04

I don't think I'm using service pack 3. I bought the boxed product, and the CDs do not indicate a service pack. I tried to open a ticket with suse on this, but even though my support contract says "Call reception by phone, email, fax or web-form", when I actually called the number in Germany, they said, support is email only..... I explained that I openned a ticket on Friday, Feb 13 and that I haven't heard back yet, and the only suggestion was to try again..... Sigh! Enough ranting about my problems with support. So, here are my questions now: 1) Where can I get service pack 3 2) How can I apply it to the spooled distribution on the NFS server? I went to the maintenance portal, logged in and it seems to only have information on using yast2 to do an online update to an already installed server. Anas Nashif wrote: >> >> >> game82(a)unixpeople.com wrote: >> > >>>> Hi, >>>> I have autoinstallation working with SLES8, but I have two problems. >>>> >>>> 1) At the end of the installation, it installs lilo. After installing >>>> lilo, it pops up a dialog box that simply tells me that lilo has >>>> been installed and it gives me the command line to restore the boot >>>> sector. I then have to click on the OK button. I really need this to >>>> be completely hands off. Is there anyway to suppress this dialog box? >>>> > >> A known bug >> Are you using SP3? lilo would be installed only if you have LVM or RAID. >> so if you dont have those, most likely you are not using SP3. >> There is another workaround for this, configure reporting to not show >> messages. >> (Adding this to the FAQ) >> >> There is a new driverupdate coming soon with additional fixes and >> enhancements that you can use isntead of the one on SP3. For testing >> purposes only until its released officially, hopfully next week >> >> http://www.suse.de/~nashif/driverupdate/ >> >> >> > >>>> 2) In trying to troubleshoot the problem above, I wanted to switch to >>>> text mode (most of my servers are headless, so this will be necessary >>>> eventually). >>>> I appended textmode=1 to the line in the pxe config file, but it >>>> still starts in graphical mode. >>>> >>>> Here is the entry from the pxe config file: >>>> --------------------------------------------- >>>> label suse_standard_server_8 >>>> kernel linux.suse_standard_server_8 >>>> append initrd=initrd.suse_standard_server_8 ramdisk_size=64000 >>>> root=/dev/ram3 >>>> install=nfs://192.168.1.36/usr/software/linux_distributions/suse_standard_server_8 >>>> autoyast=nfs://192.168.1.36/usr/software/linux_distributions/kickstart/yast_profiles/suseServer8.xml >>>> textmode=1 > >> >> >> the command line is too long! try reducing it a bit. This is a known >> issue. i.e. use symlinks instead of the long URL. in "install" and >> "autoyast". >> (This is already in the FAQ). >> > >>>> ----------------------------------------------- >>>> >>>> Please note that in my file, everything is after the append is on the >>>> same line...... >>>> >>>> >>>> If anyone has any ideas, I'd appreciate it. >>>> >>>> > >>

2 1

differences between sles8 and suse9 autoyast
by Helge Koehn 20 Feb '04

20 Feb '04

hi there, am i right that the version delivered with sles8 is not able to handle rules.xml files as described in the documentation of suse9?! what would happen if i install the version for suse9 on sles8 platform?! or how could i get with sles8 these rulebased build mechanism for autoyast.xml files?! and one more question, the final autoyast.xml is parsed and interpreted at installation runtime of the system?! does that mean, if i install sles8 i only can use the sles8 mimic in the autoyast process and if i install suse9 i can use the rulebased mechanisms? that would mean the installation of the suse9 autoyast packages on sles8 wouldn't help to get a rulebased installation process there ... thanks for answers. helge.

1 0

How to configure GRUB for boot on SCSI or IDE?
by K.-W. Grabbe 20 Feb '04

20 Feb '04

Hello, I want to install systems with IDE and SCSI harddisks. Does anybody now, how to configure GRUB for this case?? Regards, K.-W. Grabbe -- GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...) jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++

1 0

automatic xml creation?
by Andreas Vetter 20 Feb '04

20 Feb '04

Hi! Is there a way to create a xml file containing the configuration after installation for later use as a autoconfig.xml? I mean, RedHats anaconda produces the anaconda-ks.cfg file automatically. Does yast do something similar? Regards, Andreas Vetter

2 1

SLES 8, PXE, can't get textmode=1 to work, also prompt about lilo install...
by game82＠unixpeople.com 20 Feb '04

20 Feb '04

Hi, I have autoinstallation working with SLES8, but I have two problems. 1) At the end of the installation, it installs lilo. After installing lilo, it pops up a dialog box that simply tells me that lilo has been installed and it gives me the command line to restore the boot sector. I then have to click on the OK button. I really need this to be completely hands off. Is there anyway to suppress this dialog box? 2) In trying to troubleshoot the problem above, I wanted to switch to text mode (most of my servers are headless, so this will be necessary eventually). I appended textmode=1 to the line in the pxe config file, but it still starts in graphical mode. Here is the entry from the pxe config file: --------------------------------------------- label suse_standard_server_8 kernel linux.suse_standard_server_8 append initrd=initrd.suse_standard_server_8 ramdisk_size=64000 root=/dev/ram3 install=nfs://192.168.1.36/usr/software/linux_distributions/suse_standard_server_8 autoyast=nfs://192.168.1.36/usr/software/linux_distributions/kickstart/yast_profiles/suseServer8.xml textmode=1 ----------------------------------------------- Please note that in my file, everything is after the append is on the same line...... If anyone has any ideas, I'd appreciate it.

2 1

Chroot Script
by Lenz, Fabian 19 Feb '04

19 Feb '04

Hello! In the documentation on page 29 from Anas Nashif is the description about Chroot environment post-install scripts, but i don´t know what it means. Can somebody explain what the sentence mean or what a chroot script is and what chroot mean? The sentence from the documentation: Chroot environment post-install scripts Chroot scripts are exexuted in the chroot environment befpre Yast2 boots for the first time and before the boot loader is installed. Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/

2 1

yaboot.conf not created during ppc64 autoinstall
by Dustin Kirkland 19 Feb '04

19 Feb '04

I've been working extensively with Autoyast and SLES 8 to create custom automated installations for testing purposes on several platforms. I've been able to work around a few problems on ix86 and x86_64 platforms, but I've hit a road block on ppc64 that I simply cannot solve. The hardware is an IBM PSeries P615, PowerPC architecture. I'm trying to install SLES 8 with Service Pack 3 via autoyast natively on the box (ie not on a logical partition). The process seems to work, until the machine reboots, at which point Linux is not able to boot, as there is no /etc/yaboot.conf file. In recovery mode, I can access the system and see that the machine appears to have been installed properly, minus the delinquent yaboot.conf file. Here are the pertinent parts of my autoinst.xml file: ... <bootloader> <location>ppc_chrp</location> </bootloader> ... <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <partition_id config:type="integer">65</partition_id> <partition_nr config:type="integer">1</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">2</region_entry> </region> <size>2097153</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <region config:type="list"> <region_entry config:type="integer">2</region_entry> <region_entry config:type="integer">513</region_entry> </region> <size>1073741825</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <region config:type="list"> <region_entry config:type="integer">515</region_entry> <region_entry config:type="integer">16842</region_entry> </region> <size>35318136833</size> </partition> </partitions> <use>all</use> </drive> Help would be appreciated. Thanks, Dustin

1 0

Automatic installation with floppy and root-NFS
by Maurer, Hermann 13 Feb '04

13 Feb '04

Hello folks, I'm trying to install SuSE Linux 9.0 on my machine, which has no cd-rom drive. Therefore I decided to start the automatic installation from a floppy disk. I compiled a "small" kernel (I have got the stadand kernel from SuSE 9.0 as basic), changed the root device of it with rdev and put the compressed kernel onto a floppy. Then I installed syslinux with the command syslinux -s /dev/fd0. The syslinux.cfg on the floppy looks like this (but the values in the <> are real ip settings): ------------------------------------------------- default linux append init=/linuxrc rw root=/dev/nfs ip=<client-ip>:<server-ip>:<gateway-ip>:<netmask>::eth0: nfsroot=<server-ip>:/data/distributions/pub/suse/i386/9.0/root_fs vga=normal prompt 1 timeout 30 readinfo 2 ------------------------------------------------- On the same floppy I put the file named info, what linuxrc is to be able to read from. Here it is: ------------------------------------------------- netdevice=eth0 server=<server-ip> serverdir=/data/distributions/pub/suse/i386/9.0 ip=<client-ip> netmask=<netmask> gateway=<gateway-ip> nameserver= insmode=eepro100 autoyast=nfs://<serverip>/autoyast.xml install=nfs://<server-ip>/data/distributions/pub/suse/i386/9.0 ------------------------------------------------- So I started the computer from the floppy and saw, that the boot process runs normal, the root fs is mounted and linuxrc is started. Linuxrc then starts the automatically hardware scan, found devices etc. It can even read the info file propierly. However while it tries to access the install directory at the nfs share, it doesn't use the network connection, that has been just established, and tries to load the modules for the nic (Intel EtherExpress 10/100), it could found. The modules are e100.o and mii.o as described in the file modules/module.config. In this place I get an error on the vt3: Looking for a network server... Trying to activate eth0 Setting up localhost... done Sending DHCP request to eth0... no/incomplete answer. Ok, that didn't work; see if we can activate another network device... inmod e100 insmod mii Oops, that didn't work. No further netowrk cards found; giving up. So the automatic install process is stoped here and I'm requested to insert the module disk 3 (to let it load the further network modules in the hope, it could find some more :-) I tried some other settings (dhcp, fixed ip address etc.) but couldn't solve the problem. My nfs server and the directory structure on it look fine as I could install some other computers from CD + Floppy + NFS. Can anybody help me ? Any suggestions are appreciated. Thank you ! Mit freundlichen Grüßen/Kind Regards ----------------------------------------------------------------------- Hermann Maurer GFT Financial Solutions GmbH IT Services Frankfurt Düsseldorfer Straße 13 D-65760 Eschborn http://www.gft.com -----------------------------------------------------------------------

2 1