From: Büchmann H. <en...@bu...> - 2012-07-27 11:38:02
|
Dear Marianne, Sorry for the late response - summer and all that. I have encountered something similar, and if I remember correctly, then si_prepareclient is rather picky with the namin of the initrd file (to be packed with the kernel for later installs). si_prepareclient looks for matching file names in /boot/, but it is unaware of the newer forms "initramfs*", and only looks for "initrd*". (Can't remember if you also needthe output from uname -r in there.) My personal hack is simply to copy (or hard link) the "real" initramfs to something, which will be recognized, e.g. like: cp -av initramfs-$(uname -r).img initrd-to-sisuite-$(uname -r).img (Also, I have to remove any /boot/initrd-$(uname -r)kdump.img, but you do not seem to have such). Best, Bjarne PS: The actual (wrong) checking for si_prepareclient goes on in the sub "is_initrd" in UseYourOwnKernel.pm. On 18-07-2012 8:13, Marianne Rieckmann wrote: > Hi, > I have installed SystemImager as instructed by the manual (systemimager-manual-4.1.6.pdf) > using the RPM Based Distributions from the install script. With an image server on one machine > and a golden client on another. This is on a IBM blade cluster using CentOS6.2, with all the > DHCP, Domain name, tftp services working. > > When using the si_prepareclient, all looks good until the final part; > <pre> > This client is ready to have its image retrieved. You must now run > the "si_getimage" command on your imageserver. > > Your client has been successfully prepared. Boot kernel (copied from > this Linux distribution) and an initrd.img (generated by the > initrd_template package) can be found in /etc/systemimager/boot. > > Automatically create configuration file for systemconfigurator: > >> /etc/systemconfig/systemconfig.conf > FATAL: unable to detect an initrd for "2.6.32-220.17.1.el6.x86_64"! > WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by systemconfigurator) > </pre> > > I think it is looking for one of the files in the /boot directory? > <pre> > [root@gouda6 boot]# ls > config-2.6.32-220.17.1.el6.x86_64 symvers-2.6.32-220.17.1.el6.x86_64.gz > config-2.6.32-220.el6.x86_64 symvers-2.6.32-220.el6.x86_64.gz > efi System.map-2.6.32-220.17.1.el6.x86_64 > grub System.map-2.6.32-220.el6.x86_64 > initramfs-2.6.32-220.17.1.el6.x86_64.img vmlinuz-2.6.32-220.17.1.el6.x86_64 > initramfs-2.6.32-220.el6.x86_64.img vmlinuz-2.6.32-220.el6.x86_64 > </pre> > > What do I need to do to get this to work? > Regards, > Marianne. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > |