@Sebastian-Roth
So I put explicitly /dev/sda in “Host Primary Disk” field and run a restore task on the same host.
It seems to be ok.
The solution seems to set this field to /dev/sda.
Thank you Sebastian, I hadn’t notice this field (I didn’t need to date 
).
And thank you all.
I think I can set the post to “solved”.
@Sebastian-Roth
Yes you.re right, I don’t put anything in that field…
What I suppose to set in it ?
@Tom-Elliott
Yes, it appends exactly as mentioned in your last sentence.
When I upload, partclone shows /dev/sda and when I download (on the same host) it shows /dev/sdb
Thank you
Hi all,
First of all, I want to thank the community for the work done.
I expose now my problem with a special configuration I have.
I use the 1.2.0 stable version.
I use FOG for a while with a hundred computers (single disk) whitout problem.
For some of then I decided to put SSD disk in sda place and the old disk in sdb
sda is the disk whith the system I want to fog.
sdb id a disk that contain data that I dont whant to fog.
So I choose the “multiple partion - single dist” option for the image definition.
When I upload the host, it’s the correct disk that is uploaded (sda).
When I download to an other host, it restores on sdb.
In the /image/host folder I have the right d1.mbr, d1p1.img and d1p2.img files that compose my sda disk.
Even if I restore on the same computer (same disks plugged in the same way)
I hop the explanation was clear,
Thank you for the help
With fog 1.0.0 r1614
May be a cosmetic issue. When i create a new group, the content of the field ‘groupCreateBy’ of the groups table is :
O:4:“User”:25:{s:24:“inactivitySessionTimeout”;i:1
Thanks for all the job you provide