750GB image is freezing during capture
-
Hello,
I am trying to capture an image of my 1TB NVMe. The image itself is only 750GB, but the capturing process tends to freeze halfway through. Today I got it down to 5 minutes remaining and then it froze. Is there any way to get around this? I am using Single Disk Resizable and Partclone GZip as my imaging options. There’s also plenty of space available on the server.
-
@nerdstburns Do you get any error messages when it freezes?
Do you see the transfer speed getting slower and slower or would it just freeze suddenly?
The image itself is only 750GB…
Why is the image that big? Just wondering if you have disk encryption enabled that would make it capture in raw mode or something.
How many partitions do you have (usually you see several of those blue partclone screens one after the other showing partition names like
/dev/nvme0n1p1and so on)? Which filesystem do you see mentioned in the blue partclone screen? -
@Sebastian-Roth it’s only one major partition containing the C drive (plus the two smaller partitions which are only MBs). The image is so big because it contains a bunch of games. We are imaging a PC in a LAN center. And I am not in the location so I can’t see the screen, I am trying to image it remotely. Could you recommend the best settings to try and capture it?
-
@nerdstburns said in 750GB image is freezing during capture:
And I am not in the location so I can’t see the screen, I am trying to image it remotely.
So we don’t actually know if you get an error at some point or if it really freezes. Without knowing it’s hard to really help you. Don’t you have a colleague on site who can take a picture or watch the process?
Could you recommend the best settings to try and capture it?
This depends on a couple of things. If your source and destination disk are the same size I would use the non-resizable image type because there is no need to use it and it saves you some time as FOS does not need to shrink it.
If you use the current version FOG 1.5.9 I would recommend using Zstd instead of Gzip compression. Maybe even try using “Partclone Uncompressed” if you have enough space to store the image on your FOG server. Playing with those settings and compression ratio you might see it image a little faster in the end.
-
@sebastian-roth currently our location is closed, so no one is there, but I was able to ask the manager and take a picture. Getting an error when attempting to upload the image. Seems like the process froze, but the file system is NTFS.
We are running FOG 1.5.9 so I will try Zstd instead of Gzip. Will follow up once I test it out.
-
@nerdstburns said in 750GB image is freezing during capture:
I was able to ask the manager and take a picture. Getting an error when attempting to upload the image. Seems like the process froze, but the file system is NTFS.
Can you please share the picture here? Very often we see hints on screen that lead to a solution that others won’t notice.
-
-
@Sebastian-Roth I was able to capture the full image with the Zstd + non-resizeable, but it’s a decent amount slower, 4GB/min vs 8-18GB/min with Gzip. I tried again with Gzip + non-resizeable but it froze again.
-
@nerdstburns Adjusting compression ratio with Zstd might help to speed it up.
