O Clonezilla não irá clonar em um disco menor

1

De acordo com os documentos , o Clonezilla suporta clonagem para uma unidade menor usando a opção -icds. Vamos citar:

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"

Esse é o meu caso. Estou tentando transferir o sistema operacional e os dados da unidade com falha do meu amigo para um novo. Eu realmente quero evitar reinstalar o Win Vista 32 bits e todo o SW.

Disco de origem : SATA 320 GB Unidade WD com duas partições (C: e D :), um par de setores defeituosos. Utilizou cerca de 50 GB de todos os 320 GB.

Disco de destino : Crucial MX500 250 GB.

Eu corro o atual UBCD 5.3.8 e o Clonezilla dentro do Parted Magic. Exceto as configurações padrão, estou adicionando estas opções:

  • -rescue : para ignorar os setores defeituosos
  • -icds : este é o mais importante para permitir a clonagem em uma unidade menor
  • -k1 : cria uma tabela de partições proporcionalmente

No entanto, a clonagem pára com um erro:

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

Por que o Clonezilla não respeita a configuração -icds e não executa o Partclone com a opção -C? Como fazê-lo para realizar a clonagem?

Estou anexando o conteúdo do arquivo de log:

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...
    
por Pontiac_CZ 25.09.2018 / 23:00

2 respostas

2

Oficialmente, o Clonezilla exige que a unidade de destino seja do mesmo tamanho ou maior que a unidade mestre.

No entanto, isso pode ser feito. O problema que você está enfrentando não é o tamanho do disco, mas o tamanho da partição (s). Se a soma dos tamanhos de partição for maior que a unidade de destino, o Clonezilla falhará. Você precisa encolher as partições na unidade mestre antes executando o Clonezilla com -icds .

Isso pode ser feito em um ambiente do GParted Live ou dentro do sistema operacional (dependendo da configuração).

No Clonezilla, escolha o modo expert e ative a opção "-icds". Você também precisa escolher a opção "Redimensionar a tabela particional proporcionalmente".

Como alternativa, existem outros programas de software de clonagem de disco que podem fazer isso automaticamente.

    
por 26.09.2018 / 03:12
-3

Após encolher a partição da unidade que você deseja clonar, também é necessário mover a partição não utilizada para antes (à esquerda) da partição reduzida.

Tente isto: CloneZilla - Clonagem de uma grande unidade do Windows para uma unidade menor

    
por 01.02.2019 / 16:46