- openSUSE Autoinstall

Setting up Software Raid
by Frank Pascher 06 Jun '02

06 Jun '02

Hi, does anyone know whether automised Raid installation (Software raid) will be supported ? cheers frank +----------------------------------------------------------+ | 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 | +----------------------------------------------------------+

1 0

Getting profile with http on custom CD
by Miguel Gómez 04 Jun '02

04 Jun '02

Hi, I would like to create a custom installation CD that gets the profile from a http server, but I'm having several problems with the append parameters on my isolinux.cfg file: If I use "append initrd=initrd ramdisk_size=65536 autoyast=http://193.146.185.99/profiles/ instmode=cdrom" the installer doesn't find the profiles, although the are perfectly accessible on the server. I've tried also using "install=cdrom://" or "install=file://" instead of "instmode=cdrom", but the problem persisted. If I use "append initrd=initrd ramdisk_size=65536 autoyast=http://193.146.185.99/profiles/" (omitting the install or instmode parameter), the installer tries to locate a network installation server with a DHCP query and doesn't use the CD as installation media. I don't use a DHCP server, I just enter manually the network parameters (netdevice, ip, netmask, etc.) at the boot prompt, so I get an error at this stage. ¿Can somebody tell me what kernel parameters should I use? ¿is it a bug in yast2's automated installation? Regards, Miguel Gómez Rodríguez gomez(a)dit.upm.es

1 0

Antwort: [suse-autoinstall] How to creat a single boot floppy
by Andreas Rother 03 Jun '02

03 Jun '02

creation of a single boot floppy: - create the bootfloopy and the first module floppy - delete everything but "linux", "message" and "sysconfig.cfg" from the bootdisk (most likely, you will replace linux, too) - copy /floppy/initrd from the first module floppy to harddisk - rename initrd on harddisk to initrd.gz and decompress it - mount initrd from harddisk (with -o loop) - copy the modules 3c59x.o, aic7xxx.o, cramfs.o and reiserfs.o (or a filesystem module of you choice) from /lib/modules/2.4.18-4GB/... to <initrd-mountpoint>/modules - unmount initrd and compress it - copy initrd.gz to /floppy/initrd. Most likely you will run out of disk space! - Build your own kernel. You also can do "make cloneconfig" and disable things like ppp, video4linux, sound, usb etc (see my other posting "single boot floppy" from 29.05.). Ensure that the modules will still work or copy the modules to initrd (see above) - copy this kernel to /floppy/linux - unmount floppy and do "syslinux /dev/fd0" to make the floppy bootable For Information about control file on NFS read the documentation. You can start at file:/usr/share/doc/packages/yast2-modules-autoinst/html/index.html HTH, Andreas -- Andreas Rother - E-Plus Mobilfunk GmbH & Co. KG Phone : unbekannt / Fax : unbekannt / Mobile : unbekannt Jibin Huang <jibin(a)rbg.informatik.tu-da An: suse-autoinstall(a)suse.com rmstadt.de> Kopie: Thema: [suse-autoinstall] How to creat a single boot floppy 31.05.2002 17:14 Hi, all: I try to install SuSE 8.0 from NFS server. But I can´t find the way to build a single boot floppy for the autoinstall procedure. I need two modules for the hardware(3c59x and aic7xxx) , and put the profile in NFS server. Could somebody tell me, what should I do? Regards Jibin

1 0

How to creat a single boot floppy
by Jibin Huang 31 May '02

31 May '02

Hi, all: I try to install SuSE 8.0 from NFS server. But I can´t find the way to build a single boot floppy for the autoinstall procedure. I need two modules for the hardware(3c59x and aic7xxx) , and put the profile in NFS server. Could somebody tell me, what should I do? Regards Jibin

1 0

Re: [suse-autoinstall] Autoinstall with PXE
by Jörgen Karlsson 31 May '02

31 May '02

>> > > I always get the "Insert modules Disk 3" when running with > > autoyast=nfs://172.16.100.1/opt/suse > > set on kernel cmdline. Is this because yast2 cannot find the modules it > > need? Or does it always ask > > this question? How do I get past it? (our systems only has a serial > > console, no floppy, no cdrom). > What do you have in autoyast=nfs://172.16.100.1/opt/suse ? If you have > copied the CDs to this directory and you wish to install over NFS, you > should use install=nfs://172.16.100.1/opt/suse This is my commandline. init=/linuxrc rw autoyast=nfs://172.16.100.1/opt/SuSE/main.xml install=nfs://172.16.100.1/opt/SuSE It looks like linuxrc cannot find any modules on the ramdisk. Adding root=/dev/ram0 does not help either. Last out messages from kernel : : RAMDISK: Compressed image found at block 0 Uncompressing.........................................done. Freeing initrd memory: 65536k freed VFS: Mounted root (minix filesystem). Freeing unused kernel memory: 120k freed Moving into tmpfs... done. ramdisk /dev/ram0 freed >>> SuSE installation program v1.3 (c) 1996-2002 SuSE Linux AG <<< Starting hardware detection... Activating usb devices... done Searching for infofile...... /Jörgen Karlsson

3 5

console speed
by Jörgen Karlsson 31 May '02

31 May '02

How do you set the serial speed yast2 uses? Bios, terminal, is set to 38400. Yast2 switches to 115200 during installation. Kernel cmd includes console=ttyS0,38400 but yast2 don't get it. Very annoying as we need our settings at 38400 /Jörgen Karlsson

1 0

Antwort: [suse-autoinstall] Single boot floppy - solved
by Andreas Rother 31 May '02

31 May '02

Phone : unbekannt / Fax : unbekannt / Mobile : unbekannt "Andreas Rother" <Andreas.Rother@e An: suse-autoinstall(a)suse.com plus.de> Kopie: Thema: [suse-autoinstall] Single boot floppy 29.05.2002 10:43 > If I try to mount manually on console <F9> with the command "mount > /var/adm/mount/suse/images/root /mnt -o loop" I get the error message: > "mount: invalid number of arguments" These error messages were cause by the cramfs module. The module was build for a 2.4.17-4GB kernel and refused to work with the install kernel. I copied the module from a running 8.0 and now it works. Kind regards, Andreas -- Andreas Rother - E-Plus Mobilfunk GmbH & Co. KG

1 0

Single boot floppy
by Andreas Rother 29 May '02

29 May '02

Hi all! I try to build a single boot floppy for the autoinstall procedure. As the hardware is quite similar (i.e all nodes have 3com NICs), I'm quite annoyed by the fact, that I have to use three floppies until the automatic installation starts. I use an install server (NFS) and profiles depending on the client ip (gethostip). After erasing needless things like memtest and suselogo and adding to modules (reiserfs.o and 3c59x.o) to the initrd, I still don't have enough space on the floppy for all data. So I reduced the kernel by creating a special installation kernel that lacks of ISDN, sound, v4l, IrDA etc. Now everything fits onto one floppy, but the autoinstall process hangs at the point where the root image is mounted from the NFS sever by the client. >From the log file on console <F3>: ---8<--- OK, going to mount 0.0.0.0:/home/install auto2_net_dev: 464 NFS mount ok. inst_check_instsys:780 ramdisk_ig = 0 setfont lat1-16.psfu (map none) Setting up localhost...done going fot automatic install mount: /var/adm/mount/suse/images/root: we need a loop device mount: using /dev/loop0 mount: /dev/loop0: No such device ---8<--- I've doublechecked that the network works, the installation sources are mounted and that the kernel has "loop device" enabled. If I try to mount manually on console <F9> with the command "mount /var/adm/mount/suse/images/root /mnt -o loop" I get the error message: "mount: invalid number of arguments" Any hints? Has anyone succeeded in building such a bootdisk? Kind regards, Andreas -- Andreas Rother - E-Plus Mobilfunk GmbH & Co. KG

1 0

Re: [suse-autoinstall] YAST2 - using netdevice=eth1
by Hella.Breitkopf＠varetis.de 24 May '02

24 May '02

Anas Nashif <nashif(a)suse.de> [22.05.2002 04:45]: >* Hella.Breitkopf(a)varetis.de <Hella.Breitkopf(a)varetis.de> [May 21. 2002 23:12]: >> Hi List, hi Anas, >> >> Anas Nashif's great documentation of his tool AutoYast2 mentions this: >> >> Putting this to the bootcd kernel commandline, I expected the use of >> network device "eth1" for network setup (with dhcp): >> >> linux netdevice=eth1 install=nfs://1.2.3.4/x/suse8.0 >> autoyast=nfs://1.2.3.5/y/auto.xml >> >> Unluckily the information of the "netdevice" keyword seems to be ignored: >> ----- >> Trying to activate eth0 >> Setting up localhost...done >> timed out waiting for a valid DHCP server response >> >> Sending DHCP request to eth0... no/incomplete answer >> Ok, that didn't work; see if we can activate another network device... >> No further network cards found; giving up. >> ----- > >Does linuxrc in this case actually loads both network devices periot to >sending the DHCP request... Previous to the run with eth0 there is an "empty" run. There is no try with eth1. Since on my machines both devices are using the same module, the loading of the correct module means both devices are available .. IIRC we've no "ifconfig -a" at that moment, but /proc/net/dev shows both interfaces. (But eth1 is not up). > >> If I do a "manual Installation", I *can* choose between two >> network devices. And fetching dhcp information and the following >> installation from "eth1" works. >> (An installation over "eth0" works, too - if there is a cable. >> But there are good reasons to use eth1 in this case. ) >> >> Other parameters (I tried e.g. ip,netmask,gateway) work as expected, so why >> netdevice doesn't? > >We are investigating.... >> >> Hella - my next boot cd should include that. >> (Somebody interested in a description, how to build a crude boot cd >> for network installation?) >> > >Building a boot CD will be part of the next release and would be >provided as a replacement for similar functionality available with >alice. Yes, that would quite nice and usefull. >Are you interested in a description or are you offering one...? If you >have one, that might help me while putting the docs for next release :-) I'm offering. I've to document the stuff I do, anyway. But it's a crude not very elegant solution. (So, yes, I'd be interested in a *better* description, too.) > >Regards, >Anas Regards, Hella

2 1

Autoinstall with PXE
by Jörgen Karlsson 23 May '02

23 May '02

Hi, We are currently using PXE to autoinstall (kickstart) our RedHat systems. Now we are switching to SUSE. I can't figure out what files to include in a boot image (initrd) to use for PXE boot/install. I have tried the kernel in suse/images/boot/linux and the image in suse/images/boot/initrd. Is this the correct ones? I always get the "Insert modules Disk 3" when running with autoyast=nfs://172.16.100.1/opt/suse set on kernel cmdline. Is this because yast2 cannot find the modules it need? Or does it always ask this question? How do I get past it? (our systems only has a serial console, no floppy, no cdrom). Maybe it should be enough to add all modules I need to /modules. Especially the ones from disk 3,4,5,6.... ? How does yast2 determine its ip address during installation? If it is not set in linuxrc.config or on kernel cmdline does it try dhcp by default? Can yast2 use the server ip in the dhcp response as ip for an nfs server installation? And use the boot filename in same response as path to autoinst.xml? It would be nice you didn't have to specify any ip specifics (or server paths) on either kernel cmdline and linuxrc.config. Yast should be able to pick up everything from the dhcp file. Or do I have to fix the PXE bootstrap loader to supply this information? /J Karlsson

2 1