@brico

Yes one time enough !

“/dev/sdb” works !

But it’s a little dangerous:

• we create a partition image for “/dev/sdb2” by example,
• we select a host and restore this image WITHOUT put anything on “Host Primary Disk”.

Then we’ll restore on the first disk ! And destroy /dev/sda !
That’s right ? Isn’t it ?

So, we’ll try to create 2 hosts (for the same PC):

• one host named “pc-01-HD1” (hard disk number one)(with nothing on “Host Primary Disk”)
• a second named 'pc-01-HD2" (hard disk number two)(with “/dev/hdb” on “Host Primary Disk”.

But FOG refuse: they have the same MAC address…

It’s not an important problem. We have to be carefull next time we’ll restore partition on seconde HDD.

Thanks for all. Really !!!

Thank you Fog !

Best regards.

You’re a genius !!!

I’m working in network and systems since 20 years. I repeat: “You are a genius”.

On the source machine, the SATA disk is plugged, on the motherboard, on SATA1. So, the SSD is /dev/sda, and the SATA /dev/sdb.

On the target machine, the SATA disk is plugged, on the motherboard, on SATA2. This make: the SSD is /dev/sdb, and the SATA /dev/sda !!!

On the target machine, I plugged the SATA on the moterboard on SATA1. I verify that SSD is /dev/sda and SATA is /dev/sdb.

The image “Single disk - resizable - Partition 3 only” was restored successfully to the target PC.

ALL IS WORKING FINE !!!

May I ask you an other question ?

I’m not able to save and restore the 2 partitions on the SATA disk (/dev/sdb2 and /dev/sdb3).

I’ve tried “Single disk - resizable - Partition 6 only”, and “Multiple partition image - All disks (not resizable) - Partition 6 only”, but the capture don’t make anything (I’ve seen, but I’m not sure, that the system tried to capture /dev/sda4).

Thanks for all. Thanks for all enough.

Best regards.

@sebastian-roth
Well. Below are the results.

Finally, we’d like first to clone the /dev/sdb3 partition.

After, it’l be great to clone /dev/sda2 and /dev/sda3.

Thans for all !!
Best regards.

[Tue Jun 01 root@figclient /]# lsblk
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda    8:0  0 465.8G  0 disk
|-sda1 8:1  0    16M  0 part
|-sda2 8:2  0 231.4G  0 part
-sda3 8:3  0 234.4G  0 part

sdb    8:16 0 238.5G  0 disk
|-sdb1 8:17 0   100M  0 part
|-sdb2 8:18 0    16M  0 part
|-sdb3 8:19 0 237.9G  0 part
-sdb4 8:20 0   511M  0 part

[Tue Jun 01 root@figclient /]# fdisk -l /dev/sda
Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5000AAVS-0
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: gpt
Disk identifier: D9139164-888A-48BF-B12B-A1B51B952553D

Device        Start       End   Sectors   Size  Type
/dev/sda1      2048     34815     32768    16M  Microsoft reserved
/dev/sda2     34816 485253119 485218304 231.4G  Microsoft basic data 
/dev/sda3 485253120 976773119 491520000 234.4G  Microsoft basic data 

[Tue Jun 01 root@figclient /]# fdisk -l /dev/sdb
Disk /dev/sdb: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: Sandisk X600 M.2
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: gpt
Disk identifier: 72E30632-D423-4C4E-9B81-A977B8583A5F

Device        Start       End   Sectors   Size  Type
/dev/sdb1      2048    206847    204800   100M  EFI System
/dev/sdb2    206848    239615     32768    16M  Microsoft reserved
/dev/sdb3    239616 499068125 498828810 237.9G  Microsoft basic data 
/dev/sdb4 499068928 500115455   1046528   511M Windows recovery environment

Thanks for your help.

I think we use 1.5.9 (I’ll verify monday afternoon).

For cloning, we create a new image:

• “Image type”: “Single Disk - Resizable (1)”,
• Partition: “Partition 3 only”.

Then, for restoring:

• in “Group Management” we choose the target PC, and select “Multi-Cast”.
• we boot the target PC and PXE make the cloning starting.

No error appear during cloning.

Thanks for all.

Hello (I’m French, I don’t know how to say “Bonjour” in a forum… Sorry).

Our PC owns two HDD: 1 SSD and 1 SATA.
We install first Win 10 on the SSD.
Then we install two others Win 10 on the SATA.
At the end, we have a multiboot PC with 3 OS Win 10.

If we clone the complete PC, all is working fine.
The 3 OS are working fine.

Thank you Fog ! Really !

Now, we try to clone only one partition.

We tried to clone the Win10 partition on the SSD, but we obtains a strange result:

• the target PC don’t boot.
• After having repaired, we see that the second SATA has not its real size: its size is divided by 2 (250 Go instaed of 500 Go). The second OS of SATA had desapeared.

If we clone again all the PC, it is repared, no problem.

We are shure we have tried to restore the Win 10 of the SSD (and not a small partition at the beginning of the SATA: UEFI, reserved to system, …).

My question : is it possible to clone only one partition ?

The solution is not ?

• restore one Win 10 partition,
• and then restore “small” partitions of the SATA (UEIF ? “reserved to system”, …) ?

Thanks for all.

Best regards.

Bonjour.
Nos PC possèdent deux disques durs: 1 SSD et 1 SATA.
Nous installons Win 10 d’abord sur le SSD.
Puis nous installons deux autres Win 10 sur le SATA.
Au final, le PC est multi-boot avec 3 OS Win 10.

Si nous faisons un clonage complet de la machine, aucun problème.
La nouvelle machine boote sans problème sur les 3 OS.
Merci FOG ! Super !

Nous aimerions maintenant nous protéger contre la casse d’un seul OS.

Nous avons essayé de cloner la partition contenant le Win10 du 1er disque SSD, mais le résultat est très bizarre:

• la machine résultat ne boote plus (il faut “réparer” la machine, puis modifier le BIOS pour arriver à Booter. Ensuite F9 pour chercher un des 3 OS qui accepte de booter).
• mais surtout la 2ème disque SATA n’a plus sa bonne taille (divisé par deux !), et seul le 1er OS est visible.
  Bizarre car le test de restauration de partition ne concernait que le disque SSD.
  Si on refait un clonage complet tout revient dans l’ordre.

Nous avons bien sauvegardé et restauré l’OS du SSD, et non pas les “petites partitions” présentes avant cet OS (UEFI, “réservé au système”, etc.).

Justement, la solution ne consiste-t-elle pas à sauvegarder et restaurer:

• la partition OS qui nous intéresse,
• mais aussi la ou les “petites” partitions en début de disque ?

Un grand merci d’avance.