Menu

#249 Clonezilla fails to locate image destination partition greater than boot drive

open
nobody
None
4
2016-08-07
2016-05-17
No

I noticed while trying to run Clonezilla that if your destination partition (where you want to save an image) falls after the USB drive you used to boot Clonezilla, it won't be displayed on the partimg selection screen. This is despite even with the latest testing version/yakkety where the drive does show up under the 3.0 second watch screen, but after you press ctrl+c it isn't available for selection.

For instance, the drive you want to clone is /dev/sda, the USB drive you booted from is /dev/sdb, and the external USB Hard Drive is /dev/sdc. /dev/sdc and its partitions won't show up on the image destination selection screen. I was able to workaround this by changing the boot order in the BIOS to make /dev/sda the first drive instead of "USB HDD" - somehow this caused my external drive to be /dev/sdb and the bootable USB drive to be /dev/sdc - then I was able to select sdb.

Perhaps there is a bug that causes the search script to stop once it gets to the drive used to boot to Clonezilla?

Discussion

  • Steven Shiau

    Steven Shiau - 2016-05-21

    Do you have any partition in /dev/sdc? i.e. /dev/sdc1?
    The wizard will only search partitoin, not the whole disk as the image repository.
    Could you please run:
    cat /proc/partitions
    then post the results?

    Steven

     
  • Josh Hopkins

    Josh Hopkins - 2016-07-09

    HI Steve, apologies for the delay. See output of /proc/partitions below. Also attaching two screenshots. sda is the internal HD I'm trying to clone to an image file on /dev/sdc1. /dev/sdb is the USB drive I'm booting from, /dev/sdc is an external USB HD with one partition, sdc1. I've been able to work around this issue by going to command line and mounting sdc1 manually (mount /dev/sdc1 /home/partimag) but it would be nice if the GUI would allow me to select sdc1 when sdb is the boot drive.

    major minor #blocks name

    1 0 65536 ram0
    1 1 65536 ram1
    1 2 65536 ram2
    1 3 65536 ram3
    1 4 65536 ram4
    1 5 65536 ram5
    1 6 65536 ram6
    1 7 65536 ram7
    1 8 65536 ram8
    1 9 65536 ram9
    1 10 65536 ram10
    1 11 65536 ram11
    1 12 65536 ram12
    1 13 65536 ram13
    1 14 65536 ram14
    1 15 65536 ram15
    7 0 199700 loop0
    8 0 125034840 sda
    8 1 55203 sda1
    8 2 124487892 sda2
    8 16 1974272 sdb
    8 17 1973248 sdb1
    8 32 976762584 sdc
    8 33 976758784 sdc1

     
  • Steven Shiau

    Steven Shiau - 2016-07-17

    This is weird. Since /dev/sdc1 exists, prep-ocsroot should show that.
    Besides, I can not reproduce the issue here so that I have no idea how to fix that. Which version of Clonezilla live did you use? Could you please give the latest testing Clonezilla live a try? Like 2.7.13?
    http://clonezilla.org/downloads.php

    Steven

     
  • Josh Hopkins

    Josh Hopkins - 2016-07-20

    I just tried 20160719-yakkety (not sure if that is 2.7.13) but the issue still exists there. Let me know if there is any other testing or log creation I can do to help.

     
  • Steven Shiau

    Steven Shiau - 2016-07-24

    Here you can find Clonezilla live 2.4.7-20:
    http://clonezilla.org/downloads.php
    The linux kernel comes with it is newer than that in clonezilla live 20160719-yakkety, i.e. 4.6 vs. 4.4. Therefore please try Clonezilla live >=2.4.7-20.

    Steven

     
  • Josh Hopkins

    Josh Hopkins - 2016-07-24

    Thanks, just tried 2.4.7-20, same thing.

    Regards, Josh.

     
  • Josh Hopkins

    Josh Hopkins - 2016-07-24

    Yes it happens with To RAM too. I also tried another PC and was able to reproduce. I think to reliably reproduce this issue, boot Clonezilla from a bootable USB that will be seen as /dev/sdb. Once you get to the 3 second watch screen, THEN plug in your external USB hard drive. That will cause it to be seen as /dev/sdc and then /dev/sdc1 won't show up in the selection list.

    Anyway a workaround is possible and it doesn't seem like anyone else is having trouble with this except me so it probably doesnt make much sense to spend time fixing this.

     
  • Steven Shiau

    Steven Shiau - 2016-08-07

    @Josh,
    Thanks. This issue is really weird, and somehow I could not reproduce it here. Not sure it's hardware related or not. Did you try on different hardware? Is it reproducible on different machine?
    Thanks.

    Steven

     

Log in to post a comment.

MongoDB Logo MongoDB