June 2010 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] "Invalid partition table" on SLES10SP2/3 with soft RAID
by Andreas Taschner 17 Jun '10

17 Jun '10

Hi This may very well not be an AutoYaST problem, but ... I am trying to duplicate a problem at a customer that has a RAID1 setup with /boot, / and other partitions on md. For this I install SLES10SP2 as step one and upgrade to SLES10SP3 as step2. Doing this manually works fine, but when installing SP2 or upgrading to SP3 using AutoYaST, the system fails to boot and reports "Invalid partition table" before even reaching the grub menu. Whether I use initialize true on sda, sdb and md in the installation profile or not, makes no difference. The strange thing is when I install SLES manually after being in the error situation, it recognizes all partitions and RAID setup. When booting into rescue mode and doing an fdisk -l it sees all sd{a,b}* partitions correct, bootable is /dev/sdb1. It also lists the /dev/md{0-4], but only md0 is claimed to contain a valid partition table (though not containing any partitions). md1-4 are marked as invalid. mdadm --scan --detail print shows that all RAID devices contain two devices. /boot/grub/menu.lst refers to /dev/md? and I have tried configuring device.map to map to both /dev/sd? and /dev/disk/by-id/*. Another funny observation : Switching the bootable flag from sdb1 to sda1 changes the boot error from "Invalid partition able" to "No operating system" So it looks like the RAID setup somehow does not make it to disk when using AutoYaST. Any ideas ? Thank you. Best regards Andreas Taschner Designated Support Engineer Novell -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] registration against SMT using autoyast
by Matthew Delves 08 Jun '10

08 Jun '10

Hey List, I'm wondering if there is a known way of registering a server against SMT using autoyast. Thanks, Matt Delves. -- --------------------------------------------- Matthew Delves System Administrator Information Systems Networks & Infrastructure University of Ballarat ph: 03 5327 9732 email: m.delves(a)ballarat.edu.au -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] What should my module return?
by Erico Mendonça 02 Jun '10

02 Jun '10

I'm running a self-written YaST module at the start of the installation (via control.xml, inserted right before the prepareprogress module), and even though my modules finishes with success, I get a YaST error (red screen). Do I need to return/set any specific values? I already tried returning true/false/0/1/nil/GetInstArgs(0), etc, all with the same result. There doesn't seem to be any specific error messages in the log, it just informs that the YaST client module was finished. -- -- Erico -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] grub boots wrong kernel after stage 1
by Antje Bendrich 01 Jun '10

01 Jun '10

Good morning, we are using PXE to boot into autoyast and install the packages from local repositories via http and are having a problem since Suse released a new kernel package in April. Everything works fine up to the first reboot after finishing stage 1. Then grub has two kernels to choose from: 2.6.31.12-0.1-default, which is the kernel of the autoyast installation, and 2.6.31.12-0.2-desktop, which is the newest kernel freshly installed from our repositories. Grub boots the 2.6.31.12-0.1-default-kernel, complains (with good cause) 'unable to canonicalize path "/lib/modules/2.6.31.12-0.1-default/systemtap/preloadtrace.ko": No such file or directory' and continues booting, but fails to load the modules for the network card and the graphics card (and probably others). This leads to X not starting and -worse- autoyast failing to load some configuration files via ftp, configured like this: <file> <file_path>/etc/somefile</file_path> <file_owner>root:root</file_owner> <file_permissions>644</file_permissions> <file_location>ftp://somehost/files/etc/somefile</file_location> </file> Autoyast does not complain very visibly about this failure while it's running. The files not loaded do exist on the system afterwards, alas with a size of 0 bytes. The normal system logs do not contain that first boot, so it is kinda hard to figure out exactly why the final system does not work like it should. If I babysit the installation and manually choose the other kernel version (2.6.31.12-0.2-desktop) when grub comes up after stage 1, everything continues like it should, but I don't really want to wait to hit "down down return" at the exact right time... So: Why is the installation kernel still configured in grub when it is not fully functional anymore? How do I get rid of it at this early time? Or is our error something else entirely? Thanks in advance, Antje -- Antje Bendrich (Team IT-Services), Phone +49 40 808077-642 DFN-CERT Services GmbH, https://www.dfn-cert.de/, Phone +49 40 808077-555 Sitz / Register: Hamburg, AG Hamburg, HRB 88805, Ust-IdNr.: DE 232129737 Sachsenstraße 5, 20097 Hamburg/Germany, CEO: Dr. Klaus-Peter Kossakowski

2 5

[opensuse-autoinstall] Cannot create raid with autoyast on 11.3 M7
by Peter Pointner 01 Jun '10

01 Jun '10

Hello, I try to create a raid-1 with autoyast on opensuse-11.3 Milestone 7 x86_64. It fails with "Error while configuring partitions. Try again." The same xml-file works with opensuse-11.2 x86_64. Did I miss relevant changes between 11.2 and 11.3? Should I provide more information here on the list or open a bug on bugzilla? Peter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3