June 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Driver Disk
by Martin Möser 20 Jul '04

20 Jul '04

Hi all, does anyone know how to make a Driver Disk accessible for autoyast CD-installation? Is there a possibility to put it on the CD in order to not have an extra floppy? Thanks, Martin

2 3

Working autoyast file ?
by Wayne Pascoe 02 Jul '04

02 Jul '04

Hi all, Can anyone provide me with a working autoyast file to start from, as well as any additional information about loading drivers, etc. ? I've done a setup of a SLES9 RC1 machine and then generated a reference profile from that machine - this doesn't work however... The boot process happens and the installation starts. I then get a screen that looks roughly as follows: Left Pane: Please wait while the system is prepared for autoinstallation Right Window: [x] Probe Hardware => Retrieve read control file - ... - ... The bar at the bottom of this screen stops at 28% and it goes nowhere. This is the very same machine that I used to create the reference profile, so I'm confused as to why it's not working :( Regards, -- Wayne Pascoe

1 2

Autoinstall from HDisk
by Werner Hack 01 Jul '04

01 Jul '04

Hi, I try to install a PC from local HDisk using a selfmade BootCD. These are my parameters for autoyast : autoyast=device://hda9/install/autoyast/profiles/pc.xml serverdir=/install/autoyast/SuSE/ partition=hda9 I copied the SuSE DVD Distribution to 'serverdir'. Booting from CD is working fine, the autoyast-file is read. But then I get an error message : > Could not set base selection: default > Error while configuring software selections Any idea why this happens ? Thanks in advance. Regards, Werner Hack --

2 2

FastTrack Driver ft.o for autoinstallation (SLES8) on Blade Server
by Martin Möser 30 Jun '04

30 Jun '04

Hello, we use autoyast with Custom-CD for installing control-servers. Now, we have to use a diskless BladeServer as control-server. Thus, we need the module ft.o (FastTrack Driver) in order to let the Blade determine the Harddisk (sda) to be used. Is there any possibility to tell autoyast to load this driver before detecting the harddisk? The only opportunity we see is giving kernel parameters at boot-loader-time, but where do we have to place the driver then? Is it possible to make it accessible from CD or do we have to provide a floppydisk? We'd like to have it fully automatic! Thanks, Martin

1 0

exit code 127
by Thorsten Alge 30 Jun '04

30 Jun '04

Hi, i´ve set up an AutoYaST Installation Server. I want to install my clients via PXE-BOOT. When the client is booting, everything works fine but when yast ist starting, i got en error. In the log it says: starting /mounts/instsys/sbin/inst_setup yast install program exit code is 127 sync... ok i can´t find out what the hell means "exit code 127", becouse it seems that everything is well configured and works fine. thanks... thorsten

1 0

PXE/TFTP 9.1 Autoinstall on AMD64
by Charles Smith 28 Jun '04

28 Jun '04

Hello, I currently have SuSE 9.1 Pro PXE/TFTP booting/autoinstalling working great with our 32-bit machines. My problem is that I can't seem to get this to also work with our x86_64 machines. I don't know if there is a graceful way to separate 32 and 64-bit stuff in the /tftpboot directory, so what I initially tried to do was make an isolinux.cfg menu option which specified an alternate (64-bit) linux and initrd, but when it loads the 64-bit kernel and initrd, the machine immediately reboots. I tried to boot it off the 32-bit kernel/initrd just to do the install, but as soon as it loads the data into ramdisk, it goes to a blue yast screen with the message "An error occurred during installation!" (very helpful) Switching to other consoles at this point reveals only a little more info, such as the messages: lockd:failed to open /var/lib/nfs/state: err=2 request_module: runaway loop modprobe binfmt-464x (5 of these) Lastly, I backed up the /tftpboot directory and blew it away, making a brand new one with only stuff from the 64-bit distribution in there, and it behaved exactly like it did when I tried specifying the alternate linux and initrd (rebooted). Now this situation suggests that setting up 64bit network booting the same way as with the 32-bit stuff doesn't work with my 64-bit systems, and that there is something special I need to be doing for them. Is there some documentation specific to 64-bit network booting / autoinstalling? Does it in fact differ from the 32-bit procedure (aside from having an x86_64 kernel/initrd/distro/control-files)? I know Anas is still working on the 9.1 docs, but has anyone successfully PXE/DHCP/TFTP/autoinstalled an AMD64 machine? Perhaps it is just a compatibility problem with my hardware? The 64bit systems I'm installing are AMD Opteron 146's on Asus SK8N motherboards (nForce chipset). I've tried floppy booting, but it doesn't talk to the NIC correctly (not sure my problem would be avoided anyway). Otherwise I may go ask the suse-amd64 list as well. Thanks in advance, -Charles Smith

1 0

how to get aborted autoinstall log
by Carl Pecinovsky 28 Jun '04

28 Jun '04

This is probably a newbie question, but the scenario is that I'm trying to install a ppc LPAR partition on iSeries with SLES9 (rc2). I pass the install kernel parms for autoyast, install, and networking. The install proceeds to read the autoyast control file, do some more setup which flies by, and then pops the text installer out to the root "Main menu". No error condition was given -- it just popped out and the same thing happens if I repeat the process by choosing option 4 to start system installation. How do I look at the install log at this point? I don't know how to exit the main menu and get to the ramdisk, etc. Thanks. Carl Pecinovsky Dept X8X: eServer Middleware Enablement, 015-3/H106 "It is never safe to look into the future with eyes of fear." --E.H Harriman

3 5

sles8 on AMD 64?
by Stephen Mah 28 Jun '04

28 Jun '04

Does Autoyast work on Suse 8 64bit? I have a colleage that said it didn't work too well. here is his email: Unfortunately Autoyast appears has not yet been ported for SuSE 8 64. When you run /sbin/yast2 autoyast or /sbin/yast2 austyast2 the product fails to start. I tried downloading the autoyast2 and alice updates and have had no luck with them. Due to time constraints, my time would be better spent building the systems by hand than trying to create a automatic build process. -- cheers steve

2 1

max size with LVM volumes?
by David Corlette 28 Jun '04

28 Jun '04

Hello there, I'm trying to set up a disk as follows: /dev/hda1: / 2GB /dev/hda2: swap auto size /dev/hda3: lvm "system" max (rest of disk) /dev/sys/var_lv: /var 200MB /dev/sys/home_lv: /home max (rest of LVM space) I would think this would be a pretty common arrangement (e.g. to have LVM fill a disk, and then a volume within that fill the LVM space), but for some reason the "/home" partition always ends up being of "unknown" size. Is there any way to get this to work, or am I hosed? Thanks! Here's the relevant section of my control file: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <use>all</use> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <mount>/</mount> <size>2GB</size> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> </partition> <partition> <mount>swap</mount> <size>auto</size> <format config:type="boolean">false</format> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> </partition> <partition> <lvm_group>system</lvm_group> <size>max</size> <partition_type>primary</partition_type> </partition> </partitions> </drive> <drive> <use>all</use> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>var_lv</lv_name> <mount>/var</mount> <size>200mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>home_lv</lv_name> <mount>/home</mount> <size>max</size> </partition> </partitions> <pesize>4M</pesize> </drive> </partitioning> Dave C --------------------------------------------------------- David Corlette mailto:corlette@huarp.harvard.edu (617)495-5922 http://www.arp.harvard.edu

2 1

Confused about clone / reference profile on SLES9 RC1
by Wayne Pascoe 28 Jun '04

28 Jun '04

Hi all, I'm trying to create an autoyast configuration with SLES9 RC1. I've done some searching and found that the clone function is now refered to as creating a reference profile. I've done this, but I'm a bit concerned by the outcome. I selected Partitioning, Boot Loader and Software under basic resources, but none of this appears to have taken. The machine I am doing this on has a minimal install. Yet when I check Package selection after creating my reference profile it is set to default, not minimal. Under partitioning, all I see is Drives Total of 1 drive * No specific device configured I'm also not seeing any configuration information under Network devices either. Ideally, I'm just trying to get to the point where I can do an auto-deploy, then I'll fiddle with the control file to do things like LVM, etc. Can anyone advise me on the best way to do this please? I'm currently trialing SLES against Red Hat Enterprise Linux AS 3, and the one thing that RHAS has going for it is that when you install a machine, a kickstart file is created in the /root directory as part of the install. So to create a profile for each machine, all you have to do is install one machine manually, and it's all there for you. Are there any plans for this in SLES ? Regards, -- Wayne Pascoe

2 1