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

[Bernard Li]

Title: RE: Ramdisk size too small? Getting errors

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 ;-)

 

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).

 

Cheers,

 

Bernard

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leidner, Jason (JLEIDNER)
Sent: Friday, May 26, 2006 12:05
To: Leidner, Jason (JLEIDNER); sisuite-users@lists.sourceforge.net
Subject: [Sisuite-users] 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); 'sisuite-users@lists.sourceforge.net'
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:     'sisuite-users@lists.sourceforge.net'
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