January 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

SLES and LVM error
by Rob Thompson 11 Jan '06

11 Jan '06

Hi, I am trying to use autoyast and format 5 LVM partitions during install (dont ask ;-). The control file is read correctly, and when I look in the Partitioning portion of the YAST installer everything looks proper - but when I choose accept and autoyast begins formating the drives I get the following error: LVM ERROR echo y|/sbin/pvcreate -ff -M2 /dev/sda5 /dev/sda5: Couldn't find device. Here is my XML file: Thanks, Rob </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>+100MB</size> </partition> <partition> <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">131</partition_id> <partition_type>primary</partition_type> <size>+16GB</size> </partition> <partition> <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>+10GB</size> </partition> <partition> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">130</partition_id> <partition_type>extended</partition_type> <size>max</size> </partition> <partition> <lvm_group>VG00</lvm_group> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">142</partition_id> <size>+35GB</size> </partition> </partitions> </drive> <drive> <device>/dev/VG00</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <mount>/home</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm01</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+10GB</size> </partition> <partition> <mount>/tmp</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm02</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+5GB</size> </partition> <partition> <mount>/var</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm03</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+5GB</size> </partition> <partition> <mount>/usr</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm04</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+5GB</size> </partition> <partition> <mount>/opt</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm05</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+10GB</size> </partition> </partitions> <use>all</use> <pesize>4M</pesize> </drive> </partitioning> <software>

2 3

software raid through autoyast
by Reynold L Demarco 11 Jan '06

11 Jan '06

Has anyone been able to successfully setup a software raid using autoyast? I've seen a bunch of posts with questions on getting it working, but I haven't seen any successful responses. Specifically I'm trying to mirror /boot, /, and swap without using LVM. I want to keep it simple before I get advanced. It parses my xml file fine, it just can't configure my software RAID. Below is my parititioning section. I've tried many variations on it with no success. Any help is appreciated. My typical error is... "Could not format /dev/md2. You can continue if you know what you are doing, but, to prevent damage your file systems, it is safer to cancel and reboot." <partitioning config:type="list"> <drive> <device>/dev/hde</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_type>raid1</raid_type> <size>512M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_type>raid1</raid_type> <size>2g</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <raid_type>raid1</raid_type> <size>200g</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdg</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_type>raid1</raid_type> <size>512M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_type>raid1</raid_type> <size>2g</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <raid_type>raid1</raid_type> <size>200g</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">false</format> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiserfs</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> </partitioning> -- Reynold De Marco Scientific Computing Services

4 5

A better error message...
by Frank Steiner 10 Jan '06

10 Jan '06

Hi, if there's any parse error in rules.xml, autoyast just complains that no profile could be found. It would be very very helpful, if autoyast could tell the reason for that, i.e. "Parse error in rules.xml. Could not find any profile" or sth. I've gone mad searching for this cause :-) cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 3

profile file not being accepted
by joe.richter＠gmx.net 10 Jan '06

10 Jan '06

hello everyone, the exact error message is "A profile for this machine could not be found or retrieved. Check that you entered the correct location on the command line and try again. Because of this error, you can only enter a URL to a profile and not a directory. If you are using rules or host name-based control files, restart the installation process and make sure the control files are accessible." I generated a config file using yast autoyast within NLD9 (SP2). DTD check says it's okay. And yast is retrieving the file upon its installation attempt: [5] Tue 10Jan06 10:34:15 - (000009) Connected to x.x.x.77 (Local address x.x.x.10) [5] Tue 10Jan06 10:34:15 - (000009) ANONYMOUS logged in, password: CURL_BY_DANIEL(a)HAXX.SE [3] Tue 10Jan06 10:34:15 - (000009) Sending file f:\ftproot\nld9\xml\autoyast.xml [3] Tue 10Jan06 10:34:15 - (000009) Sent file f:\ftproot\nld9\xml\autoyast.xml successfully (338 kB/sec - 4501 Bytes) [5] Tue 10Jan06 10:34:15 - (000009) Closing connection for user ANONYMOUS (00:00:00 connected) Still I get the error message quoted above.. so what's wrong? my very basic 'just getting started' profile file: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> </configure> <install> <bootloader> <activate config:type="boolean">false</activate> <global config:type="list"/> <loader_device></loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"/> </bootloader> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</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>auto</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>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <addons config:type="list"> <addon>Novell-Software</addon> <addon>SuSE-Documentation</addon> <addon>Office</addon> <addon>Gnome_Desktop</addon> </addons> <base>Gnome</base> </software> </install> </profile> best regards /JR. -- 10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail +++ GMX - die erste Adresse f�r Mail, Message, More +++

2 1

LVM and autoyast
by LDB 10 Jan '06

10 Jan '06

If you configure autoyast to produce LVM partitions, is there anything in addition that must be done in addition to what is in autoyast.xml. For example, a script or something that must be executed during the post-installation phase. I ask because my autoyast installation completed without any intervention but LVM did not quite make it when I logged in. Any suggestions would be great .. Thanks, LDB

2 3

LVM and autoyast on SuSE 10.0
by LDB 08 Jan '06

08 Jan '06

Below you find a portion of my autoyast.xml file specifying an LVM setup. When the autoinstallation gets to this point and says, "Error: A logical volume with the requested size could not be created." What am I doing wrong? <partitioning> ... <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <lvm_group>apps</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/apps</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <lv_name>var_spool_lv</lv_name> <filesystem config:type="symbol">reiser</filesystem> <mount>/var/spool</mount> <size>50gb</size> </partition> <partition> <lv_name>srv_lv</lv_name> <mount>/srv</mount> <filesystem config:type="symbol">reiser</filesystem> <size>5gb</size> </partition> </partitions> <pesize>4M</pesize> </drive> .... </partitioning>

1 1

Re: [suse-autoinstall] Placing autoyast.xml on boot CD
by LDB 08 Jan '06

08 Jan '06

Anton Altaparmakov wrote: > On Sun, 8 Jan 2006, LDB wrote: >> I am not making myself clear. The autoyast.xml file is on the boot CD. The >> installation media is elsewhere. When it comes time for the autoyast.xml file >> to be recognized it is not found by the installer. The directives >> autoyast=file:///autoyast.xml does not work. >> >> This is what my installation root looks on the CD, >> >> drwxr-xr-x 5 root root 176 2006-01-07 23:30 ./ >> drwxrwxrwt 45 root root 2456 2006-01-08 11:45 ../ >> -rw-r--r-- 1 root root 17360 2006-01-07 23:30 autoyast.xml >> drwxr-xr-x 3 root root 328 2005-09-14 21:04 boot/ >> -r--r--r-- 1 root root 692 2005-09-14 19:34 content >> drwxr-xr-x 2 root root 152 2005-09-14 19:55 media.1/ >> drwxr-xr-x 2 root root 48 2005-09-14 21:04 suse/ >> >> Am I wrong in thinking it can be recognized on the boot CD? > > You are right in that but you are doing it wrong. You have to place the > file in the initrd of the cd not in the root directory of the cd if you > want to use the autoyast=file syntax. > > If you place it in the root of the cd, then the correct syntax is: > > autoyast=device://hda/autoyast.xml > > Assuming hda is your cdrom drive (which it is on a scsi/sata only + pata > cd/dvd-rom drive system). > > That works fine for me. > > Best regards, > > Anton Excellent .. thank you ... LDB

1 0

Placing autoyast.xml on boot CD
by LDB 08 Jan '06

08 Jan '06

I have placed autoyast.xml in the root of my boot CD. I have passed in the correct parameters in, boot/loader/isolinux.cfg which is, append initrd=initrd showopts install=ftp://suse.mirrors.tds.net/pub/opensuse/distribution/SL-10.0-OSS/in… autoyast=default load_ramdisk=1 textmode=1 So, is it possible to put the autoyast.xml file on the boot CD while the installation source is elsewhere? Thanks, LDB

2 2

SLES9-SP3: SATA-driver not installed?
by suselist＠nlsn.nu 06 Jan '06

06 Jan '06

Hi everyone, I have successfully installed SLES9 SP2 via autoyast and are now switching to SLES9 SP3 install-source. Install goes fine, but after reboot I get: Waiting for device /dev/sda5 to appear: .....not found -- device nodes: <list of devices, no sda> No root device found: exiting to bin/sh It a machine with SATA-controller, and it seems like SATA-support is missing from the installed kernel? I read in the docs that the system with drivers has changed, now a custom initrd is built during install. Seems like it cannot identify the correct driver for the SATA-card and does add that to the initrd. How do I add this driver myself during install? ( Or, is this really another problem? ) Regards Daniel

5 4

keytable
by Frank Steiner 06 Jan '06

06 Jan '06

Hi, since 10.0 the keytable-keyword doesn't work in the info file. I used to have Language: de_DE Display: color Keytable: us in the info file that we put into the initrd. But during the installation, the keymap is german when I switch to e.g. Alt+F2. Also lilo is using german as default keymap after installation. Grepping for "keytable" in the files from the autoyast2(-installation) rpms, I don't find any entry for keytable anymore (except for the docu which still lists the option, while there used to be some like AutoinstLinuxrc.ycp: keytable = settings["keytable"]:""; for earlier versions, like on SuSE 9.0. Has this option been dismissed? Any way to set the keyboard and the language independently? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 9