SystemImager install problem

Discussion in 'HOWTO-Related Questions' started by poisen, Mar 11, 2008.

  1. poisen

    poisen New Member

    Hello everybody,

    I am trying to install SystemImager on my "golden-client" running OpenSuse 10.3, it's a dedicated server hosted at Strato and I was pretty impressed by the nice tutorials that I've found.

    During the installation of the client running prepareclient --server serverip I got the following error and I don't know what to do next:

    Code:
    >> Evaluating initrd size to be added in the kernel boot options
    >> (e.g. /etc/systemimager/pxelinux.cfg/syslinux.cfg):
     >>	suggested value -> ramdisk_size=67683.5
    
    I couldn't identify your kernel file.  Please try to use --kernel option.
    
    maybe somebody can help me out. Thanks a lot.

    -Eddie
     
  2. falko

    falko Super Moderator ISPConfig Developer

    IS there something about the --kernel option in
    Code:
    man prepareclient
    ?
     
  3. poisen

    poisen New Member

    this is what I've found in the man pages

    Code:
           --kernel FILE
                  Do  not  detect  the  kernel  to use with UYOK, but instead use the file specified by the argument FILE.  Use this parameter only with --mod‐
                  ules_dir and only if you use UYOK feature.
    
           --modules-dir DIR
                  Get kernel modules to use with UYOK from the DIR repository.  Use this parameter only with --kernel and only if you use UYOK feature.
    
    I tried around a little bit and ran this si_prepareclient --server myImageServerIP --kernel /boot/config-2.6.22.9-0.4-default
    and got the following output, but I don't know if that is okay?

    Code:
    Using "sfdisk" to gather information about disk:
        /dev/sda
    
    Using "sfdisk" to gather information about disk:
        /dev/sdb
    
    Use of uninitialized value in pattern match (m//) at /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm line 576.
    WARNING: couldn't find a valid filesystem for initrd.img!
    WARNING: trying with cpio initramfs...
    >>> Choosing filesystem for new initrd:  cpio
    >>> Creating new initrd from staging dir:  /tmp/.systemimager.0
     >> cd /tmp/.systemimager.0 && find . ! -name "*~" | cpio -H newc --create | gzip -9 > /etc/systemimager/boot/initrd.img
    27441 blocks
     >> ls -l /etc/systemimager/boot/initrd.img
    -rw-r--r-- 1 root root 5560230 Mar 11 21:03 /etc/systemimager/boot/initrd.img
    
    >> Evaluating initrd size to be added in the kernel boot options
    >> (e.g. /etc/systemimager/pxelinux.cfg/syslinux.cfg):
     >>	suggested value -> ramdisk_size=23960.5
    
    >>> Using kernel from:          /boot/config-2.6.22.9-0.4-default
     >> ls -l /etc/systemimager/boot/kernel
    -rw-r--r-- 1 root root 80417 Mar 11 21:03 /etc/systemimager/boot/kernel
    
    Starting or re-starting rsync as a daemon.....
    done!
    
    This client is ready to have its image retrieved.  You must now run 
    the "si_getimage" command on your imageserver.
    
    Your client has been successfully prepared.  Boot kernel (copied from
    this Linux distribution) and an initrd.img (generated by the
    initrd_template package) can be found in /etc/systemimager/boot.
    
    Automatically create configuration file for systemconfigurator:
      >> /etc/systemconfig/systemconfig.conf
    WARNING: unable to detect kernel release of "/boot/config-2.6.22.9-0.4-default"!
    WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by systemconfigurator)
    
    There are a few files in my /boot/ folder and I don't know what to use, in the code above I used
    Code:
    /boot/config-2.6.22.9-0.4-default
    
    but I also did the whole thing once with the file
    Code:
    /boot/initrd-2.6.22.9-0.4-default
    
    and got the same output as stated above.

    I'd be thankful for any hints / tips
     
    Last edited: Mar 11, 2008
  4. falko

    falko Super Moderator ISPConfig Developer

    What are the outputs of
    Code:
    uname -a
    and
    Code:
    ls -la /boot
    ?
     
  5. poisen

    poisen New Member

    Code:
    deltaone:~ # uname -a
    Linux deltaone 2.6.22.9-0.4-default #1 SMP 2007/10/05 21:32:04 UTC i686 athlon i386 GNU/Linux
    
    
    deltaone:~ # ls -la /boot
    total 7950
    drwxr-xr-x  4 root root    1024 2008-03-10 13:25 .
    drwxr-xr-x 20 root root    4096 2008-03-10 14:34 ..
    -rw-------  1 root root     512 2007-10-16 10:33 backup_mbr
    lrwxrwxrwx  1 root root       1 2008-03-10 14:11 boot -> .
    -rw-r--r--  1 root root   80417 2007-10-08 13:50 config-2.6.22.9-0.4-default
    -rw-r--r--  1 root root      45 2008-03-10 13:25 device.map
    drwxr-xr-x  2 root root    1024 2008-03-10 23:32 grub
    lrwxrwxrwx  1 root root      27 2008-03-10 13:25 initrd -> initrd-2.6.22.9-0.4-default
    -rw-r--r--  1 root root 2753959 2008-03-10 13:25 initrd-2.6.22.9-0.4-default
    drwx------  2 root root   12288 2008-03-10 14:06 lost+found
    -rw-r--r--  1 root root  138222 2007-10-08 13:52 symsets-2.6.22.9-0.4-default.tar.gz
    -rw-r--r--  1 root root  400506 2007-10-08 13:52 symtypes-2.6.22.9-0.4-default.gz
    -rw-r--r--  1 root root  116261 2007-10-08 13:51 symvers-2.6.22.9-0.4-default.gz
    -rw-r--r--  1 root root  842872 2007-10-08 13:46 System.map-2.6.22.9-0.4-default
    -rwxr-xr-x  1 root root 2147342 2007-10-08 13:50 vmlinux-2.6.22.9-0.4-default.gz
    lrwxrwxrwx  1 root root      28 2008-03-10 14:11 vmlinuz -> vmlinuz-2.6.22.9-0.4-default
    -rw-r--r--  1 root root 1593788 2007-10-08 13:46 vmlinuz-2.6.22.9-0.4-default
    
    
     
  6. falko

    falko Super Moderator ISPConfig Developer

    Try /boot/vmlinuz-2.6.22.9-0.4-default.
     
  7. poisen

    poisen New Member

    just ran the script using
    Code:
    si_prepareclient --server ImageServerIP --kernel /boot/vmlinuz-2.6.22.9-0.4-default
    
    and got the following output, pretty much the same as the one before

    Code:
    Using "sfdisk" to gather information about disk:
        /dev/sda
    
    Using "sfdisk" to gather information about disk:
        /dev/sdb
    
    Use of uninitialized value in pattern match (m//) at /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm line 576.
    WARNING: couldn't find a valid filesystem for initrd.img!
    WARNING: trying with cpio initramfs...
    >>> Choosing filesystem for new initrd:  cpio
    >>> Creating new initrd from staging dir:  /tmp/.systemimager.0
     >> cd /tmp/.systemimager.0 && find . ! -name "*~" | cpio -H newc --create | gzip -9 > /etc/systemimager/boot/initrd.img
    27441 blocks
     >> ls -l /etc/systemimager/boot/initrd.img
    -rw-r--r-- 1 root root 5560237 Mar 13 18:37 /etc/systemimager/boot/initrd.img
    
    >> Evaluating initrd size to be added in the kernel boot options
    >> (e.g. /etc/systemimager/pxelinux.cfg/syslinux.cfg):
     >>	suggested value -> ramdisk_size=23960.5
    
    >>> Using kernel from:          /boot/vmlinuz-2.6.22.9-0.4-default
     >> ls -l /etc/systemimager/boot/kernel
    -rw-r--r-- 1 root root 1593788 Mar 13 18:37 /etc/systemimager/boot/kernel
    
    Starting or re-starting rsync as a daemon.....
    done!
    
    This client is ready to have its image retrieved.  You must now run 
    the "si_getimage" command on your imageserver.
    
    Your client has been successfully prepared.  Boot kernel (copied from
    this Linux distribution) and an initrd.img (generated by the
    initrd_template package) can be found in /etc/systemimager/boot.
    
    Automatically create configuration file for systemconfigurator:
      >> /etc/systemconfig/systemconfig.conf
    WARNING: unable to detect kernel release of "/boot/vmlinuz-2.6.22.9-0.4-default"!
    WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by systemconfigurator)
    
    
     
  8. falko

    falko Super Moderator ISPConfig Developer

    I'm afraid I don't know a solution (other then not to use SUSE...).
     
  9. poisen

    poisen New Member

    what would you suggest to use? I am pretty experienced with SuSE, but I am also willing to use something else. I could choose between CentOS 5, Fedora 7 or Debian 4.0. Running a webserver with probably 40 websites.

    I'd be happy for some suggestions
     
  10. falko

    falko Super Moderator ISPConfig Developer

    Debian. :):)
     

Share This Page