RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs

[B. Erdelyi]

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?  Wouldn’t 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