March 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Manual Parititioning with autoyast .
by Yogesh Bhanu 04 Mar '05

04 Mar '05

Hi , I have just started using autoyast and have met with some success . We have plethora of systems with different disks types and sizes . Is it possible that while running autoyast I can choose my partitioning schema. I mean while running my autoconf.xml I can choose which disks I want to use and with which partition . Thanks in advance yogesh

1 0

CDROM Based Load With Network Access Confirmation
by Francois, Jean (J.L.) 04 Mar '05

04 Mar '05

I have an interesting problem I am trying to solve. Due to the nature of where I am doing the install, I have dialup speeds and can't do effective network installs so I have to do a SLES8 and SLES9 Load from CDROM with the control file in the floppy drive. I want to be able to make sure the server that is doing the install has its IP address in the ACL at a tracking web server that would normally get used for AutoYaST installs. Is there a way to trigger an AutoYaST install that : 1. does a complete install from the CDROM 2. reads the autoinst.xml control file from the floppy drive 3. grabs some content from a web server and does not get a 404 without having to write a <PRE> script or modify the install root image on the CDROM image? If I do end up using lwp or wget, is there a smart way to integrate this so it can interrupt the install process if a file cannot be retrieved from a web server? -- Jean L. Francois Sends... - Enterprise Platform Engineering & Certification ( LINUX ) - Linux Counter Registered User #8863 1994-12-13 06:39:24 http://www.novell.com/linux/truth/ - Torquemada Linux - For the Inquisitive...

2 1

RE: [suse-autoinstall] autoyast2 and LVM creation
by Marlier, Ian 03 Mar '05

03 Mar '05

And now I'll answer my own question, because I figured it out about 10 seconds after sending this e-mail. The problem was this parameter: <size>max</size> Which I used when defining the size of the Logical Volume. Unfortunately, this isn't a supported behavior. You have to specify a size in the standard <size>XXXgb</size> format. Which makes sense, but it would be nice to be able to do a <size>max</size> (if anyone out there who's reading this happens to feel like making that happen :-) - Ian -----Original Message----- From: Marlier, Ian [mailto:ian.marlier@studentuniverse.com] Sent: Thursday, March 03, 2005 1:37 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] autoyast2 and LVM creation I found a message about this exact problem from way back (7 April 2004 -- http://lists.suse.com/archive/suse-autoinstall/2004-Apr/0026.html), but there wasn't an answer to it. I'm hoping that there might be one now... When running an autoinstall using a control file that has an LVM group configured in it, I consistently get an error that the Logical Volume needs more space during the software selection configuration section. =20 After that message times out, the setup process continues, then halts with an error when it tries to create the Logical Volume. The error in that case is "lvm create_lv invalid parameter". Once the second error comes up, I can manually create the Logical Volume with the standard `lvcreate -n space vg_name` command. I'm using autoyast2, and installing SuSE pro 9.2. The relevant section of the configuration file is this: <drive> <device>/dev/sdc</device> <partitions config:type=3D"list"> <partition> <lvm_group>suvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/suvg</device> <is_lvm_vg config:type=3D"boolean">true</is_lvm_vg> <partitions config:type=3D"list"> <partition> <filesystem config:type=3D"symbol">jfs</filesystem> <lv_name>space_lv</lv_name> <mount>/space</mount> <size>max</size> </partition> </partitions> <use>all</use> </drive> -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

autoyast2 and LVM creation
by Marlier, Ian 03 Mar '05

03 Mar '05

I found a message about this exact problem from way back (7 April 2004 -- http://lists.suse.com/archive/suse-autoinstall/2004-Apr/0026.html), but there wasn't an answer to it. I'm hoping that there might be one now... When running an autoinstall using a control file that has an LVM group configured in it, I consistently get an error that the Logical Volume needs more space during the software selection configuration section. =20 After that message times out, the setup process continues, then halts with an error when it tries to create the Logical Volume. The error in that case is "lvm create_lv invalid parameter". Once the second error comes up, I can manually create the Logical Volume with the standard `lvcreate -n space vg_name` command. I'm using autoyast2, and installing SuSE pro 9.2. The relevant section of the configuration file is this: <drive> <device>/dev/sdc</device> <partitions config:type=3D"list"> <partition> <lvm_group>suvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/suvg</device> <is_lvm_vg config:type=3D"boolean">true</is_lvm_vg> <partitions config:type=3D"list"> <partition> <filesystem config:type=3D"symbol">jfs</filesystem> <lv_name>space_lv</lv_name> <mount>/space</mount> <size>max</size> </partition> </partitions> <use>all</use> </drive>

1 0

Dhcp Problems?
by Matt Poepping 03 Mar '05

03 Mar '05

I am trying to autoyast a machine, and when it is plugged directly into another machine it works fine, but when I plug it into the network, the dhcp servers do not seem to be responding fast enough for it and then install will fail to manual mode. In manual mode, it can then go out and get a dhcp address. I have tried editing the linuxrc.config file within the initrd file, to up the timeout, but that doesn't seem to work. I've also tried to point to an info file with the same info, and that seems to be ignored also. Thanks, Matt

2 1

Script length issue?
by Schumacher, Gordon 02 Mar '05

02 Mar '05

I'm doing an autoinstall under SuSE 9.2, and I have one reasonably long script (~100 or so lines). I'm finding that under the autoinstaller, it is terminating after line 68 (no matter what that line is). If I run the very same script in a normal BASH shell, it runs fine. Is there perhaps a bug in the autoinstaller that could cause this? Or have I run into something else?

1 0

Re: WELCOME to suse-autoinstall@suse.com
by Luca Pacor 02 Mar '05

02 Mar '05

Hello everybody, I am asking myself whether it would be possible to online_update the autoinstall repository: it would be nice to be able to install new machines using an up-to-date repository reducing this way the install time ... Any hint would be greatly appreciated. Many thanks in advance Luca

1 1

SLES9 SP1 Multisource
by Lee Mayes 02 Mar '05

02 Mar '05

We recently downloaded SLES9 SP1 iso's and I integrated them into our HTTP installation tree as outlined by Anas in a previous memo. However, when I went to install from them, the actual RPMS were not in the path the client was looking for them. My setup: /sles9/CD1/ /core9/CD[1-5]/ /SLES9-SP1/CD[1-3]/ Symlinks as directed # cat yast/instorder /SLES9-SP1/CD1 /sles9/CD1 /core9/CD1 # cat yast/order /SLES9-SP1/CD1 /SLES9-SP1/CD1 /sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1 Looking at the errors in apache's logfile, the clients are attempting to find the SP1 RPMS at /SLES9-SP1/CD1/suse/i586/ (and i686 or noarch). However, on my isos the RPMS are actually at the path: /SLES9-SP1/CD1/i386/update/SUSE-CORE/9/rpm/i586 Creating symlinks to i586/i686/noarch under /suse to ../i386/update/SUSE-CORE/9/rpm allowed my installations to work, but I'm wondering if I have something setup incorrectly, or perhaps we downloaded the wrong SLES9 SP1 iso images from Novell? Here's what we have: # cat SLES-9-SP-1.MD5SUM 3282ab591c3bf1d50053e837026d15e0 SLES-9-SP-1-i386-RC5-CD1.iso 320b3c795f9732a7f45ec6323dab9240 SLES-9-SP-1-i386-RC5-CD2.iso 36e798f4868aece793b592c3d0f05e62 SLES-9-SP-1-i386-RC5-CD3.iso Thanks and Best Regards, Lee

1 0

RE: [suse-autoinstall] post-install scripts
by Suffin, Charles 02 Mar '05

02 Mar '05

Todd, Thanks for the reply. I think what's going on is that you're installing 9.2 or something other than SLES9, and this was the source of my confusion... After discussing this last week, I think some of us concluded that your script simply wouldn't work on SLES9... I have noted that the network is not yet operational during the post-install scripting execution environment of SLES9 when I was working with it a couple of months ago. I think it is necessary to either bring up the network in the script via ifconfig ethX up (Andreas suggested this, I have not tried it myself), or you can simply wget the files that you need during a chroot-script instead and store them on the disk for when you need it (in /mnt, that is, which becomes root during post-install). Best wishes. -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Wednesday, March 02, 2005 9:38 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts I am doing http installs i.e. install=http://1.1.1.1/directory/CD1 autoyast=http://1.1.1.1/install/autoinstall.xml Either in the info file or on the boot cd command line. -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 9:26 AM To: 'Andreas.Matthieu(a)tfa.brandenburg.de'; Suffin, Charles; suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts What you're saying is great, guys (thanks!), but Todd's post-install script in his XML fragment does not do network initialization (I think) before executing wget. I do not understand why his script works... Thanks! -- Charlie p.s./ I didn't mean to rathole Mitko's original email! I am shutting up now! :) -----Original Message----- From: Andreas.Matthieu(a)tfa.brandenburg.de [mailto:Andreas.Matthieu@tfa.brandenburg.de] Sent: Thursday, February 24, 2005 11:21 AM To: Charles.Suffin(a)stratus.com; suse-autoinstall(a)lists.suse.com Subject: AW: [suse-autoinstall] post-install scripts Hi Charles, at postinstall step network are not running [SLES9: AY boot, setup network, install packages (second step), stop network, configure network (but let it down), start postscripts, continue boot with startup network]. Try "ifconfig ethX up" in postscript before use network. Regards, Andreas -----Ursprüngliche Nachricht----- Von: Charles.Suffin(a)stratus.com [SMTP:Charles.Suffin@stratus.com] Gesendet am: Donnerstag, 24. Februar 2005 16:41 An: todd.ness(a)eds.com; suse-autoinstall(a)lists.suse.com Betreff: RE: [suse-autoinstall] post-install scripts Hmm... OK, I'd swear I was unable to use http: during my post-install scripts (when I did my testing), but maybe I goofed. Thanks! -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Thursday, February 24, 2005 10:36 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts This happens during the post-scripts section of the auto install process. Also, I am doing network builds so the networking has to be up and running. So, I download one script that downloads and executes the rest of the scripts. <scripts> <pre-scripts config:type="list"> </pre-scripts> <post-scripts config:type="list"> <script> <filename>cleanup</filename> <interpreter>shell</interpreter> <source> <![CDATA[ echo writing profile echo "d-default" > /etc/MSDprofile echo getting scripts /usr/bin/wget http://1.2.3.4/install/postinst.sh -O /tmp/postinst.sh chmod 555 /tmp/postinst.sh /tmp/postinst.sh exit 0]]> </source> </script> </post-scripts> </scripts> -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 7:38 AM To: Ness, Todd; suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts Guys, quick question... I found that the post-install scripting environment -- which runs after the reboot -- didn't have networking set up yet (whereas chroot scripts run before the reboot and have the network running). Do you guys (Todd) do some magic to enable the network for the operation of post-install scripts so you could use wget? What I do is use wget during chroot scripts and store the files in /mnt/... (which gets mounted as root after the reboot). -- Charlie -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Thursday, February 24, 2005 9:31 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts Just a thought, I wrote a post-install wrapper that gets scripts via wget and those scripts are S01name.. S20name and then executes them serially similar to rc startup scripts. -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Thursday, February 24, 2005 7:15 AM To: Mitko Haralanov Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] post-install scripts They are executed in the order they appear in the XMl file. Anas Mitko Haralanov wrote: > I have recently started working on a autoyast configuration file for > SuSE9.1. In the process of generating the file, I have created several > post-install scripts which configure different parts of the system. > The question that I have is: what is the order in which the scripts > are going to be executed? Currently some of the post-install scripts > depend on others and I need to be sure in what order they will be > executed. > > Thanx > -- 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 -- 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 -- 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

2 1

multiple raid and autoyast
by Jeremy Sanders 02 Mar '05

02 Mar '05

Hi - I'm trying to make a autoyast configuration file which will install a machine with 3 software raid 1 devices (root, swap, and a data partition) using SLES 9. The partitions will already exist on the drives. Unfortunately this doesn't seem to work. yast seems to want to mount the individual component partitions as /data1 ... /data6. It only seems to want to use the /dev/md2 device, and ignores md0-md1. Can anyone see the problem, or does someone have a similar working file I can look at?  <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list">  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> </partition>  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> </partition>  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> </partition> </partitions> </drive> <drive> <device>/dev/hdb</device> <partitions config:type="list">  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> </partition>  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> </partition>  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> </partition> </partitions> </drive>  <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> </drive>  <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> </drive>  <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">false</format> <mount>/soft3</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> </drive> </partitioning> Thanks Jeremy -- Jeremy Sanders <jss(a)ast.cam.ac.uk> http://www-xray.ast.cam.ac.uk/~jss/ X-Ray Group, Institute of Astronomy, University of Cambridge, UK. Public Key Server PGP Key ID: E1AAE053

1 3