Menu

-icds doesn't help?

Help
2013-02-20
2013-04-05
  • Duane Pittman

    Duane Pittman - 2013-02-20

    I just purchased a new Dell Poweredge T420 server. The primary drive (500GB) had 3 partitions: the first two are the Dell utility stuff and the third is the C drive/Windows Server 2008 R2 install. I used clonezilla 2012-01-27 to make an image of the entire disk. I then tried to restore that image to a RAID 1 array of two 500GB disks. I got the error message that the target was too small because the drive size had gone from 500.1 to 499.5GB. So I did a little research and read about the -icds option. I tried to restore with that option enabled and now I get a new error after it writes the partition table:
    ~~~~~
    The partition table in this disk is illegal/invalid: /dev/sdb
    Does this partition table file fit this disk: /tmp/2013-02-20-09-img-newserver-tmp-cnvted/sdb-pt.sf ?
    Is this disk too small: /dev/sdb ?
    The error messages from parted are:
    **********
    Error: Can't have a partition outside the disk!
    **********
    Program terminated!!

    I have also tried Clonezilla 2012-12-17. Same results with and without -icsd option.

    Any suggestions for what to try next?

     
  • Steven Shiau

    Steven Shiau - 2013-02-21

    The option "-icds" only skips the partition size checking before writing partition table. However, in the later steps when partition table is really written, parted might detect the partition table is illegal, so it won't go on.

    One possible solution is you create the partition table on the destination disk manually, then use Clonezilla live 20130219-raring or 2.1.0-22 to do that. Before you restore the image, edit the file /etc/drbl/drbl-ocs.conf, change
    PARTCLONE_RESTORE_OPT_INIT="-m 1024"
    as
    PARTCLONE_RESTORE_OPT_INIT="-m 1024 -C"
    then start restore the image with the option "-k".
    //NOTE// Backup important data before you use Clonezilla. Just in case.

    Steven.

     
  • Duane Pittman

    Duane Pittman - 2013-02-22

    Thank you for the reply. I actually found a way to work around the issue. I undid all my RAID setup and restored my first image back onto one standalone disk. Then I resized one of the partitions so the total amount of space being used was smaller than the target disk. Made a new disk image (not a partition image), re-created my RAID disk and restored the new image. Then I can use the OS to resize the partition back to the desired size.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.