Dann,
It seems to be not executing the rsync before the chroot i.e

I added some echo's to the image.master as follows

*******************
echo "done 1"
rsync -av --numeric-ids $IMAGESERVER::$IMAGENAME/ /a/ || shellout
echo "done 2"
# Leave notice of which image is installed on the client
echo $IMAGENAME > /a/etc/systemimager/IMAGE_LAST_SYNCED_TO || shellout

chroot /a/ systemconfigurator --runboot || shellout
*************************
When I boot the client I get

done 1
@ERROR: chroot failed



dann frazier wrote:

> On Wed, Jan 21, 2004 at 11:32:02AM +0100, Vinodh Velusamy wrote:
> > I am having a problem when booting a client from cdrom. We are running
> >  SystemImager version 2.0.1. The boot process goes through creating the
> > partitions fine, but then gets the error: @ERROR: chroot failed.
> >
> > Before this message it says:
> >
> > Writing superblocks and filesystem accounting information : done
> >
> > This filesystem will be automatically checked every 23 mounts or 180
> > days, whichever comes first. Use tune2fs -c or -i to override.
>
> It seems like you sould've seen an image transfer in between the two.
> Check out your /var/lib/systemimager/scripts/<image>.sh file, and
> maybe add some debug echos.
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Sisuite-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/sisuite-users

--
Vinodh Velusamy               Ubizen
Software Engineer             We Secure e-Business

Phone  +32 16 28 73 14
Fax    +32 16 28 71 00        http://www.ubizen.com

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to