So I think SIS creates a ramdisk after installing the node, and whatever it's incorrectly identifying the first time (causing you to insmod the module manually), I think it's also incorrectly identifying for the initrd. If you can modify the script so the node doesn't umount stuff and restart after installation, you could interactively create the ramdisk with the correct SCSI module. Once figured out, you might want to put the correction into the install script itself.
Jeremy
At 09:52 PM 10/8/2003, Sundaram A wrote:
Dear Jeremy,
I have installed OSCAR-2.3 with Zeon Processor + Adaptec AIC 79xx SCSI. The master node working fine. When I add a slaves using auto install floppy it gives following error.
Error No 1:
partition table for /dev/sda: Error : Could not stat device /dev/sda - No such file or directory Parted -s --/dev/sda mklabel msdos || shellout Error : Could not stat device /dev/sda - No such file or directory
after this error it goes to bash shell #.
>From the shell I have loaded the scsi module using #insmod aic79xx, It manages to install the SCSI HDD with AIC7901a driver, after that I have executed the #/scripts/oscarnodexx.sh from the scripts directory. It went everything fine like transferring files from the master node. After the completion when I reboot the node it gives an VFS Kernel panic message. The detailed message is
Error No 2:
kmod : failed to execute /sbin/modprobe -s -k block-major-8, errno=2 VFS : cannot open root device "806" or 08:06 please append a correct "root=" boot option kernel panic : VFS : unable to mount root fs on 08:06
At this point the node just hungs there, need to hard reboot to boot the machine again.
As well I have tried to boot the machine using LAN, here it gives tftpboot timeout. When I look into the /var/log/messages it shows the following.
Error No 3:
Oct 8 09:17:05 oscarnode1 dhcpd: dhcpd startup succeeded Oct 8 09:17:06 oscarnode1 dhcpd: DHCPDISCOVER from 00:07:e9:05:7a:12 via eth1 Oct 8 09:17:06 oscarnode1 dhcpd: DHCPOFFER on 192.168.168.4 to 00:07:e9:05:7a:12 via eth1 Oct 8 09:17:14 oscarnode1 dhcpd: DHCPREQUEST for 192.168.168.4 (192.168.168.1) from 00:07:e9:05:7a:12 via eth1 Oct 8 09:17:14 oscarnode1 dhcpd: DHCPACK on 192.168.168.4 to 00:07:e9:05:7a:12 via eth1 Oct 8 01:17:14 oscarnode1 in.tftpd[3892]: RRQ from 192.168.168.4 filename pxelinux.0 Oct 8 01:17:14 oscarnode1 in.tftpd[3892]: tftp: client does not accept options Oct 8 01:17:14 oscarnode1 in.tftpd[3893]: RRQ from 192.168.168.4 filename pxelinux.0 Oct 8 01:17:14 oscarnode1 in.tftpd[3894]: RRQ from 192.168.168.4 filename pxelinux.cfg/C0A8A804 Oct 8 01:17:14 oscarnode1 in.tftpd[3894]: sending NAK (1, File not found) to 192.168.168.4 Oct 8 01:17:14 oscarnode1 in.tftpd[3895]: RRQ from 192.168.168.4 filename pxelinux.cfg/C0A8A80 Oct 8 01:17:14 oscarnode1 in.tftpd[3895]: sending NAK (1, File not found) to 192.168.168.4 Oct 8 01:17:14 oscarnode1 in.tftpd[3896]: RRQ from 192.168.168.4 filename pxelinux.cfg/C0A8A8 Oct 8 01:17:14 oscarnode1 in.tftpd[3896]: sending NAK (1, File not found) to 192.168.168.4 Oct 8 01:17:14 oscarnode1 in.tftpd[3897]: RRQ from 192.168.168.4 filename pxelinux.cfg/C0A8A Oct 8 01:17:14 oscarnode1 in.tftpd[3897]: sending NAK (1, File not found) to 192.168.168.4 Oct 8 01:17:14 oscarnode1 in.tftpd[3898]: RRQ from 192.168.168.4 filename pxelinux.cfg/C0A8 Oct 8 01:17:14 oscarnode1 in.tftpd[3898]: sending NAK (1, File not found) to 192.168.168.4 Oct 8 01:17:14 oscarnode1 in.tftpd[3899]: RRQ from 192.168.168.4 filename pxelinux.cfg/C0A Oct 8 01:17:14 oscarnode1 in.tftpd[3899]: sending NAK (1, File not found) to 192.168.168.4 Oct 8 01:17:14 oscarnode1 in.tftpd[3900]: RRQ from 192.168.168.4 filename pxelinux.cfg/C0 Oct 8 01:17:14 oscarnode1 in.tftpd[3900]: sending NAK (1, File not found) to 192.168.168.4 Oct 8 01:17:14 oscarnode1 in.tftpd[3901]: RRQ from 192.168.168.4 filename pxelinux.cfg/C Oct 8 01:17:14 oscarnode1 in.tftpd[3901]: sending NAK (1, File not found) to 192.168.168.4 Oct 8 01:17:15 oscarnode1 in.tftpd[3902]: RRQ from 192.168.168.4 filename pxelinux.cfg/default Oct 8 01:17:15 oscarnode1 in.tftpd[3903]: RRQ from 192.168.168.4 filename message.txt Oct 8 01:17:15 oscarnode1 in.tftpd[3903]: sending NAK (1, File not found) to 192.168.168.4 Oct 8 01:17:20 oscarnode1 in.tftpd[3904]: RRQ from 192.168.168.4 filename kernel Oct 8 01:17:20 oscarnode1 in.tftpd[3905]: RRQ from 192.168.168.4 filename initrd.img
I hope it will usefull to track the issue, if need any more info about my installation errors please mail me.
Best Regards Sundaram. A
-----Original Message----- From: Jeremy Enos [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 9:12 AM To: Sundaram A Cc: [EMAIL PROTECTED] Subject: Re: FW: FW: [Oscar-users] Node Installation Failure.
Sundaram- Please keep the list copied on all transactions so we can track this issue and get you all the help necessary. It would be helpful to know what is
coming out on the node consoles. This is sounding like it could be an SI kernel problem.
Jeremy
At 08:01 PM 10/8/2003, Sundaram A wrote: >Dear Jeremy, > >Can you help me on it too I have tired many methods I am unable to >solve this issue. > >I have tried but still it is nor working, is there any other method to >install except using either auto install floppy nor network install. > >I thing the SCSI AIC79xx was not loaded properly in all the >installation methods. If I install the node using RedHat Installation >disk what are the things we have to do manually. I hope we need to >manually edit some configuration files in /etc/ and some other files >please refer them to me it will really helps me a lot to fix this >issue. > >Thanks & Best Regards >Sundaram. A > > >-----Original Message----- >From: Frank Crawford [mailto:[EMAIL PROTECTED] >Sent: Wednesday, October 08, 2003 11:21 AM >To: Sundaram A >Subject: RE: FW: [Oscar-users] Node Installation Failure. > > >Sundaram, > Yes, NAK means that tftpd didn't find the file, and it looks >like pxelinux.0 found everything it needed. So, the problem does lie >with the kernel it downloaded. (The NAKs are for a range of >configuration files, which all mean different things, but it eventually
>finds `default'). > > Can you plug a monitor into the slave and see what messages >come up during the boot. Hopefully it will give a better idea of why >it can't load the image, e.g. corrupt binary, truncated, etc. > >Frank > >On Wed, 2003-10-08 at 11:50, Sundaram A wrote: > > Hi Frank, > > > > I have checked the refered folders, I do have all the files you > > mentioned. As well I noticed the log file is shows bellow. What does
> > means NAK (1, file not found) from 192.168.168.4. I this due to this
> > only I am not able to add the node. Please view the attached file > > messages.txt for my log file output. > > > > Thanks & Best Regards > > Sundaram. A > > > > > > -----Original Message----- > > From: Frank Crawford [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, October 08, 2003 7:49 AM > > To: Sundaram A > > Subject: RE: FW: [Oscar-users] Node Installation Failure. > > > > > > Sundaram, > > In /usr/share/systemimager/boot/i386/standard you should have: > > > > boel_binaries.tar.gz > > config > > kernel > > initrd.img > > > > > > In /tftpboot you should have: > > > > kernel (same as in the systemimager directory) > > initrd.img (again the same one) > > pxelinux.0 > > > > plus the directories > > > > pxelinux.cfg (contains the files default and message.txt) rpm > > (contains all the RPMs, but isn't used during booting) > > > > > > The thing to look at is /var/log/messages and check for both >dhcpd > > and tftpd entries related to the client boot. It will probably show
> > what is missing. In particular, if you don't have pxelinux.0, then > > you would get the image failure message you saw. That file comes > > out of the syslinux package and the original can be found in > > /usr/lib/syslinux > > > > Frank > > > > On Tue, 2003-10-07 at 19:17, Sundaram A wrote: > > > Hi Frank Crawford, > > > > > > I am booting using network boot and I have the following files in > > > /usr/share/systemimager/boot/i386/standard > > > > > > boel_binaries.tar.gz and > > > config > > > > > > And in /tftpboot/ folder I have all the rpms from the RH 9.0 disks
> > > and > > > > > the files you sent to me earlier is kernel and initrd.img. > > > > > > Thanks & Best Regards > > > Sundaram. A > > > > > > > > > -----Original Message----- > > > From: Frank Crawford [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, October 07, 2003 12:44 PM > > > To: Sundaram A > > > Subject: RE: FW: [Oscar-users] Node Installation Failure. > > > > > > > > > Sundaram, > > > First off, are you doing a CD or a network boot? Secondly, > > > what > > > > > files do you have in /var/systemimager/boot/i386/standard > > > directory? > > > > Also, what files are in /tftpboot (if you are using network > > > booting)? > > > > > > Frank > > > > > > On Tue, 2003-10-07 at 14:34, Sundaram A wrote: > > > > Dear Frank Crawford, > > > > > > > > I have tried and now I am unable to boot the slave at all. At > > > > the boot > > > > > > > prompt it give unable to find image error. > > > > > > > > Thanks & Best Regards > > > > Sundaram. A > > > > > > > > > > > > -----Original Message----- > > > > From: Frank Crawford [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, October 07, 2003 10:04 AM > > > > To: Sundaram A > > > > Subject: RE: FW: [Oscar-users] Node Installation Failure. > > > > > > > > > > > > *********************** > > > > Warning: Your file, newPXEboot.tgz, contains more than 20 files > > > > after decompression and cannot be scanned. > > > > ***********-*********** > > > > > > > > > > > > Sundaram, > > > > Attached is a tar file, which you should extract to > > > > /usr/share/systemimager/boot/i386/standard/ (maybe backing up > > > > the things there before hand). > > > > > > > > Also, you should copy kernel and initrd.img to /tftpboot. > > > > > > > > If these work, then just use it, if not, let me know and we > > > > can > > > look > > > > at it further. > > > > > > > > Frank > > > > > > > > On Tue, 2003-10-07 at 11:01, Sundaram A wrote: > > > > > Hi Frank Crawford, > > > > > > > > > > Thanks for your information if it is a kernel issue how to > > > > > update the kernel, Can you send me the updated kenel as well > > > > > some notes to > > > update > > > > > > > > > it. > > > > > > > > > > Thanks & Best Regards > > > > > Sundaram. A > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: Frank Crawford [mailto:[EMAIL PROTECTED] > > > > > Sent: Monday, October 06, 2003 8:02 PM > > > > > To: Sundaram A > > > > > Cc: [EMAIL PROTECTED] > > > > > Subject: Re: FW: [Oscar-users] Node Installation Failure. > > > > > > > > > > > > > > > Sundaram, > > > > > The problem is most likely the boot kernel and > > > > > modules, >used > > > > > for > > > > the > > > > > tftpboot, etc, doesn't support your current hardware. If you > > > > > want, I can send you an updated kernel, etc, that may work for
> > > > > you. > > > > > > > > > > Frank > > > > > > > > > > On Mon, 2003-10-06 at 18:52, Sundaram A wrote: > > > > > > Dear All, > > > > > > > > > > > > Here is the detailed error message while booting, > > > > > > > > > > > > kmod : failed to execute /sbin/modprobe -s -k block-major-8,
> > > > > > errno=2 VFS : cannot open root device "806" or 08:06 please > > append > > > > > > > > > a correct > > > > > > > > > > "root=" boot option kernel panic : VFS : unable to mount > > > > > > root fs on 08:06 > > > > > > > > > > > > Is this due to the incompatible of SCSI mod for my Ultra > > > > > > SCSI 320 card > > > > > > > > > > > ? when I try with Ultra SCSI 160 is working fine as well as > > > > > > with IDE machines. Please help me to solve this. > > > > > > > > > > > > Thanks & Best Regards > > > > > > Sundaram. A > > > > > > > > > > > > > > > > > > ____________________________________________________________ > > > > > > __ > > > > > > __ > > > > > > __ > > > > > > __ > > > > > > __ > > > > > > > > > > > > "This email is confidential and may be privileged. If you > > > > > > are > > > > > > > not the > > > > > > > > > > > intended recipient, please delete it and notify us > > > > > > immediately; you should not copy or use it for any purpose, > > > > > > nor disclose its contents > > > > > > > > > > to any other person. Thank you." > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: [EMAIL PROTECTED] > > > > > > [mailto:[EMAIL PROTECTED] On Behalf > > > > > > Of Sundaram > > > > > > > > > > > A > > > > > > Sent: Friday, October 03, 2003 5:15 PM > > > > > > To: [EMAIL PROTECTED] > > > > > > Subject: [Oscar-users] Node Installation Failure. > > > > > > > > > > > > > > > > > > Dear All, > > > > > > > > > > > > I have installed my cluster with OSCAR-2.3 with Zeon > > > > > > Processor > > > > > > + Adaptec AIC 79xx SCSI. The master node working fine > > > > > > + without > > > > > > any > > > > issue. > > > > > > > > > > > When I add a slaves using the auto install floppy it gives > > > > > > an error message as bellow. > > > > > > > > > > > > > > > > > > partition table for /dev/sda: > > > > > > Error : Could not stat device /dev/sda - No such file or > > > > > > directory > > > > > > > > > Parted -s --/dev/sda mklabel msdos || shellout Error : Could
> > > > > > not > > > > stat > > > > > > device /dev/sda - No such file or directory > > > > > > > > > > > > after this error it goes to bash shell. > > > > > > > > > > > > From the shell I have loaded the scsi module using insmod, > > > > > > after > > > > > > > > that I have executed the oscarnodexx.sh from the scripts > > > > > > directory. It > > > > went > > > > > > > > > > > everything fine. After the completion when I reboot the node
> > > > > > it gives an VFS Kernel panic message. > > > > > > > > > > > > As well I have tried to boot the machine using LAN, here it > > > > > > gives tftpboot timeout. Have anyone had same kind of > > > > > > problem. > > > > > > > > > > > > Thanks & Best Regards > > > > > > Sundar > > > > > > > > > > > > ____________________________________________________________ > > > > > > __ > > > > > > __ > > > > > > __ > > > > > > __ > > > > > > __ > > > > > > "This email is confidential and may be privileged. If you are > > not > > > > the > > > > > > > > > > > intended recipient, please delete it and notify us > > > > > > immediately; you should not copy or use it for any purpose, > > > > > > nor disclose its contents > > > > > > > > > > to any other person. Thank you." > > > > > > >-- >ac3 >Suite G16, Bay 7, Locomotive Workshop Phone: 02 9209 4600 >Australian Technology Park Fax: 02 9209 4611 >Eveleigh NSW 1430
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
