Clone deploy not imaging drive *no active harddrive image was found*

  1. 5 weeks ago

    Hello,

    Im trying to clobber deploy on a specific drive sda. sdb is a floppy drive.

    However when ever clone deploy gets to it, it fails.

    can you help me out?

    attached is a photo of the error

    Sometimes the ordering of drives can get messed up. CloneDeploy has a way to handle this. In your image profile deploy options, select modify image schema. Then you can set the destination for the image. You could set it to /dev/sda or whatever. If you wouldn't mind posting one of the deploy logs where the floppy drive was enabled it would be helpful so I could figure out why /dev/sdb was listed before /dev/sda

  2. Disabled floppy and/or diskeet drive in bios and worked.

  3. clonedeploy

    Nov 6 Administrator Answer

    Sometimes the ordering of drives can get messed up. CloneDeploy has a way to handle this. In your image profile deploy options, select modify image schema. Then you can set the destination for the image. You could set it to /dev/sda or whatever. If you wouldn't mind posting one of the deploy logs where the floppy drive was enabled it would be helpful so I could figure out why /dev/sdb was listed before /dev/sda

  4. ** Looking For Active Task For ec:b1:d7:3b:79:e6.2UA53222GQ.F703E280-359E-11E5-9178-ECB1D73B79E6 **
     
    {"computerId":"false","task":"ond","taskId":null}
     
    ...... This Computer Was Not Found
     
    ** Looking For Active Task For ec:b1:d7:3b:79:e6 **
     
    {"computerId":"false","task":"ond","taskId":null}
     
    ...... This Computer Was Not Found
     
    No Active Web Tasks Were Found For This Computer. Starting Clobber Imaging.
     
    ** Displaying Boot Arguments **
     
    BOOT_IMAGE=/kernels/4.13.2x64 root=/dev/ram0 rw ramdisk_size=156000 task=clobber image_profile_id=5 consoleblank=0 web=http://10.40.47.248/clonedeploy/api/ClientImaging/ USER_TOKEN=4718ec9b-f69f-4f66-a67b-4cbe533b7023 MAC: ec:b1:d7:3b:79:e6
    Linux client_console.localdomain 4.13.2 #1 SMP Mon Sep 18 12:18:16 EDT 2017 x86_64 GNU/Linux
     
    Boot Image Version: 1008
     
    ** Using Clobber Mode **
     
    image_name=ICT-9-22-2107 profile_id=5 server_ip=10.40.47.248 pre_scripts="" post_scripts="" file_copy=False sysprep_tags="" task_completed_action="Reboot" osx_target_volume="" munki_repo_url="" change_computer_name=true fix_bootloader=true partition_method=dynamic dp_id="1" computer_id=-103703
     
    ...... Success
     
    ** Checking Current Queue **
     
    ...... Complete
     
    ** Mounting SMB Share **
     
    ...... Connecting To Clonedeploy
     
    ...... Success
     
    ** Looking For Hard Drive(s) **
     
    ...... Displaying Available Devices
    RO RA SSZ BSZ StartSec Size Device
    rw 256 512 1024 0 159744000 /dev/ram0
    rw 256 512 4096 0 256060514304 /dev/sda
    rw 256 512 4096 2048 256059465728 /dev/sda1
    rw 256 2048 2048 0 70260736 /dev/sdb
    Disk /dev/ram0: 152.4 MiB, 159744000 bytes, 312000 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
     
     
    Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x25fb7c98
     
    Device Boot Start End Sectors Size Id Type
    /dev/sda1 * 2048 500118191 500116144 238.5G 7 HPFS/NTFS/exFAT
     
     
    Disk /dev/sdb: 67 MiB, 70260736 bytes, 34307 sectors
    Units: sectors of 1 * 2048 = 2048 bytes
    Sector size (logical/physical): 2048 bytes / 2048 bytes
    I/O size (minimum/optimal): 2048 bytes / 2048 bytes
     
    ...... Found Drive(s)
     
    ...... Drive(s): /dev/sdb /dev/sda
     
    ** Processing /dev/sdb **
     
    Get hd_schema: profileId=5&clientHdNumber=0&newHdSize=281042944&schemaHds=&clientLbs=2048
     
    {"BootPartition":null,"Guid":null,"IsValid":"false","Message":"The Logical Block Size Of This Hard Drive 2048 Does Not Match The Original Image 512","PartitionType":null,"PhysicalPartitionCount":0,"PhysicalPartitions":null,"SchemaHdNumber":0,"UsesLvm":null}
     
    ...... The Logical Block Size Of This Hard Drive 2048 Does Not Match The Original Image 512
     
    ** Processing /dev/sda **
     
    Get hd_schema: profileId=5&clientHdNumber=1&newHdSize=256060514304&schemaHds=&clientLbs=512
     
    {"BootPartition":null,"Guid":null,"IsValid":"false","Message":"No Active Hard Drive Images Were Found To Deploy.","PartitionType":null,"PhysicalPartitionCount":0,"PhysicalPartitions":null,"SchemaHdNumber":-1,"UsesLvm":null}
     
    ...... No Active Hard Drive Images Were Found To Deploy.
     
    ** Closing Active Task **
  5. as well... the schema is set to /dev/sda

  6. clonedeploy

    Nov 7 Administrator

    That's not the correct location. That's the original schema stating it was uploaded from /dev/sda. It doesn't have anything to do with where it deploys to.

  7. @clonedeploy That's not the correct location. That's the original schema stating it was uploaded from /dev/sda. It doesn't have anything to do with where it deploys to.

    looked over your answer again. figured it out.

    Thank you!

 

or Sign Up to reply!