All, I discovered that systemimager-4.0.4 has been tagged one year ago but never officially announced. I am creating RPMs for that version, there are a lot of bug fixes, that may solve some of the issues we are currently facing with RHEL/CentOS.
I will send an email on the two mailing lists (oscar-devel and oscar-user) as soon as everything will be ready for RHEL/CentOS. Most certainly later today. Regards, ----- "Mitchell Baker" <mdba...@rose-hulman.edu> a écrit : > When I was researching RHEL about it, I found some old threads where > it > was mentioned that it was compiled into the kernel itself. After I > got > it working I have not looked into it further. As so as I get some > time > I am going to see where things are missing if I can. > > --Mitch > > On Thu, 2009-07-16 at 13:42 -0400, Pawela, Christopher wrote: > > Thank you for the prompt response, > > > > There has to be a simpler solution. My head node doesn't even use > this amd74xx driver and it has the exact same hardware as the slave > nodes. Using the more /proc/modules command I don't see it listed on > the head node. I tried using the UYOK option in the Network Setup but, > that did not solve the problem. There has to be a way to prevent the > systemimager kernel from identifying this module or bypassing it. > > > > Thank you, > > > > Chris Pawela > > > > > > > > -----Original Message----- > > From: Mitchell Baker [mailto:mdba...@rose-hulman.edu] > > Sent: Thu 7/16/2009 11:53 AM > > To: Pawela, Christopher > > Cc: oscar-users@lists.sourceforge.net > > Subject: RE: [Oscar-users] Problems after node installation > > > > I had to just manually install RHEL 5 on one of my client system. > Then > > I took the files from /boot > > > > config-2.6.18-128.el5 > > initrd-2.6.18-128.el5.img > > symvers-2.6.18-128.el5.gz > > System.map-2.6.18-128.el5 > > vmlinuz-2.6.18-128.el5 > > > > Copied them onto the head node in the image I created for the > clients in > > /var/lib/systemimager/images/(imagename). > > > > On the reboot of the client after imaging, I also had to stop the > boot, > > exit the kernel line to add selinux=0 to prevent another panic. > > > > After that I just added that to the /boot/grub.conf file for > further > > boots. > > > > This is not a nice, clean or even OSCAR recomended way to do it, but > it > > was the only way I found at the time, and I was under the gun to get > the > > cluster up and running. A better solution is being worked... > > > > --Mitch > > > > On Thu, 2009-07-16 at 12:41 -0400, Pawela, Christopher wrote: > > > Hello, > > > > > > I tried Thilo's solution and I have run into the exact same > problem you are describing. The amd74xx driver is missing. Could you > provide more details on how you worked around this problem? > > > > > > Thank you, > > > > > > Chris > > > > > > > > > > > > -----Original Message----- > > > From: Mitchell Baker [mailto:mdba...@rose-hulman.edu] > > > Sent: Thu 7/16/2009 7:23 AM > > > To: oscar-users@lists.sourceforge.net > > > Subject: Re: [Oscar-users] Problems after node installation > > > > > > Please let me know how this works for you. I ran into the same > problem > > > and have been working with this matter. RHEL 5.3 system. I was > not able > > > to build a good on the client systems due to missing dependencies > for > > > the amd74xx driver. Maybe what Thilo has will work. I had to use > a > > > kernel and initrd create on one of the client nodes and placed in > the > > > oscar environment for distribution. > > > > > > Please let me know if this solution works for you. > > > > > > --Mitch > > > > > > On Thu, 2009-07-16 at 04:54 -0400, Thilo Bangert wrote: > > > > Hi Christoph, > > > > > > > > "Pawela, Christopher" <cpaw...@mcw.edu> said: > > > > > Hello, > > > > > > > > > > I have successfully deployed the new version of oscar on > redhat el 5.0 > > > > > with no problems using the oscar_wizard. However, after I > rsync the > > > > > nodes I get this message upon bootup at the node. > > > > > > > > > > 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 > > > > > kernel panic - not syncing: Attempted to kill init! > > > > > > > > > > I am using the exacty same hardware on the head node and the > slave > > > > > nodes. The redhat kernel has no problems booting the head > node. I used > > > > > the correct scsi.disk for making the node image. (I am using > serial-ata > > > > > drives "sda") > > > > > > > > > > > > > thanks for reporting the issue. it has been reported before, but > its good > > > > to know that it hits other people as well. > > > > > > > > the problem is, that the initrd isnt being (re)generated after > the image > > > > has been deployed. > > > > > > > > i have created a post-install script which will do this for you. > see > > > > http://surl.dk/63y/ > > > > or > > > > http://www.mail-archive.com/oscar- > > > > us...@lists.sourceforge.net/msg08015.html > > > > > > > > > Any suggestions on how to proceed will be appreciated. > > > > > > > > a) extract the script from the message above > > > > b) place it into /var/lib/systemimager/scripts/post-install > > > > c) make sure your controller driver is defined as > scsihostadapter alias > > > > in /etc/modprobe.conf in the image > > > > d) redeploy your cluster > > > > > > > > please report back your experiences with this workaround. > > > > (it was created for centos, and should work fine on rhel 5) > > > > > > > > this may get you running, while the real fix is in the works. > > > > > > > > kind regards > > > > Thilo > > > > > > > -- > > > Mitchell Baker <mdba...@rose-hulman.edu> > > > Rose-Hulman Institute of Technology > > > > > > > > > > ------------------------------------------------------------------------------ > > > 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 > > > > > -- > > Mitchell Baker <mdba...@rose-hulman.edu> > > Rose-Hulman Institute of Technology > > > > > -- > Mitchell Baker <mdba...@rose-hulman.edu> > Rose-Hulman Institute of Technology > > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
