I have attached the log file for what was a completed installation to a compute node. After compute node reboot, it boots up and then I just get a blinking cursor.
Thank you for the help. On Thu, Nov 6, 2008 at 1:24 AM, Bernard Li <[EMAIL PROTECTED]> wrote: > On Wed, Nov 5, 2008 at 7:03 PM, <[EMAIL PROTECTED]> wrote: > > > Nope, I know for a fact that there was no OS on the compute node's drive > > before I started. The image installed on the machine. For example, The > > /etc/hosts is correct for what I imaged. I can use boot cd to get onto > > machine, use chroot (to /mnt/sysimage/) and then nsf mount /home on the > > oscar master node and see files on the head node. I would not be able to > do > > that if the image had not installed. > > > > The major hardware difference is the hard drive (4TB raid on master node > and > > 73 GB SAS on compute node). > > > > I guess I will simply set up oscar from another fresh OS install on one > of > > the compute nodes, then image the other compute nodes (with UYOK). > > What/where will the major differences be on the image from the raid head > > node and the compute node temporarily made to be a head node? Will the > only > > difference important differences show up in the > > /var/lib/systemimager/images/<image_name> directory? > > Your log clearly shows that SystemImager cannot detect your HD, > therefore it will not be able to rsync anything over. So I am > confused how your HD got imaged at all. Perhaps you pasted a > different log file, I'm not sure. What should've happened after > "enumerate_disks" is "DISKS=1" (meaning SystemImager detected you have > 1 disk, instead you get DISK=0 meaning SystemImager cannot detect any > disks) and it will start partitioning your disk according to your > .master script and start rsyncing your image over. > > Anyway, if your image server has different hardware than your compute > node, you should do a lsmod comparison of the loaded modules between > your image server and compute node, and attempt to load the missing > storage modules on your image server. Once they are loaded with > modprobe, re-run UYOK kernel/initrd generation, that should create a > ramdisk with the suitable storage adaptor (SAS) modules loaded which > should hopefully work with your client imaging. > > If you are to use a compute node as a headnode, you will not be able > to use your original headnode to control your compute nodes, i.e. with > any manual hackery. The created image (in > /var/lib/systemimager/images) should be identical, the only difference > should be the UYOK initrd (which when generated on your compute node > should contain the correct storage modules). > > Regards, > > Bernard >
install-log6.gz
Description: GNU Zip compressed data
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
