November 2013 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] SuSE 12.3 hangs after installation
by Daniel Spannbauer 21 Nov '13

21 Nov '13

Hello, I try to install openSuSE 12.3 with autoyast. Works fine so far. But one thing is annoying: after the installation the system trys to reboot...but it hangs. It stops at this screen: https://www.dropbox.com/s/feiywfylkmd8rzf/CIMG1099.JPG Any hints about this? Is it a known problem? How can I find the error causing this? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] SLES 11 SP3 Error during "Configuring System according to auto-install settings"
by Hans-Joachim Ehlers 20 Nov '13

20 Nov '13

Hi Short question: During the Step: "Configuring System according to auto-install settings" I get AFTER the step: "Configuring mail" the error message: " Error Error running SuSEconig OK " After pressing OK the system proceeds with: "Configuring nfs" Question: Is the problem related to the "mail" or "NFS" section and any idea to look for what in the y2logs ? Tia Hajo P.S I know that i can remove the mail or NFS section from the xml file. -- Hans-Joachim Ehlers UNIX Systems Engineer MetaModul GmbH on behalf of EUMETSAT Tel : +49 6151 807-7307 http://www.eumetsat.int N��r��y隊Z)z{.�殶��֥�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�殶��֥��0��Ǩ�

4 11

[opensuse-autoinstall] SLES 11 SP3 network / udev not working anymore ?
by Hans-Joachim Ehlers 19 Nov '13

19 Nov '13

Hi Given: OS: SLES 11 SP3 (64b) HW: Server with eth0,eth1,eth2,eth3 Task: Install via network and reconfigure configure eth1 -> eth0 , eth2 -> eth1 and create a bond0 interface build of eth0,eth1 Note - The mac address are known. - 2 adapters are not used. Autoyast file: </networking> <interfaces config:type="list"> <interface> <bonding_master>yes</bonding_master> <bonding_module_opts>mode=active-backup miimon=1000 arp_ip_target=10.11.0.1</bonding_module_opts> <bonding_slave0>eth0</bonding_slave0> <bonding_slave1>eth1</bonding_slave1> <bootproto>static</bootproto> <device>bond0</device> <ipaddr>10.11.14.2</ipaddr> <netmask>255.255.0.0</netmask> <prefixlen>16</prefixlen> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>none</bootproto> <device>eth0</device> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>none</bootproto> <device>eth1</device> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <managed config:type="boolean">false</managed> <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value>34:40:B5:C8:E2:42</value> </rule> <rule> <name>eth1</name> <rule>ATTR{address}</rule> <value>34:40:B5:C8:E2:46</value> </rule> </net-udev> </networking> Problem: After installation i have $ ifconfig -a | grep -E "eth|bond" - eth2 - eth3 - eth4 - eth5 But no bond device. Analyse: I checked the /etc/udev/rules.d/70-persistent-net.rules and see ... # Generated by autoyast # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="34:40:B5:C8:E2:42", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="34:40:B5:C8:E2:46", NAME="eth1" # PCI device 0x19a2:0x0710 (be2net) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="34:40:b5:c8:e2:44", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x19a2:0x0710 (be2net) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="34:40:b5:c8:e2:42", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" # PCI device 0x19a2:0x0710 (be2net) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="34:40:b5:c8:e2:46", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4" # PCI device 0x19a2:0x0710 (be2net) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="34:40:b5:c8:e2:40", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5" ... So the adapters will be added for whatever reason again and we end up in eth2,3,3,5 and eth0,eth1 are not available. The not so fun thing is that the even after fixing the /etc/udev/rules.d/70-persistent-net.rules it will be regenerated. ( FROM WHERE?) Note: A via yast generate network section looks like: <interfaces config:type="list"> <interface> <bonding_master>yes</bonding_master> <bonding_module_opts>mode=active-backup miimon=1000 arp_ip_target=10.11.0.1</bonding_module_opts> <bonding_slave0>eth0</bonding_slave0> <bonding_slave1>eth1</bonding_slave1> <bootproto>static</bootproto> <device>bond0</device> <ipaddr>10.11.14.2</ipaddr> <netmask>255.255.0.0</netmask> <prefixlen>16</prefixlen> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>none</bootproto> <device>eth0</device> <name>Emulex OneConnect 10Gb NIC (be3)</name> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>none</bootproto> <device>eth1</device> <name>Emulex OneConnect 10Gb NIC (be3)</name> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value>34:40:b5:c8:e2:42</value> </rule> <rule> <name>eth1</name> <rule>ATTR{address}</rule> <value>34:40:b5:c8:e2:46</value> </rule> </interfaces config:type="list"> So no real difference except that i did not provide the <name>..</name> in my profile. Any hints ? Hajo Note The docu form https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_aut… is not very helpful. -- Hans-Joachim Ehlers UNIX Systems Engineer MetaModul GmbH on behalf of EUMETSAT Tel : +49 6151 807-7307 http://www.eumetsat.int N��r��y隊Z)z{.�殶��֥�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�殶��֥��0��Ǩ�

1 1

[opensuse-autoinstall] Working iSCSI example?
by Floris Bos / Maxnet 18 Nov '13

18 Nov '13

Hi, Does anyone having a working autoyast example that uses iSCSI as storage? Tried: == <partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning> [...] <iscsi-client> <initiatorname>iqn.2013-13.eu.maxnet:inittest</initiatorname> <targets config:type="list"> <listentry> <authmethod>None</authmethod> <portal>192.168.178.12:3260</portal> <startup>onboot</startup> <target>iqn.2008-08.com.starwindsoftware:jaguar-test</target> </listentry> </targets> <version>1.0</version> </iscsi-client> == But it does not seems to work and shows "device '' not found by storage backend" in Yast. Also tried not specifying an iSCSI section and passing the information through the iBFT in the hope that the installer picks it up automatically (which does work for other OS like CentOS and Windows Server), with the same result. Yours sincerely, Floris Bos -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 2

[opensuse-autoinstall] AutoYaST - Automated installation from openSUSE 12.3 DVD does not work
by Sebastian Siebert 18 Nov '13

18 Nov '13

Hi folks, I am helping someone that he want to use the automated installation with AutoYaST and the openSUSE installation DVD. The issue is that YaST could not find the DVD YaST2 repository. We went as follows: 1. Download the openSUSE 12.3 DVD ISO 2. Install the "ISO master" from Packman 3. Modify the ISO: add the AutoYaST file to /autoinst.xml 4. Modify the ISO: add boot parameter in the file /boot/x86_64/loader/isolinux.cfg: install=cd autoyast=file:///autoinst.xml The hint comes from: <http://users.suse.com/~ug/AutoYaST_FAQ.html#a6> 5. Save the new ISO content 6. Boot the ISO in VirtualBox for test. AutoYaST starts automatically. 7. While system probing we get an error message: --- START --- Unable to create repository from URL 'cd:/?devices=/dev/disk/by-id/ata-VBOX_CD-ROM-VB2-01700376'. Details: [|] Valid metadata not found at specified URL History: - [|] Repository type can't be determined. Try again? --- END --- We had tried following boot parameter: 1. install=cd autoyast=file:///autoinst.xml 2. autoyast=file:///autoinst.xml 3. autoyast=file:///autoinst.xml install=cd 4. install=cd:/ autoyast=file:///autoinst.xml 5. install=cd:/?devices=sr0 autoyast=file:///autoinst.xml 6. install=cd:/?devices=sr* autoyast=file:///autoinst.xml 7. namescheme="" autoyast=file:///autoinst.xml 8. namescheme="" install=cd autoyast=file:///autoinst.xml But none of them works. Interesting issue is if we select "Source HTTP" instead "Source DVD" in the boot menu. YaST adds the online OSS repository but it could not find the AutoYaST file anymore. It is so weird. The error message is: --- START --- An error occured while fetching the profile: Reading file on /var/adm/mount//autoinst.xml filed. Reading file on /autoinst.xml failed. Reading a file on CD failed: /tmp/YaST-02942-IMvaKW/tmp_mount//autoinst.xml. --- END --- The question is: How we can fixed it in the boot parameter for the openSUSE 12.3 DVD installation? Thanks for any advice on this problem. -- Kind regards, Sebastian - openSUSE Member (Freespacer) Website/Blog: <http://www.sebastian-siebert.de> Important notes on openSUSE Mailing List: <http://en.opensuse.org/openSUSE:Mailing_list_netiquette> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] Start only second stage in console mode
by Joschi Brauchle 14 Nov '13

14 Nov '13

Hello everyone, I have a autoyast setup where I would like to install a headless server. The machine starts an Xserver in Stage 1 of the installation process just fine and installation begins (a monitor is attached but turned off). After RPM installation and rebooting/kexec into stage 2, starting XDM fails for some reason. As the machine is supposed to run headless in console mode anyway, I would not care at all. I even disable XDM completely later on as it is not needed. But I seems like the second stage fails to start due to XDM failing. Instead of fixing the reason for XDM failing, I would like to tell the *second* stage ahead of time to simply start in console mode. Is this possible somehow? I.e.: start stage 1 with X enabled, start stage 2 with X disabled in console mode. The AutoYast configuration options for services is done at the end of stage 2, which is too late for this case. Thanks for any suggestions!

2 3