@Sebastian-Roth Here’s the results of the Debug…
Here is the upload attempt when the Image is set to Multiple Partition Image - Single Disk (Not Resizable)
Damn that screen on the XPS 13 is shiny
Just a feature that may be a ‘nice thing to have’ would be to be able to set time of day replication.
Eg, Be able to set time schedules for when image replication occurs between storage nodes.
This is so that replication can occur during quieter times when there is less network traffic. Especially useful for replication to remote sites that go out via the WAN.
ah right… i think i understand you.
So at the moment, I have a Sydney Storage Group and a Melbourne Storage Group, in which each Storage Node is in their respective Storage Group.
What I should be doing is scrapping that and having just 1 Storage Group called, Australia (for eg). And then putting the Sydney & Melbourne Storage Nodes in to that Australia Storage Group with Sydney being set as the Master?
Was this changed or has it always been like that?
Just strange that it worked in its current form at trunk 3594 but is different with the latest trunk.
@Arrowhead-IT Thanks for the suggestion! I modified the Host Primary Disk value as you suggested and I then got the error saying “No resizable partitions found”.
So I then went to the Image properties and changed the Image Type from Single Disk - Resizable to Multiple Partition Image - Single Disk (Resizable), but it just hung after…
* Using Hard Disk: /dev/nvme0n1
I then changed it to Raw Image and it is now currently uploading.
@Arrowhead-IT The notebook and FOG server are on a Gigabit connections and at the moment, the upload rate is displaying 5.14GB/min
What’s the implications of using RAW when restoring to drives larger than what its currently being imaged? Will it just be a matter of manually expanding the partition to take up the remainder of the space?
@Arrowhead-IT ok cool… well the image on the server came to 20GB. That’s from a 256GB SSD and the Image Compression setting set to 6. Still not too bad actually considering a captured Windows 10 image from the previous model XPS 13 with a 256GB SATA disk using Single Disk - Resizable is about 17GB.
Now I guess the big test is to restore the Image on to the same machine and see if it boots.
@Tom-Elliott Thanks Tom, have updated and performed an upload using Single Disk Resizable and it uploaded without any errors.
I also then performed a deployment task of the Image and it was successful, windows boots up fine etc… just saw it come up with an error about changing the hostname.
@Tom-Elliott Hi Tom, running that command seems to have resolved the issue and it was able to successfully upload the image to the FOG server. This is while the image was set to Multiple Partition Image - Single Disk (Not Resizable)
When I changed it to single disk - resizable, the below error appeared…
Got the Dell tech to replace the motherboard today.
Latest Fog trunk now recognises the nvme SSD.
When the Image is set to Single Disk - Resizable, it hangs at…
* Saving original patition table......................
When Image is set to Multiple Partition Image - Single Disk (Not Resizable), it hangs at…
* Now FOG will attempt to upload the image using Partclone * Processing Hard Disk: /dev/nvme0n1
When Image is set to Raw Image, it starts the upload…
I’m fine with using Raw Image if that’s what works.