openSUSE Autoinstall August 2005

autoinstall@lists.opensuse.org

38 participants
60 discussions

YOU wants to install patches that are already installed by multiple source autoinstall
by Teun 07 Sep '05

07 Sep '05

Hello, After a lot of trouble setting up an installation server, serving both a SuSE 9. 3 Pro source and an update source, i finally was able to autoinstall a machine which installed all packages and updates in one go. (So it installs the updated packages straight away and not first the older version.) However, when i then run YaST Online Update on the machine it still wants to install all the updates that are already on the system. It even reports that the installed version of a particular package is the exact same package as the one it wants to install. I already found that if i move a file from /var/lib/YaST2/you/mnt/i386/update/9. 3/patches to /var/lib/YaST2/you/installed the problem is solved for that particular package. But the first directory also contains files for packages that are not installed at all, so just copying all of them would not work. I really hope there is a clean solution to fix this? Any help would be highly appreciated. Regards, Teun

1 1

Re: Intel SE7210TP1+ AutoYast installation problem
by Renato Sartori 31 Aug '05

31 Aug '05

Hi!, I fixed the problem :) Yours autoyast must have a boot kernel from Suse 9.3 ..... easy ;) I was using 9.2 version, causing problem with disk controller. []´s RSartori ----- Original Message ----- From: "Renato Sartori" <renatosartori(a)uol.com.br> To: <suse-autoinstall(a)suse.com> Sent: Tuesday, August 23, 2005 6:02 PM Subject: Intel SE7210TP1+ AutoYast installation problem > Hi Friends, > > I have a Intel SE7210 + P4 3.0 HT 1M cache + Sata Raid Array Adaptec 2810SA > w/ 6 discs Seagate Barracuda Sata 300GB that install ok with Suse 9.3 using > CDROM. > But .. whein I try to install with AutoYast by network, I had a message like > this: "Error while configuring partitions. Try again" > > ps. AutoYast works fine whit another kinds of configuration ( Intel PERLX, > Compaq DL380G3/G4, Abit IS7 etc etc) > ps2. I alread try to take off the adaptec, setting up on onbard controller > but i got the same error. > ps3. I changed the disc to a 80gb, without success. > > Someone knows whys it happens ??? > > Thaks in advance > RSartori > >

1 0

Networking
by Bill Cavalieri 31 Aug '05

31 Aug '05

Does anyone have or point me towards some examples have handling networking setup? What I would like to do is in my autoyast xml say, eth0 will be 192.168.3.254, and eth1 will be dhcp. Then during install let it detect what nic module is needed. So far I have only been able to get it to work when I specify the module. Thanks, -Bill

1 0

Re: [suse-autoinstall] Yast not starting upon VNC reconnect after reboot.
by Teun 31 Aug '05

31 Aug '05

Okay, so this only happens when you select 'minimal' during the VNC based installation process. Not very smooth if you ask me.... Teun Quoting Teun <suse(a)teund.dds.nl>: > Hello, > > I am trying to do a remote install using VNC, installing SuSE 9.3 > Professional. > This all goes fine until Yast wants to do the first reboot. The machine > reboots and after coming back up the console tells me to reconnect my VNC > viewer and finish the installation. > > However, if i reconnect my viewer i just get an empty screen. It seems to be > a > gray pattern empty X screen with a mouse pointer. But Yast is not coming back > to finish the install. > > Is this a known issue? Or is there anything i should check? > > Regards, > Teun > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > >

1 0

SLES 9 SP2 frustrations with x86_64
by Michael T. Halligan 31 Aug '05

31 Aug '05

So, I'm attempting to work with Novell's support, but that's turning into a slower process than I thought it would be. Here's my setup. I've got a dozen Dell SC1425 with dual drives, which I want to do software RAID on. I do not have these boxes setup for "hardware raid" which is the first caveat on them. My process was thus : 1. Use Yast2 to create an installation source (x86_64) 2. Use Yast2 to patch the installation source with SP2 3. build a server manually 4. Use Yast to create a reference file 5. Try to install . This always fails. I get one or two errors, either Error An error occurred whiel trying to create the partitioning plans. Make sure the control file has the correct syntax and values. Or An error occurred during partitioning. Now, beyond being all fancy, I've tried using : - The control file included on the SP1 cd - The control file from the yast2-autoinstall file I've tried doing these both with, and without any partitoning. I always get these errors. At one point, I believe I did actually get an autoinstall to work with no partitioning, but it's been so long I forget. This is really frustrating. When I create an reference file from a machine, then try to validate it, that should not fail, I don't even have the remote ability to break it. I am starting to believe that yast2's method of creating an installation is terribly broken. Here's what I end up with : drwxr-xr-x 7 root root 168 Aug 30 18:35 SUSE-CORE-Version-9 drwxr-xr-x 5 root root 120 Aug 30 18:47 SUSE-SLES-9-Service-Pack-Version-2 drwxr-xr-x 3 root root 72 Aug 30 18:30 SUSE-SLES-Version-9 lrwxrwxrwx 1 root root 28 Aug 30 18:31 boot -> SUSE-SLES-Version-9/CD1/boot lrwxrwxrwx 1 root root 31 Aug 30 18:31 content -> SUSE-SLES-Version-9/CD1/content -r--r--r-- 1 root root 17621 Aug 31 00:27 control.xml lrwxrwxrwx 1 root root 51 Aug 30 18:38 driverupdate -> SUSE-SLES-9-Service-Pack-Version-2/CD1/driverupdate lrwxrwxrwx 1 root root 44 Aug 30 18:38 linux -> SUSE-SLES-9-Service-Pack-Version-2/CD1/linux lrwxrwxrwx 1 root root 31 Aug 30 18:31 media.1 -> SUSE-SLES-Version-9/CD1/media.1 drwxr-xr-x 2 root root 104 Aug 30 18:36 yast I have tried : - Booting from the initrd & kernel which comes with SLES9 - Booting from the initrd & kernel which comes with SP2 - Copying the initrd and kernel from SP2/CD1/boot into SUSE-SLES-Version-9/CD1/boot (overwriting the default) - A hundred different variations of all this. Does anybody have any good ideas before I give up?

2 6

Re: [suse-autoinstall] SLES 9 SP2 frustrations with x86_64
by Hans-Joachim Ehlers 31 Aug '05

31 Aug '05

Hi Michael > Does anybody have any good ideas before I give up? Sure, do not give up . The first step is to verify that your installation source is in a correct state. I assume that you have read the documentation to build a SUSE-SLES-9 including SP2 So just boot your machine with a boot/installation cd and use for installation your installation server. If this works i would think that the installation server is fine. If not do your homework and RTFM. The next step is to use a simple autoinstallation file ( We assume /export/sles9/autoinstall.xml as filename ) Create this file with " yast2 autoyast " which should contain the bootloader, minimum installation ( save time for testing ) , ip . and save is as /export/sles9/autoinstall.xml Validate this file with "xmllint" Now boot from CD and supply the nessesary parameter for automatic installation If you still have a floppy drive to might use a file named "info" on a floppy. Otherwise to have to supply at least server=, serverdir=, hostip=, and autoyast= on the command line or use dhcp #Example #See file "README.linuxrc" for details textmode: 1 language: en_US instmode: nfs netdevice: eth0 ip: 10.1.0.1 netmask: 255.255.0.0 broadcast: 10.1.255.255 gateway: 10.1.0.1 server: 10.1.0.225 serverdir: /export/sles9 autoyast: /export/sles9/autoinstall.xml Now you should be able to start debugging the installation process. As mentioned before maybe the autodection for the new sata disk does not work ? hth Hajo >>> "Michael T. Halligan" <michael(a)halligan.org> 08/31/05 10:14 am >>> So, I'm attempting to work with Novell's support, but that's turning into a slower process than I thought it would be. Here's my setup. I've got a dozen Dell SC1425 with dual drives, which I want to do software RAID on. I do not have these boxes setup for "hardware raid" which is the first caveat on them. My process was thus : 1. Use Yast2 to create an installation source (x86_64) 2. Use Yast2 to patch the installation source with SP2 3. build a server manually 4. Use Yast to create a reference file 5. Try to install . This always fails. I get one or two errors, either Error An error occurred whiel trying to create the partitioning plans. Make sure the control file has the correct syntax and values. Or An error occurred during partitioning. Now, beyond being all fancy, I've tried using : - The control file included on the SP1 cd - The control file from the yast2-autoinstall file I've tried doing these both with, and without any partitoning. I always get these errors. At one point, I believe I did actually get an autoinstall to work with no partitioning, but it's been so long I forget. This is really frustrating. When I create an reference file from a machine, then try to validate it, that should not fail, I don't even have the remote ability to break it. I am starting to believe that yast2's method of creating an installation is terribly broken. Here's what I end up with : drwxr-xr-x 7 root root 168 Aug 30 18:35 SUSE-CORE-Version-9 drwxr-xr-x 5 root root 120 Aug 30 18:47 SUSE-SLES-9-Service-Pack-Version-2 drwxr-xr-x 3 root root 72 Aug 30 18:30 SUSE-SLES-Version-9 lrwxrwxrwx 1 root root 28 Aug 30 18:31 boot -> SUSE-SLES-Version-9/CD1/boot lrwxrwxrwx 1 root root 31 Aug 30 18:31 content -> SUSE-SLES-Version-9/CD1/content -r--r--r-- 1 root root 17621 Aug 31 00:27 control.xml lrwxrwxrwx 1 root root 51 Aug 30 18:38 driverupdate -> SUSE-SLES-9-Service-Pack-Version-2/CD1/driverupdate lrwxrwxrwx 1 root root 44 Aug 30 18:38 linux -> SUSE-SLES-9-Service-Pack-Version-2/CD1/linux lrwxrwxrwx 1 root root 31 Aug 30 18:31 media.1 -> SUSE-SLES-Version-9/CD1/media.1 drwxr-xr-x 2 root root 104 Aug 30 18:36 yast I have tried : - Booting from the initrd & kernel which comes with SLES9 - Booting from the initrd & kernel which comes with SP2 - Copying the initrd and kernel from SP2/CD1/boot into SUSE-SLES-Version-9/CD1/boot (overwriting the default) - A hundred different variations of all this. Does anybody have any good ideas before I give up? -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Re: [suse-autoinstall] autoyast fails on partitioning on Dell Precision 670
by GrueMaster 31 Aug '05

31 Aug '05

Thanks for the rules help. I've been studying the online documentation and was very confused about the directory structure needed for the rules.xml. Your rules.xml example worked flawlessly. I'd recommend adding your example as it is written to the documentation. I've now progressed to getting the system imaged and booting (Whoo Hoo!) Now to get my post install script running again (I yanked it to simplify debugging the partitioning issues). Next question, is there a setting to allow installing without the "Licensing" prompt, or does the timeout automaticly assume acceptance? Tobin Hans-Joachim Ehlers <HansJoachim.Ehlers(a)eumetsat.int> wrote: My partitioning section is directly AFTER . I have been told that the order shall not matter but who knows. So give it a try. If the order change will help then there is no need for a rules.xml At least at my site i have no problems with SATA and IDE drive. About SCSI i can not tell. If you need a rules.xml 1) Get the documentation about autoyast ( Mentioned in a previous post to this list by me ) 2) Below your autoinstallation source directory ( Example: MyServer:/export/suse/autoinstall/ ) create the following subdirectories: ./rules ( Will hold only the rules.xml ) ./classes ( Will hold the autoinstall.xml and sda.xml and hda.xml ) A few importent hints: A) The autoyast entry MUST end with an "/" . Example: autoyast=nfs://MyServer:/export/suse/autoinstall/ otherwise the rules.cml will NOT be parsed. B) The rules.xml MUST include a rule to include your standard "installation.xml" because it will be parsed only what has a MATCH in the rules.xml C) You must use " echo -n" in your script section to get rid of the NEWLINE. Otherwise the match will not work. The following is an example of a "rules.xml" to determine the disk type xmlns:config="http://www.suse.com/1.0/configns"> if grep hda /proc/partitions > /dev/null; then echo -n "hda" else echo -n "sda" fi; ]]> * exact classes/@custom1@.xml true * exact classes/autoinst.xml false ---------------------------------------------------------- The first rule will parse your ( sda.xml or hda.xml ) and continue to the next rule The second rule will match everything so it does include the classes/autoinst.xml File. Now further rules will be parsed afterwards. The sda.xml is just a stript down version from your autoinst.xml containing a Section like down below ( NOT tested ) . For the hda.xml you must just change the device section. To get these Section i would use "yast2 autoyast " and create a new xml file where only the paritioning section has been configured with yast2. Afterwards take everthing out of the file what is not related to the partitioning . Run "xmllint" to verify the file and you should be happy. xmlns:config="http://www.suse.com/1.0/configns"> /dev/sda all hth Hajo >>> GrueMaster 08/26/05 5:49 pm >>> I fixed the boot loader section, but that isn't where the problem is. Yast fails at "Create partition plans". Hey, I think I figured it out (somewhat). I added /dev/sda to the partitioning section and it now blows past that and installs. Now I need to figure out how to use rules, as we have IDE, SCSI, and SATA systems. SATA and SCSI will work with this config, but IDE needs /dev/hda. Any suggestions? --------------------------------- Start your day with Yahoo! - make it your home page

2 1

Software RAID examples
by Egan Ford 29 Aug '05

29 Aug '05

Can any point me to an XML autoyast file with an example of software RAID 0 or 1 with two disks. The disks must boot. Thanks.

2 2

Re: [suse-autoinstall] SLES SP2 AutoYast problems.
by Hans-Joachim Ehlers 29 Aug '05

29 Aug '05

Hi Michael, sometime things are not the way they should be. Its took me about one week to get an auto install for a simple network installation and this list to solve some major understanding problems. >From what i am right now know it should take only a hour to understand the whole process. But that's another story. So back to your problem. Like i said before: Create a simple xml file for installation. Do not use a reference. For testing there is just no need. Since you are at a remote location you might consider using the "vnc" option for installation. I never tested it. But from my understanding a VNC server will be started so you can remotely connect. ( i think it is used for headless system. ) See http://www.novell.com/coolsolutions/feature/15568.html for details Also please do not complain about autoyast: Its a nice tool which will sometimes gives you a lession in " zen and the are of patience" . So please post your info file and your command line options and try vnc to find out whats going on your client. A good book ( pdf) is: Autoyast Automatic Linux Installation and Configuration with Yast2 by Anas Nashif, Suse Linux AG hth Hajo who is now facing of MAINTAINING a suse system. >>> "Michael T. Halligan" <michael(a)halligan.org> 08/26/05 3:34 pm >>> Is there any way to redirect all of these logs to a loghost, if there's more that isn't being seen when I boot with loghost=IP.ADDR. It's pretty complicated for me to get to my datacenter right now, and remote serial console on these dells do not work (of course dell, in theirvery helpful way, has told me there will be new firmwares in a month). What I really don't get, is why should there be ANY problem with installing a server from a reference profile? Shouldn't that install also have failed then? It seems that autoyast is just writing ugly xml and then not being able to read it back in? >From my experience: >Keep thinks simple in the beginning > > >1 ) So no software raid and what so ever. > - Simple Partition schema > - Do not name the disk for installation ( SATA will be detected as >/dev/sd[a-z]X devices >2 ) use text mode for Installation ( Graphical Installations fails for >me ) >3 ) Have a large defined swap partition because if you use http for >installation autoyast will copy pretty much of the installation to its >local ram disk ( memory ) >You can use "top" on a different terminal >4) Take a look at the /var/log/Yast log files ( The ones on the ram >disk ) >5) Switch to terminal 4 ( from memory ) to see what has been loaded and >what has happend. > > >hth >Hajo > > > > >>>>"Michael T. Halligan" <michael(a)halligan.org> 08/26/05 3:02 pm >>> >>>> >>>> >So I've been struggling for a couple of days trying to get AutoYast to > >work. I can install on these servers manually.. However, if I create a > >reference profile, or creaet my own profile, >or really do anything with autoyast, every time I try to install, the >server gets as far as loading the device driver disks, then stops with >a >big red box reading "An error occurred during installation" >That's it. > > >I built an installation source using SLES 9S SP2 x86_64. I am trying >to >boot with y2debug and setting a loghost, but the messages i'm getting >aren't exactly helpful. >The servers I'm installing on are del sc1425s with single 3ghz procs >and >dual sata drives. I'm attempting to setup sles9-sp2 with software >raid1. >Any help would be >appreciated. > > >The last few lines I'll see in syslog are: >ug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] >NCurses.cc(Refresh):407 >start refresh ... >Aug 25 22:10:39 BOB yast2[3642]: <1> [ncurses] NCurses.cc(SetTitle):459 > >Draw title called >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] >NCurses.cc(Refresh):411 done refresh ... >Aug 25 22:10:39 BOB yast2[3606]: <1> [wfm] >Y2WFMComponent.cc(SetLanguage):403 SET encoding to: UTF-8 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Accept" >-> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Add" -> F3 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Back" -> F8 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Cancel" >-> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Do Not Accept" >-> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Don't install" >-> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Finish" >-> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Help" -> F1 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Install" >-> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Next" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "No" -> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "OK" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Quit" -> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Save" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Yes" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Close" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Continue" >-> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Delete" >-> F5 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Edit" -> F4 >Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:243 >before >.probe.floppy >Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:245 after > >.probe.floppy >Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:267 >FloppyDrives [] >Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] >YNCursesUI.cc(YNCursesUI):114 Stop YNCursesUI >Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] >NCurses.cc(NCurses):160 Shutdown NCurses... >Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] >NCurses.cc(NCurses):169 NCurses down >Aug 25 22:10:39 BOB yast2[3606]: <1> [liby2] >genericfrontend.cc(main):437 Finished YaST2 component >'y2base' > > > > -- Michael T. Halligan Chief Technology Officer ------------------- BitPusher, LLC http://www.bitpusher.com/ 1.888.9PUSHER 415.724.7998 (Mobile) 415.520.0876 (Fax) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Yast not starting upon VNC reconnect after reboot.
by Teun 27 Aug '05

27 Aug '05

Hello, I am trying to do a remote install using VNC, installing SuSE 9.3 Professional. This all goes fine until Yast wants to do the first reboot. The machine reboots and after coming back up the console tells me to reconnect my VNC viewer and finish the installation. However, if i reconnect my viewer i just get an empty screen. It seems to be a gray pattern empty X screen with a mouse pointer. But Yast is not coming back to finish the install. Is this a known issue? Or is there anything i should check? Regards, Teun

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall August 2005