RE: [Sisuite-users] RE: Ramdisk size too small? Getting errors

Thu, 01 Jun 2006 15:30:05 -0700

Title: RE: Ramdisk size too small? Getting errors
Can you please file a bug regarding autoinstallcd append and assign it to me?  I'll take a look at it when I got time.
 
http://sourceforge.net/tracker/?func=add&group_id=259&atid=100259
 
Regarding your errors, I'll let Andrea look into it, since he knows LVM much better than I do :-)
 
Cheers,
 
Bernard

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leidner, Jason (JLEIDNER)
Sent: Thursday, June 01, 2006 14:49
To: Leidner, Jason (JLEIDNER); [email protected]
Subject: [Sisuite-users] RE: Ramdisk size too small? Getting errors


Andrea, Bernard…

Just an update with what I have done and where I am. 

Also, my client is a x86_64bit server running RHEL4 + LVM's.

My server is a i386 server running RH7.3. 

Downloaded the RPM's that bernard built for me, upgraded both my client and my server (rpm -Uvh). 

Ran si_prepareclient on my client with the --my-modules option so that it will be smaller. 

When I was running si_getimage I received two warnings

WARNING: LVM partition "/dev/sda2" is not assigned to any group. 
WARNING: LVM group "VolGroup00" doesn't have any partitions.

This doesn't stop me from getting an image of the system.

Once the image has been captured,  I copy the initrd.img and kernel from the client (/etc/systemimager/boot/)  to my server and replace the initrd.img and kernel under /usr/share/systemimager/boot/x86_64/standard. 

I then run si_mkautoinstallcd --append ramdisk_size=50000 tmpfs_size=1990M --out-file filename and select the x86 standard image. 

Once that has been created, I burn it to CD and boot my box-to-be-imaged off of the new CD. 

It gives me the same error before about ramdisk being too small - so I guess the --apends are still not working right, and using --my-modules didn't make my initrd.img quite small enough. 

So I try and again and at the cd's boot prompt type "linux ramdisk_size=50000"

This time it makes it much farther… to where it is partitioning the disks.  This is the error I see:

"
<snip>
DISKS=2
Paritioning /dev/sda…
Old partition table for /dev/sda
Error unable to open /dev/sda - unrecognized disk label
Dd if=/dev/zero of=/dev/sda bs=512 count=1 || shellout
SCSI device sda: 285155328 512-byte hdwr sectors (146000MB)
Sda: asking for cache data failed
Sda: assuming drive cache: write through
   sda: unkown partition table
BLKRRPART: Input/output error
Killing off running processes. 
"

It drops me to the shell.  I do an lsmod to see if my modules loaded, and they have all loaded.  Seems that LVM might be messing it up. 

Please let me know what you both think… and if anyone else has seen this or has any ideas for me to try, please chime in!

Thanks,
Jason

Re: [Sisuite-users] RE: Ramdisk size too small? Getting errors

Andrea Righi
Sat, 27 May 2006 14:37:43 -0700

Hi Jason, Hi Bernard,

comments below...

Bernard Li wrote:
> Hi Jason:
> 
> I believe there was a bug where the AutoInstall CD's append statements
> do not working correctly - I'm not sure if this is fixed in trunk or not.
> 
> Anyways, I'm not too familiar with LVM setup, so if you need that,
> perhaps you should try out the code from trunk.  While you're at it,
> perhaps you can test to see if the AutoInstall CD issue is fixed, and if
> not, file a bug ;-)
> 

maybe there's still a problem in the initrd size and some files are
missing... you can try with the code in the trunk (instructions at
http://svn.sisuite.org/) and use the new --my-modules option of
si_prepareclient, that should strongly reduce the size of the initrd.

> I could build RPMs for the latest trunk, if that's more convenient for
> you to test.
> 
> (For other developers reading this thread, perhaps we should investigate
> how to build nightly RPMs from trunk, this would be extremely useful for
> testing).

It would be very very useful... what about a crontab on
systemimager.uchicago.edu? Do you think it would add too load to the
machine?

Cheers,
-Andrea

> 
> Cheers,
> 
> Bernard
>


     -----Original Message-----
    From:   Leidner, Jason  (JLEIDNER) 
    Sent:   Friday, May 26, 2006 3:05 PM
    To:     Leidner, Jason  (JLEIDNER); '[email protected]'
    Subject:        RE: Ramdisk size too small? Getting errors

    I just did that and it worked as far as getting me by that point.  At the cd boot prompt I type linux ramdisk_size=70000.  I am now getting the following error…

    Load device mapper driver  (for LVM)
    FATAL: Could not load /lib/modules/2.6.9-22.0.2.Elsmp/modules.dep  No such file or directory.
    Lvcreate -L211582976K -n LogVol00 VolGroup00 || shellout
    /dev/cdrom: open failed: no such device or address
    Volume group "VolGroup00" doesn't exist

    It then hangs. 

    Any thoughts?  Is it looking on the boot cd for 2.6.9-22-0.2.Elsmp?  The only directory under /lib/modules on the boot cd is the boel one. 

    Thanks again for your help. 

    Jason

    Bernard Li
    Fri, 26 May 2006 10:26:02 -0700

    Title: RE: Ramdisk size too small? Getting errors
    Have you tried passing it manually at boot time?  i.e. linux ramdisk_size=...
     
    Cheers,
     
    Bernard


       -----Original Message-----
      From:   Leidner, Jason  (JLEIDNER) 
      Sent:   Friday, May 26, 2006 1:03 PM
      To:     Leidner, Jason  (JLEIDNER); '[email protected]'
      Subject:        RE: Ramdisk size too small? Getting errors

      Has anyone had/seen this problem before or have any ideas as to what I can try?
      Thanks!
      Jason 

         -----Original Message-----
        From:   Leidner, Jason  (JLEIDNER) 
        Sent:   Thursday, May 25, 2006 2:46 PM
        To:     '[email protected]'
        Subject:        Ramdisk size too small? Getting errors

        Hi all,

        I'm running systemimager 3.6.3 on both my server and my client.  The server is a RedHat 9 machine.  The client is a RH4 + LVM machine. 

        I've captured an image of my client by running si_prepareclient on the client, then si_getimage on the server. 

        The way I'm setup is in the past I would create a boot cd, and for any machine that I wanted to image I would connect it to the image server via crossover cable, then boot up the client and it would grab the image I wanted. 

        While trying to image a new machine with the RH4 image I get the following error after booting from the Cd…

        RAMDISK: incomplete write (-28 != 32768) 16777216
        VFS: Mounted root (etx2 filesystem) readonly.
        Freeing unused kernel memory: 192k freed
        attempt to access beyond end of device
        ram0: rw=0, want=32776, limit=32768
        Ext2- fs error (device ram0): ext2_get_inode: unable to read inode block - inode         293, block=16387
        Warning: unable to open an initial console…. etc

        From searching online to similar problems I found that I need to pass the following arguments when creating my boot cd.  

        Si_mkautoinstallcd --append "vga=extended initrd=initrd.img root=/dev/ram ramdisk_size=43000 tmpfs_size=1990M console=ttyS0,9600 console=tty1 console=ttyS0,9600" --out-file custom.iso

        This works fine, and when I view the custom.iso file I can see that the syslinux.cfg file has my appends listed.  However, when I boot from the CD I keep getting the same error. 

        Thoughts anyone? 

        Thanks!
        Jason

        Jason Leidner
        Technical Administrative Support
        410-266-2328

Reply via email to