From awray@nc.rr.com Fri Jan 31 04:16:09 2003 From: Andy Wray To: autoinstall@lists.opensuse.org Subject: chroot scripts and mkinitrd Date: Fri, 31 Jan 2003 04:16:09 +0000 Message-ID: <000101c2c8df$77a1cd70$6401a8c0@zippy> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2820660917277634989==" --===============2820660917277634989== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit 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 that if possible). Thanks, --Andy --===============2820660917277634989==-- From nashif@suse.de Fri Jan 31 04:26:24 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] chroot scripts and mkinitrd Date: Fri, 31 Jan 2003 04:26:24 +0000 Message-ID: <20030131042549.GA5571@suse.de> In-Reply-To: <000101c2c8df$77a1cd70$6401a8c0@zippy> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6682214562101031677==" --===============6682214562101031677== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Andy, Try adding tihs to the bootloader resource and let me know if it works for yo= u: .... ..... mptbase mptscsih ..... .... the only problem that might arise is the right ordering of the modules which might be significant in the initrd. Anas * Andy Wray [Jan 31. 2003 05:16]: > 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 /. >=20 > 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. >=20 > 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 that > if possible). >=20 >=20 > > > > > >=20 >=20 > Thanks, >=20 > --Andy >=20 >=20 > --=20 > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com --=20 Anas Nashif , SuSE Linux AG Montreal (Laval), Canada --===============6682214562101031677==-- From awray@nc.rr.com Fri Jan 31 05:04:51 2003 From: Andy Wray To: autoinstall@lists.opensuse.org Subject: RE: [suse-autoinstall] chroot scripts and mkinitrd Date: Fri, 31 Jan 2003 05:04:51 +0000 Message-ID: <000001c2c8e6$3f32c3c0$6401a8c0@zippy> In-Reply-To: <20030131042549.GA5571@suse.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9081508824199813172==" --===============9081508824199813172== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit 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? Thanks again, --Andy -----Original Message----- From: Anas Nashif [mailto:nashif(a)suse.de] Sent: Thursday, January 30, 2003 11:26 PM To: Andy Wray Cc: suse-autoinstall(a)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: .... ..... mptbase mptscsih ..... .... the only problem that might arise is the right ordering of the modules which might be significant in the initrd. Anas * Andy Wray [Jan 31. 2003 05:16]: > 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 that > if possible). > > > > > > > > > > Thanks, > > --Andy > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif , SuSE Linux AG Montreal (Laval), Canada -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com --===============9081508824199813172==-- From nashif@suse.de Fri Jan 31 05:27:46 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] chroot scripts and mkinitrd Date: Fri, 31 Jan 2003 05:27:46 +0000 Message-ID: <20030131052738.GB5571@suse.de> In-Reply-To: <000001c2c8e6$3f32c3c0$6401a8c0@zippy> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3040245769028604325==" --===============3040245769028604325== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit * Andy Wray [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(a)suse.de] > Sent: Thursday, January 30, 2003 11:26 PM > To: Andy Wray > Cc: suse-autoinstall(a)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: > > .... > > ..... > > mptbase > mptscsih > > > ..... > > .... > > the only problem that might arise is the right ordering of the modules > which > might be significant in the initrd. > > Anas > > * Andy Wray [Jan 31. 2003 05:16]: > > 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 > that > > if possible). > > > > > > > > > > > > > > > > > > > > Thanks, > > > > --Andy > > > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > -- > Anas Nashif , SuSE Linux AG > Montreal (Laval), Canada > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif , SuSE Linux AG Montreal (Laval), Canada --===============3040245769028604325==-- From awray@nc.rr.com Fri Jan 31 06:54:21 2003 From: Andy Wray To: autoinstall@lists.opensuse.org Subject: RE: [suse-autoinstall] chroot scripts and mkinitrd Date: Fri, 31 Jan 2003 06:54:21 +0000 Message-ID: <000001c2c8f5$8c65a6d0$6401a8c0@zippy> In-Reply-To: <20030131052738.GB5571@suse.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8180596205343368570==" --===============8180596205343368570== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Well, I thought this was a good idea, but it didn't work. I changed the reboot option under the "general" settings section from "true" to "false" and changed the script from chroot to post and added a mk_initrd line at the end, but it still rebooted and the post script never ran. I guess the next thing would be to get the updated mkinitrd script onto the installation source somehow... Thanks again, --Andy -----Original Message----- From: Anas Nashif [mailto:nashif(a)suse.de] Sent: Friday, January 31, 2003 12:28 AM To: Andy Wray Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] chroot scripts and mkinitrd * Andy Wray [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(a)suse.de] > Sent: Thursday, January 30, 2003 11:26 PM > To: Andy Wray > Cc: suse-autoinstall(a)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: > > .... > > ..... > > mptbase > mptscsih > > > ..... > > .... > > the only problem that might arise is the right ordering of the modules > which > might be significant in the initrd. > > Anas > > * Andy Wray [Jan 31. 2003 05:16]: > > 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 > that > > if possible). > > > > > > > > > > > > > > > > > > > > Thanks, > > > > --Andy > > > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > -- > Anas Nashif , SuSE Linux AG > Montreal (Laval), Canada > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif , SuSE Linux AG Montreal (Laval), Canada --===============8180596205343368570==-- From nashif@suse.de Mon Feb 3 01:44:56 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] chroot scripts and mkinitrd Date: Mon, 03 Feb 2003 01:44:56 +0000 Message-ID: <20030203014454.GE9016@suse.de> In-Reply-To: <000001c2c8f5$8c65a6d0$6401a8c0@zippy> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5191401680142421323==" --===============5191401680142421323== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit * Andy Wray [Jan 31. 2003 07:54]: > Well, I thought this was a good idea, but it didn't work. I changed the > reboot option under the "general" settings section from "true" to > "false" and changed the script from chroot to post and added a mk_initrd > line at the end, but it still rebooted and the post script never ran. > > I guess the next thing would be to get the updated mkinitrd script onto > the installation source somehow... You have to use true to force booting the installed system directly after inital phase. Anas > > > Thanks again, > > --Andy > > > > -----Original Message----- > From: Anas Nashif [mailto:nashif(a)suse.de] > Sent: Friday, January 31, 2003 12:28 AM > To: Andy Wray > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] chroot scripts and mkinitrd > > * Andy Wray [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(a)suse.de] > > Sent: Thursday, January 30, 2003 11:26 PM > > To: Andy Wray > > Cc: suse-autoinstall(a)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: > > > > .... > > > > ..... > > > > mptbase > > mptscsih > > > > > > ..... > > > > .... > > > > the only problem that might arise is the right ordering of the modules > > which > > might be significant in the initrd. > > > > Anas > > > > * Andy Wray [Jan 31. 2003 05:16]: > > > 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 > > that > > > if possible). > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > --Andy > > > > > > > > > -- > > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- > > Anas Nashif , SuSE Linux AG > > Montreal (Laval), Canada > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > -- > Anas Nashif , SuSE Linux AG > Montreal (Laval), Canada -- Anas Nashif , SuSE Linux AG Montreal (Laval), Canada --===============5191401680142421323==-- From awray@nc.rr.com Mon Feb 3 02:14:34 2003 From: Andy Wray To: autoinstall@lists.opensuse.org Subject: RE: [suse-autoinstall] chroot scripts and mkinitrd Date: Mon, 03 Feb 2003 02:14:34 +0000 Message-ID: <000401c2cb2a$06ff3a10$6401a8c0@zippy> In-Reply-To: <20030203014454.GE9016@suse.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0933437308714351136==" --===============0933437308714351136== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Anas, Actually I finally got it to work a different way. I just changed the chroot script to copy the new mkinitrd from the nfs mount (and didn't have to run mkinitrd afterwards--from some of the debug that I was doing it looked like the chroot scripts were run before the initrd was setup): cp -f /var/adm/mount/mkinitrd /mnt/sbin Don't know why I didn't try that to begin with, but everything's simple in hindsight I guess... Thanks again for all your help, --Andy -----Original Message----- From: Anas Nashif [mailto:nashif(a)suse.de] Sent: Sunday, February 02, 2003 8:45 PM To: Andy Wray Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] chroot scripts and mkinitrd * Andy Wray [Jan 31. 2003 07:54]: > Well, I thought this was a good idea, but it didn't work. I changed the > reboot option under the "general" settings section from "true" to > "false" and changed the script from chroot to post and added a mk_initrd > line at the end, but it still rebooted and the post script never ran. > > I guess the next thing would be to get the updated mkinitrd script onto > the installation source somehow... You have to use true to force booting the installed system directly after inital phase. Anas > > > Thanks again, > > --Andy > > > > -----Original Message----- > From: Anas Nashif [mailto:nashif(a)suse.de] > Sent: Friday, January 31, 2003 12:28 AM > To: Andy Wray > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] chroot scripts and mkinitrd > > * Andy Wray [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(a)suse.de] > > Sent: Thursday, January 30, 2003 11:26 PM > > To: Andy Wray > > Cc: suse-autoinstall(a)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: > > > > .... > > > > ..... > > > > mptbase > > mptscsih > > > > > > ..... > > > > .... > > > > the only problem that might arise is the right ordering of the modules > > which > > might be significant in the initrd. > > > > Anas > > > > * Andy Wray [Jan 31. 2003 05:16]: > > > 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 > > that > > > if possible). > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > --Andy > > > > > > > > > -- > > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- > > Anas Nashif , SuSE Linux AG > > Montreal (Laval), Canada > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > -- > Anas Nashif , SuSE Linux AG > Montreal (Laval), Canada -- Anas Nashif , SuSE Linux AG Montreal (Laval), Canada --===============0933437308714351136==--