RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs

[Bernard Li]

Hi Bela:   The RPMs have the same names, but they are built at different times (with slightly different code).  This is my bad so from now on I will give them unique identifiers such that we can easily identify which version you are using.   I guess the only difference between your installation and my installation is that I do NOT run si_prepareclient etc. to create a golden image, but instead I use systeminstaller to create the image.  Also, I am using the stock SystemImager kernel/initrd.img (provided by the i386boot-standard package) but for your case, you are probably using RHEL3.1's kernel + an autogenerated initrd.img (via si_prepareclient/UseYourOwnKernel).   I am not sure how much of a difference this is, but I will test this after hearing your results on Tuesday.   Cheers,   Bernard From: [EMAIL PROTECTED] on behalf of B. Erdelyi Sent: Fri 27/01/2006 23:11 To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Message trimmed so it will post.     Bernard,   I will download the RPMs and reinstall again, but this is the same Oscar site I downloaded from in the first place.  I wouldn’t expect a miracle.   I will however not be able to do it until Tuesday, which is the earliest I can return to the site where the systems are located.   The OS being imaged is RHEL 3.1, and the image was created following step by step the procedures in the manual (prepareclient, getimage, etc).  I don’t have a copy of the manual with me but the steps described therein where followed and worked fine.  The only departure was that target computer names created by the process were named sequentially creating incorrect softlinks and DHCP configuration entries.  I had to modify the dhcp configuration file and also created new softlinks pointing to the master image file.  These deviations work fine because the autoinstall process finds the proper scripts and downloads them correctly.  I see them on the target machine upon failing the autoinstall.   By the way the image server OS is also RHEL 3.1.   In my opinion what is happening is related to the environment or environment variables being created.  The si_mkautoinstallcd call is not passing parameters correctly to its script, which is being passed over the environment.  Then the autoinstall process does not pass the variable to the mount command either.  Since you tested the same RPMs and it works correctly, then by elimination it has to be related to environment settings.  We did have SI 3.4.1 previously downloaded as tar files and installed; perhaps there are some garbage left behind from that version.  I tried to remove it as best as I could before installing v3.6.3-1.     Thanks for all the help! Bela   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Friday, January 27, 2006 7:53 PM To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs   Hi Bela:   I tested this last night and it works perfectly, I have no idea why it does not work on your system.   Just so we are on the same page - can you download the RPMs from here and try again?   http://www.bcgsc.ca/downloads/oscar/systemimager/   If you are still having problems with these set of RPMs, then I will test these exact same ones and see if I have the same problems.   What OS are you trying to image and how did you create the golden image?   Cheers,   Bernard