Last active 6 weeks ago

  1. 6 weeks ago
    Wed Oct 31 14:57:52 2018

    Correct once again!

    I have to convince my bosses to donate. Keep up the good work!

  2. Wed Oct 31 14:45:07 2018

    so what happened is that last week your website was down, so I searched a mirror to download patch 1.3.5 from here: https://netcologne.dl.sourceforge.net/project/clonedeploy/CloneDeploy%201.3.0/Patches/1.3.5.zip

    I re-downloaded the patch from your website now, and the sha is now:

    I booted into PXE correctly now with patch 1.3.5!

    pxe kernel is 4.13. Is this correct? I had in my mind 1.3.5 was kernel 4.16

  3. Wed Oct 31 14:28:20 2018

    987df814b0ae35ae9ebe396dad825fbb7d9d54c66a97d61b42c1b56b04c8b233 /tftpboot/images/initrd.xz

  4. Wed Oct 31 14:07:42 2018

    If I dont update from 1.3.0 to 1.3.5, everything works correctly. It is indeed the patch.

    I ran that chown -R before I started this topic. It didn't work either.

    Maybe I will try to patch to version 1.3.1 or 1.3.2 and see if it happens.

    I can send you the virtual machine with the error happening. Its only 2GB

  5. Wed Oct 31 10:24:24 2018

    Thanks for the reply. I understand.

    I actually reinstalled the OS and did everything again. The same happens when copying the patch folders into the original locations.

    Am I doing this right?

    $ sudo su
    $ service apache stop
    $ cp -r /1.3.5/frontend/* /var/www/html/clonedeploy/frontend/
    $ cp -r /1.3.5/application/* /var/www/html/clonedeploy/api/
    $ cp -r /1.3.5/tftpboot/* /tftpboot/

    I noticed permissions for the replaced files are all changed compared to the original files.

  6. Tue Oct 30 09:08:42 2018

    Hi guys. It seems support has stopped for this project.

    Anyone knows how to properly merge the patch 1.3.5 into 1.3.0 in ubuntu?

    After patching by simply copying the new folders into place, something fails when trying to use the program, as you can see above.

  7. 7 weeks ago
    Tue Oct 23 14:18:28 2018
    S spyshagg started the conversation After merging 1.3.5 patch, I have the following error .

    I installed a new VM with ubuntu and clonedeploy 1.3.0

    Everything seems to work up to this point.

    But after merging 1.3.5 I have this error after selecting any pxe boot option.


    Its probably permissions. How's the proper way to merge the files?

  8. last year
    Mon Dec 12 15:47:24 2016
    S spyshagg posted in Boot from local disc - Boot Error.

    Sorry to bump this topic.

    I have confirmed the pxe "boot to local disc" work well, but the pen/iso doesn't.

    Can the pxe method be ported to the pen/iso ?

  9. 2 years ago
    Wed Nov 30 15:30:33 2016

    Issue 1 was with upload + webgui task. I have searched but there are no logs :\

    thanks for the tip. If I click the image in "image profile updater" another window opens with many options about the upload! Very nice! What options to you recommend for max reliability on upload and deploy? some computers will be 500km away

    Issue 2 happened once and the log is above. I'll be sure to post my findings If it happens again.

    Thank you

  10. Wed Nov 30 10:40:37 2016
    S spyshagg started the conversation Issues when using clonedeploy on some situations.


    Although all works well when uploading/deploying to hard drives with simple existing configurations (Vanilla windows disks, vanilla linux disks), but I have found some issues. One is was pretty serious.

    1 - When uploading windows hdd's which have partitions and bootloader created/altered by Acronis true image, clonedeploy "resizes" the volumes and starts to upload. The upload failed on some partition and after rebooting the OS hanged. I had to restore a true image clone of the C partition. I haven't found any logs of this operation.

    Is there any way to prevent clonedeploy from tempering with the source material prior to the imaging?

    2- When deploying windows images to an "unclean" drive (a drive which has existing windows partitions), clonedeploy can fail with ntfs errors messages. This drive in question was a data drive, no OS, but I think this hdd had an acronis hidden partition. Not sure though.

    The log is attached bellow.

    In this case, I had to remove the HDD to another computer and delete every partition manually. After doing this the deploy occurred without issues.


View more