Hello, On Tuesday 19 February 2008 09:21, Robert Ashcraft wrote: > We had a similar problem (but had different headnode OS) and copying the > modprobe.conf file for the nodes into the image's /etc/ directory > allowed us to boot up. > > If your headnode is the same as the compute nodes, you can probably just > copy /etc/modprobe.conf (from headnode) to the image directory > (something like /var/lib/systemimager/images/<image_name>/etc/ ). Then > repeat the imaging procedure.
I copied the modprobe.conf from the master node to the compute nodes /etc after it failed to boot using rescue CD, and that didn't seem to help. I'll give your suggestion a try, but I'm just wondering if this is any different that what I've tried. BTW, I also tried changing the partitioning of the compute node to be just one root partition to simplify thing, and that didn't help either. Thanks. RDB > Hopefully this helps. > > Reuben D. Budiardja wrote: ... > > I use UYOK to install the client node as suggested in other thread here. > > The client seems to install the image just fine, but after reboot, it > > gets Kernel Panic, with messages like: > > > > mount: error 2 mount ext3 > > mount: error 6 mount none > > switchroot: mount failed: 22 > > Kernel panic âEUR" not syncing: Attempted to kill init! ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Oscar-users mailing list Oscar-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-users
