anchor.diff:  For a more detailed error report, run: bosh task 631 --debug
   </pre>
   
  +<pre class="terminal wide">
  +$ bosh cck
  +
  +Performing cloud check...
  +
  +Processing deployment manifest
  +------------------------------
  +
  +Director task 640
  +  Started scanning 1 vms
  +  Started scanning 1 vms > Checking VM states. Done (00:00:10)
  +  Started scanning 1 vms > 0 OK, 1 unresponsive, 0 missing, 0 unbound, 0 out of sync. Done (00:00:00)
  +     Done scanning 1 vms (00:00:10)
  +
  +  Started scanning 0 persistent disks
  +  Started scanning 0 persistent disks > Looking for inactive disks. Done (00:00:00)
  +  Started scanning 0 persistent disks > 0 OK, 0 missing, 0 inactive, 0 mount-info mismatch. Done (00:00:00)
  +     Done scanning 0 persistent disks (00:00:00)
  +
  +Task 640 done
  +
  +Started   2015-01-09 23:33:45 UTC
  +Finished  2015-01-09 23:33:55 UTC
  +Duration  00:00:10
  +
  +Scan is complete, checking if any problems found...
  +
  +Found 1 problem
  +
  +Problem 1 of 1: dummy/0 (i-914c046a) is not responding.
  +  1. Skip for now
  +  2. Reboot VM
  +  3. Recreate VM
  +  4. Delete VM reference (forceful; may need to manually delete VM from the Cloud to avoid IP conflicts)
  +Please choose a resolution [1 - 4]: 4
  +
  +Below is the list of resolutions you've provided
  +Please make sure everything is fine and confirm your changes
  +
  +  1. dummy/0 (i-914c046a) is not responding.
  +     Delete VM reference (forceful; may need to manually delete VM from the Cloud to avoid IP conflicts)
  +
  +Apply resolutions? (type 'yes' to continue): yes
  +Applying resolutions...
  +
  +Director task 641
  +  Started applying problem resolutions > unresponsive_agent 168: Delete VM reference (...). Done (00:00:05)
  +
  +Task 641 done
  +
  +Started   2015-01-09 23:35:20 UTC
  +Finished  2015-01-09 23:35:25 UTC
  +Duration  00:00:05
  +Cloudcheck is finished
  +</pre>
  +
  +cck determined that `i-914c046a` VM is unresponsive. Possible options are:
  +
  +1. `Skip for now`: the Director will not try to resolve this problem right now
  +
  +2. `Reboot VM`: the Director will power off and then power on existing VM
  +
  +    Note on current behaviour: cck will not wait for all release job processes to start.
  +
  +3. `Recreate VM`: the Director will delete existing VM, then create a new VM, deploy specified releases according to deployed manifest and finally start release jobs
  +
  +    Note on current behaviour: cck will not wait for all release job processes to start.
  +
  +4. `Delete VM reference`: the Director will not create new VM in its place. If cck is run again, it will not report that VM is unresponsive since it does not exist. Running `bosh deploy` after cck will backfill missing VMs.
  +
  +In the above example options 4 was picked and VM reference was deleted.
  +
   ---
   ### <a id="unattached-persistent-disk"></a> Persistent Disk is not attached
   
   Assuming there was a deployment with a VM, somehow persistent disk got detached.
   
  -<pre class="terminal">
  -bosh cck
  +<pre class="terminal wide">
  +$ bosh cck
   
   Performing cloud check...
   
  
positive.code: Next: [Automatic repair with Resurrector](resurrector.html)
  
  Previous: [Process monitoring with Monit](vm-monit.html)
  
negative.code: 
  Assuming there was a deployment with a VM, somehow that VM was deleted from the IaaS outside of BOSH, here is what cck would report:
  
  <pre class="terminal wide">
  $ bosh cck
  
  Performing cloud check...
  
  