Last active 4 months ago

  1. 4 months ago
    Fri Dec 15 16:40:57 2017
    T tkurtz posted in Failing to expand volume.

    I'm on 1.3.0

    Looking at the upgrade now.... Thanks for quick reply.

    Still having to run "dracut --force --regenerate-all" in a recovery kernel by the way, to get it to boot properly after deployment (for SOME systems).

  2. Fri Dec 15 16:32:46 2017
    T tkurtz started the conversation Failing to expand volume.

    Hey Guys,

    I have some systems that are failing to expand the volume when doing a deploy. The reference system is built in a VM with a 10gb HDD, and it's being deployed to hardware with a 500gb Hard Drive. Once deployment is finished, the partitions are only 10gb.

    Deploy log attached.

  3. Thu Dec 7 14:14:34 2017
    T tkurtz posted in Error booting after clone.

    I am creating the image on VMWare Workstation 12 Pro. I've seen the issue happen on VMWare Workstation, VMWare vSphere, Hyper-V, and on physical hardware (but not always). The last deploy I tested came down on my VMWare Workstation with no errors - booted right up beautifully.

    I realize this doesn't give you much to go on. Are there any logs from a client that failed to boot initially that might be valuable?

  4. Mon Dec 4 18:05:38 2017
    T tkurtz posted in Error booting after clone.

    Just following up. We are working around the issue for now, but I'd love to eliminate that step! Thanks.

  5. 5 months ago
    Thu Nov 9 18:20:36 2017
    T tkurtz posted in Error booting after clone.

    Thanks for trying to replicate. I wonder if it has something to do with security features I have enabled or configured?

    Requested files attached (from the reference image)

  6. Thu Nov 2 18:11:06 2017
    T tkurtz posted in Error booting after clone.

    Sorry, I meant to attach both. Here they are. I was using OnDemand deployments which worked really well it seemed.

  7. Thu Nov 2 18:03:22 2017
    T tkurtz posted in Error booting after clone.

    Okay, I got pulled away from this project but I am back on task. I essentially started over from scratch, including updating my server to 1.3 (looks great by the way).

    OnDemand Upload seems to work fine.
    OnDepand Deploy seems to work fine.

    I get this when booting for the first time.

    "Dracut-initqueue[276]: Warning: Could not boot."
    "Dracut-initqueue[276]: Warning: /dev/cl_lx-centosref/root does not exist"
    "Dracut-initqueue[276]: Warning: /dev/cl_lx-centosref/swap does not exist"
    "Dracut-initqueue[276]: Warning: /dev/mapper/cl_lx--centosref-root does not exist"
    "Starting Dracut emergency shell..."
    "Warning: /dev/cl_lx-centosref/root does not exist"
    "Warning: /dev/cl_lx-centosref/swap does not exist"

    So, I boot into the rescue kernel... works just fine.

    I run the following command...
    "dracut --force --regenerate-all"

    Reboot again - everything seems fine.

    Any tips on avoiding this problem?

  8. 6 months ago
    Wed Oct 4 14:59:52 2017
    T tkurtz posted in Error booting after clone.

    Okay - thanks. I will work on that now - I've redone a lot of steps and have not really gotten it working yet. I was able to use clonezilla to get the VM from my VMWARE Workstation to a physical harddrive, and booted up in a laptop that I have. I wanted to eliminate VMWARE as a problem, so I am now cloning the physical HDD and attempting to deploy to another physical HDD.

    here's my newest upload logs.

  9. Thu Sep 28 14:09:19 2017
    T tkurtz posted in Compression method.

    I have the same error, were you able to figure it out?

  10. Thu Sep 28 13:18:48 2017
    T tkurtz started the conversation Error booting after clone.

    Just got CloneDeploy setup and I'm having trouble getting my first clone done.

    Here's my scenario -

    • I have a reference image build on a VMWare Workstation Pro (CentOS7 with security configurations and corporate software)
    • I'm trying to deploy it to a Dell Precision Tower (T3610).
    • It seems to partition the disk and copy the hard drive image down correct
    • System fails to boot with any of the kernels I included
    • I get a whole bunch of this error "dracut-initqueue[347]: warning: dracut-initqueue timeout - starting timeout scripts"
    • followed by "A start job is running for dev-mapp...oot.device (13minute / No Limit)
    • Can't see the whole error, I assume it's dev-mapper.something.root.device, but it never goes away, it will sit there for days.

    I don't think this is related to CloneDeploy specifically, more likely it's my reference image, but I'm hoping theres some expertise there that can help. This is becoming urgent for my job, so I hope someone can help!


View more