My colleague indicates that he's seen the "unable to mount root fs, kernel panic" message before when trying to install Mandrake on IBM x330/335s, and that he worked around it by building a different kernel. Perhaps it's a kernel problem and not a configuration one. Does OSCAR simply use the kernel which the head node uses? If so, and if the kernel distributed with Man 9.2 works on both the head and the cluster nodes, then at least it should be clear that it's not a kernel problem... I think. :)
I'll have to do a little more work on this. Any more suggestions from anyone else would be appreciated. I'm not completely against RH9.0, but the fact that it's no longer supported by RedHat anymore, coupled with the fact that we're a Mandrake shop around here and have more expertise in Mandrake, makes me want to try and get it working with Mandrake. Of course, I could always try RH using one of the cluster nodes as a head node and go from there.
Any suggestions from anyone still appreciated.
Jason
On Dec 10, 2003, at 4:18 PM, Bernard Li wrote:
Hey Jason:
Wait a sec... you're right, the '/' wasn't necessary. :-)
Frankly I can't think of anything else... you did try to install Mandrake 9.2 (not through OSCAR, just from the installation CD) on the client nodes and they all boot up fine?
I hate to say this but I think the fastest way (I think) for you to bring up the cluster is to use RedHat 9.0 instead of Mandrake 9.2. I say this because we have been using RH9.0 with OSCAR 3.0 without much problems, and at least I could much easily troubleshoot your problem (since we have it set up here).
Sorry couldn't be of much more help...
Cheers,
Bernard
Jason Hlady wrote:
Hi Bernard and others,
Thanks for the reply. I did try changing that to /swap in the /var/lib/systemimager/scripts/oscarimage.master file, but this didn't work. Furthermore, on my head node:
[EMAIL PROTECTED] scripts]# cat /etc/fstab
/dev/sda1 / ext3 defaults 1 1
none /dev/pts devpts mode=0620 0 0
/dev/sda8 /home ext3 defaults 1 2
none /mnt/cdrom supermount dev=/dev/hdc,fs=udf:iso9660,ro,--,iocharset=iso8859-1 0 0
none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,codepage=850,umask=0,iocharset=iso8859 -1,sync 0 0
none /proc proc defaults 0 0
/dev/sda7 /usr ext3 defaults 1 2
/dev/sda6 /var ext3 defaults 1 2
/dev/sda5 swap swap defaults 0 0
Note that there appears to be no requirement for a preceding / in a working machine. :-(
The pertinent section of my /var/lib/systemimager/scripts/oscarimage.master file is:
### BEGIN generate new fstab file from autoinstallscript.conf ###
cat <<'EOF' > /a/etc/fstab
/dev/sda5 swap swap defaults 0 0
/dev/sda1 / ext3 defaults 1 2
/dev/sda7 /biobits ext3 defaults 1 2
/dev/sda6 /usr ext3 defaults 1 2
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
none /proc proc defaults 0 0
none /dev/pts devpts defaults 0 0
nfs_oscar:/home /home nfs rw 0 0
EOF
### END generate new fstab file from autoinstallscript.conf ###
Any other ideas out there?
Jason
On Dec 10, 2003, at 3:00 PM, Bernard Li wrote:Hi Jason:
Jason Hlady wrote:
/dev/sda5 2048 swap
You are missing a '/' - it should be /swap
:-)
I've already gone through the process of assigning MACs to nodes, and it seems that is where you decide which image you are going to use. However, if I want to try changing images to try and get one that works, what is the correct procedure? Am I correct that the partition configuration file (as shown above) is ONLY consulted during the "build image" portion of imaging? What should I do to try and build a variety of images and try each of them until I get the one that works? What should I do to check precisely which image (with what partition table, etc.) got sent to the node (particularly when it's broken in kernel panic mode)?
You are correct - the partition table is only read when you choose to 'build image' - so generally what I do is I would modify the systemimager script (more on this later) manually.
The script that you want to modify is in /var/lib/systemimager/scripts/<imagename>.master - just do a search for 'fstab' and you will be at the spot where you want to change partition information.
So for your case, you just need to modify the script, add the '/' back, re-image the node and it should be good to go.
Cheers,
Bernard
-------------- Jason Hlady, B. Sc., M. Sc. (Chem), Adv. Cert. (Comp. Sci.) Programmer/Analyst (Bioinformatics Specialist) U of Saskatchewan, Bioinformatics Research Laboratory (BIRL) [EMAIL PROTECTED] (306) 966-2075
-------------- Jason Hlady, B. Sc., M. Sc. (Chem), Adv. Cert. (Comp. Sci.) Programmer/Analyst (Bioinformatics Specialist) U of Saskatchewan, Bioinformatics Research Laboratory (BIRL) [EMAIL PROTECTED] (306) 966-2075
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users