Menu

Saving Package Info

Steve C
2011-04-05
2013-04-05
  • Steve C

    Steve C - 2011-04-05

    I am a first time Clonezilla user and am creating my first image with the server version. The client connects properly via PXE and creates the image. After creating the image, it saves the hardware, DMI, and PCI info successfully. When it gets to the "Saving Package Info" portion, I am getting an error that says:

    lockd: server  not responding, still trying
    lockd: server  OK
    lockd: server  not responding, still trying
    lockd: server  OK

    This repeats over and over.

    I stopped the first attempt and tried to create the image again with the same result. Is there anything I need to do so the image will complete? Any reason this would happen?

    Thanks in advance for your help!

    -Steve

     
  • Steven Shiau

    Steven Shiau - 2011-04-12

    Could you please follow
    http://drbl.sourceforge.net/one4all/#bug-report
    to provide more info?
    It's easier for us the reproduce the problem here.
    Thanks.

    Steven.

     
  • Steve C

    Steve C - 2011-04-12

    OS version: Fedora 14
    DRBL version: drbl-1.9.9-21.i386
    Clonezilla version: clonezilla-2.3.8-27.i386
    Server arch: i686
    Server Kernel version: 2.6.35.12-88.fc14.x86_64
    Server glibc ver: glibc-2.13-1
    Server glibc arch: x86_64
    Client kernel version: Windows XP
    Client kernel arch: i686
    NICs with private IP address in server: eth0
    Private IP address in server: 192.168.5.253
    Client IP address: 192.168.5.1

    Description of problem: Please see the initial report
    How reproducible: Try to create an image
    Steps to Reproduce: boot client machine, start creating an image and it stalls as listed above
    Actual results: image creation fails
    Expected results: Image should be created

    More info:
    When I look in the Info-packages.txt on the server, all it says is:

    Image was saved by these Clonezilla-related packages:

    Thanks for your help!
    -Steve

     
  • Kevin Steam

    Kevin Steam - 2011-04-14

    Hello,

    I encounter the same problem and I have a similar configuration

    OS version: Fedora 14
    DRBL version: drbl-1.9.9-21.i386
    Clonezilla version: clonezilla-2.3.8-27.i386
    Server arch: i686
    Server Kernel version: 2.6.35.12-88.fc14.i686.PAE
    Server glibc ver: glibc-2.13-1
    Server glibc arch: i686
    Client kernel version: Windows 7
    Client kernel arch: i686
    NICs with private IP address in server: eth1
    Private IP address in server: 10.30.0.166
    Client IP address:  10.30.0.170

    Description of problem: Please see the initial report
    How reproducible: Try to create an image
    Steps to Reproduce: boot client machine, start creating an image and it stalls as listed above
    Actual results: image creation fails
    Expected results: Image should be created

    More info:
    in the Info-packages.txt on the server, I have :

    Image was saved by these Clonezilla-related packages:

    Could you help me please ?

     
  • Steven Shiau

    Steven Shiau - 2011-04-20

    This is weird… I tried the stable DRBL and unstable one on my i686 Fedora 14 machine, both of them worked for me. I could not reproduce this issue…
    Try to upgrade your Fedora 14 system to the latest one to see if any difference.

    Steven.

     
  • David Guertin

    David Guertin - 2012-07-03

    Description of problem:

    FWIW, I'm seeing the exact same problem. I successfully created some images about 8 months ago, but now when I try to create a new image, I'm seeing this message on the client:

    lockd: server 192.168.0.254 not responding, still trying
    lockd: server 192.168.0.254 OK

    repeated over and over.

    On the server, /var/log/messages shows:

    lockd: cannot monitor cslab1150
    statd: server rpc.statd not responding, timed out

    How reproducible:

    Run drblpush -i, followed by dsc on server. Select options to create a new disk image. Then reboot client to network, and allow Clonezilla to do its thing.

    Steps to Reproduce:

    Actual results:

    Clonezilla completes image creation:

    Finished saving /dev/VolGroup/lv_root as /data/2012-07-03-img-fedora17/VolGroup-lv_root.ext4-ptc1-img.gz
    ************************
    ************************
    Saving hardware info by lshw…
    Saving DMI info…
    Saving package info…
    lockd: server 192.168.0.254 not responding, still trying
    lockd: server 192.168.0.254 OK
    <last two lines repeated ad infintum>

    Contents of /data/2012-07-03-11-img-fedora17/Info-packages.txt:
    Image was saved by these Clonezilla-related packages:
    <blank>

    Expected results:

    Clonezilla write package info to server.

    Some info about the DRBL environment (PLEASE DO NOT EDIT THEM!):

    OS version: Fedora 14
    Server arch: x86_64
    Server CPU:  Intel(R) Xeon(R) CPU           X5677  @ 3.47GHz
    Server memory size: 1022984 kB
    Server Kernel version: 2.6.35.14-106.fc14.x86_64
    Installed DRBL-related packages:  drbl-1.10.31-1drbl.i386 clonezilla-2.3.58-1drbl.i386 mkswap-uuid-0.1.1-1.i386 partclone-0.2.24-2drbl.i386 drbl-chntpw-0.0.20040818-7.i386 mkpxeinitrd-net-1.6.10-1drbl.i386 ipxe-20110811-1drbl.i386 freedos-1.0-15drbl.i386 partimage-0.6.9-1.fc14.x86_64 ntfsprogs-2011.4.12-5.fc14.x86_64 gzip-1.4-1.fc14.x86_64 bzip2-1.0.6-1.fc14.1.x86_64 lzop-1.03-2.fc14.x86_64 pigz-2.1.6-1.fc14.x86_64 pbzip2-1.1.1-1.fc14.x86_64 udpcast-20071228-6.fc12.x86_64
    Server glibc ver and arch: glibc-2.13-2.x86_64
    glibc-2.13-2.i686 x86_64i686
    Client kernel version: 2.6.35.14-96.fc14.x86_64
    Client kernel arch: x86_64
    NICs with private IP address in server: eth1
    Private IP address in server: 192.168.101.254
    Total client no: 26
    Client IP address: 192.168.101.150 192.168.101.151 192.168.101.152 192.168.101.153 192.168.101.154 192.168.101.155 192.168.101.156 192.168.101.157 192.168.101.158 192.168.101.159 192.168.101.160 192.168.101.161 192.168.101.162 192.168.101.163 192.168.101.164 192.168.101.165 192.168.101.166 192.168.101.167 192.168.101.168 192.168.101.169 192.168.101.170 192.168.101.171 192.168.101.172 192.168.101.173 192.168.101.174 192.168.101.175

     
  • David Guertin

    David Guertin - 2012-07-03

    Sorry, typo in my above message: The IP adresses are all 192.168.101.*

     
  • Steven Shiau

    Steven Shiau - 2012-07-05

    This looks like the problem is on some NFS-related services.
    Did you try to upgrade your Fedora 14 and DRBL?

    Steven.

     
  • David Guertin

    David Guertin - 2012-07-05

    That's on the agenda for today. Are there any limitations on how recent an OS I can upgrade to? Will Clonezilla support RHEL 6 or Fedora 17?

     
  • Steven Shiau

    Steven Shiau - 2012-07-05

    For RHEL 6, it should be OK (we do not have RHEL 6 here). Here we have tested successfully on CetnOS 6.
    As for Fedora 17, no.

    Steven.

     
  • David Guertin

    David Guertin - 2012-07-05

    Hmm. RHEL 6 may be supported, but the installation will take a bit of persuasion. drblsrv -i fails:

    # /opt/drbl/sbin/drblsrv -i

        *****************************************************.
        Installing DRBL for RedHat/Fedora Linux…
        This version is not supported: RH6.3
        If you are sure this GNU/Linux distribution is compatible with those distributions which DRBL supports, you can try to use /opt/drbl/sbin/drblsrv-offline.

    So I try drblsrv-offline to force the issue, and it too fails:

    # /opt/drbl/sbin/drblsrv-offline -s `uname -r`

        These required packages are not installed:  mkinitrd.

    In RHEL 6, /sbin/mkinitrd is not provided by the mkinitrd RPM. Instead, it is provided by dracut, which is installed:

        # rpm -qf /sbin/mkinitrd
        dracut-004-283.el6.noarch

    So how can I tell drblsrv-offline to look for dracut instead of mkinitrd (or just not bother checking at all)?

    Sorry if this is drifting this thread into a new topic.

     
  • David Guertin

    David Guertin - 2012-07-05

    Never mind, I found it: Change mknitrd to dracut in /opt/drbl/conf/drbl.conf, and everything goes smoothly.

     

Log in to post a comment.

Auth0 Logo