opensubscriber
   Find in this group all groups
 
Unknown more information…

s : sisuite-users@lists.sourceforge.net 27 August 2009 • 12:48AM -0400

[sisuite-users] Kernel panic: No init found. Try passing init= option to kernel
by RICHARD GREEN

REPLY TO AUTHOR
 
REPLY TO GROUP






Hi everyone, I have successfully created a golden client and retrieved it to my
systemimager (3.7.5-1) server, I have done this in the past with few problems.
The hardware that I am placing the image on is the exact same hardware that
I got the image off of.  At first I was not using the correct kernel initrd.img so I took Bernard's advice and used UYOK by

# si_prepareclient --server servername --no-rsyncd --my-modules

Then copied the kernel and imnitrd from

/etc/systemimager/boot/ in my golden client

copy to tftpboot and set it up in my pxe boot settings, When I boot a node to load the image, it now generates a new message (see error message below)

  error (device cobd(117,0)): ext2_read_inode: unable to read inode block
- inode=16385, block=32772
Kernel panic: No init found.  Try passing init= option to kernel.

I thought maybe it was just I didn't have ram disk size high enough, but I don't believe that's it. I have the correct image, hard ware, kernel, initrd.img. I have imaged different heterogenous systems this way before. Any suggestions as to what I might be missing? Any help folks have is muchly appreciated.

Thanks
-Rich



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
sisuite-users mailing list
sisuite-users@list...
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.