Mailinglist Archive: opensuse-autoinstall (64 mails)

[Marcel Ritter <Marcel.Ritter@xxxxxxxxxxxxxxxxxxxx>]

On Mon, 19 Aug 2002, Anas Nashif wrote:

> * Marcel Ritter <Marcel.Ritter@xxxxxxxxxxxxxxxxxxxx> [Aug 19. 2002 13:10]:
> > Hi again!
> >
> > By adding a separate /boot partition the situation inproves.
> > (lilo is installed), however the install location (I specified "mbr" here)
> > was ignored (Yast had chosen "hda5" instead).
> >
> > So I changed "mbr" do "hda" and it worked...
> >
> > ... I think there's still some work to do - and some documentation to
> > write :-)
>
> The autoyast2 documentation is not a replacement for other
> documentation. The issue with the /boot partition is described
> elsewhere. The autoyast2 documentation does not cover these topics, as
> it is part of the general installation also.

It may be necessary/useful to add a boot partition, however my problems
cannot be solved by adding /boot (I tried). The problem seems to be
related to the updated module yast2-module-autoinst-2.5.27-0 (hope this
one is the latest). I tried the same setup with the original install
filesystem (suse/images/root) and it works fine. As soon as I replace
yast2-module-autoinst I can't get my system to reboot: I always end up
with some LILO error message (currently LI, but I've seen other, too)

Partitioning:

<partitioning config:type="list">
  <drive>
     <device>/dev/sda</device>
     <partitions config:type="list">
        <partition>
          <crypt_fs config:type="boolean">false</crypt_fs>
          <crypt_key/>
          <filesystem config:type="symbol">ext2</filesystem>
          <filesystem_id config:type="integer">131</filesystem_id>
          <format config:type="boolean">true</format>
          <mount>/boot</mount>
          <size>50</size>
          <type>Linux native</type>
        </partition>
        <partition>
          <crypt_fs config:type="boolean">false</crypt_fs>
          <crypt_key/>
          <filesystem config:type="symbol">swap</filesystem>
          <filesystem_id config:type="integer">131</filesystem_id>
          <format config:type="boolean">true</format>
          <mount/>
          <size>512</size>
          <type>Linux native</type>
        </partition>
        <partition>
          <crypt_fs config:type="boolean">false</crypt_fs>
          <crypt_key/>
          <filesystem config:type="symbol">ext3</filesystem>
          <filesystem_id config:type="integer">131</filesystem_id>
          <format config:type="boolean">true</format>
          <mount>/</mount>
          <size>max</size>
          <type>Linux native</type>
        </partition>
     </partitions>
     <use>all</use>
   </drive>
 </partitioning>


Bootmanager:

<bootloader>
  <activate config:type="boolean">false</activate>
  <linear config:type="boolean">false</linear>
  <parameters/>
</bootloader>



If I got it right, the problem lies in the call to
/usr/lib/YaST2/bin/dolilo:

According to y2log in the original version

'/usr/lib/YaST2/bin/dolilo / -m /dev/sda -a /dev/sda1'

is called. The same setup with the newer packages calls

'/usr/lib/YaST2/bin/dolilo / -m '

The option -m should be followed by the boot device if I got the comments
in dolilo right. Doesn't seem to work with the new code ...

I tried to attach the according y2log files but they exceeded the 20000
byte limit on this mailing list. If you'd like to have them simply tell me
...

Hope you can help.

Ciao,
  Marcel

> Anas
> --
> Anas Nashif <nashif@xxxxxxxx>, SuSE Linux AG
> Montreal (Laval), Canada

----
Marcel Ritter
Linux Betreuer
Regionales Rechenzentrum Erlangen
----
Unix _IS_ user friendly... It's just selective about who its friends are.