[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sisuite-users
Subject:    Re: [Sisuite-users] systemimager disaster- please help!
From:       Sean Dague <sean () dague ! net>
Date:       2003-12-06 14:13:35
[Download RAW message or body]

On Fri, Dec 05, 2003 at 11:10:11PM -0700, dann wrote:
> On Fri, Dec 05, 2003 at 09:03:40PM -0600, Luke Palmer wrote:
> > kjournald starting.  Commit interval 5 seconds
> > EXT3-fs: corrupt root inode, run e2fsck
> > mount: error 22 mounting ext3
> > pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> > umount /initrd/proc failed: 2
> > Freeing unused kernel memory: 276k freed
> > Kernel panic: No init found.  Try passing init= option to the kernel.
> > 
> > Now, this many hard disks could not have failed at once.  Systemimager
> > did something very bad.  Does anyone have any idea what?
> 
> does your new kernel use an initrd?
> systemconfigurator attempts to generate an initrd for the target hardware
> during post install.
> 
> if your new kernel does not use an initrd, comment out the initrd line
> in your bootloader (lilo/grub) config file.  if it does use initrd, and you
> did generate an initrd that works on your golden client, sc may be 
> generating a broken one.  
> 
> try editing your master script & changing '--configsi' to
> '--confignet --runboot'.  i think that will stop it from regenerating an
> initrd.

From the man page:

--configsi
Configure those things that SystemImager needs.  Currently this is exactly
the same as "--confighw --confignet --runboot".

it *does not* attempt to generate an initrd as there isn't enough info to do
it (i.e. what kernel do you want it for, etc).

You can fix your problem by doing one of the following:

1) add kernel stanzas in systemconfig.conf via the man page, and add
configrd & configboot to the list of options.  This will autogenerate your 
initrd during install

2) build the initrd manually on your golden client, adjust your lilo.conf or
grub.conf as required, "make sure it works", then capture this image and
distribute it to all your clients.

It would be nice to add logic to systemconfigurator to try to auto setup
kernels if required, but that isn't there.  Because of this you need to
manually add the kernel stanzas if you want auto initrd generation.

	-Sean

-- 
__________________________________________________________________

Sean Dague                                       Mid-Hudson Valley
sean at dague dot net                            Linux Users Group
http://dague.net                                 http://mhvlug.org

There is no silver bullet.  Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
__________________________________________________________________

[Attachment #3 (application/pgp-signature)]
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[prev in list] [next in list] [prev in thread] [next in thread]