Menu

restore fails - Unable to find target partition

2018-04-27
2018-05-11
  • karl johnson

    karl johnson - 2018-04-27

    Getting an error restoring from image to disk. Tried in a VM and physical machine. Version clonezilla_live_stable-2.5.5-38-i686-pae.iso

    Source machine:
    Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 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
    Disklabel type: dos
    Disk identifier: 0x1ec476d8

    Device Boot Start End Sectors Size Id Type
    /dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
    /dev/sda3 584740864 983656447 398915584 190.2G f W95 Ext'd (LBA)
    /dev/sda4 983656448 1000214527 16558080 7.9G 82 Linux swap / Solaris
    /dev/sda5 584744960 983656447 398911488 190.2G 83 Linux

    Partition table entries are not in disk order.

    Target log:
    Partition table file for disk was found: sda
    MBR file for this disk was found: sda
    The image of this partition is restorable: sda1
    The image of this partition is restorable: sda5
    All the images of partition or LV devices in this image were checked and they are restorable: 2018-04-26-22-img
    Running: task_restoreparts "2018-04-26-22-img-tmp-cnvted" "sdb1 sdb5" ""
    ********.
    The following step is to restore an image to the hard disk/partition(s) on this machine: "/tmp/2018-04-26-22-img-tmp-cnvted" -> "sdb sdb1 sdb5"
    The image was created at: 2018-0426-2230
    WARNING. THE EXISTING DATA IN THIS HARDDISK/PARTITION(S) WILL BE OVERWRITTEN! ALL EXISTING DATA WILL BE LOST:
    *******.
    Machine: VirtualBox
    sdb (500GB___JMicron_USB_to_SATA_bridge_20170424336C-0:0)
    *******.
    This program is not started by clonezilla server.
    *******.
    Let me ask you again.
    The following step is to restore an image to the hard disk/partition(s) on this machine: "/tmp/2018-04-26-22-img-tmp-cnvted" -> "sdb sdb1 sdb5"
    The image was created at: 2018-0426-2230
    WARNING. THE EXISTING DATA IN THIS HARDDISK/PARTITION(S) WILL BE OVERWRITTEN! ALL EXISTING DATA WILL BE LOST:
    *******.
    Machine: VirtualBox
    sdb (500GB___JMicron_USB_to_SATA_bridge_20170424336C-0:0)
    *******.
    Shutting down the Logical Volume Manager
    Finished Shutting down the Logical Volume Manager
    Creating partition in /dev/sdb...
    Trying to clean the MBR and GPT partition table on the destination disk first: /dev/sdb
    Informing the OS of partition table changes... done!
    **********.
    Fri Apr 27 02:27:12 UTC 2018
    Writing the partition table...
    No partition table exists in target disk /dev/sdb, try to initialize one so that we can get the disk size by parted... Running: parted -s /dev/sdb mklabel msdos
    done!
    Running: LC_ALL=C sfdisk --force /dev/sdb < /tmp/2018-04-26-22-img-tmp-cnvted/sdb-pt.sf 2>&1 | tee -a /var/log/clonezilla.log
    Checking that no-one is using this disk right now ... OK

    Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 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: 0x54a6e74a

    Old situation:

    Script header accepted.
    Script header accepted.
    Script header accepted.
    Script header accepted.
    Created a new DOS disklabel with disk identifier 0x1ec476d8.
    /dev/sdb1: Created a new partition 1 of type 'HPFS/NTFS/exFAT' and of size 100 MiB.
    /dev/sdb2: Created a new partition 3 of type 'W95 Ext'd (LBA)' and of size 187 GiB.
    /dev/sdb4: Start sector 983656448 out of range.
    Failed to add #4 partition: Numerical result out of range
    Leaving.

    Checking that no-one is using this disk right now ... OK

    Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 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: 0x54a6e74a

    Old situation:

    Script header accepted.
    Script header accepted.
    Script header accepted.
    Script header accepted.
    Created a new DOS disklabel with disk identifier 0x1ec476d8.
    /dev/sdb1: Created a new partition 1 of type 'HPFS/NTFS/exFAT' and of size 100 MiB.
    /dev/sdb2: Created a new partition 3 of type 'W95 Ext'd (LBA)' and of size 187 GiB.
    /dev/sdb4: Start sector 983656448 out of range.
    Failed to add #4 partition: Numerical result out of range
    Leaving.

    This was done by: LC_ALL=C sfdisk --force /dev/sdb < /tmp/2018-04-26-22-img-tmp-cnvted/sdb-pt.sf 2>&1 | tee -a /var/log/clonezilla.log
    Checking the integrity of partition table in the disk /dev/sdb...
    Informing the OS of partition table changes..................................................... done!
    ********.
    The first partition of disk /dev/sdb starts at .
    The hidden space between MBR and 1st partition is "-1" sectors, which is smaller than the hidden data /tmp/2018-04-26-22-img-tmp-cnvted/sdb-hidden-data-after-mbr) size "2047" sectors.
    Skip restoring the hidden data between MBR and 1st partition.
    *******.
    *******.
    Restoring partition /dev/sdb1...
    Unable to find target partition "sdb1".
    ********.
    The disk and partition in this system:
    major minor #blocks name

    8 0 10485760 sda
    8 1 9436160 sda1
    8 2 1 sda2
    8 5 1046528 sda5
    11 0 235520 sr0
    7 0 197652 loop0
    8 16 488386584 sdb
    8 32 312571224 sdc
    8 33 307200 sdc1
    8 34 289294336 sdc2
    8 35 17722368 sdc3
    8 36 5237760 sdc4
    ***********.
    Check if the partition sdb1 really exists, otherwise maybe the kernel is too old.
    Program terminated!.

     
  • karl johnson

    karl johnson - 2018-04-28

    Ok - so I'm an idiot. Missed the fact that the source drive had a paritition all the way at the end of the drive. That was causing the error. Moved the freespace to the end and magic!! Thanks.

     
  • Steven Shiau

    Steven Shiau - 2018-05-11

    Thanks for sharing that.

    Steven

     

Log in to post a comment.

MongoDB Logo MongoDB