Hi Bernard, Thanks for the quick update. It works fine for the rsync connection problems and it started really imaging. Great!
But I still got the following error during the imaging. ---------------<Error log on the client node>---------------- mkdir -p /a/sys || shellout mount sysfs /a/sys -t sysfs -o defaults || shellout Evaluating image size. Report task started. Quietly installing image... /rsync -aHS --exclude=lost+found/ --exclude=/proc/* --numeric-ids 129.79.246.46::oscarimage/ /a/ -|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-|/-Report task stopped. | stop_spinner rsync -av --numeric-ids 129.79.246.46::overrides/oscarimage/ /a/ rsync -av --numeric-ids 129.79.246.46::overrides/peach1/ /a/ rsync: link_stat "/peach1/." (in overrides) failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1532) [receiver=3.0.0pre6] Override directory peach1 doesn't seem to exist, but that may be OK. Editing files for actual disk configuration... /dev/sda -> /dev/sda /etc/fstab /etc/systemconfig/systemconfig.conf mount /dev /a/dev -o bind || shellout Detecting systemconfigurator: --- systemconfigurator - 2.2.11 Written by Sean Dague, Donghwa John Kim, et al. Copyright (C) 2001-2002 International Business Machines This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. --- 2007-12-3 14:30:51 [Network :: Line 58] Setting up network type Network::LinuxConf 2007-12-3 14:30:51 [Initrd :: Line 69] Testing for ramdisk type 'Initrd::SuSE' 2007-12-3 14:30:51 [Initrd :: Line 69] Testing for ramdisk type 'Initrd::RH' 2007-12-3 14:30:51 [Initrd :: Line 71] Setting up ramdisk type 'Initrd::RH' 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 94] Setting up kernel: for root device: /dev/sda2 2007-12-3 14:30:51 [Initrd :: Line 69] Testing for ramdisk type 'Initrd::Debian' 2007-12-3 14:30:51 [Boot::YaBoot :: Line 93] YaBoot executable is set to: . 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::YaBoot 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::Iseries 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::EFI 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::Elilo 2007-12-3 14:30:51 [Boot::Lilo :: Line 76] Lilo executable set to: . 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::Lilo 2007-12-3 14:30:51 [Boot::Grub :: Line 132] grub supports --no-floppy argument. 2007-12-3 14:30:51 [Boot::Grub :: Line 107] Grub executable set to: . 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::Grub 2007-12-3 14:30:51 [Boot::Grub :: Line 151] bootloader = 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::Palo 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::Aboot BOOTDEV option under [BOOT] section ignored. 2007-12-3 14:30:51 [Boot::ZIPL :: Line 74] ZIPL executable set to: . 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::ZIPL 2007-12-3 14:30:51 [Boot :: Line 66] Attempting to setup Boot::Kboot Error: None of the following bootloaders were successfully setup on your system: YaBoot,Iseries,EFI,Elilo,Lilo,Grub,Palo,Aboot,ZIPL,Kboot Killing off running processes. write_variables <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is the SystemImager autoinstall system ---------------<Error log on the client node>---------------- Looks like that it requires overrides/peach1 which apparently does not exist. Any clue of why this thing happens? Regards, - DongInn Bernard Li wrote: > Hi DongInn: > > On 12/3/07, Bernard Li <[EMAIL PROTECTED]> wrote: > >> I've changed CONFIG_FEATURE_TAR_GNU_EXTENSIONS=y in the busybox >> config, am now rebuilding systemimager 4.0.x branch and will get >> DongInn to retest. > > Latest SystemImager 4.0.x branch snapshot is available here: > > http://therealms.org/oss/systemimager/snapshots/ > > Please re-test and let us know whether this works for you... > > Thanks, > > Bernard > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Oscar-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/oscar-devel ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
