Hello,

I was able to fix the problem by adding a modprobe.conf to the image and 
running the sequence Martin suggested. I left out the lines containing the 
amd74xx module. For some reason the kernels involved in installing oscar 
recognize the amd74xx module even though it is compiled directly in the new 
kernels. Anyway I am able to rsync the slave nodes now. I do however, face a 
new problem.

The ssh system is broken. The automatic ssh logon between nodes is 
nonfunctional. I am not sure if this is an issue with the current release of 
oscar. 

Also, as reported before the Select Packages to Install is nonfunctional.

Thank you for the help in solving this problem,

Chris Pawela
 

-----Original Message-----
From: geoffroy.val...@free.fr [mailto:geoffroy.val...@free.fr] 
Sent: Friday, July 17, 2009 3:14 PM
To: Pawela, Christopher
Cc: oscar-devel
Subject: Re: [Oscar-devel] Testing Latest Release

Pawela,

Can you send me the logs related to the installation of selected packages? I do 
not think i received a full log to try to fix the problem (or i missed it).

Also, can you try to add the "alias scsi_hostadapter1 amd74xx " line to the 
/etc/modprobe.conf of your image (what Martin suggested).

Regards,

----- "Christopher Pawela" <cpaw...@mcw.edu> a écrit :

> I did copy a modprobe.conf file to the /etc image directory on the
> head node. Here it is.
> 
> alias scsi_hostadapter sata_nv
> alias scsi_hostadapter1 usb-storage
> alias peth0 tg3
> alias eth0 tg3
> 
> The modprobe.conf for the head node is
> 
> alias scsi_hostadapter sata_nv
> alias scsi_hostadapter1 usb-storage
> alias peth0 tg3
> alias eth0 tg3
> alias eth1 tg3
> 
> The only difference is that I disabled the second ethernet card on the
> slave nodes. I am completely stumped. I was able to get the mkinitrd
> to run in the post_install script suggested on this forum by Thilo by
> adding --omit-scsi-drivers. The problem is that the slave nodes can't
> seem to find the hard disk directory upon bootup. This is very strange
> because upon bootup the drivers and modules seem to load with no
> issues.
> 
> Any further suggestions would be helpful.
> 
> I also ran into the issue described by Mark were the Select Packages
> to Install Failed on the oscar_wizard.
> 
> Thank you for your prompt response,
> 
> Christopher Pawela
> 
> Is there anyway to snapshot a bootlog from a nonfunctioning slave node
> so that I can properly post it on this forum?
> 
> 
> -----Original Message-----
> From: geoffroy.val...@free.fr [mailto:geoffroy.val...@free.fr]
> Sent: Fri 7/17/2009 2:42 PM
> To: oscar-de...@lists.sourceforge.net
> Cc: bern...@vanhpc.org; Pawela, Christopher
> Subject: Re: [Oscar-devel] Testing Latest Release
>  
> Bernard,
> 
> This is supposed to be done automatically if you are using the
> "unstable" repo but you have a good point: Pawela can you give us the
> content of /etc/modprobe.conf for both the headnode and the image?
> 
> On my side, i will double-check i did not forgot to create one of the
> new RPMs.
> 
> Regards,
> 
> ----- "Bernard Li" <bern...@vanhpc.org> a écrit :
> 
> > Hi Christopher:
> > 
> > On Fri, Jul 17, 2009 at 11:24 AM, Pawela,
> Christopher<cpaw...@mcw.edu>
> > wrote:
> > 
> > > I tested the latest OSCAR release from last night. I ran into the
> > same problem as before. For some reason the amd74xx module is not
> > available during the mkinitrd process. I tried the fix from Thilo
> as
> > well with the same failure.  The slave nodes still kernel panic
> upon
> > reboot after installation.
> > >
> > > Mounting root filesystem.
> > > mount: could not find filesystem '/dev/root
> > > Setting up other filesystems.
> > > Setting up new root fs
> > > setuproot: moving /dev failed: No such file or directory
> > > no fstab.sys, mounting internal defaults
> > > setuproot: error mount /proc: No such file or directory
> > > setuproot: error mount /sys: No such file or directory
> > > Switching to new root and running init.
> > > unmounting old /dev
> > > unmounting old /proc
> > > unmounting old /sys
> > > switchroot: mount failed: No such file or directory
> > >
> > > I really really don't want to have to install redhat el5 on one
> of
> > the slave nodes and then move the files over to the boot directory.
> > The head node and the server node use the same hardware. I don't
> > understand why this is happening? The cluster is in a blade server
> > like case and I don't have good access to the slave nodes to
> install
> > redhat. I am still searching for a work around with amd74xx. I
> assume
> > the problem is with the kernel. Apparently this module is now
> > incorporated in the kernel and was not before??? Is there a
> workaround
> > in the systemimager code?
> > 
> > I think the issue is with /etc/modprobe.conf.  Have you tried to
> copy
> > a known working modprobe.conf to your image/imaged node and boot it
> > up?
> > 
> > Cheers,
> > 
> > Bernard
> > 
> >
> ------------------------------------------------------------------------------
> > Enter the BlackBerry Developer Challenge  
> > This is your chance to win up to $100,000 in prizes! For a limited
> > time, 
> > vendors submitting new applications to BlackBerry App World(TM)
> will
> > have
> > the opportunity to enter the BlackBerry Developer Challenge. See
> full
> > prize  
> > details at: http://p.sf.net/sfu/Challenge
> > _______________________________________________
> > Oscar-devel mailing list
> > oscar-de...@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/oscar-devel

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Oscar-users mailing list
Oscar-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to