Hi, On 2010年10月01日 17:17, Gilles wrote: > At 03:00 01/10/2010, Steven Shiau wrote: > >> Does this problem occur when you do disk to disk cloning, or image restoring? >> > When restoring an image from /sda2 to /sda1 on my test host. I only > use Clonezilla to restore an image into a partition, so as to be able > to test applications in the different versions of Windows. That's > also why it was important for me to understand exactly what CZ does > to the MBR, especially the bootloader part, when restoring just one partition. > When you restore a partition image, Clonezilla won't touch MBR by default, unless you enter expert mode and check the option to force it to do that. > >> Normally Clonezilla should honor the partition table of source disk, >> and create the same table on the destination disk. No idea why there is >> > Does Clonezilla rewrite the partition table in the MBR even when just > restoring an image in a single partition (instead of restoring the > image of a whole disk)? > No. As mentioned in the above. > >> Could you please run the following commands on the source disk: >> 1. sudo fdisk -l /dev/sda >> 2. sudo parted -s /dev/sda print >> (Replace /dev/sda as the source disk device name) >> then tell us the results? >> > Here goes: > //================ fdisk -l /dev/sda > Disk /dev/sda: 160.0 GB, 160041885696 bytes > 255 heads, 63 sectors/track, 19457 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0xa2e3ce9a > Device Boot Start End Blocks Id System > /dev/sda1 * 1 2550 20482843+ 7 HPFS/NTFS > /dev/sda2 2551 7649 40957717+ 83 Linux > /dev/sda3 10200 10330 1052257+ 5 Extended > /dev/sda5 10200 10330 1052226 82 Linux swap / Solaris > > //================ parted -s /dev/sda print > Model: ATA WDC WD1600AAJS-2 (scsi) > Disk /dev/sda: 160GB > Sector size (logical/physical): 512B/512B > Partition Table: msdos > Number Start End Size Type File system Flags > 1 32.3kB 21.0GB 21.0GB primary ntfs boot > 2 21.0GB 62.9GB 41.9GB primary ext2 > 3 83.9GB 85.0GB 1078MB extended > 5 83.9GB 85.0GB 1077MB logical linux-swap(v1) > From what you have mentioned, I think it's correct. There is an existing partition table on the destination disk, and clonezilla does not touch it, it just restores the image to the partition without touch the partition table. Therefore in this case, you have to tune the partition table by yourself, or you can enter expert mode, check the option to force clonezilla to recreate the partition table on the destination disk.
Steven. > I didn't know Base64 could look this cute :-) > http://img705.imageshack.us/img705/1020/clonezillashiaubase64.jpg > > Cheers, > Gilles. > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Clonezilla-live mailing list > Clonezilla-live@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau<steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Clonezilla-live mailing list Clonezilla-live@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/clonezilla-live
