Hello,
I have a 100 node cluster running Suse SLES Enterprise 9 with a modified Kernel (to support the Lustre Filesystem). I updated some of the cluster nodes to Suse SLES SP2. I took a golden image of the nodes using si_getimage. When I tried using si_updateclient to push out the image to nodes with SP1, it seemed to muck them up. Before pushing the image, uname -r gives a kernel name of 2.6.xxx.smp. After pushing the image , uname -r yields: 2.6.xxxx.lustre.xxx. It thinks that it is running the old kernel again. I also tried putting SP2 on a node, then pushing the image, thinking that maybe it was too much for system imager to handle the SP2 update, but this also failed. After rebooting any of the nodes with the new image, they lose their network interfaces. Dmesg tells me that the system can't find the NIC driver module, which is named tg3.ko. After looking in /lib/modules, I found that the image process somehow blows away a /drivers/directory in the /lib/modules/... Directory. Any ideas what's going on? Is there a --exclude I can use to get around this? Regards, Anthony ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
