Re: [suse-autoinstall] chroot scripts and mkinitrd

31 Jan 2003


      * Andy Wray <awray@nc.rr.com> [Jan 31. 2003 06:04]:
...
Anas,
Thanks very much for the prompt reply!  I did give this a shot, and as
you mentioned, order is important, and unfortunately it came out
backwards this way.  I suppose I could put an insmod=mptbase on the
kernel command line and see if this makes mptbase load first.  Is there
an easy way to setup the module dependencies from the autoyast
configuration file to fix this?
No. 
Does the machine boot before the installation is finished? You can force it to
continue and use the script you have written for chroot as postinstall and
recreate the mkinitrd.

Anas
...
Thanks again,
--Andy
-----Original Message-----
From: Anas Nashif [mailto:nashif@suse.de] 
Sent: Thursday, January 30, 2003 11:26 PM
To: Andy Wray
Cc: suse-autoinstall@suse.com
Subject: Re: [suse-autoinstall] chroot scripts and mkinitrd
Andy,
Try adding tihs to the bootloader resource and let me know if it works
for you:
....
<bootloader>
    .....
    <initrd_modules config:type="list">
        <module>mptbase</module>
        <module>mptscsih</module>
    </initrd_modules>
.....
</bootloader>
....
the only problem that might arise is the right ordering of the modules
which
might be significant in the initrd.
Anas
...
I'm trying to setup an unattended network install on a system with an
LSI
53c1030 SCSI controller running the boot drive.  There's a bug in the
SuSE 8.1 installer (SuSE 8.1 is what I'm trying to install) that
leaves
the mptbase driver that is needed by the mptscsih driver out of the
/etc/sysconfig/kernel file, and consequently it isn't included in the
initrd, so on the first bootup, mptscsih fails to load and the system
can't mount /.
To fix this I thought I'd run a chroot script to update the
/etc/sysconfig/kernel file.  However, although this file appears to
run
(there's output in the /var/adm/autoinstall/logs directory), the
/etc/sysconfig/kernel file remains unchanged.  Of course, even if this
worked, I'm not sure if it would fix the problem since I'm not sure if
the chroot scripts run before or after mkinitrd.
I've appended a portion of the autoyast installation file below.  Can
anyone help me with this?  (The alternative I have right now is that
there is a replacement mkinitrd on the SuSE ftp site provided as a
diskette image, but this doesn't help much for an unattended network
install.  mkinitrd appears to be part of the aaa_base package, so I
was
thinking I could replace it in that package, but I'd rather not do
* Andy Wray <awray@nc.rr.com> [Jan 31. 2003 05:16]:
that
...
if possible).
<scripts>
      <chroot-scripts config:type="list">
        <script>
          <filename>fixinitrd.sh</filename>
          <interpreter>shell</interpreter>
          <source>
<![CDATA[
#!/bin/sh
cat /mnt/etc/sysconfig/kernel #for debug
sed 's/mptscsih/mptbase mptscsih/g' /mnt/etc/sysconfig/kernel >
/mnt/etc/sysconfig/kernel.new
cat /mnt/etc/sysconfig/kernel.new #for debug
rm -f /mnt/etc/sysconfig/kernel
mv /mnt/etc/sysconfig/kernel.new /mnt/etc/sysconfig/kernel
cat /mnt/etc/sysconfig/kernel.new #for debug
]]>
          </source>
        </script>
      </chroot-scripts>
    </scripts>
Thanks,
--Andy
-- 
To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com
For additional commands, e-mail: suse-autoinstall-help@suse.com
-- 
Anas Nashif <nashif@suse.com>, SuSE Linux AG
Montreal (Laval), Canada
-- 
To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com
For additional commands, e-mail: suse-autoinstall-help@suse.com
-- 
Anas Nashif <nashif@suse.com>, SuSE Linux AG
Montreal (Laval), Canada