May 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] SLES10-RC1 autoinstall directory layout changed?
by Pete Nishimoto 24 May '06

24 May '06

Hi, I've set the <signature-handling> section in my autoyast file as well as regenerated the DVD with the .33 version of makeSUSEdvd and I *still* get the problem "Could not set patters or selections: default" error box. Is there something more to try. Another datapoint is that if I use the DVD from the CD reader (i.e., not PXE), and do the installation by hand, SLES10 installs as expected. Pete At 03:08 AM 5/24/2006, Matt Gillard wrote: > > -----Original Message----- > > From: Uwe Gansert [mailto:ug@suse.de] > > Sent: Wednesday, 24 May 2006 12:12 AM > > To: suse-autoinstall(a)suse.com > > Subject: Re: [suse-autoinstall] SLES10-RC1 autoinstall > > directory layout > > changed? > > > > > > On Tuesday 23 May 2006 15:48, Pete Nishimoto wrote: > > > > > 1) installation stops at the "Preparing System > > for Automated > > > Installation" screen > > > on the "Configure Software Selections" > > bullet as it can't find > > > selection "default". > > > > try this: > > http://lists.suse.com/archive/suse-autoinstall/2006-Apr/0052.html > > in your autoyast profile. If that helps, that signatures are > > broken on your > > new built DVD. > > > >I had problems doing an autoinstall of SLES10-RC1. >First problem was fixed by doing the ignore signatures as mentioned above. > > > > Anyone else see any problems with this on SLES10 RC1? > > > > > > Note that I generated the DVD from the seperate CD images using > > > makeSUSEdvd. > > > > get the latest makeSUSEdvd script and read: > > http://en.opensuse.org/Making_a_DVD_from_CDs > > > >Second problem is currently logged with Novell under SR 10267001181 >whereby the /mnt/etc/fstab is not updated so the installation fails >when creating the initrd for Lilo with no / in /etc/fstab error. Our >partition layout is /boot as primary and LVM for rest of disk. Then >all remaining filesystems are in the LVM partition (incl. root). > >matt > >-- >Matt Gillard >UNIX Systems Engineer >Coles Myer Ltd | Lvl 4 236 Bourke St | +61 3 963 51926 > >This email and any attachments may contain privileged and >confidential information and are intended for the named addressee >only. If you have received this e-mail in error, please notify the >sender and delete this e-mail immediately. Any confidentiality, >privilege or copyright is not waived or lost because this e-mail has >been sent to you in error. It is your responsibility to check this >e-mail and any attachments for viruses. No warranty is made that >this material is free from computer virus or any other defect or >error. Any loss/damage incurred by using this material is not the >sender's responsibility. The sender's entire liability will be >limited to resupplying the material. > >-- >To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

SLES9/SP3 Auto-Install LVM Partitioning Problem
by warren＠leetnet.com 24 May '06

24 May '06

I'm having an issue setting this up. I've gotten regular partitions to work but when I introduce LVM to the config I get barked at regarding a bogus control file during the install. Below is the problematic portion of my control file. I'm probably missing something obvious here, but I can't figure it out. Any assistance would be greatly appreciated. I followed Uwe's guide as close as possible, and modified for my needs. ------------------------- <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <create config:type="boolean">true</format> <mount>/boot</mount> <partition_type>primary</partition_type> <partition_nr config:type="integer">1</partition_nr> <size>auto</auto> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <mount>swap</mount> <partition_type>primary</partition_type> <partition_nr config:type="integer">2</partition_nr> <size>auto</size> </partition> <partition> <lvm_group>system</lvm_group> <partition_type>primary</partition_type> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <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>usr_lv</lv_name> <mount>/usr</mount> <size>4gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>var_lv</lv_name> <mount>/var</mount> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>tmp_lv</lv_name> <mount>/tmp</mount> <size>1gb</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> ------------------------- Thanks, Warren ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

RE: [suse-autoinstall] SLES10-RC1 autoinstall directory layout changed?
by Matt Gillard 24 May '06

24 May '06

> -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Wednesday, 24 May 2006 12:12 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES10-RC1 autoinstall > directory layout > changed? > > > On Tuesday 23 May 2006 15:48, Pete Nishimoto wrote: > > > 1) installation stops at the "Preparing System > for Automated > > Installation" screen > > on the "Configure Software Selections" > bullet as it can't find > > selection "default". > > try this: > http://lists.suse.com/archive/suse-autoinstall/2006-Apr/0052.html > in your autoyast profile. If that helps, that signatures are > broken on your > new built DVD. > I had problems doing an autoinstall of SLES10-RC1. First problem was fixed by doing the ignore signatures as mentioned above. > > Anyone else see any problems with this on SLES10 RC1? > > > > Note that I generated the DVD from the seperate CD images using > > makeSUSEdvd. > > get the latest makeSUSEdvd script and read: > http://en.opensuse.org/Making_a_DVD_from_CDs > Second problem is currently logged with Novell under SR 10267001181 whereby the /mnt/etc/fstab is not updated so the installation fails when creating the initrd for Lilo with no / in /etc/fstab error. Our partition layout is /boot as primary and LVM for rest of disk. Then all remaining filesystems are in the LVM partition (incl. root). matt -- Matt Gillard UNIX Systems Engineer Coles Myer Ltd | Lvl 4 236 Bourke St | +61 3 963 51926 This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

1 0

SLES10-RC1 autoinstall directory layout changed?
by Pete Nishimoto 23 May '06

23 May '06

I was able to layout the directory tree for a SLES10 Build 9 to install on our PXE server by providing the following links at the top of the tree: autoyast.xml boot -> sles10/boot content -> sles10/content content.asc -> sles10/content.asc content.key -> sles10/content.key control.xml -> sles10/control.xml media.1 -> sles10/media.1 sles10 suse -> sles10/suse Where ./sles10 has the contents of the DVD. I reproduce this exactly for the SLES10-RC1 DVD and 2 issues occur: 1) installation stops at the "Preparing System for Automated Installation" screen on the "Configure Software Selections" bullet as it can't find selection "default". I'm using the same autoyast.xml file as I did for SLES10 Build 9. Furthermore, putting ethereal on the PXE server, the last access for a file was a failure for the file 'repodata' at the top of the tree. There is no 'repodata' file/directory on the DVD, so I can't link to anything. 2) If I say to continue anway (after the selection failure), it stops at the "Finish Basic Installation" screen at the "Install Boot Manager" bullet, with 72% on the completion bar (having the title "Creating initrd..."). This looks like a similar (previously fixed) problem where I didn't have the link to the 'boot' directory at the top of the tree. Anyone else see any problems with this on SLES10 RC1? Note that I generated the DVD from the seperate CD images using makeSUSEdvd. Thanks in advance. Pete

2 1

AutoinstallRules.ycp error
by Antonio Beamud Montero 22 May '06

22 May '06

Hi all: I'm trying to install a SuperMicro machine with Suse 9.1 network autoinstall. The problem arises with the network card, because with the module included in the default kernel for broadcom cards (tg3), this netcard doesn't works. I've solved this creating a floppy with the last version of this module and all works ok, but the installation stops when try to download the autoinstall profile... it seems not to find the associated profile... I've checked all and is ok (I have installed a lot of machines with the same method), but in this case the y2log file shows: ------------------------ 2006-05-19 17:33:23 <3> linux(821) [Interpreter] AutoInstallRules.ycp:813 Argument (AutoInstallRules::mac) to toupper(...) is nil 2006-05-19 17:33:23 <3> linux(821) [Interpreter] AutoInstallRules.ycp:813 Argument (toupper (AutoInstallRules::mac)) to add(...) is nil 2006-05-19 17:33:23 <3> linux(821) [Interpreter] AutoInstallRules.ycp:814 Argument (tomerge) to add(...) is nil 2006-05-19 17:33:23 <3> linux(821) [Interpreter] AutoInstallRules.ycp:815 Argument (tomerge) to add(...) is nil 2006-05-19 17:33:23 <1> linux(821) [YCP] AutoInstallRules.ycp:816 Created default rules=nil 2006-05-19 17:33:23 <1> linux(821) [YCP] AutoInstallRules.ycp:625 Getting Rules: nil 2006-05-19 17:33:23 <3> linux(821) [Interpreter] AutoInstallRules.ycp:634 Argument (tomerge) to foreach(...) is nil 2006-05-19 17:33:23 <1> linux(821) [YCP] AutoInstallRules.ycp:664 No files from rules found ------------------- Inspecting the code, the system makes a hwinfo, with the old network module, gets the network info, loads the updated network module and then try to find the profile with the incorrect info... How I can solve this problem? Greetings.

1 0

format some partitions, don't format others
by John SJ Anderson 22 May '06

22 May '06

Hi -- I'm working on setting up an autoinstall infrastructure that will be used to convert around 750 machines from a customized Slackware distribution to SLES9SP3. Obviously, automation of as much as possible is key. We'd also like to borrow a page from the ROCKS folks and make re-installs as painless as possible, because it's something that comes up in our environment a fair bit. The general idea is to have two "standard" partitions, / and /var, on /dev/md0 (sd[ab]1) and /dev/md1 (sd[ab]2), respectively, and then have some more specific RAID partitions on the remaining parts of the disk (with different sorts of machines having different sorts of partitioning schemes). During an initial install (which can be assumed to mean "an install onto disks that don't have a partition table yet"), all of these partitions would need to be created and initialized, the RAIDs set up, and the filesystems created. During a reinstall, we would only want to reformat '/' and '/var' -- any other partitions/RAID devices/filesystems should be left alone. The /etc/fstab file will be managed with our configuration management system, so having that maintained properly across reinstalls isn't a concern -- as long as the reinstall can get to the point where it will boot and mount / and /var, everything will converge to the desired state once the tool runs. The goal is to do this with only a single install.xml config file. It's not clear from the AutoYaST PDF whether or not this is possible -- can anybody here shed some light on whether this particular windmill is a good tilting target or not? thanks, john. -- It's easy to get the *wrong* answer in O(1) time. Mark Jason Dominus's Good Advice #11963

2 1

Configuring SLES 9 autoinstall with new RPMs
by Spangler, Tim 22 May '06

22 May '06

Hello, I've created a SUSE auto install server and have configured it to apply SP3 during the install process. Now I need to configure it to allow me to copy new and updated RPMs into a folder and apply them when necessary. For example, I want to deploy the newest version of Bastille to each new server I build and then create a post install script that runs Bastille to lockdown the server right during install. In a month I may decide I need to put the newest version of perl in the install directory and have it automatically deployed. In other words this needs to be a solution where I can just copy RPMs into the updates folder and have them be applied. So far I've created an updates directory in the root install directory and have configured the instorder and order files to look in the updates folder like follows: /updates /sles9sp3/cd1 /sles9/cd1 /core9/cd1 I've copied the newest Bastille rpm into the updates folder, but when the auto install runs I get an error that says "reading media description failed". Any ideas on where am I going wrong? Thanks, -Tim Spangler

2 1

Using GPT partitions with SLES9
by Jeremy Silver 18 May '06

18 May '06

All, I am trying to create an install profile for a system with >2TB disk (a raid array). Can anyone tell me how I can specify a disk be partitioned using GPT instead of the standard partitioning scheme? I have no problem setting up the disk using parted, but I have yet to see anything close to this in the documentation or list archives. Thanks in advance. -- Jeremy Silver Jeremy-list(a)broadware.com

2 4

Linking error with vsftpd
by naveen penumala 18 May '06

18 May '06

I'm trying to build vsftpd, and I have downloaded version 2.0.4 on SUSE linux 10.1. gcc -c access.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -c features.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -c readwrite.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -c ssl.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -c sysutil.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc sysutil.c: In function âvsf_sysutil_connect_timeoutâ: sysutil.c:1744: warning: pointer targets in passing argument 5 of âgetsockoptâ differ in signedness gcc -c sysdeputil.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -o vsftpd main.o utility.o prelogin.o ftpcmdio.o postlogin.o privsock.o tunables.o ftpdataio.o secbuf.o ls.o postprivparent.o logging.o str.o netstr.o sysstr.o strlist.o banner.o filestr.o parseconf.o secutil.o ascii.o oneprocess.o twoprocess.o privops.o standalone.o hash.o tcpwrap.o ipaddrparse.o access.o features.o readwrite.o ssl.o sysutil.o sysdeputil.o-Wl,-s `./vsf_findlibs.sh` -pie /lib/libpam.so.0: could not read symbols: File in wrong format collect2: ld returned 1 exit status make: *** [vsftpd] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.97854 (%build) It seems to me that there is some trouble reading symbols defined in libpam - but why? thnaks Naveen.P

2 1

RE: [suse-autoinstall] SLES 9 SP3 Network Install Issue
by warren＠leetnet.com 17 May '06

17 May '06

Installing with a 100MB boot partition worked. Thanks for your help figuring this out. Now on to actually doing the autoyast stuff along with some post-install scripts. Thanks! Warren Quoting anoop kundathil <anoopbharathan(a)yahoo.com>: > Warren, > > It is clear that your installation setup has no issues now. Things can be > suspected is > 1.Your partitoning scheme > 2. additional hardware which is connected to your system ( any usb cd/key > etc ) > also try to install with 100MB boot partition as i suggested earlier > > thanks > Anoop > > warren(a)leetnet.com wrote: > Thanks for the reply. See below: > > Quoting Hans-Joachim Ehlers : > > > Some thoughts about the SLES reposirtoy > > 1) If you create a SLES9 SP3 repository for the installation server - > > actually the machine from where you create the repository - should be > > forhand updated to SP3 > > This is exactly what was done. > > > 2) use the yast installation server menues to create the repository > > Again, this is what was done. (I actually did it manually before realizing > that > I could do it through YaST - once I realized it I started from scratch and > did > it through YaST) > > > 3) The most important thing is that you use at least the SP3 boot CD. In > our > > current enviroment we build the boot CD from the fresh created repository. > > I've tried booting from SP3 and I've tried the regular SLES boot CD as well > with > the same results. This disk was created prior to me coming to this company, > however it installs SP3 just fine and was added to the repository through > YaST > with no issues. > > > Regarding dell > > Nowaday DELL machine have SATA drives. The SLES GM release does not supoort > > SATA afaik but at least SP2 does. > > To install from a SLES GM release you can switch in the DELL bios the SATA > > mode to combined meaning that ATA will be used. > > Problem with that: > > SLES GM will see hdX device but after installation you might have sdX > > devices. In this case grub will fail. > > So you are might back to point 3) above ;-) > > I'm using GX260's for testing purposes initially, which are IDE. The > bootloader > is trying to load from /dev/hdax as well. > > This morning I am going to do as suggested before and try another network > install and create a 100MB boot partition instead of letting the boot > directory > sit on the / partition. I'll post back the results. > > Anymore insight into this issue would be greatly appreciated. > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > --------------------------------- > How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0