Ok, once you have a modprobe.conf file that you want to try, you have to make a copy of the file in systemimager's override directory.
First put the contents of the client node's modprobe.conf file in a file somewhere on the head node as root, lets call it /root/client_modprobe.conf. Then, if your image name is oscarimage you would do something like mkdir /var/lib/systemimager/overrides/oscarimage/etc cp /root/client_modprobe.conf /var/lib/systemimager/overrides/oscarimage/etc Then you use netbootmgr to set the boot action for your nodes to be install and reimage them. They should use the new modprobe.conf file instead of the default one systemimager makes when it reboots. If you named your image something besides oscarimage, just use that name instead of oscarimage in the example. There is not a particularly good reason to make a copy of the modprobe.conf file in /root, I just like to keep extra copies of things there so I remember what I have changed. On 3/27/07, Baldassi Maurizio <[EMAIL PROTECTED]> wrote: > > Hi, > > I have some questions about yor answer: > > 1) when you say 'boot the node of the fc5 install disk' do you mean the > client node (the one which crashed) or the head node? I booted the > client node in rescue mode from the first fc5 cd-rom and it succeeded > (the formerly installed system was mounted in /mnt/sysimage); I then > found a file modprobe.conf in /tmp (no other file with that name was > found) containing the following rows: > > alias eth0 e100 > alias scsi_hostadapter aic7xxx > alias scsi_hostadapter1 DAC960 > > then I copied it in the directory (in the head node) you suggested. > > 2) is that correct? > 3) if yes, should I repeat from start the whole installation process? > 4) the corrections I made to oscarimage.master and the other files are > to be kept? > > (after copying the file, I also tried to reboot the client node in > install mode, but booting the node after the imaging process yelded > again the same kernel panic - I then restarted the client node in rescue > mode and tried to reboot it after copying the file /tmp/modprobe.conf in > /mnt/sysimage/etc/modprobe.conf, unfortunately with no luck!) > > Best regards > > Maurizio Baldassi > Settore Innovazione Tecnologica > ARPA FVG - Direzione Centrale > tel.: 0432922691 - 3404979509 > > > -----Messaggio originale----- > Da: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Per conto di > [EMAIL PROTECTED] > Inviato: sabato 24 marzo 2007 20.11 > A: oscar-users@lists.sourceforge.net > Oggetto: Oscar-users Digest, Vol 10, Issue 40 > > Send Oscar-users mailing list submissions to > oscar-users@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/oscar-users > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Oscar-users digest..." > > > Today's Topics: > > 1. Re: kernel panic after client node local boot (Michael Edwards) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 23 Mar 2007 21:21:15 -0500 > From: "Michael Edwards" <[EMAIL PROTECTED]> > Subject: Re: [Oscar-users] kernel panic after client node local boot > To: oscar-users@lists.sourceforge.net > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > The modprobe.conf file which FC5 made for your nodes is probably > wrong, it isn't loading the storage drivers correctly and so the > kernel is crashing when it tries to reference them. If possible, boot > the node of the fc5 install disk and go into "rescue mode". If that > succeeds you just need to make a copy of the modprobe.conf file it > uses and put that in > > /var/lib/systemimager/overrides/etc/modprobe.conf > > SIS will use that file instead of its automatically generated version. > > If you know what modules it needs to load, you can of course just make > it by hand. :) > > On 3/23/07, Baldassi Maurizio <[EMAIL PROTECTED]> wrote: > > Hi everybody, > > > > I am trying to set up a small cluster using OSCAR version 5.0 on Linux > > Fedora Core 5 using i386 H/W architecture (I have got five - rather > aged > > and almost identical - NEC servers featuring a Pentium III running at > > 866 MHz, with a Mylex DAC960 RAID controller). > > > > I installed Fedora Core 5 on a server, then I downloaded OSCAR 5.0 > files > > and I started the installation of the head node. > > > > Everything worked fine up to (and including) step 6. I went into > > troubles when I started imaging of clients; the first problem I had > was > > the incorrect naming of partitions in the main client-autoinstall > script > > oscarimage.master. The script correctly created the partitions using > the > > device name /dev/rd/c0d0 and then tried to refer to them (for mke2fs > > etc.) as /dev/rd/c0d01, /dev/rd/c0d05 and so on. With these names > mke2fs > > failed regularly, so, after some investigations, I found that the real > > names of the partitions where /dev/rd/c0d0p1, /dev/rd/c0d0p5 etc. > (there > > where an extra 'p' between the device name and the partition number). > I > > then edited the script (which is included in the attached file > together > > with the logs) in order to reflect the correct partition naming. > > > > After these modifications, the script was able to correctly format > > partitions, but I got further errors - related to attempts of string > > concatenations using uninitialized values - when the script called the > > function 'run_post_install_scripts'. I then edited again the script, > > making further modifications related to the incorrect naming of the > > partitions (in the section where the string '/dev/hda' is modified in > > the files /etc/fstab etc. - you'll find comments I made by searching > for > > the string 'baldax'). For the same reason, I tried to edit the file > > systemconfig.conf too. > > > > After that, I rebooted the client again, and this time only two errors > > where left (you'll see them in the lines with a '** ==>' prepended in > > the file si_monitor.log included in the attachment), both two related > to > > concatenating uninitialized values. > > > > Anyway I saw the GRUB splash and the menu, and after few seconds the > > system started to boot; but after about two or three screens of > > lightning-fast system messages (see attached file > LastBootLogLines.txt), > > it ended up with a kernel panic. > > > > I tried to search through the lists for a similar problem, but I had > no > > results. > > > > Thanks for your kind attention > > > > Best regards > > > > Maurizio Baldassi > > Settore Innovazione Tecnologica > > ARPA FVG - Direzione Centrale > > tel.: 0432922691 - 3404979509 > > > > > > > ------------------------------------------------------------------------ > - > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > > opinions on IT & business topics through brief surveys-and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE > V > > _______________________________________________ > > Oscar-users mailing list > > Oscar-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/oscar-users > > > > > > > > > > ------------------------------ > > ------------------------------------------------------------------------ > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE > V > > ------------------------------ > > _______________________________________________ > Oscar-users mailing list > Oscar-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oscar-users > > > End of Oscar-users Digest, Vol 10, Issue 40 > ******************************************* > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Oscar-users mailing list > Oscar-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oscar-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-users mailing list Oscar-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-users
