March 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] PXE install trouble with initrd
by Achim Öhlenschläger 10 Mar '04

10 Mar '04

Anas Nashif schrieb: > Hi, > make sure you are using the latest pxelinux.0. I've downloaded syslinux version 2.08-1, now everything works perfectly. Thanks for the hint. > > Anas > > Achim Öhlenschläger wrote: > >> I'm trying to install Suse Linux on a single board computer >> (net4801) with no CD or floppy drive and the console is on a serial line via minicom. >> To do so, I'm following the instructions from the support database article: >> "Network Installation of SuSE Linux via PXE Boot" ... >> RAMDISK: Couldn't find valid RAM disk image starting at 0. >> Freeing initrd memory: 4545k freed >> kmod: failed to exec /sbin/modprobe -s -k block-major-3, errno = 2 >> VFS: Cannot open root device "" or 03:02 >> Please append a correct "root=" boot option >> Kernel panic: VFS: Unable to mount root fs on 03:02 ...

1 0

install option textmode & vga entry in grub
by grant williamson 10 Mar '04

10 Mar '04

Hi, I prefer to install using textmode(less bloat) however this means that as default I do not get the framebuffer once a machine is installed. I need to add a vga=.... to grubs menu.lst. Is there a way in a textmode install to add something to the autoinst.xml, so it will append this to the kernel on boot. -- grant williamson <traxtopel(a)fastmail.fm>

1 0

Change inst. source..?
by Miro Barbu 10 Mar '04

10 Mar '04

Is it possible to change the inst. source on the client with autoyast..? When autoinstiall is finished, the inst source points to my nfs mount. Instead it would be great if it could point to a public ftp-server. Thanks. Miro.

2 1

Re: [suse-autoinstall] Question/suggestion Linux Installation ove r Network]
by Dustin Kirkland 09 Mar '04

09 Mar '04

forgot to copy everyone else (sorry)

1 0

Re: [suse-autoinstall] Question/suggestion Linux Installation ove r Network
by Lenz, Fabian 09 Mar '04

09 Mar '04

When you boot from CD, there comes the Question, if you want to install or if you want to boot the local System, it is not possible to build in something like this? You load the kernel over the network and ask then, if you want to install or start the installed system. >Using syslog-ng on the remote logging server (boot server) you could use >something like that: >destination tftp { program("/usr/local/bin/client-booting"); }; >#destination tftp { file("/var/log/openwbem"); }; >log { source(src); filter(f_tftp); destination(tftp); }; >in syslog-ng.conf and let the script do the magic :-) This is a fine idea. i will test it. >Or I could add a message to the yast2 log which now supports syslog and >remote logging which says that it safe to change the config files on the >boot server. Such a message can be identified using a filter in >syslog-ng and the switching from netboot to localboot can be done. Which version supports syslog? This idea i think is the best, so you have a status and you can switch. The idea from Bjørn is very easy and not bad, but when you have more than 100 PC´s, you look for a better way. ;-)

2 1

PXE install trouble with initrd
by Achim Öhlenschläger 09 Mar '04

09 Mar '04

Hello, I hope this is the right list for my question. I'm trying to install Suse Linux on a single board computer (net4801) with no CD or floppy drive and the console is on a serial line via minicom. To do so, I'm following the instructions from the support database article: "Network Installation of SuSE Linux via PXE Boot" Initially I tried to install version 9.0, but to follow the instructions as close as possible I downloaded the necessary files for version 8.1 from the SuSE FTP server. Setting up the installation repository, the TFTP server and pxelinux was no problem and the board started the kernel via the network. According to the log on my TFTP server, also the inird is being loaded. However the boot procedure stops with the message: --Snip-- RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 4545k freed kmod: failed to exec /sbin/modprobe -s -k block-major-3, errno = 2 VFS: Cannot open root device "" or 03:02 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 03:02 --Snip-- My pxelinux.cfg/default file looks like: --snip-- SERIAL 0 19200 0 default suse81 ... label suse81 kernel linux81 append console=ttyS0,19200n81 initrd=initrd81 ramdisk_size=65536\ ide=nodma apm=off acpi=off insmod=natsemi\ install=nfs://192.168.1.99/usr/local/dist/suse ... implicit 0 display message prompt 1 timeout 100 --snip-- I've actually some more labels in my default file, because I was trying a lot of things like compiling my own kernel, trying different versions etc. but always with the same result. I have no clue what to do to make it work, any help would be greatly appreciated. Achim PS: By compiling the network driver into the kernel and specifying a NFS root I was able to get to a shell prompt, but I wasn't able to launch the installation from there either. So if somebody knows a recipe how to continue from there, that may also help.

3 2

RE: [suse-autoinstall] Installation from CD
by Ness, Todd 08 Mar '04

08 Mar '04

I have this working, the NFS builds work fine, but, when building from CD I do not get any software selection files. This is curios, I have the same suse/setup/descr/* files on the CD as the NFS repository. If anybody has any idea as to why the selections and software can not be found I would appreciate the help. Todd -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Monday, March 08, 2004 2:24 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Installation from CD Is it possible to create a new bootable cd for a sles8 set, that has customized initrd, and suse/setup/descr, xmls files and customized packages that I could boot off without having to edit disk1 in the set? Example: I have a 5 disk set, I make my own rpms, I add some .sel files to suse/setup/descr, I make an info file in an initrd that installs via nfs, one for booting off cd and uses xml files located in /profiles of the initrd. Has a custom isolinux.cfg to choose which xml script to use. I then bundle all of that up into a bootable disk6 boot off of this disk, choose a boot menu choice. And then have it ask me to insert CD1? Thanks, Todd Ness -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Installation from CD
by Ness, Todd 08 Mar '04

08 Mar '04

Is it possible to create a new bootable cd for a sles8 set, that has customized initrd, and suse/setup/descr, xmls files and customized packages that I could boot off without having to edit disk1 in the set? Example: I have a 5 disk set, I make my own rpms, I add some .sel files to suse/setup/descr, I make an info file in an initrd that installs via nfs, one for booting off cd and uses xml files located in /profiles of the initrd. Has a custom isolinux.cfg to choose which xml script to use. I then bundle all of that up into a bootable disk6 boot off of this disk, choose a boot menu choice. And then have it ask me to insert CD1? Thanks, Todd Ness

1 0

autoyast and loadorder of modules
by Helge Koehn 08 Mar '04

08 Mar '04

hi, we face a problem where we have to load kernelmodules in a specific order to get our scsi devices recognized correctly! we are doing an autoyastinstallation via pxe. we send with the append parameter in the pxe-config file the modules to load, that works. our scsi device are recognized in the correct order. in the autoyast.xml we are partitioning the scsi devices and write the bootloader to /dev/sda. the stuff from disk 1 is transfered to the installed system. after the first initial boot, the order we have with the append parameter in the pxe-config file no longer works, autoyast has build its own initrd for the initial boot and with that the devices are changing because of loading the adapterdrivers in the wrong order! how can we arrange that our wanted order of devices also works after the initial boot. so that /dev/sda remains /dev/sda and not switches to /dev/sdb thanks for an answer. helge.

1 0

Question/suggestion Linux Installation over Network
by Lenz, Fabian 06 Mar '04

06 Mar '04

Hello! I install Linux over network with pxe! There is a DHCP/tftp server and a nfs server. The installation works, but the installation starts always when the PC is booting. On page 41, chapter 7.1.2, example 7-2 and 7-3, is an example how to stop the installation after the reboot. Is there a way to solve the problem without remove a file or a symlink, like an autoyastdaemon? Here is the way how I install the PC´s now: (DHCP Discover) PC ------------------------------------------> DHCP Server (DHCP and tftp server are on one machine) <----------------------------------------- (DHCP Offer) (bootfile/tftpserver) ........ (tftp bootfile/pxelinux.o) PC -----------------------------------------> tftp server <---------------------------------------- -----------------------------------------> (tftp pxelinux.cfg) ......... (nfs mount) PC -----------------------------------------> nfs Server Installation starts *** new,my suggestion with autoyast daemon **** same as above, but asking the installion status before starting Sould I really install? PC ------------------------------------------> autoyast server ( e.g. IP from dhcp Option >128) <------------------------------------------ yes/no Start installation or locally boot and now after installation: Status Install ready PC ---------------------------------------------> autoyast daemon There could be an autoyast server (daemon), and the client would get the autoyast server ip from the dhcp server, option > 128! The autoyast on the install pc could ask or set a status via the daemon. So we would have a stateful installation with a central instance were the installation could be monitored and controlled. In some further versions something like 'ZenWorks light' could be possible, putting all the installation configs in a LDAP directory. This autoyast server could also be able to send the autoinst.xml and the package selection, which then could be taken from our LDAP directory. 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/

3 2

Re: [suse-autoinstall] Question/suggestion Linux Installation over Network
by damien.selles＠eu.effem.com 05 Mar '04

05 Mar '04

Hi Bjorn, And what if your boot disk crashes.. ? or even our MBR crashes... your system will re install automatically.. without warning... (and maybe making you loose some data.)? Don't you think Fabian's process allow you a better control over "re- installation"? Regards, Damien. Bjorn Tore Sund <bjornts(a)mi.uib.no> mi.uib.no To: 05/03/2004 13:46 suse-autoinstall(a)suse.com cc: Subject: Re: [suse-autoinstall] Question/suggestion Linux Installation over Network -------------------------------------------------------------------------------------------------------------------------- On Fri, 5 Mar 2004, Lenz, Fabian wrote: > Hello! > > I install Linux over network with pxe! There is a DHCP/tftp server and a nfs server. > The installation works, but the installation starts always when the PC is booting. > > On page 41, chapter 7.1.2, example 7-2 and 7-3, is an example how to stop the installation after the reboot. > Is there a way to solve the problem without remove a file or a symlink, like an autoyastdaemon? My approach to this is rather simpler, and I'll implement it sometime Real Soon Now(tm). I've got the hard drive before the NIC in the boot order in BIOS. On a new PC, there's no bootable MBR so the machine skips the hard drive and boots from the NIC. When you want to reinstall a machine all you have to do is make the hard drive unbootable: 'dd if=/dev/zero of=/dev/hda bs=512 count=1' before a reboot should do the trick - this bit I haven't tested yet... Bjørn -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 teknisk(a)mi.uib.no Email: bjornts(a)mi.uib.no http://www.mi.uib.no/ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

UNSUSCRIBE ME PLEASE!
by Isabel Falcon 05 Mar '04

05 Mar '04

Ing. Isabel Falcón Consultor de Ventas Afina Sistemas ifalcon(a)afina.com.ve <mailto:ifalcon@afina.com.ve> Av Libertador Multicentro Empresarial del Este Torre Libertador Nucleo B Piso 3 Of B31 Chacao 1060 - Caracas - Venezuela tel: 58-212-2661163 // 7755 // 8980 fax: 58-212-2636502 mobile: 58-412-3729747 web: www.afina.com.ve <http://www.afina.com.ve> -----Original Message----- From: damien.selles(a)eu.effem.com [mailto:damien.selles@eu.effem.com] Sent: Viernes, 05 de Marzo de 2004 09:41 a.m. To: Bjorn Tore Sund Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Question/suggestion Linux Installation over Network Hi Bjorn, And what if your boot disk crashes.. ? or even our MBR crashes... your system will re install automatically.. without warning... (and maybe making you loose some data.)? Don't you think Fabian's process allow you a better control over "re- installation"? Regards, Damien. Bjorn Tore Sund <bjornts(a)mi.uib.no> mi.uib.no To: 05/03/2004 13:46 suse-autoinstall(a)suse.com cc: Subject: Re: [suse-autoinstall] Question/suggestion Linux Installation over Network -------------------------------------------------------------------------------------------------------------------------- On Fri, 5 Mar 2004, Lenz, Fabian wrote: > Hello! > > I install Linux over network with pxe! There is a DHCP/tftp server and a nfs server. > The installation works, but the installation starts always when the PC is booting. > > On page 41, chapter 7.1.2, example 7-2 and 7-3, is an example how to stop the installation after the reboot. > Is there a way to solve the problem without remove a file or a symlink, like an autoyastdaemon? My approach to this is rather simpler, and I'll implement it sometime Real Soon Now(tm). I've got the hard drive before the NIC in the boot order in BIOS. On a new PC, there's no bootable MBR so the machine skips the hard drive and boots from the NIC. When you want to reinstall a machine all you have to do is make the hard drive unbootable: 'dd if=/dev/zero of=/dev/hda bs=512 count=1' before a reboot should do the trick - this bit I haven't tested yet... Bjørn -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 teknisk(a)mi.uib.no Email: bjornts(a)mi.uib.no http://www.mi.uib.no/ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Autoyast on pSeries machines.
by Paul Edgar 03 Mar '04

03 Mar '04

We have written a series of scripts for SuSE SLES 8that will setup the machine for autoyast installation and reboot the machine for installation. All works well on Intel and opteron platforms, but when we try to make a PPC machine install we run into a few issues. 1. It looks like the machine installs the OS, until the first reboot. At that time the machine refuses to boot up. If we put the installation CD in the cdrom drive, boot with that, we can select 'Boot installed system". 2. After selecting this, the machine boots up and finishes up the installation just like normal. Here is what I see when the machine does it's first reboot during install. /dev/sda invalid device Then I go into rescue CD mode from the installation CD and look at /etc/yaboot.conf which does not exist. So I chroot the mounted and look at lilo.conf which has the following in it. This does not look correct from what I have seen when the system is installed macnually. default=linux timeout=100 boot= activate image = /boot/vmlinux label = linux root = /dev/sda3 initrd = /boot/initrd append = "" If I try to run lilo at this point, it errors out on boot= which should be /dev/sda1. Activate is an extra parameter I have not seen before. Image pointed to /boot/vmlinux.initrd initrd = was not there append = "" was not there Any suggestions, questions, or pointers would be helpful. -- Paul Edgar Verification Engineer Linux Technology Center / IBM External 512.838.1493 / TieLine 678-1493 javaoops(a)us.ibm.com No trees were destroyed in the sending of this message, however, a significant number of electrons were terribly inconvenienced.

4 7

How to avoid booting confirmation?
by Robert Pollak 03 Mar '04

03 Mar '04

Hello! I use the appended control file autoinst.xml on a floppy during installation from the original SLES8 CDs. At the end of the "Finishing Basic Installation" screen, i am asked > The LILO boot sector has been written to disk. You can restore > the old boot sector in the installed system with "lilo -u /dev/sda" > > Now booting your system... > [OK-Button] , and the installer waits for interactive confirmation. How can i change the control file such that this confirmation is not needed? Or can't it be suppressed by any of the <mode> entries? -Robert ****************autoinst.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"> <configure> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>XXXXXX</user_password> (<- pw removed) <username>root</username> </user> </users> </configure> <install> <bootloader> <location>mbr</location> </bootloader> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Vienna</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <mode> <installation config:type="boolean">true</installation> <upgrade config:type="boolean">false</upgrade> <confirm config:type="boolean">false</confirm> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"/> <use>all</use> </drive> </partitioning> <software> <base>Minimal</base> </software> </install> </profile>

2 2