RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Hi Bela: It appears that you can mount the initrd.img and write to it: mv initrd.img initrd.img.gz gunzip initrd.img.gz mount -o loop initrd.img /mnt Modify the file, then gzip it. Hopefully it'll work. Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. ErdelyiSent: Fri 03/02/2006 20:22To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, My thinking is that for whatever reason this has to do with BusyBox and the environment that it is running on our machine. The options are not being passed on. To test this theory I wanted to hardwire the mount tmpfs command in the script to see what happens. I found the command in the functions script and replaced it with: mount tmpfs /new_root t tmpfs o size=2g,nr_inodes=2000,mode=777 || shellout Then I recreate the initrd.img with mkcramfs, gziped it and placed it in the standard flavor directory. Unfortunately, when I load from the new autoinstall cd I get an error indicating that the file system is read only and the rcS script cannot write a text file to it (line 41 of the rcS script). What am I doing wrong? I thought that the mode command with 777 would create the file system with full access. Is there other options being passed on via the $tmpfs_opt variable? Or should I be setting rw access somewhere else when I recreate the cramfs initrd.img? I would really like to test this out to see if by bypassing the parameter passing solves the issue. It may give you a better hint at what is going on. Any suggestions will be appreciated. Thanks, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Thursday, February 02, 2006 1:22 AMTo: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi Bela: If the tmpfs parameters were indeed passed onto the kernel, then the tmpfs size should be what you specified. I am really ata loss as to what has gone wrong... Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. ErdelyiSent: Wed 01/02/2006 16:08To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, I finally installed and tested the new build. One problem has gone away which is the setting of append options. By specifying the tmpfs size and inodes in the append string they now get passed on to the syslinux.cfg file without having to modify the script. However, the autoinstall still fails at the target with the same 99% full message. The tmpfs is created at the same size as before: 452788. The tmpfs size specification has no effect on this. I did not reinstall the client side of systemimager, only the server side and used the same golden master image file as previously created. I dont believe such should have any impact on this issue since the autoinstall cd is created on the server. I believe the problem lies with the initial linux kernel in memory. Let me know if I am missing anything and whether I should reinstall the client side and recreate the golden image. Thanks, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Saturday, January 28, 2006 3:09 AMTo: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs 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
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Bernard, Thanks, but to clarify: I basically did that, it was unzipped, mounted as a loop device, modified the function script and then I recreated initrd.img with mkcramfs then gzipped it. Are you saying that I should not create a cramfs file from the initrd directory? Otherwise the steps in your response are the same as performed. Thanks, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Friday, February 03, 2006 11:35 PM To: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi Bela: It appears that you can mount the initrd.img and write to it: mv initrd.img initrd.img.gz gunzip initrd.img.gz mount -o loop initrd.img /mnt Modify the file, then gzip it. Hopefully it'll work. Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. Erdelyi Sent: Fri 03/02/2006 20:22 To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, My thinking is that for whatever reason this has to do with BusyBox and the environment that it is running on our machine. The options are not being passed on. To test this theory I wanted to hardwire the mount tmpfs command in the script to see what happens. I found the command in the functions script and replaced it with: mount tmpfs /new_root t tmpfs o size=2g,nr_inodes=2000,mode=777 || shellout Then I recreate the initrd.img with mkcramfs, gziped it and placed it in the standard flavor directory. Unfortunately, when I load from the new autoinstall cd I get an error indicating that the file system is read only and the rcS script cannot write a text file to it (line 41 of the rcS script). What am I doing wrong? I thought that the mode command with 777 would create the file system with full access. Is there other options being passed on via the $tmpfs_opt variable? Or should I be setting rw access somewhere else when I recreate the cramfs initrd.img? I would really like to test this out to see if by bypassing the parameter passing solves the issue. It may give you a better hint at what is going on. Any suggestions will be appreciated. Thanks, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Thursday, February 02, 2006 1:22 AM To: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi Bela: If the tmpfs parameters were indeed passed onto the kernel, then the tmpfs size should be what you specified. I am really ata loss as to what has gone wrong... Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. Erdelyi Sent: Wed 01/02/2006 16:08 To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, I finally installed and tested the new build. One problem has gone away which is the setting of append options. By specifying the tmpfs size and inodes in the append string they now get passed on to the syslinux.cfg file without having to modify the script. However, the autoinstall still fails at the target with the same 99% full message. The tmpfs is created at the same size as before: 452788. The tmpfs size specification has no effect on this. I did not reinstall the client side of systemimager, only the server side and used the same golden master image file as previously created. I dont believe such should have any impact on this issue since the autoinstall cd is created on the server. I believe the problem lies with the initial linux kernel in memory. Let me know if I am missing anything and whether I should reinstall the client side and recreate the golden image. Thanks, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Saturday, January 28, 2006 3:09 AM To: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs 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
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Bernard, I just though of something that my have caused the read only problem. I may have gotten the initrd.img by extracting it from a mounted autoinstall iso image file which is an iso9660 ro file system rather than using the original initrd.img. I should perhaps retry this by starting with the initrd.img file under the standard boot i386 directory. Sorry for the premature post, hope this will fix the problem. Thanks, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. Erdelyi Sent: Saturday, February 04, 2006 12:35 AM To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, Thanks, but to clarify: I basically did that, it was unzipped, mounted as a loop device, modified the function script and then I recreated initrd.img with mkcramfs then gzipped it. Are you saying that I should not create a cramfs file from the initrd directory? Otherwise the steps in your response are the same as performed. Thanks, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Friday, February 03, 2006 11:35 PM To: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi Bela: It appears that you can mount the initrd.img and write to it: mv initrd.img initrd.img.gz gunzip initrd.img.gz mount -o loop initrd.img /mnt Modify the file, then gzip it. Hopefully it'll work. Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. Erdelyi Sent: Fri 03/02/2006 20:22 To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, My thinking is that for whatever reason this has to do with BusyBox and the environment that it is running on our machine. The options are not being passed on. To test this theory I wanted to hardwire the mount tmpfs command in the script to see what happens. I found the command in the functions script and replaced it with: mount tmpfs /new_root t tmpfs o size=2g,nr_inodes=2000,mode=777 || shellout Then I recreate the initrd.img with mkcramfs, gziped it and placed it in the standard flavor directory. Unfortunately, when I load from the new autoinstall cd I get an error indicating that the file system is read only and the rcS script cannot write a text file to it (line 41 of the rcS script). What am I doing wrong? I thought that the mode command with 777 would create the file system with full access. Is there other options being passed on via the $tmpfs_opt variable? Or should I be setting rw access somewhere else when I recreate the cramfs initrd.img? I would really like to test this out to see if by bypassing the parameter passing solves the issue. It may give you a better hint at what is going on. Any suggestions will be appreciated. Thanks, Bela
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Hi Bela: Don't think you need to "recreate initrd.img with cramfs" - once you mount it and modify the functions file, just umount initrd.img, then gzip it then rename it back to initrd.img and put it in /tftpboot (or re-make autoboot CD). If that doesn't work, then I recommend you install the SRPM, modify the source and rebuild the RPMs (this may take a while). Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. ErdelyiSent: Fri 03/02/2006 21:35To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, Thanks, but to clarify: I basically did that, it was unzipped, mounted as a loop device, modified the function script and then I recreated initrd.img with mkcramfs then gzipped it. Are you saying that I should not create a cramfs file from the initrd directory? Otherwise the steps in your response are the same as performed. Thanks, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Friday, February 03, 2006 11:35 PMTo: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi Bela: It appears that you can mount the initrd.img and write to it: mv initrd.img initrd.img.gz gunzip initrd.img.gz mount -o loop initrd.img /mnt Modify the file, then gzip it. Hopefully it'll work. Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. ErdelyiSent: Fri 03/02/2006 20:22To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, My thinking is that for whatever reason this has to do with BusyBox and the environment that it is running on our machine. The options are not being passed on. To test this theory I wanted to hardwire the mount tmpfs command in the script to see what happens. I found the command in the functions script and replaced it with: mount tmpfs /new_root t tmpfs o size=2g,nr_inodes=2000,mode=777 || shellout Then I recreate the initrd.img with mkcramfs, gziped it and placed it in the standard flavor directory. Unfortunately, when I load from the new autoinstall cd I get an error indicating that the file system is read only and the rcS script cannot write a text file to it (line 41 of the rcS script). What am I doing wrong? I thought that the mode command with 777 would create the file system with full access. Is there other options being passed on via the $tmpfs_opt variable? Or should I be setting rw access somewhere else when I recreate the cramfs initrd.img? I would really like to test this out to see if by bypassing the parameter passing solves the issue. It may give you a better hint at what is going on. Any suggestions will be appreciated. Thanks, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Thursday, February 02, 2006 1:22 AMTo: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi Bela: If the tmpfs parameters were indeed passed onto the kernel, then the tmpfs size should be what you specified. I am really ata loss as to what has gone wrong... Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. ErdelyiSent: Wed 01/02/2006 16:08To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, I finally installed and tested the new build. One problem has gone away which is the setting of append options. By specifying the tmpfs size and inodes in the append string they now get passed on to the syslinux.cfg file without having to modify the script. However, the autoinstall still fails at the target with the same 99% full message. The tmpfs is created at the same size as before: 452788. The tmpfs size specification has no effect on this. I did not reinstall the client side of systemimager, only the server side and used the same golden master image file as previously created. I dont believe such should have any impact on this issue since the autoinstall cd is created on the server. I believe the problem lies with the initial linux kernel in memory. Let me know if I am missing anything and whether I should reinstall the client side and recreate the golden image. Thanks, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Saturday, January 28, 2006 3:09 AMTo: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs 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.
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Bernard, I finally installed and tested the new build. One problem has gone away which is the setting of append options. By specifying the tmpfs size and inodes in the append string they now get passed on to the syslinux.cfg file without having to modify the script. However, the autoinstall still fails at the target with the same 99% full message. The tmpfs is created at the same size as before: 452788. The tmpfs size specification has no effect on this. I did not reinstall the client side of systemimager, only the server side and used the same golden master image file as previously created. I dont believe such should have any impact on this issue since the autoinstall cd is created on the server. I believe the problem lies with the initial linux kernel in memory. Let me know if I am missing anything and whether I should reinstall the client side and recreate the golden image. Thanks, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Saturday, January 28, 2006 3:09 AM To: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs 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
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Hi Bela: If the tmpfs parameters were indeed passed onto the kernel, then the tmpfs size should be what you specified. I am really ata loss as to what has gone wrong... Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. ErdelyiSent: Wed 01/02/2006 16:08To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, I finally installed and tested the new build. One problem has gone away which is the setting of append options. By specifying the tmpfs size and inodes in the append string they now get passed on to the syslinux.cfg file without having to modify the script. However, the autoinstall still fails at the target with the same 99% full message. The tmpfs is created at the same size as before: 452788. The tmpfs size specification has no effect on this. I did not reinstall the client side of systemimager, only the server side and used the same golden master image file as previously created. I dont believe such should have any impact on this issue since the autoinstall cd is created on the server. I believe the problem lies with the initial linux kernel in memory. Let me know if I am missing anything and whether I should reinstall the client side and recreate the golden image. Thanks, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Saturday, January 28, 2006 3:09 AMTo: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs 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
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
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. ErdelyiSent: Fri 27/01/2006 23:11To: sisuite-users@lists.sourceforge.netSubject: 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 wouldnt 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 dont 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 LiSent: Friday, January 27, 2006 7:53 PMTo: sisuite-users@lists.sourceforge.netSubject: 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
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Hi Bernard, Checked the CD's isolinux/syslinux.cfg, tmpfs values are not being appended. For each LABEL systemimager, kernel, linux and boel the APPEND entry contains the same line: APPEND vga=extended initrd=initrd.img root=/dev/ram I just issued the following commands: si_mkautoinstallcd --flavor standard --append tmpfs_size=2G tmpfs_nr_inodes=2000 --out-file test1.iso and si_mkautoinstallcd --append tmpfs_size=1g --out-file test2.iso Neither one created a correct syslinux.cfg. In reference to the 3.6.3 RPM build it has a date of Tue 10 Jan 2006 on host chip03.bcgsc.ca. It seems like I suspected that the tmpfs parameters are not being passed on. Now I see that this is happening at the mkautoinstallcd step. Is there a script that I can modify to correct this as a quick temporary fix? Thanks, Bela Hi Bela: Can you check the resulting CD's isolinux/syslinux.cfg to make sure that the append statements are actually there? It should look something like: LABEL systemimager KERNEL kernel APPEND vga=extended initrd=initrd.img root=/dev/ram tmpfs_size=2G tmpfs_nr_inodes=2000 I just tested my 3.6.3 RPMs and I can specify the tmpfs size without any problems, the command I used was: si_mkautoinstallcd --append tmpfs_size=2G tmpfs_nr_inodes=2000 --out-file /tmp/test.iso What's the build date of your 3.6.3 RPMs, mine are: Mon 09 Jan 2006 09:31:01 PM PST Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. Erdelyi Sent: Thu 26/01/2006 08:16 To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, No I am not using LVM, the source fstab shows: LABEL=/ / ext3 default 1 1 LABEL=/boot /boot ext3 default 1 2 none /devpts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs default 0 0 none /dev/proc proc default 0 0 /dev/cciss/c0d0p3 swap swap default 0 0 dev/cdrom /mnt/cdrom udf,iso9660 de/fd0 /mnt/floppy auto and sfdisk on the source shows three partitions p1, p2, p3 (/, /boot and swap) for /dev/cciss/c0d0, which size is 142253280. This corresponds with what SI tries to create as a dev/cciss/c0d0 of the same size on the target, with part1, part2, part3 components. Thanks, Bela P.S. My first transmissions dont seem to post to this list for some reason. The second time it works, dont know why. I apologize if this appears as a duplicate post but after 3 days I have not seen the post on the site. I do receive each message via email from the list however. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Saturday, January 21, 2006 7:33 PM To: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Are you using LVM? Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. Erdelyi Sent: Fri 20/01/2006 11:11 To: sisuite-users@lists.sourceforge.net Subject: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi, I am attempting an image install with si_mkautoinstallcd using SI 3.6.3. The tmpfs mounted as / is not large enough to create the entire file structure. The process ends with tmpfs 99% full. I have attempted to specify the append option to si_mkautoinstallcd with various values without success. The following parameters were specified: tmpfs_size=2G tmpfs_nr_inodes=2000 tmpfs_size=1g tmpfs_nr_inodes=1000 tmpfs_size=1g Regardless, tmpfs is created each time the same size with or without the mount options specified at: 452,788 1-k blocks. This is weird since the machine has 2G of RAM, I would expect to see a default tmpfs mount of about 1G. It seems that si_mkautoinstallcd is not passing the arguments to the mount tmpfs command. Is there a place in the scripts where I could explicitly specify the tmpfs mount options? I have searched the autoinstall and SystemImager::Server.pm scripts, but I cannot find the logical place to impact a change
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Bernard, The two (source and destination) machines are HP DL360 G4 with single i386 32-bit processor each. The image server is also a HP DL360 G3 i386 machine. I will take a look at the script, attempt to modify it and advice on how it goes. I will also generate the rpm qa output later and send it as you requested. Best, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Friday, January 27, 2006 2:28 PM To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Trimming my response so it goes through... From: Bernard Li Sent: Friday, January 27, 2006 11:26 To: 'sisuite-users@lists.sourceforge.net' Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs If you want to work around it, modify si_mkautoinstallcd. It's still weird that it doesn't work for you. Can you show me the output of 'rpm -qa | grep systemimager'? Also, are you on x86_64 or i386? I tested it on i386, perhaps you are on x86_64 and there is a bug in the code? Cheers, Bernard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. Erdelyi Sent: Friday, January 27, 2006 11:20 To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi Bernard, Checked the CD's isolinux/syslinux.cfg, tmpfs values are not being appended. For each LABEL systemimager, kernel, linux and boel the APPEND entry contains the same line: APPEND vga=extended initrd=initrd.img root=/dev/ram I just issued the following commands: si_mkautoinstallcd --flavor standard --append tmpfs_size=2G tmpfs_nr_inodes=2000 --out-file test1.iso and si_mkautoinstallcd --append tmpfs_size=1g --out-file test2.iso Neither one created a correct syslinux.cfg. In reference to the 3.6.3 RPM build it has a date of Tue 10 Jan 2006 on host chip03.bcgsc.ca. It seems like I suspected that the tmpfs parameters are not being passed on. Now I see that this is happening at the mkautoinstallcd step. Is there a script that I can modify to correct this as a quick temporary fix? Thanks, Bela Hi Bela: Can you check the resulting CD's isolinux/syslinux.cfg to make sure that the append statements are actually there? It should look something like: LABEL systemimager KERNEL kernel APPEND vga=extended initrd=initrd.img root=/dev/ram tmpfs_size=2G tmpfs_nr_inodes=2000 I just tested my 3.6.3 RPMs and I can specify the tmpfs size without any problems, the command I used was: si_mkautoinstallcd --append tmpfs_size=2G tmpfs_nr_inodes=2000 --out-file /tmp/test.iso What's the build date of your 3.6.3 RPMs, mine are: Mon 09 Jan 2006 09:31:01 PM PST Cheers, Bernard
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
And you cannot PXE-boot? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. ErdelyiSent: Friday, January 27, 2006 11:41To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, The two (source and destination) machines are HP DL360 G4 with single i386 32-bit processor each. The image server is also a HP DL360 G3 i386 machine. I will take a look at the script, attempt to modify it and advice on how it goes. I will also generate the rpm qa output later and send it as you requested. Best, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Friday, January 27, 2006 2:28 PMTo: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Trimming my response so it goes through... From: Bernard Li Sent: Friday, January 27, 2006 11:26To: 'sisuite-users@lists.sourceforge.net'Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs If you want to work around it, modify si_mkautoinstallcd. It's still weird that it doesn't work for you. Can you show me the output of 'rpm -qa | grep systemimager'? Also, are you on x86_64 or i386? I tested it on i386, perhaps you are on x86_64 and there is a bug in the code? Cheers, Bernard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. ErdelyiSent: Friday, January 27, 2006 11:20To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi Bernard, Checked the CD's isolinux/syslinux.cfg, tmpfs values are not being appended. For each LABEL systemimager, kernel, linux and boel the APPEND entry contains the same line: APPEND vga=extended initrd=initrd.img root=/dev/ram I just issued the following commands: si_mkautoinstallcd --flavor standard --append "tmpfs_size=2G tmpfs_nr_inodes=2000" --out-file test1.iso and si_mkautoinstallcd --append "tmpfs_size=1g" --out-file test2.iso Neither one created a correct syslinux.cfg. In reference to the 3.6.3 RPM build it has a date of Tue 10 Jan 2006 on host chip03.bcgsc.ca. It seems like I suspected that the tmpfs parameters are not being passed on. Now I see that this is happening at the mkautoinstallcd step. Is there a script that I can modify to correct this as a quick temporary fix? Thanks, Bela Hi Bela: Can you check the resulting CD's isolinux/syslinux.cfg to make sure that the append statements are actually there? It should look something like:LABEL systemimagerKERNEL kernelAPPEND vga=extended initrd=initrd.img root=/dev/ram tmpfs_size=2G tmpfs_nr_inodes=2000 I just tested my 3.6.3 RPMs and I can specify the tmpfs size without any problems, the command I used was: si_mkautoinstallcd --append "tmpfs_size=2G tmpfs_nr_inodes=2000" --out-file /tmp/test.iso What's the build date of your 3.6.3 RPMs, mine are: Mon 09 Jan 2006 09:31:01 PM PST Cheers, Bernard
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
I tried that in the beginning but encountered some issues with the NICs, which I need to resolve. I figured I will work on that later once I determined that systemimager is the solution we are looking for. Incorrectly I assumed that for the evaluation I could just make a quick install CD and be done with it (where it boots from would be immaterial). I may end up resolving the PXE issue and try it that way. First, I will try once more via the autoinstall CD. However, am I missing something here? Wouldnt it have the same problem of creating a tempfs on the target of the proper size? I guess you are saying that the configuration for PXE based boot would likely work correctly. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Friday, January 27, 2006 2:46 PM To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs And you cannot PXE-boot? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. Erdelyi Sent: Friday, January 27, 2006 11:41 To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, The two (source and destination) machines are HP DL360 G4 with single i386 32-bit processor each. The image server is also a HP DL360 G3 i386 machine. I will take a look at the script, attempt to modify it and advice on how it goes. I will also generate the rpm qa output later and send it as you requested. Best, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Friday, January 27, 2006 2:28 PM To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Trimming my response so it goes through... From: Bernard Li Sent: Friday, January 27, 2006 11:26 To: 'sisuite-users@lists.sourceforge.net' Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs If you want to work around it, modify si_mkautoinstallcd. It's still weird that it doesn't work for you. Can you show me the output of 'rpm -qa | grep systemimager'? Also, are you on x86_64 or i386? I tested it on i386, perhaps you are on x86_64 and there is a bug in the code? Cheers, Bernard
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
The configuration for PXE-boot is in /tftpboot/pxelinux.cfg/default (on the imageserver), so you can just modify that easily. I don't understand why it works on my system but not yours - as far as I know we haven't changed the code to si_mkautoinstallcd for quite some time. Try hardcoding for now. Cheers, Bernard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. ErdelyiSent: Friday, January 27, 2006 11:55To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs I tried that in the beginning but encountered some issues with the NICs, which I need to resolve. I figured I will work on that later once I determined that systemimager is the solution we are looking for. Incorrectly I assumed that for the evaluation I could just make a quick install CD and be done with it (where it boots from would be immaterial). I may end up resolving the PXE issue and try it that way. First, I will try once more via the autoinstall CD. However, am I missing something here? Wouldnt it have the same problem of creating a tempfs on the target of the proper size? I guess you are saying that the configuration for PXE based boot would likely work correctly. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Friday, January 27, 2006 2:46 PMTo: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs And you cannot PXE-boot? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. ErdelyiSent: Friday, January 27, 2006 11:41To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, The two (source and destination) machines are HP DL360 G4 with single i386 32-bit processor each. The image server is also a HP DL360 G3 i386 machine. I will take a look at the script, attempt to modify it and advice on how it goes. I will also generate the rpm qa output later and send it as you requested. Best, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Friday, January 27, 2006 2:28 PMTo: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Trimming my response so it goes through... From: Bernard Li Sent: Friday, January 27, 2006 11:26To: 'sisuite-users@lists.sourceforge.net'Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs If you want to work around it, modify si_mkautoinstallcd. It's still weird that it doesn't work for you. Can you show me the output of 'rpm -qa | grep systemimager'? Also, are you on x86_64 or i386? I tested it on i386, perhaps you are on x86_64 and there is a bug in the code? Cheers, Bernard
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Hi Bernard, I modified the si_mkautoinstallcd script by replacing the $append_string variable with tmpfs_size=1G tmpfs_nr_inodes=1000. This worked correctly and inserted the correct APPEND line in the syslinux.cfg file generated on the CD. However, the same problem still happens with tmpfs being created at a size 452788K (as per df) exactly as before, hence still getting the 99% full error. It seems that tmpfs_size is not being passed on to the mount tmpfs command at all during the autoinstall process. This is falling out somewhere else in the process. As requested here is the output from rpm qa | grep systemimager: systemimager-common-3.6.3-1 systemimager-server-3.6.3.-1 systemimager-i386boot-standard-3.6.3-1 Thanks, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Friday, January 27, 2006 3:01 PM To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs The configuration for PXE-boot is in /tftpboot/pxelinux.cfg/default (on the imageserver), so you can just modify that easily. I don't understand why it works on my system but not yours - as far as I know we haven't changed the code to si_mkautoinstallcd for quite some time. Try hardcoding for now. Cheers, Bernard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. Erdelyi Sent: Friday, January 27, 2006 11:55 To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs I tried that in the beginning but encountered some issues with the NICs, which I need to resolve. I figured I will work on that later once I determined that systemimager is the solution we are looking for. Incorrectly I assumed that for the evaluation I could just make a quick install CD and be done with it (where it boots from would be immaterial). I may end up resolving the PXE issue and try it that way. First, I will try once more via the autoinstall CD. However, am I missing something here? Wouldnt it have the same problem of creating a tempfs on the target of the proper size? I guess you are saying that the configuration for PXE based boot would likely work correctly. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Friday, January 27, 2006 2:46 PM To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs And you cannot PXE-boot? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. Erdelyi Sent: Friday, January 27, 2006 11:41 To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, The two (source and destination) machines are HP DL360 G4 with single i386 32-bit processor each. The image server is also a HP DL360 G3 i386 machine. I will take a look at the script, attempt to modify it and advice on how it goes. I will also generate the rpm qa output later and send it as you requested. Best, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Friday, January 27, 2006 2:28 PM To: sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Trimming my response so it goes through... From: Bernard Li Sent: Friday, January 27, 2006 11:26 To: 'sisuite-users@lists.sourceforge.net' Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs If you want to work around it, modify si_mkautoinstallcd. It's still weird that it doesn't work for you. Can you show me the output of 'rpm -qa | grep systemimager'? Also, are you on x86_64 or i386? I tested it on i386, perhaps you are on x86_64 and there is a bug in the code? Cheers, Bernard
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 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. ErdelyiSent: Friday, January 27, 2006 16:42To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi Bernard, I modified the si_mkautoinstallcd script by replacing the $append_string variable with tmpfs_size=1G tmpfs_nr_inodes=1000. This worked correctly and inserted the correct APPEND line in the syslinux.cfg file generated on the CD. However, the same problem still happens with tmpfs being created at a size 452788K (as per df) exactly as before, hence still getting the 99% full error. It seems that tmpfs_size is not being passed on to the mount tmpfs command at all during the autoinstall process. This is falling out somewhere else in the process. As requested here is the output from rpm qa | grep systemimager: systemimager-common-3.6.3-1 systemimager-server-3.6.3.-1 systemimager-i386boot-standard-3.6.3-1 Thanks, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Friday, January 27, 2006 3:01 PMTo: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs The configuration for PXE-boot is in /tftpboot/pxelinux.cfg/default (on the imageserver), so you can just modify that easily. I don't understand why it works on my system but not yours - as far as I know we haven't changed the code to si_mkautoinstallcd for quite some time. Try hardcoding for now. Cheers, Bernard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. ErdelyiSent: Friday, January 27, 2006 11:55To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs I tried that in the beginning but encountered some issues with the NICs, which I need to resolve. I figured I will work on that later once I determined that systemimager is the solution we are looking for. Incorrectly I assumed that for the evaluation I could just make a quick install CD and be done with it (where it boots from would be immaterial). I may end up resolving the PXE issue and try it that way. First, I will try once more via the autoinstall CD. However, am I missing something here? Wouldnt it have the same problem of creating a tempfs on the target of the proper size? I guess you are saying that the configuration for PXE based boot would likely work correctly. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Friday, January 27, 2006 2:46 PMTo: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs And you cannot PXE-boot? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of B. ErdelyiSent: Friday, January 27, 2006 11:41To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, The two (source and destination) machines are HP DL360 G4 with single i386 32-bit processor each. The image server is also a HP DL360 G3 i386 machine. I will take a look at the script, attempt to modify it and advice on how it goes. I will also generate the rpm qa output later and send it as you requested. Best, Bela -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Friday, January 27, 2006 2:28 PMTo: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Trimming my response so it goes through... From: Bernard Li Sent: Friday, January 27, 2006 11:26To: 'sisuite-users@lists.sourceforge.net'Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs If you want to work around it, modify si_mkautoinstallcd. It's still weird
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 wouldnt 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 dont 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
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Bernard, No I am not using LVM, the source fstab shows: LABEL=/ / ext3 default 1 1 LABEL=/boot /boot ext3 default 1 2 none /devpts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs default 0 0 none /dev/proc proc default 0 0 /dev/cciss/c0d0p3 swap swap default 0 0 dev/cdrom /mnt/cdrom udf,iso9660 de/fd0 /mnt/floppy auto and sfdisk on the source shows three partitions p1, p2, p3 (/, /boot and swap) for /dev/cciss/c0d0, which size is 142253280. This corresponds with what SI tries to create as a dev/cciss/c0d0 of the same size on the target, with part1, part2, part3 components. Thanks, Bela P.S. My first transmissions dont seem to post to this list for some reason. The second time it works, dont know why. I apologize if this appears as a duplicate post but after 3 days I have not seen the post on the site. I do receive each message via email from the list however. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Saturday, January 21, 2006 7:33 PM To: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Are you using LVM? Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. Erdelyi Sent: Fri 20/01/2006 11:11 To: sisuite-users@lists.sourceforge.net Subject: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi, I am attempting an image install with si_mkautoinstallcd using SI 3.6.3. The tmpfs mounted as / is not large enough to create the entire file structure. The process ends with tmpfs 99% full. I have attempted to specify the append option to si_mkautoinstallcd with various values without success. The following parameters were specified: tmpfs_size=2G tmpfs_nr_inodes=2000 tmpfs_size=1g tmpfs_nr_inodes=1000 tmpfs_size=1g Regardless, tmpfs is created each time the same size with or without the mount options specified at: 452,788 1-k blocks. This is weird since the machine has 2G of RAM, I would expect to see a default tmpfs mount of about 1G. It seems that si_mkautoinstallcd is not passing the arguments to the mount tmpfs command. Is there a place in the scripts where I could explicitly specify the tmpfs mount options? I have searched the autoinstall and SystemImager::Server.pm scripts, but I cannot find the logical place to impact a change
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Hi Bela: Can you check the resulting CD's isolinux/syslinux.cfg to make sure that the append statements are actually there? It should look something like:LABEL systemimagerKERNEL kernelAPPEND vga=extended initrd=initrd.img root=/dev/ram tmpfs_size=2G tmpfs_nr_inodes=2000 I just tested my 3.6.3 RPMs and I can specify the tmpfs size without any problems, the command I used was: si_mkautoinstallcd --append "tmpfs_size=2G tmpfs_nr_inodes=2000" --out-file /tmp/test.iso What's the build date of your 3.6.3 RPMs, mine are: Mon 09 Jan 2006 09:31:01 PM PST Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. ErdelyiSent: Thu 26/01/2006 08:16To: sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Bernard, No I am not using LVM, the source fstab shows: LABEL=/ / ext3 default 1 1 LABEL=/boot /boot ext3 default 1 2 none /devpts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs default 0 0 none /dev/proc proc default 0 0 /dev/cciss/c0d0p3 swap swap default 0 0 dev/cdrom /mnt/cdrom udf,iso9660 de/fd0 /mnt/floppy auto and sfdisk on the source shows three partitions p1, p2, p3 (/, /boot and swap) for /dev/cciss/c0d0, which size is 142253280. This corresponds with what SI tries to create as a dev/cciss/c0d0 of the same size on the target, with part1, part2, part3 components. Thanks, Bela P.S. My first transmissions dont seem to post to this list for some reason. The second time it works, dont know why. I apologize if this appears as a duplicate post but after 3 days I have not seen the post on the site. I do receive each message via email from the list however. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard LiSent: Saturday, January 21, 2006 7:33 PMTo: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Are you using LVM? Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. ErdelyiSent: Fri 20/01/2006 11:11To: sisuite-users@lists.sourceforge.netSubject: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi, I am attempting an image install with si_mkautoinstallcd using SI 3.6.3. The tmpfs mounted as / is not large enough to create the entire file structure. The process ends with tmpfs 99% full. I have attempted to specify the append option to si_mkautoinstallcd with various values without success. The following parameters were specified: tmpfs_size=2G tmpfs_nr_inodes=2000 tmpfs_size=1g tmpfs_nr_inodes=1000 tmpfs_size=1g Regardless, tmpfs is created each time the same size with or without the mount options specified at: 452,788 1-k blocks. This is weird since the machine has 2G of RAM, I would expect to see a default tmpfs mount of about 1G. It seems that si_mkautoinstallcd is not passing the arguments to the mount tmpfs command. Is there a place in the scripts where I could explicitly specify the tmpfs mount options? I have searched the autoinstall and SystemImager::Server.pm scripts, but I cannot find the logical place to impact a change
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Bernard, No I am not using LVM, the fstab shows: LABEL=/ / ext3 default 1 1 LABEL=/boot /boot ext3 default 1 2 none /devpts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs default 0 0 none /dev/proc proc default 0 0 /dev/cciss/c0d0p3 swap swap default 0 0 dev/cdrom /mnt/cdrom udf,iso9660 de/fd0 /mnt/floppy auto and sfdisk shows three partitions p1, p2, p3 (/, /boot and swap) for /dev/cciss/c0d0, which size is 142253280. This corresponds with what SI tries creates a dev of the same size, and part1, part2, part3 components. Thanks, Bela -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Saturday, January 21, 2006 7:33 PM To: sisuite-users@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs Are you using LVM? Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. Erdelyi Sent: Fri 20/01/2006 11:11 To: sisuite-users@lists.sourceforge.net Subject: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi, I am attempting an image install with si_mkautoinstallcd using SI 3.6.3. The tmpfs mounted as / is not large enough to create the entire file structure. The process ends with tmpfs 99% full. I have attempted to specify the append option to si_mkautoinstallcd with various values without success. The following parameters were specified: tmpfs_size=2G tmpfs_nr_inodes=2000 tmpfs_size=1g tmpfs_nr_inodes=1000 tmpfs_size=1g Regardless, tmpfs is created each time the same size with or without the mount options specified at: 452,788 1-k blocks. This is weird since the machine has 2G of RAM, I would expect to see a default tmpfs mount of about 1G. It seems that si_mkautoinstallcd is not passing the arguments to the mount tmpfs command. Is there a place in the scripts where I could explicitly specify the tmpfs mount options? I have searched the autoinstall and SystemImager::Server.pm scripts, but I cannot find the logical place to impact a change. It seems that the golden image will install properly if I could just get tmpfs to increase in size. Thanks, Bela
RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Are you using LVM? Cheers, Bernard From: [EMAIL PROTECTED] on behalf of B. ErdelyiSent: Fri 20/01/2006 11:11To: sisuite-users@lists.sourceforge.netSubject: [Sisuite-users] Problem with mkautoinstallcd tmpfs Hi, I am attempting an image install with si_mkautoinstallcd using SI 3.6.3. The tmpfs mounted as / is not large enough to create the entire file structure. The process ends with tmpfs 99% full. I have attempted to specify the append option to si_mkautoinstallcd with various values without success. The following parameters were specified: tmpfs_size=2G tmpfs_nr_inodes=2000 tmpfs_size=1g tmpfs_nr_inodes=1000 tmpfs_size=1g Regardless, tmpfs is created each time the same size with or without the mount options specified at: 452,788 1-k blocks. This is weird since the machine has 2G of RAM, I would expect to see a default tmpfs mount of about 1G. It seems that si_mkautoinstallcd is not passing the arguments to the mount tmpfs command. Is there a place in the scripts where I could explicitly specify the tmpfs mount options? I have searched the autoinstall and SystemImager::Server.pm scripts, but I cannot find the logical place to impact a change. It seems that the golden image will install properly if I could just get tmpfs to increase in size. Thanks, Bela
