Hi I forgot to end this thread.

We solve this problem by going full Legacy bios on all machines. restoring a singledisk multipartition works great (root partition resizing included)

Thanks everybody for this great project.

Upgrade worked perfectly ! Great. thanks

Hello , even if it was 4 years ago I answer my thread because we now use 1.5.0 which works great .

I can now restore a Full EFI Layout ( EFI + Root + Swap) ( However I restore on a BIOS legacy machine as Booting UEFI PXe is still not setup correctly on my side)

But Now When I deploy image to a Twice Bigger disk ( either SATA or PCIE ) I get :

• EFI partition : 512 MB same size
• Root partition ext4 : Twice Bigger ( proportionnaly)
• Swap Partition : Twice Bigger

Then I wonder if I could avoid that the Swap is twice Bigger ? Because when drive will be 4 times bigger , that will be a Big swap.

Thanks

Hi ,

just to say that I deployed the same Image to a new SATA disk and the 3rd partition (Swap) had a fixed size as Expected.

So I guess that was a mistake on my side.

Problem solved !

Hi , I used the USB image creator script ( with my FOG IP) create-usb-image.sh but face some systematic error when trying to image MacBookPro 2015 with USB ethernet adapter

• No problem to get an IP and access the FOG server
• Registration works great
• When trying to image I get a /tmp/hinfo.txt not found and then a lot of errors I guess linked to the missing hardware info

So I tried to verify :

wget -q -O hinfo.txt “http://192.168.2.254/fog/service/hostinfo.php?mac=002432ae6bb2”
And I just get " cannot view from browser"

Other PXE bootable computers works perfectly

Any idea on what could cause this ? Many thanks

Just a note , I had the same problem ( SATA to NVME ) with CloneZilla , had to fiddle with Windows liveUSB BCD to update the Boot manager

Thanks,

TO help the previous image ( W10 1809 like this one ) can be flashed to NVME and SATA without problems.

I also think that this is a naming convention problem

Hi,

it seems we did not have this problem before 1.5.7 :

• Capturing on a 250G Sata SSD
• Restoring on a 1 To NVME

Fail to boot with the blue smiley screen.

Is this a scenario where windows cannot boot usually or something on what fog is doing when restoring ?

thanks

@Sebastian-Roth Thanks We’ll wait 1.5.6 as it’s non-blocking

Actually it happen also with Linux image so it’s more about the nvme aspect I guess …

Many thanks , won’t the init be updated when I will upgrade FOG to latest version ?

that would be simpler

Hi,

This is not a critical issue as the imaged disk seems to work.

We are using Fog 1.5.0 with W10 1809 images built from a NVME disk and restored on NVME disk

Each time we restore the image , we get a "fail to restore disk GUID " on the first partition as you can see :

Hi ,

just to say that I deployed the same Image to a new SATA disk and the 3rd partition (Swap) had a fixed size as Expected.

So I guess that was a mistake on my side.

Problem solved !

Forget my last post

So yes fixed partitions was initialized with :1:3

So it seems that the third partition (swap here) should not be resized proportionnaly as I understood.