Mailinglist Archive: opensuse-autoinstall (83 mails)

< Previous Next >
SUSE 9.1 Autoyast woes
  • From: Peter Schwenk <schwenk@xxxxxxxxxxxxx>
  • Date: Tue, 25 May 2004 13:28:14 +0000 (UTC)
  • Message-id: <FBA45859-AE4E-11D8-8A57-0003939CCFDE@xxxxxxxxxxxxx>
Hello:

I'm new to SUSE and autoyast. I've been using Red Hat for years now and automating installations with their Kickstart scheme. Since Fedora, I've been looking for a better distribution, and SUSE, once installed, seems to be very nice. Everything's there and already nicely configured for my average user.

Autoyast, however, is eluding me. So far, I realize that I need a floppy disk with an 'info' file to load the right network interface modules and assign the IP address, etc. I've generated an autoinst.xml file using the 'autoyast' module of yast2, but the install seems to ignore my disk partitioning directives. I want yast to wipe the drive of existing partitions and make 4 new ones: /, swap, /boot, and /home. Here's an excerpt from my autoinst.xml file that's supposed to be doing this:

<partitioning config:type="list">
<drive>
<device>/dev/hda</device>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
<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>
<size>10000</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">ext2</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>
<size>auto</size>
</partition>
<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>
<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>/home</mount>
<partition_id config:type="integer">131</partition_id>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>

While yast is running, it looks like it is trying to partition, format, and mount the partitions, but it isn't successful. After choosing "Continue" several times, the installation proceeds, but the ramdisk (I'm assuming) is the place where stuff is getting installed. The filesystem fills up after a short time, and yast asks if I want to abort the installation, which I do.

Does anyone have any ideas why my partitioning scheme isn't being accepted? A manual install from the same NFS source seems to proceed without incident. The manual install asks for confirmation of several kernel modules, mostly USB stuff but there's a couple dm_* modules loaded by yast, too.

The machine is a Gateway E-1800 (Celeron 1300MHz, IDE disks, 256MB RAM, on-board Intel graphics).


--
- Peter A. Schwenk | Mathematical Sciences
- schwenk@xxxxxxxxxxxxx | University of Delaware
- (302) 831-0437 | Newark, DE 19716-2553 USA


< Previous Next >