Skip to main content

cloning - Clonezilla won't clone to a smaller disk

According the docs, Clonezilla supports cloning to a smaller drive using the option -icds. Let's cite:



If you are sure all the data from the image could fit the smaller disk, i.e. it won't be written to the wrong disk space, you can check the option "-icds"



That's my case. I am trying to transfer the OS and data from my friend's failing drive to a new one. I really want to avoid reinstalling Win Vista 32bit and all the SW.


Source disk: SATA 320 GB WD drive with two partitions (C: and D:), a couple of bad sectors. Used about 50 GB out of the entire 320 GB.


Target disk: Crucial MX500 250 GB.


I run current UBCD 5.3.8 and Clonezilla within Parted Magic. Except the default settings I am adding these options:



  • -rescue: to ignore the bad sectors

  • -icds: this is the important one to allow for cloning onto a smaller drive

  • -k1: create partition table proportionally


However, the cloning stops with an error:



Target partition size(163830 MB) is smaller than source(209716 MB). Use option -C to disable size checking(Dangerous). Failed to clone /dev/sda1 to /dev/sdb1



Why does not Clonezilla respect the -icds setting and does not run Partclone with the -C switch? How to make it to perform the cloning?


I am attaching the content of the log file:


Starting /usr/sbin/ocs-onthefly at 2018-09-25 01:49:59 UTC...
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
PS. Next time you can run this command directly:
/usr/sbin/ocs-onthefly -g auto -e1 auto -e2 -j2 -r -rescue -icds -k1  -f sda -t sdb
*****************************************************.
*****************************************************.
The first partition of disk /dev/sda starts at 2048.
Saving the hidden data between MBR (1st sector, i.e. 512 bytes) and 1st partition, which might be useful for some recovery tool, by:
dd if=/dev/sda of=/tmp/ocs_onthefly_local.S1OeQB/src-hidden-data.img skip=1 bs=512 count=2047
2047+0 records in
2047+0 records out
1048064 bytes (1.0 MB) copied, 0.00758521 s, 138 MB/s
*****************************************************.
Collecting partition /dev/sda1 info...
Collecting partition /dev/sda2 info...
Non-grub boot loader found on /tmp/ocs_onthefly_local.S1OeQB/sdb-mbr...
The CHS value of hard drive from EDD will be used for sfdisk.
Searching for data partition(s)...
WARNING! THE EXISTING DATA IN THIS HARDDISK/PARTITION(S) WILL BE OVERWRITTEN! ALL EXISTING DATA WILL BE LOST: sdb
*****************************************************.
Machine: M56S-S3
sdb (250GB_CT250MX500SSD1__CT250MX500SSD1_1829E14A98AF)
sdb1 (152.6G_boot(In_CT250MX500SSD1_)_CT250MX500SSD1_1829E14A98AF)
sdb2 (80.3G(In_CT250MX500SSD1_)_CT250MX500SSD1_1829E14A98AF)
*****************************************************.
Will create the partition on the target machine...
Let me ask you again.
*****************************************************.
 [1;33mMachine: M56S-S3
sdb (250GB_CT250MX500SSD1__CT250MX500SSD1_1829E14A98AF)
sdb1 (152.6G_boot(In_CT250MX500SSD1_)_CT250MX500SSD1_1829E14A98AF)
sdb2 (80.3G(In_CT250MX500SSD1_)_CT250MX500SSD1_1829E14A98AF)
 [0;39m*****************************************************.
 [1;33mWARNING!!! WARNING!!! WARNING!!!
WARNING! THE EXISTING DATA IN THIS HARDDISK/PARTITION(S) WILL BE OVERWRITTEN! ALL EXISTING DATA WILL BE LOST: sdb
 [0;39mAre you sure you want to continue? ? (y/n) OK, let's do it!!
Shutting down the Logical Volume Manager
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
Trying to clean the MBR and GPT partition table on the destination disk first: /dev/sdb
Creating MBR type's partition table...
 [1;33mCreate the proportional partition table based on /tmp/ocs_onthefly_local.S1OeQB/tgt-pt.sf and the size of /dev/sdb...
 [0;39mNo partition table exists in target disk /dev/sdb, try to initialize one so that we can get the disk size by parted... done!
The ratio for target disk size to original disk size is .7812.
The partition table to write in /dev/sdb:
*****************************************
unit: sectors
/dev/sdb1 : start= 2048, size= 319979520, Id=7, bootable
/dev/sdb2 : start= 319981568, size= 168371623, Id=7
/dev/sdb3 : start= 0, size= 0, Id=0
/dev/sdb4 : start= 0, size= 0, Id=0
*****************************************
Running: sfdisk --force -C 38912 -H 255 -S 63 /dev/sdb < /tmp/new_sf.2tdNbd

Disk /dev/sdb: 38912 cylinders, 255 heads, 63 sectors/track
Old situation:
Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdb1          1   30400   30400  244188000   83  Linux
/dev/sdb2          0       -       0          0    0  Empty
/dev/sdb3          0       -       0          0    0  Empty
/dev/sdb4          0       -       0          0    0  Empty
New situation:
Units: sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
/dev/sdb1   *      2048 319981567  319979520   7  HPFS/NTFS/exFAT
/dev/sdb2     319981568 488353190  168371623   7  HPFS/NTFS/exFAT
/dev/sdb3             0         -          0   0  Empty
/dev/sdb4             0         -          0   0  Empty
Successfully wrote the new partition table

Re-reading the partition table ...

Partition table was created by: sfdisk --force -C 38912 -H 255 -S 63 /dev/sdb < /tmp/new_sf.2tdNbd
done!
*****************************************************.
The first partition of disk /dev/sdb starts at 2048.
Restoring the hidden data between MBR (1st sector, i.e. 512 bytes) and 1st partition, which might be useful for some recovery tool, by:
dd if=/tmp/ocs_onthefly_local.S1OeQB/tgt-hidden-data.img of=/dev/sdb seek=1 bs=512 count=2047
2047+0 records in
2047+0 records out
1048064 bytes (1.0 MB) copied, 0.0247041 s, 42.4 MB/s
*****************************************************.
Cloning the boot loader (executable code area) from "sda" to "sdb"...
Now we will start to clone data to the target machine...
Searching for data partition(s) in source disk: sda ...
Source partition file system is ntfs...
Cloning the /dev/sda1 to /dev/sdb1...
Using partclone to clone...
Run partclone: partclone.ntfs -z 10485760 -N --rescue -L /var/log/partclone.log -b -s /dev/sda1 -O /dev/sdb1
Partclone v0.2.66 http://partclone.org
Starting to back up device(/dev/sda1) to device(/dev/sdb1)
we need memory: 6408260 bytes
image head 4160, bitmap 6400000, crc 4100 bytes
Calculating bitmap... Please wait... get device size 163829514240 by ioctl BLKGETSIZE64,
Target partition size(163830 MB) is smaller than source(209716 MB). Use option -C to disable size checking(Dangerous).
Failed to clone /dev/sda1 to /dev/sdb1
Source partition file system is ntfs...
Cloning the /dev/sda2 to /dev/sdb2...
Using partclone to clone...
Run partclone: partclone.ntfs -z 10485760 -N --rescue -L /var/log/partclone.log -b -s /dev/sda2 -O /dev/sdb2
Partclone v0.2.66 http://partclone.org
Starting to back up device(/dev/sda2) to device(/dev/sdb2)
we need memory: 3375908 bytes
image head 4160, bitmap 3367648, crc 4100 bytes
Calculating bitmap... Please wait... get device size 86206270976 by ioctl BLKGETSIZE64,
Target partition size(86207 MB) is smaller than source(110352 MB). Use option -C to disable size checking(Dangerous).
Failed to clone /dev/sda2 to /dev/sdb2
*****************************************************.
Searching for data partition(s) in target disk for post process: sdb...
Now tuning the file system size on partition /dev/sdb1 to fit the partition size...
"boot" is an unknown or unsupported filesystem... Skip resizing that.
*****************************************************.
Now tuning the file system size on partition /dev/sdb2 to fit the partition size...
Unknown or unsupported partition (/dev/sdb2) found! Skip this partition /dev/sdb2.
*****************************************************.
Creating the swap partition if exists...
*****************************************************.
Trying to remove udev hardware record in the restored OS...
The specified destination device: sdb1 sdb2
Trying to remove udev persistent files. The devices to be searched: sdb1 sdb2...
Now searching possible device /dev/sdb1...
Skip /dev/sdb2 (No file system. Extended partition?).
done!
*****************************************************.
Device /dev/sdb1 is not a FAT partition.
Skip updating syslinux on that.
Device /dev/sdb2 is not a FAT partition.
Skip updating syslinux on that.
*****************************************************.
Run grub install on disk sdb...
The grub directory is NOT found. Maybe it does not exist (so other boot manager exists) or the file system is not supported in the kernel. Skip running grub-install.
*****************************************************.
Try to run partclone.ntfsfixboot for NTFS boot partition if it exists. Scanning partition(s):  sdb1 sdb2...
The NTFS boot partition was not found or not among the restored partition(s). Skip running partclone.ntfsfixboot.
*****************************************************.
Ending /usr/sbin/ocs-onthefly at 2018-09-25 01:52:34 UTC...

Comments

Post a Comment

Popular Posts

How do I transmit a single hexadecimal value serial data in PuTTY using an Alt code?

I am trying to sent a specific hexadecimal value across a serial COM port using PuTTY. Specifically, I want to send the hex codes 9C, B6, FC, and 8B. I have looked up the Alt codes for these and they are 156, 182, 252, and 139 respectively. However, whenever I input the Alt codes, a preceding hex value of C2 is sent before 9C, B6, and 8B so the values that are sent are C2 9C, C2 B6, and C2 8B. The value for FC is changed to C3 FC. Why are these values being placed before the hex value and why is FC being changed altogether? To me, it seems like there is a problem internally converting the Alt code to hex. Is there a way to directly input hex values without using Alt codes in PuTTY? Answer What you're seeing is just ordinary text character set conversion. As far as PuTTY is concerned, you are typing (and reading) text , not raw binary data, therefore it has to convert the text to bytes in whatever configured character set before sending it over the wire. In other words, when y...
Post a Comment
Read more

linux - Extract/save a mail attachment using bash

Using normal bash tools (ie, built-ins or commonly-available command-line tools), is it possible, and how to extract/save attachments on emails? For example, say I have a nightly report which arrives via email but is a zip archive of several log files. I want to save all those zips into a backup directory. How would I accomplish that? Answer If you're aiming for portability, beware that there are several different versions of mail(1) and mailx(1) . There's a POSIX mailx command, but with very few requirements. And none of the implementations I have seem to parse attachments anyway. You might have the mpack package . Its munpack command saves all parts of a MIME message into separate files, then all you have to do is save the interesting parts and clean up the rest. There's also metamail . An equivalent of munpack is metamail -wy .
Post a Comment
Read more

ubuntu - Why does my USB hdd returns SG_IO: bad/missing sense data?

I am able to boot and run commands from external USB hdd; the message in question appears for about 45 seconds then booting continues. GRUB2 is installed on internal HDD. When choosing to boot directly to /dev/sdb the message doesn't appear, however boot time is about the same as booting to internal HDD. /dev/sdb: Timing cached reads: 1018 MB in 2.00 seconds = 508.97 MB/sec Timing buffered disk reads: 80 MB in 3.03 seconds = 26.37 MB/sec pfeiffep@de:~$ sudo hdparm -i /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 10 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 HDIO_GET_IDENTITY failed: Invalid argument Gparted correctly identifies the drive as SAMSUNG MP0402H. Any ideas how to remedy the HDIO & SG_IO messages?
Post a Comment
Read more

Desktop reboots itself on sleep or hibernate

I have been using an ASUS M2NPV-VM motherboard for main home desktop workstation, operating Windows Vista x64. This computer has right from day one not been able to enter hibernate or standby; after Windows performs its final actions and brings the machine down, it would automatically revive itself for a reboot. Updating to the second latest BIOS (1201)has not helped (the latest BIOS revision would induce video refresh problems rendering it unusable). I have been reading related discussions on incidents similar to mine to no avail of a true workable solution. They appear to be more speculative guesses rather than actual knowledge on the inner workings of motherboard hardware. Does anybody have any electronic engineering experience on PC energy-saving standards to provide a more informed opinion how to go about getting this to work? More stories: this motherboard could not even reboot properly the first thing i used it. It was due to refresh rate of the onboard GPU, which had no influe...
Post a Comment
Read more