June 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

AW: AW: [suse-autoinstall] Problem Creating Logical Partitions
by Götz Rieger 21 Jun '05

21 Jun '05

Bjoern, Uwe, thank you for your help. Removing the extended partition and declaring the primary partitions solves the problem. Regards, Goetz > -----Ursprüngliche Nachricht----- > Von: Uwe Gansert [mailto:ug@suse.de] > Gesendet: Dienstag, 21. Juni 2005 13:14 > An: suse-autoinstall(a)suse.com > Betreff: Re: AW: [suse-autoinstall] Problem Creating Logical > Partitions > > > On Tuesday 21 June 2005 13:04, Götz Rieger wrote: > > > Does AutoYaST realize automatically that he would need > > an extended partition to create 5 partitions? > > yes. Remove the extended partition from your profile and you > get what you > want. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany > e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, > Fax: +49-(0)911-74053-476, Web: http://www.suse.de > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0

AW: [suse-autoinstall] Problem Creating Logical Partitions
by Götz Rieger 21 Jun '05

21 Jun '05

Hi Bjoern, thanks for your answer. But if your file works this way, I have a real problem understanding how AutoYaST handles things... ;-) Your partitions all have mountpoints and partition_id=131, whereas in my opinion extended partitions should have 15 and no mountpoint. Does AutoYaST realize automatically that he would need an extended partition to create 5 partitions? I am a bit lost here... Any help? Regards, Goetz > -----Ursprüngliche Nachricht----- > Von: Bjoern Lotz [mailto:blotz@suse.de] > Gesendet: Dienstag, 21. Juni 2005 12:38 > An: suse-autoinstall(a)suse.com > Betreff: Re: [suse-autoinstall] Problem Creating Logical Partitions > > > Hello, > > The following works for me (SLES9), creating two primary > partitions, one > extended and logical partitions within the extended: > > <partitioning config:type="list"> > <drive> > <device>/dev/hda</device> > <initialize config:type="boolean">true</initialize> > <partitions config:type="list"> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">swap</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>swap</mount> > <partition_id config:type="integer">130</partition_id> > <partition_type>primary</partition_type> > <size>1g</size> > </partition> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>/</mount> > <partition_id config:type="integer">131</partition_id> > <partition_type>primary</partition_type> > <size>1.5G</size> > </partition> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>/usr</mount> > <partition_id config:type="integer">131</partition_id> > <size>3G</size> > </partition> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>/opt</mount> > <partition_id config:type="integer">131</partition_id> > <size>1G</size> > </partition> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>/var</mount> > <partition_id config:type="integer">131</partition_id> > <size>500M</size> > </partition> > </partitions> > <use>all</use> > </drive> > </partitioning> > > Main difference seems to be that there is no partition > number, but I don't > know too much about the syntax - could also be something > else, but at least > it works like this for me. > > Björn > > Am Dienstag, 21. Juni 2005 12:09 schrieb Götz Rieger: > > Hi, > > > > I would like AutoYaST to create three primary partitions > > and one extended partition with two logical partitions inside. > > > > The primary and extended partitions are created correctly, > > but the creation of the logical partitions fails because > > YaST tries to create them _behind_ the extended partition. > > > > If I specify the logical partition sizes with region_entry as > > sectors, everything works as expected. But this is not an > > option because I don´t want to be bound to specific disk > > geometries. So I can use <size> only... > > > > I have included the relevant part of my xml-file. > > > > Any tips? > > > > Regards, > > Goetz > > > > -------8><----------------------- > > <partitioning config:type="list"> > > <drive> > > <use>all</use> > > <device>/dev/sda</device> > > <partitions config:type="list"> > > <partition> > > <filesystem config:type="symbol" >ext3</filesystem> > > <mount>/</mount> > > <partition_id config:type="integer">131</partition_id> > > <partition_nr config:type="integer">1</partition_nr> > > <size>2048mb</size> > > </partition> > ... > > -- > Dr. Björn Lotz, Linux Curriculum Developer > Novell Worldwide Training Services > Novell GmbH, Frankfurter Ring 115a, 80807 München > Tel: 089/206002000 Fax: 089/206002100 > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

3 2

Problem Creating Logical Partitions
by Götz Rieger 21 Jun '05

21 Jun '05

Hi, I would like AutoYaST to create three primary partitions and one extended partition with two logical partitions inside. The primary and extended partitions are created correctly, but the creation of the logical partitions fails because YaST tries to create them _behind_ the extended partition. If I specify the logical partition sizes with region_entry as sectors, everything works as expected. But this is not an option because I don´t want to be bound to specific disk geometries. So I can use <size> only... I have included the relevant part of my xml-file. Any tips? Regards, Goetz -------8><----------------------- <partitioning config:type="list"> <drive> <use>all</use> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol" >ext3</filesystem> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>2048mb</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>1024mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>1gb</size> </partition> <partition> <partition_id config:type="integer">15</partition_id> <partition_nr config:type="integer">4</partition_nr> <size>max</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/var/log</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/var/spool</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>2gb</size> </partition> </partitions> </drive> </partitioning> ----------------><8------------------------

2 1

Re: [suse-autoinstall] SLES9 autoinstall error
by Mike Marion 21 Jun '05

21 Jun '05

On 20 Jun, Uwe Gansert wrote: > just a guess. Can it be that your linuxrc command line has more than 255 > characters? Then the last characters would be cut off. Maybe that's it? that was going to be my guess.. we ran into this ages ago. I had to move a few of the options (like the install= option) to the info file in the initrd to save space. I really with autoyast was smart enough to do something like step through the path the autoyast= path has and see if the install tree is there instead of having to name both seperately... since we keep the autoyast bits underneath the install tree. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Talking about web page "design"] "I think my standards have lowered enough that now I think ``good design'' is when the page doesn't irritate the living fuck out of me." ==>jwz (http://www.jwz.org/gruntle/design.html)

2 1

Re: [suse-autoinstall] SLES9 autoinstall error
by Mike Marion 21 Jun '05

21 Jun '05

On 20 Jun, Ajay Mulwani wrote: > No, the entire command that I give at the PXE "boot:" prompt is: > boot: *SLES9 autoyast=nfs://abc/home/static.xml* > ** > Do I have to include all the characters which are there with the "append" > statement of "SLES9" label in the PXE "default" file? yes, all of that stuff gets cat'd together on the line.. and there will also be something added like: BOOT_IMAGE=linux (or whatever the kernel name is).. and it all adds up pretty fast. for a quick test.. just echo the whole line after append, and your added bits above and pipe to wc.. if it's anywhere near, or especially over 200.. then that's probably it. I'd recommend moving at least install to the info file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Talking about web page "design"] "I think my standards have lowered enough that now I think ``good design'' is when the page doesn't irritate the living fuck out of me." ==>jwz (http://www.jwz.org/gruntle/design.html)

2 1

Dynamic changes in autoYast control file (Not through rules)
by Alexander Dubinin 20 Jun '05

20 Jun '05

Hi all, Does anybody know, which variables I can use in AutoYast control file, reflecting system configuration? Or can I use any at all? Is it possible to use XML XInclude for AutoYast in SLES9? Idea is to generate swap partition size automatically, using script. Does I have possibility to start some script _before_ autoyast config file is processed? Preferable is a way, similar to used in RedHat KickStart - run pre-configuration script, generate partition layout and pass this layout to AutoYast like "include" in KickStart. Really, I prefer to do this in "pre" scripts - which have network configured and have set of basic tools, like wget (To download needed binaries from WEB, for example) -- Regards, Alexander Dubinin

1 0

SLES9 autoinstall error
by Ajay Mulwani 20 Jun '05

20 Jun '05

Hello, I am using the network installation method to install SLES9 and providing an nfs path to the autoinst.xml file. Now the two issues that I am facing with all/ any of my installations are: 1. The system displays the following error: "Your computer does not fulfill all requirements for a graphical installation.There is less than 96MB memory or the X server could not be started. As a fallback, the text found-end of YaST will guide you through the installation. This front-end offers the same functionality as the graphical one, but the screens differ from those in the manual." ... and the entire installation is in text mode. 2. After displaying the message in (1) above; when autoyast tries to read the control (autoinst.xml) file; it truncates the path to that file then asks for the same path again which was correctly defined at the PXE "boot:" prompt. Once the path to autoinst.xml is entered again the entire installation goes fine unattended in text mode and the system comes up with graphics/ video correctly configured. Any suggestions to resolve these issues will be highly appreciated. Thank you, Ajay

3 5

Re: [suse-autoinstall] initrd module load order not following info file
by Michael Steinmann 16 Jun '05

16 Jun '05

Jiri Srain wrote: > Hi Mike! > > Dne pondělí 30 květen 2005 10:26 jste napsal(a): > >>Jiri Srain wrote: >> >>>Dne pondělí 30 květen 2005 09:59 jste napsal(a): > > >>>>SLES10 seems a bit too far on the horizon. This is the first system >>>>we're trying to install using autoyast with SLES9. >>> >>>It is not issue of autoinstallatino only - plain installatino is affected >>>as well. >> >>but there at least you have the option of checking the initrd before you >>boot. I tried with adding "boot confirm true" (can't remember the exact >>syntax) in autoinst.xml but that option didn't seem to have any effect >>as the machine booted automatically right after installation finished. > > > Don't know, pass the question to the list. > > >>I would be happy if I had the chance to alter the MKINITRD and create a >>correct initrd _before_ the initial reboot, as we're not really looking >>for fully-automated setups. >>Any idea on why this might not work? > > > No, no idea. I didn't know about this option before. That's (or rather was) the option in autoinst.xml: <install> <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">false</forceboot> </mode> According to autoyast documentation here http://www.suse.de/~nashif/autoinstall/9.1/autoyast.pdf it has been dropped for SuSE9.1/SLES9. >>>It is not possible to add all modules which are in info file to initrd - >>>because it would put there a lot of modules which are not needed. >>> >>> >>>>Where does the MKINITRD variable get set? Which file would I have to >>>>look into to tweak it myself? >>> >>>/usr/share/YaST2/modules/Initrd.ycp, after modifying it needs to be >>>recompiled by 'ycpc -c Initrd.ycp'. >> >>thanks for the pointer. I'll look into it tomorrow when I'm on site. > > > If you just want to update sysconfig and recreated initrd before the reboot, > the probably easiest would be to add to /usr/share/YaST2/clients/inst_finish > just after bootloader is installed eg. > > Popup::Message (_("Update the inirdd now")); > > This will show you message after bootloader is saved and you can switch to the > console to change anything you want to. > > Just remember that you have to change the file in the installation system > (which is stored on CD1 in /boot/root). It is cramfs image. that sounds like a good workaround, thanks.

3 2

gfxboot bootlogo
by Stefan K 13 Jun '05

13 Jun '05

Hello auto-installer, i want to change the bootlogo file on a SuSE 8.2 CD (the CD boot with isolinux) . Does anybody knows how i must convert my pcx file ..?? commands and examples are welcome ;o) thanks a lot ... Stefan __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201

3 2

autoinst.xml placed on USB-Memorystick or USB-Floppy
by Link, Johannes 13 Jun '05

13 Jun '05

Hi, we used to place our autoinst.xml files on floppy disks to autoinstall our servers. Our installation media is a customized SLES8/SLES9 CD-set. But since newer hardware (like FSC Primergy TX600S2) does not ship with an integrated floppy drive anymore, we have a little problem. Is it possible to put the autoinst.xml file on a USB-Memorystick or a USB-Floppy? How does YaST deal with integrated SCSI devices? I guess we'll get a problem when we use a commandline option like "autoyast=device://sdb/autoinst.xml" since we usually don't know how many SCSI drives are already installed. Any help would be highly appreciated. Mit freundlichem Gruß / kind regards Johannes Link Siemens Business Services SBS ORS GD AHS CC 11 Würzburger Str. 121 90766 Fürth Deutschland Fon: +49 911 978-3728 Fax: +49 911 978-4080 eFax: +49 911 978-10 3728 Email: johannes.link(a)siemens.com

1 0